Description of problem: To recreate: 1. I edited topic 252. 2. I uppercased all instances of ZIP, including the title. 3. I clicked 'Save' and entered a comment. 4. I get an Alert with the following message: An error occurred on the server. Please try again and if this problem persists, please log a bug. javax.transaction.NotSupportedException: BaseTransaction.checkTransactionState - ARJUNA016051: thread is already associated with a transaction! Version-Release number of selected component (if applicable): I tried to access a different topic and am not able to open any to edit. I get the same message on the read. How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Possible fix has been checked in at https://github.com/pressgang-ccms/PressGangCCMSREST/blob/devel/src/main/java/org/jboss/pressgang/ccms/server/rest/v1/base/BaseRESTv1.java#L1478 I have deployed this version to the dev server for testing.
*** Bug 1056695 has been marked as a duplicate of this bug. ***
The actual commit is here (incase that class changes in anyway): https://github.com/pressgang-ccms/PressGangCCMSREST/commit/3db1f5a3a8928002316daf6a1f3ca7af39950bf7
Did some testing this morning and it appears to fix the "thread is already associated with a transaction", however it doesn't take into account that the transaction might not have been active. This was then throwing exceptions if for example the expand content wasn't valid json, so i've re-added the status check but removed the rollback status conditions. See: https://github.com/pressgang-ccms/PressGangCCMSREST/commit/01958eb69df859c0c8893ca0a20bfe57fe4e5afd
Moving to CLOSED CURRENTRELEASE as we've been using this fix for a week on the test server without issues. It has also been active in production for 4 business days.