What Troubleshooting Steps Should be Taken When a Batch Client does not Start?
Last updated on FEBRUARY 08, 2017
Applies to:Oracle Agile Engineering Data Management - Version 126.96.36.199 and later
Information in this document applies to any platform.
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.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms