Some of the Wily Logs are present in TIBCO BW's TSM log.
Please help in avonding these logs in being written into TSM log as this log file is for BW logs only.
BWAgent parameter are in tra file of the application.
Once I had a similar issue on Jboss/Websphere.
The fact was that the agent was configured to report logs to console, and actually console for a process started by WAS Manager is captured by WAS logging.
So you should check that, i.e.
log4j.appender.IntroscopeAgent=INFO, logfile, console
should not include console but only logfile, or whatever appender you need to use. If you're unsure about what to include there, just be sure not to include console:
Please let us know if Roger's note help or additional assistance is needed. I will continue to monitor this thread for your response
Vaibhav's problem has been running as a support case with Olympia & me for a while and unfortunately disabling console logging did not help.
The only way seems to be to disable agent logging completely.
In short term can you please try this hot property change from this Community thread: Completely Disable Wily Lo
That will disable all agent logging so you can test it while agent is running.
If you do not want to disable all agent logging long term Olympia will refer your case to Engineering to find the root cause of the errors
I have already removed the console and still problem continues.
Lynn, We are having 200 agents which are pointing to the same profile file and if I will mention OFF/NONE in log4j then yes, we can check if logs are generating or not and if generating then either from application or agent side.
If I will mention OFF/NONE then I have to restart 200 of agents and after test we have to again start 200 of agents which is not permitting by the client.
Please suggest other way to sort out this issue.
It is a hot property so you do not need to restart the agents to test it.
After the test you can revert to current setting again as hot change.
Have you tryed sending this parameter via jvm -D option? Jvm parameters usually override profile ones.
Also you can try setting log level to Error so you Still have a minimal log if some trouble arises.
I would caution that we had problems when setting log4j properties from the command line with 10.0 agent (and probably older ones): logging reverted to the hard coded defaults. Fixed in 10.1.
I was in impression to restart the agents as Olympia and other SE told me to restart this after change.
I think that restart advice was to make sure the logging disablement to the tsm.log had the best chance of working.
For normal agent logging to the agent log file the hot change does work - I just tested it
So you can also try the same hot change to see if it will also stop the tsm.log file updates.
Hope this helps