This is going to sound funny, but I think you've fixed it.... I made the change you outlined in the source and recompiled JBoss 4.0.0.
I don't get the error anymore. The whole test suite for my app just passed including the XA tests. Connections appear to be returning to the pool, etc. Although the change may seem minor, it seems to directly address the issue I was having getting TopLink to work with JBoss. The transaction status was in conflict with TopLink's action to close the connection. I don't understand the JBoss source well enough to know what the overall impact is. I'm obviously going to spend more time with it, but it is very encouraging. I think you're onto the problem, is there anything I can do to further test this issue? Any chance of this making it into the next JBoss 4.0.x version? Nate View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3853529#3853529 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3853529 ------------------------------------------------------- This SF.Net email is sponsored by: Sybase ASE Linux Express Edition - download now for FREE LinuxWorld Reader's Choice Award Winner for best database on Linux. http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
