IBM Support

PM73349: USING ADMIN AGENT CONSOLE TO CREATE A JMS MQ QUEUE: 'NO WMQQUEUEDEFINER MBEAN FOUND' ERROR OCCURS

Fixes are available

7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
8.5.0.2: WebSphere Application Server V8.5 Fix Pack 2
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
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
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
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

  • When client uses the WSAS AdminAgent console to define a new
    MQ queue, the following error is received:
    The WMQQueueDefiner MBean has encountered an error
    No WMQQueueDefiner MBean found!
    .
    The AdminAgent SystemOut.log references a ffdc entry for the
    MQ queue definition operation:
    .
    com.ibm.ws.console.resources.jms.mqseries.MQQueueConfigDetailCon
    troller.setupFormBeanForEditAction
    .
    The ffdc log contains error stack:
    [9/12/12 15:12:40:145 EDT]     FFDC
    Exception:java.lang.NumberFormatException
    SourceId:com.ibm.ws.console.resources.jms.mqseries.MQQueueConfig
    DetailCo
    ntroller.setupFormBeanForEditAction ProbeId:95
    Reporter:com.ibm.ws.console.resources.jms.mqseries.MQQueueConfig
    DetailCo
    ntroller@57e257e2
    java.lang.NumberFormatException: null
    at java.lang.Integer.parseInt(Integer.java:428)
    at java.lang.Integer.parseInt(Integer.java:510)
    at
    com.ibm.ws.console.resources.jms.mqseries.MQQueueConfigDetailCon
    troller.
    setupFormBeanForEditAction(MQQueueConfigDetailController.java:86
    )
    com.ibm.ws.console.resources.jms.mqseries.MQJMSResourceDetailCon
    troller.
    perform(MQJMSResourceDetailController.java:109)
    at
    org.apache.struts.tiles.TilesRequestProcessor.processTilesDefini
    tion(Unknown Source)
    at
    org.apache.struts.tiles.TilesRequestProcessor.processForwardConf
    ig(Unknown Source)
    at
    com.ibm.isclite.container.controller.InformationController.proce
    ForwardConfig(InformationController.java:217)
    at org.apache.struts.action.RequestProcessor.process(Unknown
    Source)
    at org.apache.struts.action.ActionServlet.process(Unknown
    Source)
    at org.apache.struts.action.ActionServlet.doGet(Unknown Source)
    ___
    The following query: AdminServiceI.queryNames Entry
    WebSphere:type=WMQQueueDefiner,node=ttnwasdev3Node01,process
    =adminagent
    cannot find MBean. The MBean does not run on the Admin Agent ;
    the request must be targeted at the registered managednode /
    Application Server
    

Local fix

  • Define the MQ queue using the Base Application Server Admin
    Console rather than the Admin Agent console
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server using 'MQ Config' when creating WMQ  *
    *                  queues                                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: Attempt to use MBean on adminagent      *
    *                      when one doesn't exist.                 *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When creating a WebSphere MQ queue definition in the admin
    console, it is possible to select 'MQ Config' once the queue
    has been made, and subsequently connect to the MQ queue
    manager to alter the MQ settings for the queue which has been
    defined.
    If an attempt is made to use this function when running within
    the Admin Agent, the attempt will fail as it won't be able to
    find the WMQQueueDefiner MBean which handles this function.
    

Problem conclusion

  • The code has been altered to target a request to the
    WMQQueueDefiner MBean to the node which is being configured
    when the Admin Agent is being used, ensuring that the MBean
    will be available for use.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 7.0.0.27, 8.0.0.6, and 8.5.0.2.  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

    PM73349

  • Reported component name

    WEBSPHERE APP S

  • Reported component ID

    5724J0800

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-09-20

  • Closed date

    2012-09-28

  • Last modified date

    2012-11-27

  • 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

    WEBSPHERE APP S

  • Fixed component ID

    5724J0800

Applicable component levels

  • R700 PSY

       UP

  • R800 PSY

       UP

  • R850 PSY

       UP



Document information

More support for: WebSphere Application Server
General

Software version: 7.0

Reference #: PM73349

Modified date: 27 November 2012