Java Security

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Interested in getting your voice heard by members of the Developer Marketing team at Oracle? Check out this post for AppDev or this post for AI focus group information.

Deadlock formed during SSL Socket Write

User_MT5TONov 4 2020 — edited Nov 4 2020

In some odd cases (SSL) when multiple threads reading/writing on different Socket's stream, a deadlock is formed with following JAVA call stack.
Thread '[ACTIVE] ExecuteThread: '320' for queue: 'weblogic.kernel.Default
(self-tuning)'' is waiting to acquire lock 'com.rsa.sslj.x.aP@61d391b3' that
is held by thread '[ACTIVE] ExecuteThread: '104' for queue:
'weblogic.kernel.Default (self-tuning)''
Stack trace:
------------
com.rsa.sslj.x.aP.a(Unknown Source)
com.rsa.sslj.x.bo.n(Unknown Source)
com.rsa.sslj.x.bo.a(Unknown Source)
com.rsa.sslj.x.aI.z(Unknown Source)
com.rsa.sslj.x.aI.u(Unknown Source)
com.rsa.sslj.x.aI.c(Unknown Source)
com.rsa.sslj.x.ap.n(Unknown Source)
com.rsa.sslj.x.ap.a(Unknown Source)
com.rsa.sslj.x.ap.a(Unknown Source)
com.rsa.sslj.x.ap.a(Unknown Source)
com.rsa.sslj.x.am.write(Unknown Source)
java.io.OutputStream.write(OutputStream.java:75)
Under normal flow everything works fine but under heavy load this exist. Any suggestion based on above call stack (looks like JAVA internal code) will be great help. Using Oracle JDK 8.

Added on Nov 4 2020

#java, #java-secure-socket-extension-jsse, #ssl

0 comments

215 views