PK73113: JMSLISTENERMDB CLASS DISPLAYS UNNECESSARY WARNING MESSAGE WHEN APPLICATION MODULE CONTAINS NO JAX-RPC ENDPOINTS

Fixes are available

APAR status

Closed as program error.

Error description

The JAX-WS JMSListenerMDB class blindly initializes an
instance of the JAX-RPC JMSListenerMDB class, regardless of
whether there are actually  any JAX-RPC endpoints in the
module or not.
Because of this, you'll see the following warning message when
the first request is sent to the MDB class if the module
doesn't contain any JAX-RPC endpoints:

[10/1/08 10:36:35:796 CDT] 0000001e JMSListenerMD W
WSWS4123E: Could not locate the Endpoint Manager MBean for JMS
Listener.

We should eliminate this warning message in this situation by
changing the JAX-WS JMSListenerMDB class such that it creates
and initializes an instance of the JAX-RPC MDB class if and
only if it reaches a situation where it needs to delegate to
it (that is, if  an incoming request contains a port component
that is not a known JAX-WS  port component).

The presence of this warning will confuse users into thinking
that something is wrong when in fact everything is working fine.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  WebSphere Application Server V7.0 users of  *
*                  SOAP/JMS with JAX-WS web service endpoints  *
****************************************************************
* PROBLEM DESCRIPTION: The Web services SOAP/JMS component     *
*                      may log an unnecessary warning          *
*                      message if the application module       *
*                      (EJB jar) contains JAX-WS endpoints     *
*                      but contains no JAX-RPC endpoints.      *
*                      The warning message will look           *
*                      something like this:                    *
*                      [10/1/08 10:36:35:796 CDT] 0000001e     *
*                      JMSListenerMD W WSWS4123E: Could not    *
*                      locate the Endpoint Manager MBean for   *
*                      JMS Listener.                           *
*                                                              *
*                      This message can be safely ignored.     *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
In some situations, if your application module doesn't contain
any JAX-RPC endpoints, message WSWS4123E might be
inadvertently logged as a warning message.

Problem conclusion

We will eliminate this warning message in this situation by
changing the JAX-WS JMSListenerMDB class such that it creates
and initializes an instance of the JAX-RPC MDB class if and
only if it reaches a situation where it needs to delegate to
it.
The fix for this APAR is currently targeted for inclusion in
fixpack 7.0.01.  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
PK73113
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
2008-10-01
Closed date
2008-10-28
Last modified date
2008-10-28

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

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
23 October 2021

Tips

PK73113: JMSLISTENERMDB CLASS DISPLAYS UNNECESSARY WARNING MESSAGE WHEN APPLICATION MODULE CONTAINS NO JAX-RPC ENDPOINTS

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

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

Fixed component ID

Applicable component levels

R700 PSY

Document Information

Share your feedback

Need support?