IX90194: ORB'S SOCKET TIMER THREAD HANGS IN COM.IBM.JSSE2

APAR status

• Closed as program error.

Error description

• Error Message: None
  .
  Stack Trace: sun/misc/Unsafe.park(Native Method)
  java/util/concurrent/locks/LockSupport.park(LockSupport.java:186
  (Compiled Code))
  java/util/concurrent/locks/AbstractQueuedSynchronizer.parkAndChe
  ckInterrupt(AbstractQueuedSynchronizer.java:847(Compiled Code))
  java/util/concurrent/locks/AbstractQueuedSynchronizer.acquireQue
  ued(AbstractQueuedSynchronizer.java:881(Compiled Code))
  java/util/concurrent/locks/AbstractQueuedSynchronizer.acquire(Ab
  stractQueuedSynchronizer.java:1210(Compiled Code))
  java/util/concurrent/locks/ReentrantLock$NonfairSync.lock(Reentr
  antLock.java:220(Compiled Code))
  java/util/concurrent/locks/ReentrantLock.lock(ReentrantLock.java
  :296(Compiled Code))
  com/ibm/jsse2/bj.b(bj.java:266(Compiled Code))
  com/ibm/jsse2/bj.d(bj.java:3)
  com/ibm/jsse2/bj.close(bj.java:505(Compiled Code))
  com/ibm/jsse2/bj$b.close(bj$b.java:26(Compiled Code))
  com/ibm/CORBA/transport/TransportConnectionBase.removeConnection
  (TransportConnectionBase.java:480(Compiled Code))
  com/ibm/ws/orbimpl/transport/WSTCPTransportConnection.removeConn
  ection(WSTCPTransportConnection.java:273(Compiled Code))
  com/ibm/ws/orbimpl/transport/WSSSLTransportConnection.removeConn
  ection(WSSSLTransportConnection.java:341(Compiled Code))
  com/ibm/rmi/iiop/Connection.purge_calls(Connection.java:2233(Com
  piled Code))
  com/ibm/rmi/iiop/Connection.purge_calls(Connection.java:2120)
  com/ibm/rmi/transport/ConnectionTableImpl.removeConnectionsStuck
  InWrite(ConnectionTableImpl.java:615(Compiled Code))
  com/ibm/rmi/iiop/SocketTimerThread.run(SocketTimerThread.java:61
  )
  .
  This situation could result when the process at the remote end
  goes down, or if the remote process is suspended.
  

Local fix

Problem summary

• When the Socket Timer Thread tries to close a connection stuck
  in read for more than the "com.ibm.CORBA.SocketWriteTimeout"
  value, a recent change, related to TLS v1.3 support, in the
  socket close logic for TLS sockets in com.ibm.jsse2 may run into
  a hang while trying to take a ReentrantLock. This could result
  when the remote end of the TLS connection is down. Further, the
  locking could be avoided if the linger time on the socket has
  elapsed when this code is invoked.
  

Problem conclusion

• Though this is not an issue with ORB's Socket Timer Thread, this
  APAR allows users to set SO_LINGER values on ORB sockets. Two
  new properties are introduced:
  "com.ibm.CORBA.server.SocketLingerTime" is to be used to set the
  SO_LINGER timeout on server sockets
  "com.ibm.CORBA.client.SocketLingerTime" is to be used to set the
  SO_LIGNER timeout on client sockets
  We recommend that the values of these properties be lesser than
  the write timeout value set using
  "com.ibm.CORBA.SocketWriteTimeout". For immediate closure of the
  sockets, they could be set to 0. These properties would be
  ignored if they are set to negative values, or if the Socket
  Timer Thread does not exist.
  .
  These properties can be set by the user in either the
  orb.properties file or by the system property option.
  .
  This APAR will be fixed in the following Releases:
  .
  IBM SDK, Java Technology Edition
     8    SR8 FP5   (8.0.8.5)
  .
  Contact your IBM Product's Service Team for these Service
  Refreshes and Fix Packs.
  For those running stand-alone, information about the available
  maintenance can be found at:
             https://www.ibm.com/support/pages/java-sdk
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  ORB

• Fixed component ID

  620700123

Applicable component levels