Actually, in the latest MQSeries (WebSphere MQ 5.3.0.2 with CSD03 - also called WebSphere MQ 5.3.0.3 - and the WebSphere MQ Extended Transactional Clients - which requires CSD03) you have the support fro XAConnectionFactory and through regular TCP/IP connection (in previous version, you also had it, I think, but only through the "binding" mode of MQ - shared memory - forcing you to have the queue manager on the same machine as JBoss and a whole lot of MQ dlls in the JBoss path).
I do not know if the issue I had was related to the deadlock you mention or not, but here is the answer I get through the JBoss mailing list (from [EMAIL PROTECTED]):
Hi Thomas,
I have done the Websphere MQ integration with jboss in the past and ran
into the same issues. It's not you and it's not jboss. The JMS ASF
spec is a little weak in describing who/how the inbound XA transaction
gets started.
The only way JBossMQ was able to implement the ASF spec was by starting
the transaction without an associated XID. Once the message gets
delivered to the container, JBossMQ allows the container to associate an
XID with the session. The session then assigns the XID to the TX that
delivered the message. JBossMQ had to kind of jump through hoops to get
this to work.
It would have been much easier to allow JBossMQ to assign an XID to the
transaction to begin with. WebSphere MQ might be trying to do something
like that. But since it's not in the JMS ASF spec, IBM would need to
tell us what MQ is expecting (outside the spec) to get the asynch
message delivery to work.
Other ways to skin this cat:
- Don't use the current MDB container invoker (which uses the ASF to do
asynch message delivery). Write a new MDB container invoker that does
synchronous Receiver.receive() calls to get messages. The problem with
this approach is that you need to start a JTA TX before you do the
receive() and our current TM will timeout the TXs that take too long. A
solution my be to use receiveNoWait() instead.
- Implement a MDB conatiner invoker using the new JCA TX inflow stuff.
I have not had time to look into this yet or if MQ has a JCA resource
adapter but this would be the best solution.
Regards,
Hiram
Thomas Cherel
Development Manager
Phone 508-366-3888 x3399
Cell 508-615-4535
[EMAIL PROTECTED]
www.ascentialsoftware.com
-----Original Message-----
From: Adrian Brock [mailto:[EMAIL PROTECTED]]
Sent: Thursday, August 28, 2003 7:26 PM
To: [EMAIL PROTECTED]
Subject: RE: [JBoss-user] JMS: JBoss to Weblogic messaging
If was a frequently asked question in the forums for 3.0
that MQSeries didn't support an XAConnectionFactory.
You had to fallback to acknowledgements with no XA
<xa-connection>false</xa-connection> in the MDB config
3.2 detects whether a connectionfactory implements XAConnectionFactory
Somebody else pointed out a bug in JBoss's ServerSessionPool
that caused a deadlock in MQSeries. It wasn't a problem
for jbossmq (is that what you are referring to?)
Regards,
Adrian
On Thu, 2003-08-28 at 20:45, [EMAIL PROTECTED] wrote:
> I managed to have MQSeries configured as a JMS provider in JBoss (and
> then have JBoss MDB listening to MQ queues). But XA support did not
> work (got an answer from on of the JBoss developer mentioning some
> incompatibility between what MQSeries XA requires and what JBoss TM is
> doing. Seems that JMS spec has some holes in this area).
>
> I also managed to have SonicMQ working, but I did not test yet the XA
> capability.
> In any cases, if you are able to add WebLogic as a JMS provider in
> JBoss, you can basically do anything you want:
> - JBoss MDB listening to WebLogic queue/topics
> - Any JBoss component (MDB, EJB, Mbeans, ...) sending messages
> to WebLogic queue/topics
> - As long as you are within one JBoss server, and if WebLogic
> JMS XA works with JBoss TM, then you can do XA (transaction integrity)
> between all those pieces (weblogic queue/topics and other JBoss
> queue/topics or XA database sources).
>
> Thomas Cherel
>
>
>
> -----Original Message-----
> From: Adrian Brock [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, August 28, 2003 2:55 PM
> To: [EMAIL PROTECTED]
> Subject: RE: [JBoss-user] JMS: JBoss to Weblogic messaging
>
> No, a distributed TM is only required when there are multiple
> transaction managers.
>
> The JBossTM enlists the JMS's XASession/XAResource.
> There is only one transaction manager.
>
> If the MDB did a remote ejb invocation then it would require a DTM.
>
> Of course you might want a logging TM for recovery.
>
> It should work with any JMS implementation. I've only tried it
> with JBoss<->JBoss. I've heard of people doing it with Arjuna
> and MQSeries.
> Sonic seem to want you replace JBoss's ServerSessionPoolFactory
> for reasons I don't understand.
>
> Regards,
> Adrian
>
> On Thu, 2003-08-28 at 18:58, Barlow, Dustin wrote:
> > In the 3.x series, how are CMTs handled if the JBoss MDB binds to a
> queue on
> > a Weblogic instance? Doesn't this require distributed TM which
> isn't
> > currently supported in 3.x? Would this even work between two JBoss
> 3.x
> > instances?
> >
> > Dustin
> >
> > > -----Original Message-----
> > > From: Adrian Brock [mailto:[EMAIL PROTECTED]]
> > > Sent: Thursday, August 28, 2003 1:24 PM
> > > To: [EMAIL PROTECTED]
> > > Subject: Re: [JBoss-user] JMS: JBoss to Weblogic messaging
> > >
> > >
> > > There are two types of interoperability.
> > >
> > > JBoss MDB can use any messaging system (it doesn't care about
> jbossmq)
> > >
> > > Different JMS systems can transport each others messages
> > > (typically by wrapping them in their own native message) -
> > > this is obviously slower than a uniform environment.
> > >
> > > Regards,
> > > Adrian
> > >
> > > On Thu, 2003-08-28 at 17:26, Dan Christopherson wrote:
> > > > Curley, John wrote:
> > > > > Hi, All:
> > > > >
> > > > > Can anyone give me feedback on performing JMS messaging
> to/from
> > > > > JBoss/WebLogic environments?
> > > > >
> > > > > Should there be any issues with guaranteed messaging?
> > > > >
> > > > > In theory, there should be interoperability between the
> > > two environments as
> > > > > implied by the J2EE specification.
> > > >
> > > > Not really. The J2EE spec guarantees that applications will
> > > be portable
> > > > between environments, not that servers will be interoperable.
> > > >
> > > > Depending on exactly what you need to do, you can use the JBoss
> JMS
> > > > implementation from within weblogic, or the weblogic
> > > implementation from
> > > > within JBoss, by constructing your initial JNDI context
> > > appropriately.
> > > >
> > > > hth,
> > > > danch
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > -------------------------------------------------------
> > > > This sf.net email is sponsored by:ThinkGeek
> > > > Welcome to geek heaven.
> > > > http://thinkgeek.com/sf
> > > > _______________________________________________
> > > > JBoss-user mailing list
> > > > [EMAIL PROTECTED]
> > > > https://lists.sourceforge.net/lists/listinfo/jboss-user
> > >
> > >
> > >
> > > -------------------------------------------------------
> > > This sf.net email is sponsored by:ThinkGeek
> > > Welcome to geek heaven.
> > > http://thinkgeek.com/sf
> > > _______________________________________________
> > > JBoss-user mailing list
> > > [EMAIL PROTECTED]
> > > https://lists.sourceforge.net/lists/listinfo/jboss-user
> > >
> >
> >
> > -------------------------------------------------------
> > This sf.net email is sponsored by:ThinkGeek
> > Welcome to geek heaven.
> > http://thinkgeek.com/sf
> > _______________________________________________
> > JBoss-user mailing list
> > [EMAIL PROTECTED]
> > https://lists.sourceforge.net/lists/listinfo/jboss-user
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> JBoss-user mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/jboss-user
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
