ERROR message in the JBoss ON server.log file: javax.ejb.ConcurrentAccessTimeoutException: JBAS014373: EJB 3.1 PFD2 4.8.5.5.1 concurrent access timeout on ... - could not obtain lock within 5000MILLISECONDS

Issue

• In the log file of one server I see multiple of these ERRORs at a time when no users have been active:

00:49:34,633 ERROR [org.jboss.as.ejb3] (EJB default - 10) JBAS014120: Error invoking timeout for timer: [id=4b380ea3-c526-4ee9-bd47-85375cd9da77 timedObjectId=rhq.rhq-server.SystemManagerBean auto-timer?:false persistent?:false timerService=org.jboss.as.ejb3.timerservice.TimerServiceImpl@4798a8a3 initialExpiration=Fri Mar 21 08:49:29 CET 2014 intervalDuration(in milli sec)=60000 nextExpiration=Tue May 06 00:50:29 CEST 2014 timerState=IN_TIMEOUT: javax.ejb.ConcurrentAccessTimeoutException: JBAS014373: EJB 3.1 PFD2 4.8.5.5.1 concurrent access timeout on org.jboss.invocation.InterceptorContext$Invocation@4d9af2dd - could not obtain lock within 5000MILLISECONDS

• ERROR message in the JBoss ON server.log file: javax.ejb.ConcurrentAccessTimeoutException: JBAS014373: EJB 3.1 PFD2 4.8.5.5.1 concurrent access timeout on ... - could not obtain lock within 5000MILLISECONDS

• Every night after internal maintenance job, the server returns this error:

ERROR [org.jboss.as.ejb3] (EJB default - 2) javax.ejb.EJBTransactionRolledbackException: JBAS014373: EJB 3.1 PFD2 4.8.5.5.1 concurrent access timeout on org.jboss.invocation.InterceptorContext$Invocation@2ed71876 - could not obtain lock within 5000MILLISECONDS

and stops collecting data and showing graph until the reboot of the sever and it's storage nodes.