IBM Support

IV36662: ASSERTION ERROR THROWN WHEN ATTEMPTING TO CONNECT TO MQ FROM A JAVA CLIENT OVER SSL

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • An attempt to make an SSL secured connection to a queue manager
    from a v7.1 or later WebSphere MQ Classes for Java or Classes
    for JMS client, with assertions also enabled in the client JVM,
    fails with the error:
    
    Exception in thread "main" java.lang.AssertionError
    at
    com.ibm.mq.jmqi.internal.CipherSpec.<init>(CipherSpec.java:48)
    at
    com.ibm.mq.jmqi.JmqiUtils.toCipherSuite(JmqiUtils.java:320)
    at
    com.ibm.mq.jmqi.remote.impl.RemoteTCPConnection.parseCipherSpec(
    RemoteTCPConnection.java:1928)
    at
    com.ibm.mq.jmqi.remote.impl.RemoteTCPConnection.makeSocketSecure
    (RemoteTCPConnection.java:1785)
    at
    com.ibm.mq.jmqi.remote.impl.RemoteTCPConnection.connnectUsingLoc
    alAddress(RemoteTCPConnection.java:778)
    at
    com.ibm.mq.jmqi.remote.impl.RemoteTCPConnection.protocolConnect(
    RemoteTCPConnection.java:1092)
    at
    com.ibm.mq.jmqi.remote.impl.RemoteConnection.connect(RemoteConne
    ction.java:682)
    at
    com.ibm.mq.jmqi.remote.impl.RemoteConnectionSpecification.getSes
    sionFromNewConnection(RemoteConnectionSpecification.java:347)
    at
    com.ibm.mq.jmqi.remote.impl.RemoteConnectionSpecification.getSes
    sion(RemoteConnectionSpecification.java:259)
    at
    com.ibm.mq.jmqi.remote.impl.RemoteConnectionPool.getSession(Remo
    teConnectionPool.java:144)
    at
    com.ibm.mq.jmqi.remote.api.RemoteFAP.jmqiConnect(RemoteFAP.java:
    1491)
    at
    com.ibm.mq.jmqi.remote.api.RemoteFAP.jmqiConnect(RemoteFAP.java:
    1144)
    at
    com.ibm.msg.client.wmq.internal.WMQConnection.<init>
    (WMQConnection.java:337)
    at
    com.ibm.msg.client.wmq.factories.WMQConnectionFactory.createV7Pr
    oviderConnection(WMQConnectionFactory.java:6772)
    at
    com.ibm.msg.client.wmq.factories.WMQConnectionFactory.createProv
    iderConnection(WMQConnectionFactory.java:6151)
    at
    com.ibm.msg.client.jms.admin.JmsConnectionFactoryImpl.createConn
    ection(JmsConnectionFactoryImpl.java:280)
    at
    com.ibm.mq.jms.MQConnectionFactory.createCommonConnection(MQConn
    ectionFactory.java:6138)
    at
    com.ibm.mq.jms.MQConnectionFactory.createConnection(MQConnection
    Factory.java:6167)
    
    
    
    If assertions are not enabled, the connection is successful.
    

Local fix

  • Modify your scripts or code to remove the parameter which causes
    assertion to be enforced.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This issue affects users of the WebSphere MQ classes for JMS
    and WebSphere MQ classes for Java, including:
    
    - The WebSphere MQ V7.1/V7.5 classes for JMS.
    - The WebSphere MQ V7.1/V7.5 classes for Java.
    - The WebSphere MQ V7.1/V7.5 Resource Adapter.
    - The WebSphere Application Server V8.5 WebSphere MQ messaging
    provider.
    - The WebSphere Application Server V6.1 WebSphere MQ messaging
    provider who have configured the WebSphere variable
    MQ_INSTALL_ROOT to point to a WebSphere MQ V7.1/V7.5
    installation.
    
    who are making SSL connection to a queue manager while
    assertions are enabled in the JVM.
    
    Platforms affected:
    All Distributed (iSeries, all Unix and Windows) +Java
    ****************************************************************
    PROBLEM SUMMARY:
    An assertion in the client code failed when some internal data
    was not passed as expected. This data was not relevant to the
    successful connection, so this issue was not seen if assertions
    were not enabled.
    

Problem conclusion

  • The internal data is now passed as expected, and SSL connections
    complete successfully irrespective of whether assertions are
    enabled.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
                       v7.1
    Platform           Fix Pack 7.1.0.3
    --------           --------------------
    Windows            7.1.0.3
    AIX                7.1.0.3
    HP-UX (Itanium)    7.1.0.3
    Solaris (SPARC)    7.1.0.3
    Solaris (x86-64)   7.1.0.3
    iSeries            7.1.0.3
    Linux (x86)        7.1.0.3
    Linux (x86-64)     7.1.0.3
    Linux (zSeries)    7.1.0.3
    Linux (Power)      7.1.0.3
    
    Platform           v7.5
    --------           --------------------
    Multiplatforms     7.5.0.2
    
    The latest available maintenance can be obtained from
    'WebSphere MQ Recommended Fixes'
    http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037
    
    If the maintenance level is not yet available information on
    its planned availability can be found in 'WebSphere MQ
    Planned Maintenance Release Dates'
    http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309
    ---------------------------------------------------------------
    

Temporary fix

Comments

APAR Information

  • APAR number

    IV36662

  • Reported component name

    WMQ AIX V7

  • Reported component ID

    5724H7221

  • Reported release

    710

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-02-12

  • Closed date

    2013-03-07

  • Last modified date

    2013-05-13

  • 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

    WMQ AIX V7

  • Fixed component ID

    5724H7221

Applicable component levels

  • R710 PSY

       UP

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCPQ63","label":"APAR \/ Maintenance"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"710","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
13 May 2013