Oc4j Application Show Broken Pipe Error When Backend Database Is Restarted
Last updated on DECEMBER 07, 2017
Applies to:Oracle TopLink - Version 126.96.36.199 to 188.8.131.52.0
Oracle Containers for J2EE - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
***Checked for relevance on 08-Dec-2009***
- Application running fine in OC4J container, when the backend database is running.
- Errors occurred when the backend database is restarted.
- Using OC4J connection pool, setup to auto-reconnect on DB failure.
- Using TopLink for data persistance
- Problem does not occure with applications that are not using TopLink and the same data source setup.
Verified the issue by the log file opmn.log, which displays broken pipe error message:
Exception [TOPLINK-4002] (OracleAS TopLink - 10g (9.0.4) (Build 031126)):
Exception Description: java.sql.SQLException: Io exception: Broken pipe
Internal Exception: java.sql.SQLException: Io exception: Broken pipe
Error Code: 17002
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