Khudalla's patch fixes it for me in Glassfish. You need to compile it manually though as the patch isn't committed to the trunk yet (so the snapshots won't have it)..
Even with the patch, the resource adapter is still pretty useless under glassfish especially under XA transactions. If you happen to tie the use of a database, and jms together in the same transaction (common usecase) - you'll get get prepare errors from glassfish and the transaction being rolled back. for more info: http://forums.java.net/jive/thread.jspa?messageID=235026 khudalla wrote: > > Hi, Juvaraj! > > The problem is that the ManagedConnectionFactory provided in the RA is not > serializable (well, it actually is serializable but its reference to the > ResourceAdapter implementation is transient). I have created a patch for > this problem (which is most likely to occur in any J2EE environment that > tries to store instances of the ManagedConnectionFactory in JNDI and thus > serializes it). However, the patch has not yet made it into SVN :-( It is > available from JIRA though: > http://issues.apache.org/activemq/browse/AMQ-765 > > You can download the patch file and should be able to apply it to the 5.1 > snapshot sources using your favorite IDE. > > Good luck, > Kai > > -- View this message in context: http://www.nabble.com/ActiveMQ-RA-serialization-issue-in-Websphere-tp16253150s2354p16447876.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.