“SYS_ERROR (bad_transaction_state - not in transaction)” exceptions thrown when using transaction activities in the ActiveSpaces for BusinessWorks plugin.
Article ID: KB0089467
Updated On:
| Products | Versions |
|---|---|
| TIBCO ActiveSpaces | - |
| Not Applicable | - |
Description
Description:
“SYS_ERROR (bad_transaction_state - not in transaction)” exceptions thrown when using transaction activities in the ActiveSpaces for BusinessWorks plugin.
Symptoms:
<exceptiondata>
<ns0:ASException xmlns:ns0="http://schemas.tibco.com/bw/plugins/as/5.0/asExceptions">
<msg>SYS_ERROR (bad_transaction_state - not in transaction)</msg>
<msgCode>BW-AS-100001</msgCode>
<ASStatus/>
</ns0:ASException>
</exceptiondata>
Cause:
BusinessWorks thread switch mechanism.
“SYS_ERROR (bad_transaction_state - not in transaction)” exceptions thrown when using transaction activities in the ActiveSpaces for BusinessWorks plugin.
Symptoms:
<exceptiondata>
<ns0:ASException xmlns:ns0="http://schemas.tibco.com/bw/plugins/as/5.0/asExceptions">
<msg>SYS_ERROR (bad_transaction_state - not in transaction)</msg>
<msgCode>BW-AS-100001</msgCode>
<ASStatus/>
</ns0:ASException>
</exceptiondata>
Cause:
BusinessWorks thread switch mechanism.
Issue/Introduction
“SYS_ERROR (bad_transaction_state - not in transaction)” exceptions thrown when using transaction activities in the ActiveSpaces for BusinessWorks plugin.
Resolution
Set the following properties to avoid thread switching in BusinessWorks:
MaxJobs.* > 0
ActivationLimit.* = true
Engine.StepCount > the count of your activities in your processes
Example:
MaxJobs.* = 20
ActivationLimit.* = true
Engine.StepCount = 1000
MaxJobs.* > 0
ActivationLimit.* = true
Engine.StepCount > the count of your activities in your processes
Example:
MaxJobs.* = 20
ActivationLimit.* = true
Engine.StepCount = 1000
Feedback
Yes
No
Powered by
