JSR-352 batch steps aborted after 3 minutes in JBoss EAP 7

Solution Verified - Updated -

Issue

  • Running a JSR-352/JBeret batch step that is expected to take significant time to complete.
  • The JBoss EAP transactions subsystem default-timeout has been increased but batch jobs timeout after 3 minutes (ARJUNA012117, etc. can be found in the JBoss EAP server.log).

Environment

  • Red Hat JBoss Enterprise Application Platform (EAP) 7

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