jt400 driver does not timeout when the database does not respond to command from JBoss EAP

Solution Verified - Updated -

Issue

During a failure of the DB2 database, execution hangs with the stack trace below

    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:502)
    at com.ibm.as400.access.AS400ThreadedServer.receive(AS400ThreadedServer.java:339)
    at com.ibm.as400.access.AS400ThreadedServer.sendAndReceive(AS400ThreadedServer.java:492)
    at com.ibm.as400.access.AS400JDBCConnection.sendAndReceive(AS400JDBCConnection.java:3005)
    at com.ibm.as400.access.AS400JDBCStatement.commonExecute(AS400JDBCStatement.java:950)
    at com.ibm.as400.access.AS400JDBCPreparedStatement.executeBatch(AS400JDBCPreparedStatement.java:1675)
    at org.jboss.jca.adapters.jdbc.CachedPreparedStatement.executeBatch(CachedPreparedStatement.java:714)
    ...

Environment

  • Red Hat JBoss Enterprise Application Platform (EAP) 7
  • IBM DB2 accessed via jt400.jar

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