I've had this exception too, but probably in a different setup than you have. We were using mvc from persistance soft to enable ejb2.1 in jboss 2.4.x (also worked with later jboss version). This persistance mechanism had the default behaviour to only set Transaction to rollbackonly and NOT throw an EJBException when the commit on the database transaction fails. Then at a later time (the spot where your exception originates from) the transaction is rolled back (because it is set to rollbackonly) but the original error message from the database is lost. When changing the default behaviour to not only roll back the Server Transaction, but to also throw an EJBException, the message of the database is exception is not lost but can still be found at the end of a big nested exception chain within the TransactionRolledBackException.
You might have a different system setup, but maybe this explanation what happened to us helps you find your problem. Basically, the Server Transaction was set to rollbackonly at a certain point without throwing an exception there. dirk View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3947597#3947597 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3947597 ------------------------------------------------------- All the advantages of Linux Managed Hosting--Without the Cost and Risk! Fully trained technicians. The highest number of Red Hat certifications in the hosting industry. Fanatical Support. Click to learn more http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
