| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Triggered consumer app hangs on MQClient 5.3 for AIX |
« View previous topic :: View next topic » |
| Author |
Message
|
| kwekke |
 Posted: Wed Aug 13, 2003 12:04 pm Post subject: Triggered consumer app hangs on MQClient 5.3 for AIX |
 |
|
Newbie
Joined: 13 Aug 2003
Posts: 1
Location: Newark, Delaware
|
I have a triggered java consumer application that has been running on AIX for years. Since upgrading to MQCllient 5.3, the app processes all messages in the queue, but then hangs on the last get instead of returning MQRC_NO_MSG_AVAILABLE. The CPU gets pegged when the wait interval has expired.
Some other facts:
1. The problem is somehow related to the trigger. The application runs fine standalone.
2. The application runs fine triggered on MQClient 5.3 for Windows.
3. Just to be sure of my installation, I installed MQClient on a second AIX server. I got the same result.
4. WMQ server was upgraded to 5.3 a few months before the clients were upgraded, with no issues.
Has anyone encountered this?
Keith |
|
| Back to top |
|
 |
| clindsey |
| Posted: Wed Aug 13, 2003 2:26 pm Post subject: |
|
|
Knight
Joined: 12 Jul 2002
Posts: 586
Location: Dallas, Tx
|
There was a problem with a java program getting launched by the trigger monitor on 5.3. The fix is included in CSD04. It sounds like you got a little further than this though since you can process some messages. Try the CSD and see if it helps. If you need a workaround, use the sample trigger monitor /usr/lpp/mqm/samp/bin/amqstrgc.
The parms are just initqueue and optional queuemanager (no flags).
This problem is unique to AIX.
Charlie
Last edited by clindsey on Thu Aug 14, 2003 11:44 am; edited 1 time in total |
|
| Back to top |
|
|
| clindsey |
| Posted: Thu Aug 14, 2003 10:42 am Post subject: |
|
|
Knight
Joined: 12 Jul 2002
Posts: 586
Location: Dallas, Tx
|
I left out some needed information.
The fix in CSD04 enables a new environment variable. This must be set in the enviroment where the triggered application is running, e.g in a shell script that launches the jvm.
It must be set to 1.
export AMQ_NO_SIGWAIT_SIGTRAP=1
Charlie |
|
| 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
|
|
|
|
