-
Title
"RequestContext" messages in WAS logs -
Description
We are getting a large number of warning messages in a recently-deployed WebSphere application's SystemOut.log. They appear approximately 10 per second, and are causing the logs to rapidly fill and become unusable.
[1/26/11 9:32:15:869 EST] 0000004b PerformaSureA W PerformaSure Agent Received a RequestContext from an Agent that is attached to a different Nexus. Ignoring context flow and starting a new request.
I found a technote for this, where it was stated I should put Target.NEXUS.threshold = "OFF"; in the log.config file.
https://support.quest.com/Search/SolutionDetail.aspx?id=SOL65160&category=Solutions&SKB=1However, after doing this and restarting the nodeagent and WebSphere application's JVM, there is no change in behavior.What can I do to get rid of these messages? Also, the JavaEEDeploymentManager agent properties details states that I could theoretically set "ERROR" to avoid seeing warnings - would this be a better value to use than "OFF"? -
Cause
This juSt means there are requests spanning multiple jvm's where one is instrumenetd and the other isnt or they are reporting to different FMS. We follow the tag and follow technology where we track requests spanning multiple jvm's. So if one of them is isntrumenetd and other isnt, it will throw this warning message.
-
Resolution
Target.WEBSPHERE.threshold = "OFF";
Target.CONSOLE.threshold = "OFF"
Setting in the log.config should ideally turn off Foglight from writing anything to websphere logs. Log.config is in JavaEE_Home\config directory. BUT there are certain errors/exceptions that websphere throws which may be initiated by our agent. We don’t have control over those exceptions. But other than those exceptions, this log setting would turn off those WARN messagesSet both the Target.NEXUS.threshold = "OFF" and Target.WEBSPHERE.threshold = "OFF" in the JavaEE-Management agent properties and ensure those were removed from the log.config on the agents.This can be done by editing in Agents -> Agent Properties -> JavaEE-Management -> JavaEEDeploymentManager -> LogConfig" entryYou could set it to INFO or turn it OFF completely. You would have to reactivate the JavaEEDeploymentManger agent once you make these changes provided .