Explanation of the "Connection timed out" before the end of the transaction

Solution Verified - Updated -


  • See in the server.log an END USER COMMAND, but immediately before it a Connection timed out, shouldn't the transaction been CANCELED?
11:59:36,711 WARN  [org.teiid.TRANSPORT] (New I/O worker #53) TEIID40114 Unhandled exception, closing client instance: Connection timed out
11:59:36,711 INFO  [org.teiid.COMMAND_LOG] (Worker8212_QueryProcessorQueue1004958)  END USER COMMAND:   endTime=2019-04-12 11:59:36.711 requestID=uTvjJ42E2NIM.5    txID=null   sessionID=uTvjJ42E2NIM  principal=user@ldap-security    vdbName=ExampleVDB  vdbVersion=1    finalRowCount=12
11:59:36,711 DEBUG [org.teiid.AUDIT_LOG] (New I/O worker #53)  [user@ldap-security] <session.logoff> 


  • Red Hat JBoss Data Virtualization (DV) 6

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