PK39983: EXCESSIVE SIB CONNECTION PROBLEM FFDCS WITH MESSAGE CWSIJ0077E

APAR status

• Closed as duplicate of another APAR.

Error description

• When there is a network problem, the Service Integration Bus
  may generate ffdcs at the point of failure.  In rare cases, the
  SIB code may generate excessively large numbers of ffdcs (~3000
  per minute) showing message CWSIJ0077E ("An unexpected condition
  caused a network connection to close").  When there are too many
  ffdcs, WebSphere Application Server may fail to start.  Here is
  a sample of the ffdc:
  .
  key =
  com.ibm.wsspi.sib.core.exception.SIConnectionDroppedException
  com.ibm.ws.sib.jfapchannel.impl.ConnectionWriteCompletedCallback
  00060004
  Exception =
  com.ibm.wsspi.sib.core.exception.SIConnectionDroppedException
  Source =
  com.ibm.ws.sib.jfapchannel.impl.ConnectionWriteCompletedCallback
  probeid = 00060004
  Stack Dump =
  com.ibm.wsspi.sib.core.exception.SIConnectionDroppedException:
  CWSIJ0077E: An unexpected condition caused a network connection
  to close.
  at com.ibm.ws.sib.jfapchannel.impl.PriorityQueue.dequeue(Priorit
     yQueue.java(Compiled Code))
  at com.ibm.ws.sib.jfapchannel.impl.ConnectionWriteCompletedCallb
     ack.dequeueTransmissionData(ConnectionWriteCompletedCallback.
     java(Compiled Code))
  at com.ibm.ws.sib.jfapchannel.impl.ConnectionWriteCompletedCallb
     ack.complete(ConnectionWriteCompletedCallback.java(Compiled C
     ode))
  at com.ibm.ws.sib.jfapchannel.impl.ConnectionWriteCompletedCallb
     ack.proddle(ConnectionWriteCompletedCallback.java(Compiled Co
     de))
  at com.ibm.ws.sib.jfapchannel.impl.Connection.send(Connection.ja
     va (Compiled Code))
     ...
  

Local fix

•   To suppress ffdcs temporarily, it is possible to edit the
  "install_root"/properties/ffdcRun.properties file and change the
  first property from "FFDC=true" to "FFDC=false".
  

Problem summary

Problem conclusion

Temporary fix

Comments

• Large numbers of FFDC errors with a
  SIConnectionDroppedException are produced.
  Under some circumstances the connection may remain
  open, resulting in locked messages.
  
  One of these FFDCs is expected if the connection has been
  lost, the symptom of this problem is very large numbers
  of the same FFDC error.
  
  Problem Conclusion: The APAR solves the problem by allowing
  the thread to continue, rather than looping producing FFDCs.
  A single FFDC entry will still be generated after this APAR
  has been applied, if the connection is broken again.
  
  This is a duplicate of APAR PK48027.
  

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

  PLAT MSG COM

• Fixed component ID

  620400101

Applicable component levels