IBM Support

PI28473: FIX USABILITY DEFECTS IN JMS

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Fix several usability issues that have been found within the JMS
    feature.These include:
    .
    1) Messaging flows should ignore the Bus Name, because there is
    no Bus concept in Websphere Application Server Liberty Profile.
    2) Rectify the jmsMajorVersion and jmsMinorVersion in
    JMS-Connection metadata.
    3) Print high-message threshold in logs when queue's max depth
    have been reached.
    4) User-name must be printed in logs when there is an
    authentication failure.
    5) Remov duplicate CWSID0122I messages in logs when messaging
    engine id is not provided in the server configuration file.
    6) Rename "WebSphere Embedded Queue Connection Factory" to
    "Embedded Messaging" and in the same way for Topic Connection
    factory and Connection Factory
    7) Prevent destination UUID's from being printed in the logs
    when a destination is deleted.
    8) Fix NullPointerException when wasJmsServer-1.0 feature is
    removed.
    9) Remove irrelevant messages like CWSIP0181W and CWSIU0006I
    from appearing in logs when a RECEIVE operation is being
    performed in queue.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server Liberty Profile                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: Fix several usability issues for JMS    *
    *                      feature                                 *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Fix several usability issues:
    
    1) Messaging flows should ignore
    the Bus Name, because there is no Bus concept in Websphere
    Application Server Liberty Profile.
    2) Rectify the
    jmsMajorVersion and jmsMinorVersion in JMS-Connection
    metadata.
    3) Print high-message threshold in logs when queue's
    max depth have been reached.
    4) User-name must be printed in
    logs when there is an authentication failure.
    5) Remov duplicate
    CWSID0122I messages in logs when messaging engine id is not
    provided in the server configuration file.
    6) Rename "WebSphere
    Embedded Queue Connection Factory" to "Embedded Messaging" and
    in the same way for Topic Connection factory and Connection
    Factory
    7) Prevent destination UUID's from being printed in the
    logs when a destination is deleted.
    8) Fix NullPointerException
    when wasJmsServer-1.0 feature is removed.
    9) Remove irrelevant
    messages like CWSIP0181W and CWSIU0006I from appearing in logs
    when a RECEIVE operation is being performed in queue.
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    PI28473

  • Reported component name

    WAS LIBERTY COR

  • Reported component ID

    5725L2900

  • Reported release

    855

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2014-10-28

  • Closed date

    2014-10-29

  • Last modified date

    2014-11-11

  • 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

    WAS LIBERTY COR

  • Fixed component ID

    5725L2900

Applicable component levels

  • R855 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSD28V","label":"WebSphere Application Server Liberty Core"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"855","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 April 2022