Why did stateful session beans (SFSB) change transactional behaviour in EAP 7

Solution Verified - Updated -

Issue

  • Custom PhaseListener with UserTransaction fails with ConcurrentAccessTimeoutException error:

    WFLYEJB0034: EJB Invocation failed on component Resources for method public javax.persistence.EntityManager org.jboss.as.quickstarts.tasksJsf.Resources.getEm(): javax.ejb.ConcurrentAccessTimeoutException: WFLYEJB0228: EJB 3.1 FR 4.3.14.1 concurrent access timeout on Resources - could not obtain lock within 5000 MILLISECONDS
    at org.jboss.as.ejb3.component.stateful.StatefulSessionSynchronizationInterceptor.processInvocation(StatefulSessionSynchronizationInterceptor.java:94)
    at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:240)
    

Environment

  • JBoss Enterprise Application Platform (EAP)
    • 7.0.x
    • 7.1.0

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content