| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| Search found 4 matches |
| Author |
Message |
 Topic: Reason code 2033 even though message seems to exist on queue |
westi
Replies: 4
Views: 4420
|
 Forum: IBM MQ Java / JMS Posted: Thu Jun 14, 2007 12:53 pm Subject: Reason code 2033 even though message seems to exist on queue |
I should probably have mentioned that we use clustered managers/queues.
Anyway that was the reason for occasionally not finding the reply.
When closing the connection between request and reply the ... |
| Topic: Reason code 2033 even though message seems to exist on queue |
westi
Replies: 4
Views: 4420
|
Forum: IBM MQ Java / JMS Posted: Tue Jun 12, 2007 7:41 am Subject: Reason code 2033 even though message seems to exist on queue |
Hi all,
We have a test app that uses JMS API to send a message on a queue and then straight after receives the very same message and logs it.
This is done to reproduce the following problem in our ... |
| Topic: Correlation ids & IMS transactions |
westi
Replies: 3
Views: 7905
|
Forum: Mainframe, CICS, TXSeries Posted: Thu May 10, 2007 11:15 pm Subject: Correlation ids & IMS transactions |
The default in JMS for the request reply service is:
a) the correlation ID is already set => it is passthrough
b) the correlation ID is not set => put the messageId into the correlationId fiel ... |
| Topic: Correlation ids & IMS transactions |
westi
Replies: 3
Views: 7905
|
Forum: Mainframe, CICS, TXSeries Posted: Thu May 10, 2007 1:15 am Subject: Correlation ids & IMS transactions |
Hi,
The context:
I have developed a Java app using the WMQ 6 JMS client API to do TCP connections to our MQ Manager. Through this I am calling various newly developed IMS transactions (via the IMS ... |
|
|
|
