Hmmm - having delved a bit further by turning on the SQL debugging (as per the Wiki - very useful!), it appears as though I have a problem with deadlocking occuring that is being hidden by some suspect exception handling on my part. When creating a new entity, it is associated with the id of another entity of the same type by running a finder on the same entity type within the business method doing the create. This is deadlocking and causing the whole tx to roll back. Looks like the issue is an application level one and I might be better to look up the parent entity before getting to the save, rather than inside the same transaction. Not sure why it only shows up in the cluster though...
Thanks for listening! Nothing like explaining the problem to someone else to help in solving it ;) Jon View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3837315#3837315 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3837315 ------------------------------------------------------- This SF.Net email is sponsored by the new InstallShield X. >From Windows to Linux, servers to mobile, InstallShield X is the one installation-authoring solution that does it all. Learn more and evaluate today! http://www.installshield.com/Dev2Dev/0504 _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
