IBM Support

PH08934: MQ LISTENER PORT STOPPED WORKING AFTER UPGRADING TO WEBSPHERE V9.0.0.9

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • A JMS Listener port is configured against Websphere MQ queue.
    After upgrading from WebSphere v9.0.0.7 to WebSphere
    v9.0.0.9,MDB fails to consume messages from the MQ queue,
    leading to a buildup of messages. SystemOut.log shows the
    following errors:
    WSVR0501E: Error creating component
    com.ibm.ws.runtime.component.
    CompositionUnitMgrImpl@de90ed4
    com.ibm.ws.exception.RuntimeWarning:
    com.ibm.ws.exception.RuntimeError:
    com.ibm.ws.exception.RuntimeError:
    java.lang.RuntimeException: com.ibm.ws.cdi.CDIRuntimeException:
    com.ibm.ws.cdi.CDIDeploymentRuntimeException:
    com.ibm.ws.cdi.CDIException: Failed to open zip handle
    [ XXX_XXX_EAR ]
    at com.ibm.ws.runtime.component.CompositionUnitMgrImpl.
     startCUList(CompositionUnitMgrImpl.java:1303)
    at com.ibm.ws.runtime.component.CompositionUnitMgrImpl.
     start(CompositionUnitMgrImpl.java:275)
    at com.ibm.ws.runtime.component.ContainerHelper.start
     Components(ContainerHelper.java:540)
    at com.ibm.ws.runtime.component.ContainerImpl.start
     Components(ContainerImpl.java:627)
    at com.ibm.ws.runtime.component.ContainerImpl.start
     (ContainerImpl.java:618)
    at com.ibm.ws.runtime.component.ApplicationServerImpl.
     start(ApplicationServerImpl.java:252)
    at com.ibm.ws.runtime.component.ContainerHelper.start
     Components(ContainerHelper.java:540)
    at com.ibm.ws.runtime.component.ContainerImpl.start
     Components(ContainerImpl.java:627)
    at com.ibm.ws.runtime.component.ContainerImpl.
     start(ContainerImpl.java:618)
    at com.ibm.ws.runtime.component.ServerImpl.
     start(ServerImpl.java:555)
    at com.ibm.ws.runtime.WsServerImpl.bootServerContainer
     (WsServerImpl.java:311)
    at com.ibm.ws.runtime.WsServerImpl.start
     (WsServerImpl.java:224)
    at com.ibm.ws.runtime.WsServerImpl.main
     (WsServerImpl.java:697)
    at com.ibm.ws.runtime.WsServer.main(WsServer.java:59) ...
    Caused by: java.io.FileNotFoundException:
    ZipFile [ /xxx/xxx/xxx/com.ibm.mq.jms.Nojndi.jar ] does not
    exist
    at
    com.ibm.ws.cdi.classic.zipcache.ZipFileHandle.<init>(ZipFileHand
    le.java:70)
    at
    com.ibm.ws.cdi.classic.zipcache.ZipFileHandleStore.register(ZipF
    ileHandleStore.java:66)
    at
    com.ibm.ws.cdi.classic.RuntimeFactory.getZipHandle(RuntimeFactor
    y.java:97)
    at
    com.ibm.ws.cdi.classic.AbstractClassicCDIArchive.<init>(Abstract
    ClassicCDIArchive.java:223)
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server                                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: CDI's file access routines cannot       *
    *                      handle non-existant files               *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    To reduce resource consumption CDI was given a file caching
    subsystem. This subsystem gives the error "Failed to open zip
    handle" if it is asked to open a file which does not exist
    

Problem conclusion

  • A new chcek was added so CDI will log a message on a
    non-existant file rather than try and fail to process it.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 9.0.5.0.  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

    PH08934

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-02-22

  • Closed date

    2019-06-03

  • Last modified date

    2019-06-06

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

    PH08937

Fix information

  • Fixed component name

    WEBS APP SERV N

  • Fixed component ID

    5724H8800

Applicable component levels

  • R900 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":"9.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
02 November 2021