[ http://jira.jboss.com/jira/browse/JBMQ-17?page=history ]
Adrian Brock updated JBMQ-17:
-----------------------------
Description:
A java.io.NotSerializableException is thrown when using JBossMQ as a
transactional "Generic JMS Provider" under IBM WebSphere Application Server
5.0.2. The IBM class com.ibm.ejs.jts.jta.XID is not serializable and causes
the SpyXAResourceManager.prepare(...) method to fail. The solution is to:
1) Clone (deep copy) the non-serializable Xid to a new a new serializable Xid
wrapper: JBossMQXid.java.
2) The org.jboss.mq.TransactionRequest class' writeExternal(...) method must be
modified to perform the wrapping
3) The JBossMQXid class must now be available under both client and server. I
think the packaging jboss-3.2.6-src product needs to be modified so that upon a
build the JBossMQXid class gets made available in the "jbossmq" server (created
when /jboss-3.2.6/docs/examples/jms/standalone/build.xml is run). I had to
manually add the jbossmq-client.jar to servers/jbossmq/lib to make it work.
was:
A java.io.NotSerializableException is thrown when using JBossMQ as a
transactional "Generic JMS Provider" under IBM WebSphere Application Server
5.0.2. The IBM class com.ibm.ejs.jts.jta.XID is not serializable and causes
the SpyXAResourceManager.prepare(...) method to fail. The solution is to:
1) Clone (deep copy) the non-serializable Xid to a new a new serializable Xid
wrapper: JBossMQXid.java.
2) The org.jboss.mq.TransactionRequest class' writeExternal(...) method must be
modified to perform the wrapping
3) The JBossMQXid class must now be available under both client and server. I
think the packaging jboss-3.2.6-src product needs to be modified so that upon a
build the JBossMQXid class gets made available in the "jbossmq" server (created
when /jboss-3.2.6/docs/examples/jms/standalone/build.xml is run). I had to
manually add the jbossmq-client.jar to servers/jbossmq/lib to make it work.
Version: JBossAS-4.0.1
(was: JBossAS-3.2.6)
> Fix for Use of Non-Serializable Xid Implementations
> ---------------------------------------------------
>
> Key: JBMQ-17
> URL: http://jira.jboss.com/jira/browse/JBMQ-17
> Project: JBoss MQ
> Type: Patch
> Components: Transport, Persistence
> Versions: JBossAS-4.0.1
> Environment: WebSphere Application Server 5.0.2
> Reporter: Daniel Ramagem
> Assignee: Adrian Brock
> Attachments: JBossMQXid.java, JBossMQXid.java, TransactionRequest.java,
> TransactionRequest.java.diff
>
>
> A java.io.NotSerializableException is thrown when using JBossMQ as a
> transactional "Generic JMS Provider" under IBM WebSphere Application Server
> 5.0.2. The IBM class com.ibm.ejs.jts.jta.XID is not serializable and causes
> the SpyXAResourceManager.prepare(...) method to fail. The solution is to:
> 1) Clone (deep copy) the non-serializable Xid to a new a new serializable Xid
> wrapper: JBossMQXid.java.
> 2) The org.jboss.mq.TransactionRequest class' writeExternal(...) method must
> be modified to perform the wrapping
> 3) The JBossMQXid class must now be available under both client and server.
> I think the packaging jboss-3.2.6-src product needs to be modified so that
> upon a build the JBossMQXid class gets made available in the "jbossmq" server
> (created when /jboss-3.2.6/docs/examples/jms/standalone/build.xml is run). I
> had to manually add the jbossmq-client.jar to servers/jbossmq/lib to make it
> work.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
