Check for a behavior change for message priority and the NoLocal attribute

This rule flags behavior changes for the wmqJmsClient-2.0 feature that affect message priority and the NoLocal attribute. If your application does not use the wmqJmsClient-2.0 feature, these results can be ignored. If you want to use the previous behavior, set the com.ibm.mq.jms.SupportMQExtensions property to true. This rule flags references to the following items:

The setPriority(-1) method is flagged because the value of -1 is no longer valid in Java Message Service (JMS) 2.0. In prior versions of JMS, messages used a value of -1 to indicate that a queue's default priority is used. If the value of the int parameter cannot be determined, the method reference is flagged. Examine the flagged references to determine whether this behavior change affects the application.

The NOLOCAL constant and methods that take a boolean noLocal parameter with a value of true are flagged because when this attribute is enabled in JMS 2.0 a consumer cannot receive messages that are published by the same client ID. In prior versions of JMS, this attribute was set on a subscriber to prevent the subscriber from receiving messages that are published by its own connection. If the value of the boolean noLocal parameter cannot be determined, the method reference is flagged. Examine the flagged references to determine whether this behavior change affects the application.

For more information, see the following resource: