My Oracle Support Banner

Why Does It Happen That the Java Client Is Inoperable After Some Time of Inactivity? (Doc ID 1607646.1)

Last updated on JUNE 21, 2018

Applies to:

Oracle Agile Engineering Data Management - Version 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] - 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[ Connection refused: connect]


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.
My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.