PK97182: FUNCTIONALITY OF 'MESSAGESELECTOR' FOR ACTIVATION SPECIFICATIONS CHANGED TO MEET SPECIFICATION

Fixes are available

APAR status

Closed as program error.

Error description

There are 2 issues here.
1. With WebSphere Application Server v7, once a value for the
'message selector' field is set for an Activation
Specification it cannot be removed.
2. If there is no 'message selector' entry in the Activation
Specification, the value of messageSelector in the MDB's
deployment descriptor is ignored.
Additional Keywords : messageSelector

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  Users of IBM WebSphere Application Server   *
*                  Version 7.0, using WebSphere MQ as a        *
*                  messaging provider                          *
****************************************************************
* PROBLEM DESCRIPTION: The messageSelector field for           *
*                      WebSphere MQ activation specifications  *
*                      cannot be cleared, and MDBs might       *
*                      receive messages that do not match the  *
*                      selection criteria specified in their   *
*                      deployment descriptor                   *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
1. Once a value for the 'message selector' field is set for
   a WebSphere MQ Activation Specification, it cannot be
   removed. After entering a blank value in the field and
   applying the change, the previous value reappears when you
   next view the Activation Specification panel.
2. For a newly created WebSphere MQ activation specification,
   or an activation specification migrated from a listener
   port, the  following entries are seen in the
   SystemOut.log when starting an MDB that specifies a
   message selector in its deployment descriptor:
    J2CA0291I: Application EJB.jar#EJB has an
    <activation-config-property>, messageSelector, for which
     there is no corresponding property on the ActivationSpec
    class jms/<actspec>
    (com.ibm.mq.connector.inbound.ActivationSpecImpl)
    of ResourceAdapter. This property will be ignored. This may
    have undesirable effects.
   The MDB is then delivered messages that do not match its
   message selector.

Problem conclusion

The fix for this APAR ensures that there is always an entry in
the resources.xml file, even if it has a value="", so that the
MDB can override it. The fix also allows the value to be
set back to "".

To correct the configuration of activation specifications
mentioned in J2CA0291I errors, navigate to the activation
specification in the administrative console and click 'OK'
(with the fix for this APAR applied).

The fix for this APAR is currently targeted for inclusion in
fix pack 7.0.0.9.  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
PK97182
Reported component name
PLAT MSG COM
Reported component ID
620800101
Reported release
300
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-09-25
Closed date
2009-11-26
Last modified date
2009-11-26

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
PLAT MSG COM
Fixed component ID
620800101

Applicable component levels

R300 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:
25 October 2021

Tips

PK97182: FUNCTIONALITY OF 'MESSAGESELECTOR' FOR ACTIVATION SPECIFICATIONS CHANGED TO MEET SPECIFICATION

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

R300 PSY

Document Information

Share your feedback

Need support?