| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| 2033 error even before timeout interval |
« View previous topic :: View next topic » |
| Author |
Message
|
| magesh_chandren |
 Posted: Tue Nov 09, 2004 8:01 am Post subject: 2033 error even before timeout interval |
 |
|
Novice
Joined: 16 Feb 2004
Posts: 12
|
Hi,
Using java MQ api is put and get messages on queues
I used to wait for messages with a particual correlation ID
(ie gmo.matchOptions = MQC.MQMO_MATCH_CORREL_ID;)
and with MQGMO_WAIT option on with a wait of 2 mins
(ie gmo.options = MQC.MQGMO_WAIT;
gmo.waitInterval = 120000;
)
It works fine. But sometimes, it so happens that I get a 2033 error even before the expiry of 2 mins.
I noted the time just before I started waiting and just after I got the 2033 error, and I found that the time was far less than 2 mins.
Can anyone tell me where Iam going wrong ? |
|
| Back to top |
|
 |
| bower5932 |
| Posted: Tue Nov 09, 2004 11:07 am Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
| Exactly how long is it waiting when it waits 'far less than two minutes'? |
|
| Back to top |
|
|
| clindsey |
| Posted: Tue Nov 09, 2004 2:33 pm Post subject: |
|
|
Knight
Joined: 12 Jul 2002
Posts: 586
Location: Dallas, Tx
|
Is this on Solaris? See if you get a new FDC in /var/mqm/errors at the time of the symptom. The FDC will have a probe of XC33xxxx, i.e. async signal caught.
I saw a similar problem once because the jvm was throwing SIGSEGV and MQ's signal handler caught the signal. It seemed to cause the wait semaphore to pop prematurely. As I recall, a later fix level for the jvm resolved the problem.
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
|
|
|
|
