Last updated on NOVEMBER 13, 2015
Applies to:Oracle WebLogic Server - Version 10.3.5 to 10.3.6
Information in this document applies to any platform.
Under the following configuration, incoming data will cause consumption of 100% CPU, and a restart of the server is necessary to recover.
- Tuxedo, version 126.96.36.199.0, 64-bit, Patch Level (none),
- Jolt libraries packaged with it from tuxedo11gR1\udataobj\jolt\,
- JSSE and nativeIO enabled on Microsoft Windows, and
- NTSocketMuxer is used.
The problem with each CPU core being consumed by weblogic.socket.NTSocketMuxer will appear visibly to happen in several steps as per the WebLogic Server (WLS) log files:
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