Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1140720

Summary: javax.ejb.ConcurrentAccessTimeoutException in SimpleAsyncExecutorService
Product: [Retired] JBoss BRMS Platform 6 Reporter: Marek Winkler <mwinkler>
Component: Business CentralAssignee: manstis
Status: CLOSED WONTFIX QA Contact: Marek Winkler <mwinkler>
Severity: high Docs Contact:
Priority: high    
Version: 6.1.0CC: jlocker, kverlaen
Target Milestone: ER2   
Target Release: 6.1.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-12-04 15:19:09 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
server.log part with the stacktrace none

Description Marek Winkler 2014-09-11 14:14:10 UTC
Created attachment 936578 [details]
server.log part with the stacktrace

Description of problem:

When working with business-central, javax.ejb.ConcurrentAccessTimeoutException is thrown in SimpleAsyncExecutorService and reported in the server log (see the attachment for full stacktrace):

15:50:56,127 ERROR [org.jboss.as.ejb3.invocation] (EJB default - 9) JBAS014134: EJB Invocation failed on component SimpleAsyncExecutorService for method public void org.uberfire.commons.async.SimpleAsyncExecutorService.execute(java.lang.Runnable): javax.ejb.ConcurrentAccessTimeoutException: JBAS014373: EJB 3.1 PFD2 4.8.5.5.1 concurrent access timeout on org.jboss.invocation.InterceptorContext$Invocation@73c92338 - could not obtain lock within 5000MILLISECONDS

It seems the problem is connected with running incremental build but you might need to perform several actions in the GUI (create a new DRL, build project, create a new process, build project).

Version-Release number of selected component (if applicable):

BRMS 6.1.0 DR2
EAP 6.3.0 GA

How reproducible:

I started BRMS 3 times, the exception occured every time but after a different action.

Steps to Reproduce:
1. Log in to business-central.
2. Create a new DRL (with a dummy rule with empty when and then parts)
3. Build and deploy the project
4. Create a new Process, save it, delete it
...

Watch the server.log - the first time, I got the exception after the process had been created. Then I stopped EAP and started it again, I got the exception right after I logged in. After the next EAP restart, I saw the exception in the log when designer was opening (but it seems that incremental build was running at that time too).

Actual results:

The server.log contains the error message with the exception.

Expected results:

The server.log does not contain the error message.

Additional info:

It seems there is no impact on functionality, but this exception might indicate a problem which is not visible right now.

Comment 1 manstis 2014-09-11 14:35:59 UTC
I believe this is a manifestation of the referenced BZ.