Author |
Message
|
gbveu8 |
Posted: Wed Aug 09, 2006 6:41 am Post subject: MSG DON'T APPEAR ON JMS DESTINATIONS WHEN SENT FROM WAS v5.x |
|
|
Newbie
Joined: 09 Aug 2006 Posts: 5
|
MESSAGES DON'T APPEAR ON JMS DESTINATIONS WHEN SENT FROM APPLICATION RUNNING INSIDE OF WAS 5.X
Environment set up:
- WebSphere Application Server (WAS) v5.1 installed on AIX
- MQ Client support on AIX
- MQ server installed on Z/OS main frame with REQ and REPLY queues
The situation:
- Session EJB (not MDB) running in WAS invokes a JMS PUT program and put a message on the REQ queue and then invokes a GET program to wait for a reply on the CorelID for a time limit.
The problem:
- The message does not appear on the REQ queue until the GET JMS program has timed out and the EJB return.
Things tried with no affect:
- Wrote and tried successfully with individual PUT and GET JMS programs.
- Made sure all objects in PUT program are nullified before invoking PUT program. |
|
Back to top |
|
 |
jefflowrey |
Posted: Wed Aug 09, 2006 6:45 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
You aren't committing your request. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
gbveu8 |
Posted: Wed Aug 09, 2006 7:02 am Post subject: |
|
|
Newbie
Joined: 09 Aug 2006 Posts: 5
|
thanks for the quick response jefflowrey! Sorry, I should have mentioned that was something I have also tried. WAS complaint something about global transaction as I opened the SESSION with TRANSACTION = FALSE; |
|
Back to top |
|
 |
jefflowrey |
Posted: Wed Aug 09, 2006 7:12 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
If you don't receive an exception from your send, and the message is not on the queue, then you haven't committed it. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
gbveu8 |
Posted: Wed Aug 09, 2006 7:23 am Post subject: |
|
|
Newbie
Joined: 09 Aug 2006 Posts: 5
|
The following ERROR message is what I got when doing a commit with the SESSION object (transaction=TRUE): "Method not permitted in global transaction".
Have I missed something out?
Is QueueSession the only object I need to/can do commit on? |
|
Back to top |
|
 |
fjb_saper |
Posted: Wed Aug 09, 2006 12:36 pm Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
gbveu8 wrote: |
The following ERROR message is what I got when doing a commit with the SESSION object (transaction=TRUE): "Method not permitted in global transaction".
Have I missed something out?
Is QueueSession the only object I need to/can do commit on? |
Yes you missed the part in the manual where it is stated that WAS ignores the QueueSession settings for transactionality and enforces what has been set at the EJB method level.
You need to call a different method on the EJB and set it to not support transactionality for the send.
Enjoy  _________________ MQ & Broker admin |
|
Back to top |
|
 |
|