IBM Support

IT08780: WEBSPHERE MQ SUITE OPEN SESSION SERVICE AND WEBSPHERE MQ ASYNC RECEIVE ADAPTER RESPOND WITH ZERO BYTE CERTIFICATE.

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • WebSphere MQ Suite Open Session service and Websphere MQ Async
    Receive adapter respond with zero byte certificate when 2-way
    SSL authentication is used.
    
    SSL functions fine when server performs the authentication
    (system cert is used, but no CA cert).
    
    Packet capture shows that after Server Hello is done and server
    send certificate and server requested certificate, client
    (Sterling B2b Integrator) responds with zero byte certificate.
    
    WebSphereMQSuite.log
    [2015-04-06 17:36:41.026] ALL
    <WSMQSession-oxnard:-457609:14c80a65e10:e6f--1093052933>
    ##[DEBUG]## Attempting to open a connection with the following
    values:
    MQEnvironment version_notice=Websphere MQ classes for Java
    v7.5.0.2
    hostname=MyHostName
    port=123
    qManager=MyQue
    channel=SYSTEM.DEF.SVRCONN
    userid=mqadmin
    password provided
    The SSL Paramaters used are listed below
    TrustedCertID=<certid placeholder>
    KeyCertID=<key id placeholder>
    CipherSuite=SSL_RSA_WITH_3DES_EDE_CBC_SHA
    
    [2015-04-06 17:36:41.144] ERROR
    <WSMQSession-oxnard:-457609:14c80a65e10:e6f--1093052933>
    MQException during MQCONN: CC=2 RC=2397
    [2015-04-06 17:36:41.144] ERROR [1428356201144] MQJE001:
    Completion Code '2', Reason '2397'.
    [2015-04-06 17:36:41.144] ERRORDTL
    [1428356201144]com.ibm.mq.MQException: MQJE001: Completion Code
    '2', Reason '2397'.
        at
    com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.
    java:247)
        at
    com.ibm.mq.MQClientManagedConnectionFactoryJ11._createManagedCon
    nection(MQClientManagedConnectionFactoryJ11.java:588)
        at
    com.ibm.mq.MQClientManagedConnectionFactoryJ11.createManagedConn
    ection(MQClientManagedConnectionFactoryJ11.java:630)
        at
    com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnectio
    n.java:107)
        at
    com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimple
    ConnectionManager.java:205)
        at
    com.ibm.mq.MQQueueManagerFactory.obtainBaseMQQueueManager(MQQueu
    eManagerFactory.java:911)
        at
    com.ibm.mq.MQQueueManagerFactory.procure(MQQueueManagerFactory.j
    ava:799)
        at
    com.ibm.mq.MQQueueManagerFactory.constructQueueManager(MQQueueMa
    nagerFactory.java:750)
        at
    com.ibm.mq.MQQueueManagerFactory.createQueueManager(MQQueueManag
    erFactory.java:157)
        at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:681)
        at
    com.sterlingcommerce.woodstock.services.wsmqSuite.WSMQSession.op
    enConnection(WSMQSession.java:313)
        at
    com.sterlingcommerce.woodstock.services.wsmqSuite.WSMQSession.op
    enSession(WSMQSession.java:291)
        at
    com.sterlingcommerce.woodstock.services.wsmqSuite.WSMQImpl.openS
    ession(WSMQImpl.java:121)
        at
    com.sterlingcommerce.woodstock.services.wsmqSuite.WSMQImpl.proce
    ssData(WSMQImpl.java:63)
        at
    com.sterlingcommerce.woodstock.workflow.activity.engine.Activity
    EngineHelper.invokeService(ActivityEngineHelper.java:1818)
        at
    com.sterlingcommerce.woodstock.workflow.activity.engine.Activity
    EngineHelper.nextMainLogic(ActivityEngineHelper.java:631)
        at
    com.sterlingcommerce.woodstock.workflow.activity.engine.Activity
    EngineHelper.next(ActivityEngineHelper.java:362)
        at
    com.sterlingcommerce.woodstock.workflow.queue.WorkFlowQueueListe
    ner.doWork(WorkFlowQueueListener.java:459)
        at
    com.sterlingcommerce.woodstock.workflow.queue.WorkFlowQueueListe
    ner.run(WorkFlowQueueListener.java:240)
        at
    com.sterlingcommerce.woodstock.workflow.queue.WorkFlowQueueListe
    ner.onMessage(WorkFlowQueueListener.java:197)
        at
    com.sterlingcommerce.woodstock.workflow.queue.WorkFlowQueueListe
    ner.onMessage(WorkFlowQueueListener.java:184)
        at
    com.sterlingcommerce.woodstock.workflow.queue.wfTransporter.run(
    wfTransporter.java:444)
        at
    com.sterlingcommerce.woodstock.workflow.queue.BasicExecutor$Work
    er.run(BasicExecutor.java:508)
        at java.lang.Thread.run(Thread.java:804)
    

Local fix

  • STRRTC - 462087
    SB/SB
    Circumvention:NONE
    

Problem summary

  • Users Affected:
    WebSphere MQ Suite users
    
    Problem Description:
    SSL client authentication for WebSphere MQ Suite Open Session
    service and Websphere MQ Async Receive adapter does not work.
    
    Platforms Affected:
    All
    

Problem conclusion

  • Resolution Summary:
    A code fix has been provided.
    
    Delivered in:
    5020500_5
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT08780

  • Reported component name

    STR B2B INTEGRA

  • Reported component ID

    5725D0600

  • Reported release

    525

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2015-05-07

  • Closed date

    2015-05-19

  • Last modified date

    2015-05-26

  • 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

    STR B2B INTEGRA

  • Fixed component ID

    5725D0600

Applicable component levels

  • R525 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS3JSW","label":"IBM Sterling B2B Integrator"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.2.5","Edition":"","Line of Business":{"code":"LOB02","label":"AI Applications"}}]

Document Information

Modified date:
26 May 2015