What Troubleshooting Steps Should be Taken When a Batch Client does not Start? (Doc ID 2231649.1)

Last updated on FEBRUARY 08, 2017

Applies to:

Oracle Agile Engineering Data Management - Version 6.1.3.0 and later
Information in this document applies to any platform.

Goal

 What Troubleshooting Steps Should be Taken When a Batch Client does not Start?  Some of the errors seen may include (in no particular order):

Caught java.net.SocketException: Broken pipe while closing socket
ERROR: com.agile.eci.ConnectionException: Not connected
WrapperManager Debug: Load native library.  There are multiple possible file names and the first to be found will be used.  Errors loading non-existing files is normal and is only a problem if they all fail.

 

Solution

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