Transactional behavior of distributed EJB invocations in EAP6

Solution Verified - Updated -

Issue

  • Are EJB invocations from server to server transactional?
  • Do I need JTS for Server to Server EJB calls to be within the same transaction on JBoss EAP 6?
  • Is the transaction distributed if an EJB deployed on a different server is called remote?
  • If a remote EJB which is marked as transactional NEVER is called from another server application the invocation fail. Since we are using JTA this should never happen!

    javax.ejb.EJBException: JBAS014163: Transaction present on server in Never call (EJB3 13.6.2.6)
    
  • After migrating from EAP 4.x/5x to EAP 6 the transactional behaviour of applications, which are deployed on different servers but interact, will be different. The database changes of the sub-call will be rolled-back if the front EJB will be rollback the transaction. Because we are using JTA transaction manager we are not expecting this behaviour.

  • How can we expose our SLSBs to make sure any incoming call does not propagate the transaction between the two EAP instances? We are happy to make changes to either side of the server configurations.

Environment

  • JBoss Enterprise Apllication Platform (EAP)
    • 6.x

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In