Why Does It Happen That the Java Client Is Inoperable After Some Time of Inactivity?
Last updated on MARCH 08, 2017
Applies to:Oracle Agile Engineering Data Management - Version 22.214.171.124 and later
Information in this document applies to any platform.
What could cause the Java Client to hang / shutdown with following error messages in the Java Client trace file:
ERROR 2013-12-04 07:53:03,708 [Thread-19] - java.io.IOException: IpcBytePacketReader.readBlock: Unexpected end of stream (0/11)
ERROR 2013-12-04 11:05:19,754 [ExitWorker] - [AxalantRepository@5f44ec] Connection com.agile.eci.EciClient@11c248a[/g13107/plm_prod] died
ERROR 2013-12-04 13:22:40,111 [AWT-EventQueue-0] - com.agile.eci.ConnectionException: Connection failed[java.net.ConnectException: Connection refused: connect]
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms