ALSB 2.6 is Causing CLOSE-WAIT sockets by not Closing the Inbound Connections When the HTTP Proxy Client Request Fails With 401 Errors (Doc ID 954522.1)

Last updated on MAY 12, 2023

Applies to:

Oracle Service Bus - Version 2.5 to 2.6.1RP [Release Aqualogic Service Bus]
Information in this document applies to any platform.

Goal

Each time a client calls a proxy service with HTTP(S) transport, netstat -a shows one more socket in CLOSE_WAIT. After a while, you get thousands of CLOSE_WAIT sockets making the server unavaillable.

This happens if the client fails to authenticate and receives a HTTP 401 error.

In the log file you will find TooManyOpenFileError messages.The number of allowed file descriptors will be used by the java process running the ALSB/WebLogic Server.

Solution

	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

Goal

Solution

References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.

ALSB 2.6 is Causing CLOSE-WAIT sockets by not Closing the Inbound Connections When the HTTP Proxy Client Request Fails With 401 Errors (Doc ID 954522.1)

Applies to:

Goal

Solution

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!