Message in WECTrace.txt suggesting that the TCPForwarder is constantly starting in TIBCO LogLogic Lasso Enterprise

Message in WECTrace.txt suggesting that the TCPForwarder is constantly starting in TIBCO LogLogic Lasso Enterprise

book

Article ID: KB0077448

calendar_today

Updated On:

Products Versions
TIBCO LogLogic Lasso Enterprise 2.0.10 and higher

Description

With full tracing enabled there is a message in WECTrace.txt which appears regularly suggesting that the TCPForwarder was constantly starting but there were no other error messages associated with this.

With normal trace level logging in Lasso, a message appeared in WECTrace.txt when WEC \ WELP were restarted, which suggested that Lasso was performing a DNS lookup on the forwarder address (even though it was defined as an IP). Lasso appears to successfully collect DLLs and populates the MessageFileRepository folder.

Issue/Introduction

This article explains how to resolve a message in WECTrace.txt suggesting that the TCPForwarder is constantly starting in Lasso Enterprise.

Resolution

The solution to this is to:
1.  Add an entry to the c:\windows\system32\drivers\etc\hosts with the IP address and hostname of the LogLogic LMI appliance.

2.  Restart Lasso services.


After this WECTrace.txt will immediately show an entry which indicating that a connection was successfully made to the LogLogic appliance on port 514. This message was previously missing and there was no associated error relating to a failed attempt.

The previous message regarding TCPForwarder starting no longer appears and events will be successfully delivered to the LogLogic LMI appliance.