Sockets and Memory Leak in Service Bus Due to java.net.SocketException: Broken Pipe Errors.
(Doc ID 838671.1)
Last updated on APRIL 14, 2021
Applies to:Oracle Service Bus - Version 2.5 to 10.3 [Release Aqualogic Service Bus to AS10gR3]
Information in this document applies to any platform.
ALSB is causing sockets to stay in status CLOSE-WAIT, not closing the inbound connections, when the http proxy client request failed after an unsuccessful authentication with a HTTP 401 response.
Memory leaks occur if outbound HTTP call fails with Broken Pipe Exception.
Server log files might contain the following exception messages:
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