Last updated on MARCH 23, 2016
Applies to:JDBC - Version 10.2.0.1 and later
Information in this document applies to any platform.
JDBC connections going through a firewall experience intermittent "Broken Pipe" errors, particularly during periods of high load.
The details of the exception stack may vary depending upon the application or container being used; for example, the exception stack when using Oracle's JDBC driver from WebLogic may resemble the following:
<15-Sep-2010 04:13:34 o'clock BST> <Error> <JDBC> <BEA-001112> <Test "SELECT 1 FROM DUAL" set up for pool "A50-sbs-get-image-service-images-DS-1" failed with exception:
"java.sql.SQLException: [BEA][Oracle JDBC Driver]Write failed: Broken pipe".>
[Wed Sep 15 04:34:46 2010] GC reason: Large object allocation failed (69648 bytes), cause: Alloc Queue
[Wed Sep 15 04:34:46 2010] Stopping of javathreads took 1.965 ms
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