| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| Empty MQ_ID and CORRELATION_ID |
« View previous topic :: View next topic » |
| Author |
Message
|
| jefflowrey |
 Posted: Wed Jul 28, 2004 6:11 am Post subject: |
 |
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
But it still has nothing to do with the "errors", whatever they are, related to the content of the Message ID and Correlation ID.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
 |
| clindsey |
| Posted: Wed Jul 28, 2004 6:46 am Post subject: |
|
|
Knight
Joined: 12 Jul 2002
Posts: 586
Location: Dallas, Tx
|
Yes, this is an ignorable error.
xehAsySignalHandler catches async signals so it can do recovery if needed, but it always writes an FDC for you so you know what signal was trapped. The program name may be one of your application programs or it may be a WMQ process like the runmqlsr in this case. The other piece of info you need to be aware of is the signal that was caught. It is logged in the Arith1 field (once in decimal and once in hex). In this case, the signal was a 1. You can look in /etc/sys/signal.h to get defines for the signal numbers. For a signal 1 you will see
| Code: |
#define SIGHUP 1 /* hangup, generated when terminal disconnects */
|
It could be due to someone sending kill -1 but it more likely to be as Peter said that someone started the listener and then disconnected.
So, whether or not it is truly an ignorable error depends on the signal. If it were a 6 or 11 and happens regularly then I wouldn't ignore it.
Hope this helps,
Charlie |
|
| Back to top |
|
|
|
|
|
|
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
|
|
|
|
