IBM Support

PK83641: CWSIT0039E ENTRIES ARE LOGGED IN THE JVM LOGS OF A SERVER HOSTING A MESSAGING ENGINE

Fixes are available

7.0.0.5: WebSphere Application Server V7.0 Fix Pack 5 for AIX
7.0.0.5: WebSphere Application Server V7.0 Fix Pack 5 for IBM i
7.0.0.5: WebSphere Application Server V7.0 Fix Pack 5 for Windows
7.0.0.5: WebSphere Application Server V7.0 Fix Pack 5 for HP-UX
7.0.0.5: Java SDK 1.6 SR5 Cumulative Fix for WebSphere Application Server
7.0.0.5: WebSphere Application Server V7.0 Fix Pack 5 for Solaris
7.0.0.5: WebSphere Application Server V7.0 Fix Pack 5 for Linux
Java SDK 1.5 SR10 Cumulative Fix for WebSphere Application Server
7.0.0.7: WebSphere Application Server V7.0 Fix Pack 7 for IBM i
7.0.0.7: WebSphere Application Server V7.0 Fix Pack 7 for AIX
7.0.0.7: WebSphere Application Server V7.0 Fix Pack 7 for Windows
7.0.0.7: WebSphere Application Server V7.0 Fix Pack 7 for HP-UX
7.0.0.7: Java SDK 1.6 SR6 Cumulative Fix for WebSphere Application Server
7.0.0.7: WebSphere Application Server V7.0 Fix Pack 7 for Solaris
7.0.0.7: WebSphere Application Server V7.0 Fix Pack 7 for Linux
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for IBM i
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for Windows
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for AIX
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for HP-UX
7.0.0.9: Java SDK 1.6 SR7 Cumulative Fix for WebSphere Application Server
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for Solaris
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for Linux
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for IBM i
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Windows
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for HP-UX
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for AIX
7.0.0.11: Java SDK 1.6 SR7 Cumulative Fix for WebSphere Application Server
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Solaris
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Linux
6.1.0.29: Java SDK 1.5 SR11 Cumulative Fix for WebSphere Application Server
6.1.0.31: Java SDK 1.5 SR11 FP1 Cumulative Fix for WebSphere Application Server
6.1.0.33: Java SDK 1.5 SR12 FP1 Cumulative Fix for WebSphere
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for AIX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for HP-UX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for IBM i
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Linux
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Solaris
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Windows
7.0.0.13: Java SDK 1.6 SR8FP1 Cumulative Fix for WebSphere Application Server
6.1.0.35: Java SDK 1.5 SR12 FP2 Cumulative Fix for WebSphere
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for AIX
7.0.0.15: Java SDK 1.6 SR9 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for HP-UX
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for IBM i
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Linux
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Solaris
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Windows
6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere
7.0.0.17: WebSphere Application Server V7.0 Fix Pack 17
7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
6.1.0.39: Java SDK 1.5 SR12 FP4 Cumulative Fix for WebSphere Application Server
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The following error message is logged in the JVM logs of an
    application server hosting a messaging engine:
    
    CWSIT0039E: An internal error occurred. There is a connection
    protocol error while communicating with messaging
    engine <ME_NAME>, the received messagetype is null but the
    expected message type is ME_CONNECT_REPLY.
    
    An FFDC report containing the following details is also logged:
    Exception = java.lang.IllegalStateException
    Source = com.ibm.ws.sib.mfp.impl.JsMsgObject.encode
    probeid = jmo550
    Stack Dump = java.lang.IllegalStateException:
    UniqueLinkObject not seen on handshake
    at com.ibm.ws.sib.mfp.impl.SchemaManager.sendSchemas(
                                           SchemaManager.java:223)
    at com.ibm.ws.sib.mfp.impl.JsMsgObject.
                                      encode(JsMsgObject.java:596)
    at com.ibm.ws.sib.mfp.impl.TrmFirstContactMessageImpl.
                       encode(TrmFirstContactMessageImpl.java:260)
    at com.ibm.ws.sib.trm.contact.MeConnectHandler.
                                 connect(MeConnectHandler.java:90)
    at com.ibm.ws.sib.comms.server.mesupport.MEConnectionImpl.
                                connect(MEConnectionImpl.java:345)
    at com.ibm.ws.sib.trm.contact.Connect.contact(Connect.java:119)
    at com.ibm.ws.sib.trm.contact.Neighbourhood.
                                      _scan(Neighbourhood.java:375)
    at sun.reflect.NativeMethodAccessorImpl.
                                             invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.
                           invoke(NativeMethodAccessorImpl.java:85)
    at sun.reflect.NativeMethodAccessorImpl.
                           invoke(NativeMethodAccessorImpl.java:58)
    at sun.reflect.DelegatingMethodAccessorImpl.
           invoke(DelegatingMethodAccessorImpl.java(Compiled Code))
    at java.lang.reflect.Method.invoke(Method.java(Compiled Code))
    at com.ibm.ws.sib.trm.contact.Neighbourhood.
                                     direct(Neighbourhood.java:755)
    at com.ibm.ws.sib.trm.general.ServiceThread.
                                         run(ServiceThread.java:79)
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  Users of the default messaging provider for *
    *                  IBM WebSphere Application Server Version    *
    *                  6.0, Version 6.1 or Version 7.0             *
    ****************************************************************
    * PROBLEM DESCRIPTION: A FFDC report on a system contains      *
    *                      the following exception:                *
    *                      java.lang.IllegalStateException:        *
    *                      UniqueLinkObject not seen on handshake  *
    *                                                              *
    *                      This exception can occur on             *
    *                      server (or client application)          *
    *                      connecting to the messaging engine      *
    *                      over a network, or on a server          *
    *                      hosting a messaging engine in a bus     *
    *                      with multiple members.                  *
    *                                                              *
    *                      In addition the following error might   *
    *                      seen in the JMV logs of a process       *
    *                      running a messaging engine:             *
    *                                                              *
    *                      CWSIT0039E: An internal error           *
    *                      occurred. There is a connection         *
    *                      protocol error while communicating      *
    *                      with messaging engine myME in bus       *
    *                      myBus, the received message type is     *
    *                      null but the expected message type is   *
    *                      ME_CONNECT_REPLY.                       *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The IllegalStateException exception occurs due to a problem
    with network connection re-use logic within the JFAP component
    of the service integration bus.
    This code holds network connections open for re-use for a
    short period of time before they are disconnected. This allows
    a new messaging engine to messaging engine, or client to
    messaging engine, connection to be established within
    that time period without the overhead of creating a new
    network connection.
    
    There was a problem with the re-use code that caused the
    creation of thew connection to fail, because some required
    state associated with the connection had been discarded.
    This caused the code requesting the connection to be thrown an
    exception, and need to make an additional attempt to establish
    the connection.
    

Problem conclusion

  • The fix for this APAR prevents the required state from being
    discarded until after the connection has been removed from the
    pool of JFAP network connections eligible for re-use.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 6.0.2.37, 6.1.0.27 and 7.0.0.7.  Please refer to the
    Recommended Updates page for delivery information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

Comments

APAR Information

  • APAR number

    PK83641

  • Reported component name

    PLAT MSG COM

  • Reported component ID

    620400101

  • Reported release

    100

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-03-30

  • Closed date

    2009-04-20

  • Last modified date

    2009-05-06

  • 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

  • R100 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
29 December 2021