| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Excessive Logging to stderr file |
« View previous topic :: View next topic » |
| Author |
Message
|
| wyatt |
 Posted: Wed Oct 20, 2010 10:40 am Post subject: Excessive Logging to stderr file |
 |
|
Voyager
Joined: 28 Nov 2004
Posts: 76
|
A couple weeks back we started to get a lot of logging written to the stderr files in every execution group.
/var/wmqi/components/QMGRX/xxxxxxxx-x601-x000-xxxxx-a1fdfdasaca38d
For example
<JNI ReleaseStringChars: buffer=0000000117E07630>
<JNI GetStringChars: buffer=0x0000000117E07630>
<JNI ReleaseStringChars: buffer=0000000117E07630>
<JNI GetStringChars: buffer=0x0000000117E07630>
<JNI ReleaseStringChars: buffer=0000000117E07630>
This is on AIX servers running WMB/WTX most execution groups have Java Compute nodes.
Any suggestions on how I can determine what is writing to these files.. It doesnt appear to the the Java Compute node (application code)...
Thanks |
|
| Back to top |
|
 |
| rbicheno |
| Posted: Thu Oct 21, 2010 2:56 am Post subject: |
|
|
Apprentice
Joined: 07 Jul 2009
Posts: 43
|
Has anything changed recently since you started seeing the problem? Code changes? New fixpack installed?
Is it really causing you an issue? I have seen these written to before but very little and so infrequent not worth worrying about. How much output are you seeing?
If the problem really is severe I would narrow it down by:
create a fresh EG check the stderr file is not updated for that EG. If its still updating then it maybe product and not your code, i would Raise a PMR.
Deploy your flows one at a time and check the stderr for updates, also send a test message through each one at a time, check the time modified for the file after each one.
Hopefully this will help narrow it down to a certain flow(s). The you could follow a similar process carving up your flow to find potential node issues. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Oct 21, 2010 10:28 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20696
Location: LI,NY
|
Look at your egs in the explorer and make sure non of them is in debug logging. 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| wyatt |
| Posted: Fri Oct 22, 2010 6:14 am Post subject: jni |
|
|
Voyager
Joined: 28 Nov 2004
Posts: 76
|
turns out someone exported the following variables in the profile. The "jni" switch is the culprit.
MQSIJVERBOSE=-verbose:class,gc,jni
Thanks for the responses |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
