"WARN [[ACTIVE] ExecuteThread: '25' for queue: 'weblogic.kernel.Default (self-tuning)']"ARN [[ACT (4324460)

JavaEE agents monitoring weblogic domains are split between couple of FMS server pairs, when these domains interact a lot, a lot of warnings messages are logged in the managed server logs

YYYY-MM-DD HH:MM:SS WARN Received a RequestContext from an Agent that is attached to a different Nexus. Ignoring context flow and starting a new request.

and similar warnings in the Foglight Server logs

YYYY-MM-DD HH:MM:SS ECHO < WebLogic Agent "qvprdB-admin-qvprdb.baplc.com:7999-blx31ah01-bls1" (Agent ID: 126) > WARN [[ACTIVE] ExecuteThread: '25' for queue: 'weblogic.kernel.Default (self-tuning)'] com.sitraka.pas.agent.request.ContextDelegate - Received a RequestContext from an Agent that is attached to a different Nexus. Ignoring context flow and starting a new request.

When two weblogic servers are interacting with each other and are not connected to the same FMS. Ideally we recommend that when they split appservers between Foglight Managemet Servers (FMS), that all those that interact with each other would connect to the same FMS. That would let them enable our Tag and Follow feature (of JavaEE Cartridge), where our agents keeps track of the root request that crosses multiple JVMs.

The WARN message simply says that a request that crossed multiple JVMs could not be tracked as one request (but shown in FMS as two requests) because they are connected to two Nexus (FMS). This message is only informational which is echoed to the FMS logs.

In the Agent log, there is not a way to turn off just this log message or for that matter, the "Tag and follow" feature. One can turn off *all* WARN messages (by tweaking log.config in JavaEEAgent install directory) from the logs but this will stop logging all WARN messages

In the FMS logs, this can be done by tweaking log.config in JavaEEAgent install directory.

Target.NEXUS.threshold = "OFF";

Will turn off all ECHO messages in the FMS logs.