|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Not Getting Messages With XASession |
« View previous topic :: View next topic » |
Author |
Message
|
jvenugopal |
Posted: Tue Nov 16, 2004 10:06 am Post subject: Not Getting Messages With XASession |
|
|
Newbie
Joined: 16 Nov 2004 Posts: 2 Location: Hyderabad
|
Hi,
I want to use jms in two phase commit transactions.
I am using XAQueueConnectionFactory, XAConnection and XASession for receiving messages from MQ Series.
For this I tried the sample which is bundled with the Server, ASFClient1.java(Application Server Facilities). In that class I changed all connection and session to XA enabled. With out the XA enabled everything ran fine. But when I make it XA enable, I am not receiving the messages (MessageListener is not getting the messages)
I observed that the messages are coming till ServerSession, but when the ServerSession calls session.run() which gives the message to the listener, is not working. That means there is some problem in session.run().
I am using MQ Series Specific API to create XAQueueConnectionFactory. Can anybody suggest what went wrong here.
Does WebSphereMQ support Two Phase Commit Protocol With JMS?
I am glad to provide you any other information that is required.
Thanks,
Venu. |
|
Back to top |
|
 |
fjb_saper |
Posted: Tue Nov 16, 2004 11:49 am Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
If you are not using the Websphere(WAS) transaction manager but just the one delivered with MQ this behavior is normal.
You have to use a WAS and its J2EE compliant transaction manager.
Then use the WAS MDB setup. Worked for us.
Enjoy  |
|
Back to top |
|
 |
jvenugopal |
Posted: Tue Nov 16, 2004 8:32 pm Post subject: Not Getting Messages With XASession |
|
|
Newbie
Joined: 16 Nov 2004 Posts: 2 Location: Hyderabad
|
Hi,
Thanks for the reply.
As I am writing a plug-in for Pramati Application Server, I am using Pramati Transaction Manager (instead of WAS Transaction Manager). The MDB which is deployed on Pramati App Server is trying to receive messages from MQ Series. While deploying the MDB, Pramati App Server is trying to make XAConnection and XASession to the MQ Series for its ConnectionConsumer.
Is it possible to use Another App Server's Transaction Manager instead of WAS?
Thanks,
Venu. |
|
Back to top |
|
 |
jefflowrey |
Posted: Wed Nov 17, 2004 6:01 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
Yes, you can use a different transaction manager.
However, you will still have to configure the queue manager to participate in the transactions as a resource manager. This is documented, I believe, in the System Administration Guide. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
fjb_saper |
Posted: Wed Nov 17, 2004 2:12 pm Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
Sure you can use another transaction manager ... as long as it is fully J2EE compliant...
We tried with ATG's transaction manager and cannot make a 2 phase commit on the inboud. (old version of ATG)... Outbound 2 phase commit is supported.
Part of the fun is having a good relationship between the JTA and MQ. If not everything works as expected you could get a few surprises like MDB working with a QCF but not with an XAQCF! !
Enjoy  |
|
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
|
|
|
|