Red Hat Bugzilla – Bug 990620
ResourceException: IJ000459: Transaction is not active is thrown clicking on Tasks List and on starting a task
Last modified: 2015-06-01 21:35:24 EDT
Created attachment 781189 [details]
ResourceException: IJ000459: Transaction is not active is thrown clicking on Tasks List and on starting a task. See the whole attached server.log.
16:30:52,232 ERROR [stderr] (http-localhost/127.0.0.1:8080-4) Caused by: javax.resource.ResourceException: IJ000459: Transaction is not active: tx=TransactionImple < ac, BasicAction: 0:ffff0a221e05:5eb07097:51f91842:1a5 status: ActionStatus.ABORT_ONLY >
This is thrown by clicking on Tasks List.
16:36:09,966 ERROR [stderr] (http-localhost/127.0.0.1:8080-2) Caused by: javax.resource.ResourceException: IJ000459: Transaction is not active: tx=TransactionImple < ac, BasicAction: 0:ffff0a221e05:5eb07097:51f91842:1e0 status: ActionStatus.ABORT_ONLY >
This is thrown by clicking on a start task button.
How to reproduce:
1.) Install jBPM 6 CR1 into EAP 6.1
2.) Add user guest to eap6 config files:
guest=b5d048a237bfd2874b6928e1f37ee15e # guest/guest
3.) clone git repository from
4.) build a deploy project bpms-perf
5.) start process HumanTask (it's a simple custom process Start->HT->End, actor is guest)
This bug does not seem to affect functionality, the task is completed (tries only with empty task data) and also the process is completed. However such exceptions should not be thrown if everything is ok, or there's a risk that such exception can be source of problems later.
JBoss EAP 6.1
jBPM 6 CR1
To clone the bpms-assets repository use read-only mirror:
git clone git://git.app.eng.bos.redhat.com/bpms-assets.git
the cause of this issue was due to user and group has exactly same id (guest/guest)and that is not allowed as they are kept inside same table. Although the cause is clear the actual exception was swallowed which allowed to make the next operation inline (query) which in turn failed as the insert of group marked transaction as rollback only.
Change was applied to ensure that the exception is propagated up to the caller with actual cause.
Ensuring that user and groups are unique resolves the issue completely.
Commit on 6.0.x branch:
When the same name is used for user name and group, a proper exception is thrown.
Verified in BPMS 6 ER2 (redhat-2).