WebLogic 12 Socket Leak handling method

Live WebLogic News <DynamicListenThread[Default]> <<wls kernel>> <> <> <1417715701920> <BEA-002631> <max threshold reached for open sockets [Total open sockets:5,000, allowed max:5,000]. No More Connections allowed.>

There are two ways to handle this:

bea-002631-reached Maximum Open Sockets/leak of Sockets in Close_wait State (document ID 1673969.1)

Go to bottom

In this Document Symptoms Cause Solution References Applies to:oracle WebLogic server-version 12.1.2.0.0 and later Information in this document applies to any platform. Symptoms In a lightly loaded staging environment, the maximum open sockets is reached as below. 06-dec-2013 20:03:03 o ' clock GMT Warning Server rds09470app145 rdms1-restgp2b Dynamiclistenthread[default] WLS Kernel 138 6360183611 BEA-002631 Max threshold reached for open sockets [Total open sockets:1,000, allowed max:1,000]. No more connections allowed. In WLS 11g and 8.1 domains running on the same hardware with a. Sockets, this issue is not observed. Cause Using Niosocketmuxer (the default socket muxer in 12.1.2), the socket closure depends on the finalizer mechanism. If The finalizer thread does not kick in (e.g., no GC), the socket closure won't happen and you'll reach the number O F Open sockets configured. A second issue is that disabling the Max-open-sock-count setting requires a reboot, although the console says that a Rebo OT is unnecessary. A third issue was that although the first issue are solved, a number of sockets in Close_wait were still found, leading to The server ceasing to process requests. Observations: For the first issue, when using JFR (that is regularly kicks GC), the issue does not happen. The source code analysis confirms this. For the second issue, this is shown in console and while reproducing the first issue. For the third issue, one could watch, only on the customer instances, this phenomenon, although first issue is fixed! The same symptom occurred (leak of close_wait sockets) but in this case, stopping JFR does don't make the issue disappear. Solution Solution retained by this customer are to drop max-open-sock-count and to apply the known workaround against the deadlock. The other solution are to install the following patches on WLS 12.1.2: Patch 18108916 Patch 18289179 Patch 16784672 REFERENCES Bug:18396023-nio:many NATIVE SOCKETS in close_wait, NO JAVA SOCKET LEAKS Bug:18289179-setting max-open-sock-count REQUIRES ENTITY REBOOT

WebLogic 12 Socket Leak handling method