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. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3859687#3859687 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3859687 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
