5 Replies Latest reply on Dec 27, 2004 5:02 PM by danielbr

WebSphere 5.0.2 with JBossMQ 3.2.6 for Distributed Transacti

marcfleury Dec 21, 2004 4:50 PM

I am trying to use JBoss as a "Generic JMS Provider" for distributed transactions under WebSphere Application Server (WAS) v.5.0.2, following the general guidelines in an IBM tutorial detailing how to configure WAS 5.0 with SonicMQ (http://www-106.ibm.com/developerworks/websphere/library/tutorials/0309_chen/chen_reg.html).

I have a transactional session bean method that creates an entity bean and places a message in a queue. The session bean uses an XA datasource with the entity bean and obtains a JBoss XAConnectionFactory for the JMS Queue (queue/Q1). My transaction fails with the following message in the WAS console:

[12/21/04 15:34:15:880 EST] 56767404 JTAXAResource W WTRN0083_UNEXPECTED_XA_ERROR_ON_ROLLBACK XAER_RMERR
ERROR [2004-12-21 15:34:15,973] (ClusteringAction.java:305) - javax.transaction.TransactionRolledbackException: CORBA TRANSACTION_ROLLEDBACK 0x0 No; nested exception is:
 org.omg.CORBA.TRANSACTION_ROLLEDBACK: javax.transaction.TransactionRolledbackException: minor code: 0 completed: No

But the root cause of the problem can be seen here (also from the WAS log):

nested throwable: org.jboss.mq.SpyJMSException: Cannot process a transaction; - nested throwable: (java.io.NotSerializableException: com.ibm.ejs.jts.jta.XID)
 at org.jboss.mq.Connection.send(Connection.java:1221)
 at org.jboss.mq.SpyXAResourceManager.prepare(SpyXAResourceManager.java:208)
 at org.jboss.mq.SpyXAResource.prepare(SpyXAResource.java:131)
...

So for some reason JBoss tries to serialize the IBM provided transaction ID and fails. Any ideas how to make this work?

Here's what happens inside the JBoss server log:

2004-12-21 15:34:05,645 DEBUG [org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory] Using properties: {user=sa, password=--hidden--}
2004-12-21 15:34:15,317 DEBUG [org.jboss.mq.il.uil2.SocketManager] Begin ReadTask.run
2004-12-21 15:34:15,317 DEBUG [org.jboss.mq.il.uil2.SocketManager] Begin WriteTask.run
2004-12-21 15:34:15,317 DEBUG [org.jboss.mq.il.uil2.SocketManager] Created ObjectInputStream
2004-12-21 15:34:15,317 DEBUG [org.jboss.mq.il.uil2.SocketManager] Created ObjectOutputStream
2004-12-21 15:34:15,317 DEBUG [org.jboss.mq.il.uil2.ServerSocketManagerHandler] Setting up the UILClientIL Connection
2004-12-21 15:34:15,317 DEBUG [org.jboss.mq.il.uil2.ServerSocketManagerHandler] The UILClientIL Connection is set up
2004-12-21 15:34:15,457 DEBUG [org.jboss.mq.il.uil2.ServerSocketManagerHandler] Exiting on IOE
java.io.WriteAbortedException: writing aborted; java.io.NotSerializableException: com.ibm.ejs.jts.jta.XID
 at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1303)
 at java.io.ObjectInputStream.readObject(ObjectInputStream.java:339)
 at org.jboss.mq.TransactionRequest.readExternal(TransactionRequest.java:64)
 at org.jboss.mq.il.uil2.msgs.TransactMsg.read(TransactMsg.java:56)
 at org.jboss.mq.il.uil2.SocketManager$ReadTask.run(SocketManager.java:292)
 at java.lang.Thread.run(Thread.java:595)
Caused by: java.io.NotSerializableException: com.ibm.ejs.jts.jta.XID
2004-12-21 15:34:15,457 DEBUG [org.jboss.mq.il.uil2.SocketManager] End ReadTask.run
2004-12-21 15:34:15,457 DEBUG [org.jboss.mq.il.uil2.SocketManager] End WriteTask.run
2004-12-21 15:36:35,639 DEBUG [org.jboss.resource.connectionmanager.IdleRemover] run: IdleRemover notifying pools, interval: 150000

Thanks,

Daniel.

1. Re: WebSphere 5.0.2 with JBossMQ 3.2.6 for Distributed Trans

danielbr Dec 21, 2004 5:04 PM (in response to marcfleury)

Oops, forgive the incorrect account name on the previous post. "marcfleury" is an account generated from bugmenot.com. I think my browser must have picked up a cookie on this machine from some other visit. This is my real account.

Thanks,

Daniel.
Actions
2. Re: WebSphere 5.0.2 with JBossMQ 3.2.6 for Distributed Trans

adrian.brock Dec 22, 2004 8:25 PM (in response to marcfleury)
Report it is a bug. http://jira.jboss.com/jira/browse/JBMQ

Even if the IBM Xid implementation were serializable, it would fail to deserialize
on the server unless you put that class inside JBossMQ.

The fix is trivial if you want to attempt it yourself and post the patch:

In org.jboss.mq.TransactionRequest.writeExternal()
if (xid != null && xid instanceof Xid) out.writeObject(new JBossMQXid((Xid) xid)); else out.writeObject(xid); // current code

Where there is a new class (needed on both client and server):
package org.jboss.mq; public class JBossMQXid implements Xid, Serializable

Don't forget it needs to properly implement equals and hashCode.
Actions
3. Re: WebSphere 5.0.2 with JBossMQ 3.2.6 for Distributed Trans

danielbr Dec 27, 2004 10:56 AM (in response to marcfleury)

Thanks for the reply Adrian!

I would like to do this simple fix myself and contribute it back to the project. How should I go about doing this? You mentioned submitting a patch but what does this mean exactly (is there an open CVS server, for instance)? Sorry, but I'm new on JBoss and still haven't quite figured out how to participate as a developer on the project.

Daniel.
Actions
4. Re: WebSphere 5.0.2 with JBossMQ 3.2.6 for Distributed Trans

starksm64 Dec 27, 2004 12:05 PM (in response to marcfleury)

Access to cvs is described here:
http://sourceforge.net/cvs/?group_id=22866

Patches are context diffs of the source files changes. They should be submitted to:
http://jira.jboss.com/jira/browse/JBAS
Actions
5. Re: WebSphere 5.0.2 with JBossMQ 3.2.6 for Distributed Trans

danielbr Dec 27, 2004 5:02 PM (in response to marcfleury)

The suggested fix worked and I now I have JBoss MQ providing XA transactions for WebSphere! I've placed the patch under Jira, as requested:
http://jira.jboss.com/jira/browse/JBMQ-17.

Thanks for the support!

Daniel.
Actions

Go to original post