IBM Support

IT43740: MQ Bridge to SalesForce reports NullPointerExceptions when reconnecting to Salesforce

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

  • Following a temporary loss of network connectivity between the
    IBM MQ Bridge to Salesforce and the Salesforce server, a
    NullPointerException is observed in the Salesforce log, of the
    form:
    
    2023-05-19 07:26:28.006 PDT 36 publishing on topic
    /sf/event/myEvent__e with message len 109
    [HttpClient@1491670877-36] INFO
    org.cometd.bayeux.client.ClientSession - Exception while
    invoking listener com.ibm.mq.runmqsfb.SFMessageListener@1a34267c
    java.lang.NullPointerException
            at
    com.ibm.mq.runmqsfb.SFMessageListener.onMessage(SFMessageListene
    r.java:156)
            at
    org.cometd.common.AbstractClientSession$AbstractSessionChannel.n
    otifyOnMessage(AbstractClientSession.java:602)
            at
    org.cometd.common.AbstractClientSession$AbstractSessionChannel.n
    otifyMessageListeners(AbstractClientSession.java:593)
            at
    org.cometd.common.AbstractClientSession.notifyListeners(Abstract
    ClientSession.java:299)
            at
    org.cometd.common.AbstractClientSession.receive(AbstractClientSe
    ssion.java:265)
            at
    org.cometd.client.BayeuxClient.processMessage(BayeuxClient.java:
    818)
            at
    org.cometd.client.BayeuxClient.processMessages(BayeuxClient.java
    :614)
            at
    org.cometd.client.BayeuxClient.access$3000(BayeuxClient.java:100
    )
            at
    org.cometd.client.BayeuxClient$MessageTransportListener.onMessag
    es(BayeuxClient.java:1191)
            at
    org.cometd.client.transport.LongPollingTransport$2.onComplete(Lo
    ngPollingTransport.java:224)
            at
    org.eclipse.jetty.client.ResponseNotifier.notifyComplete(Respons
    eNotifier.java:193)
            ... ... ...
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Users of the IBM MQ Bridge to SalesForce.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    When the IBM MQ Bridge to Salesforce is closing itself down,
    such as in the scenario where it is cleaning up its internal
    state following a network disconnection event between itself and
    the Salesforce server, prior to reconnecting, if the Bridge is
    busy processing received messages from either MQ (if publishing
    to Salesforce) or from Salesforce (to publish to MQ), various
    NullPointerExceptions may be observed in the Salesforce log,
    such as:
    
            2023-05-18 14:52:11.689 PDT [AMQSF037E] Error:
    Publication to Salesforce on topic
    '/sf/mqtosfb/event/fromMQPlatformEvent__e' failed with status
    500 and reason
            [AMQSF037E] Error: Publication to Salesforce on topic
    'fromMQPlatformEvent__e' failed with status 500 and reason
            null
            2023-05-18 14:52:11.689 PDT 51 Removing listener for MQ
    events
            Done.
            Exception in thread "main"
    java.lang.NullPointerException
                    at
    com.ibm.mq.runmqsfb.BridgeMain.cleanupForRetry(BridgeMain.java:5
    98)
                    at
    com.ibm.mq.runmqsfb.BridgeMain.realMain(BridgeMain.java:243)
                    at
    com.ibm.mq.runmqsfb.BridgeMain.main(BridgeMain.java:75)
    

Problem conclusion

  • The shutdown order for the various MQ Bridge to SalesForce
    components has been updated to ensure that if messages are still
    being processed from either MQ or Salesforce, components which
    those elements depend on are not closed off before the
    processing of the messages completes.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v9.1 LTS   9.1.0.20
    v9.2 LTS   9.2.0.20
    v9.3 LTS   9.3.0.10
    v9.x CD    9.3.4
    
    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

    IT43740

  • Reported component name

    IBM MQ BASE MP

  • Reported component ID

    5724H7271

  • Reported release

    910

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2023-05-12

  • Closed date

    2023-07-19

  • Last modified date

    2023-07-19

  • 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

    IBM MQ BASE MP

  • Fixed component ID

    5724H7271

Applicable component levels

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"910","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
20 July 2023