Last updated on NOVEMBER 05, 2016
Applies to:
Oracle Weblogic Server - Version: 10.3Information in this document applies to any platform.
During high load, i.e when incoming requests is increased from 2000 to 4000 Issue of a livelock happens on a 64 bit m/c only.
And server starts rejecting almost all the requests, due to the livelock in highload.
According to documentation and stack, the old deprecated com.sun.net.ssl api (jsse 1.02 provider) is used in the code, instead of the new javax.net.ssl implementation, which, according to the new JSSE standard api, implement a non-blocking engine.
Both packages are still available in jsse.jar for backward compatibility.
A sample of stack:
at com.sun.net.ssl.internal.www.protocol.https.HttpsURLConnectionOldImpl.getOutputStream(HttpsURLConnectionOldImpl.java:200)
- locked <0x0000000771085108> (a com.sun.net.ssl.internal.www.protocol.https.HttpsURLConnectionOldImpl)
at com.aciworldwide.framework.message.HTTPProcess.sendMessage(Unknown Source)
at com.aciworldwide.framework.message.HTTPProcess.sendMessage(Unknown Source)
at com.aciworldwide.commerce.gateway.payment.MerchantNotificationService.processNotice(MerchantNotificationService.java:48)
The use of the deprecated api (HttpsURLConnectionOldImpl) has been found in the stack provided.
Symptoms
1) The issue occurs when using 64 bit jdk, everything works fine when using 32 bit jdk (to a max of 800 concurrent connection.
2) The issue occurs in the 64 bit JDK when the load is high.( Starts when number of connection increases to 100 and then the server rejects almost everything when the connections reach to 400.)
3) No issue in 32 bit environment, but requirement is to use 64 bit, as 32 bit environment is not meant for handling high load.
Changes
n/aCause
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