Check for a behavior change on setClientID and createDurableSubscriber methods

This rule flags Java code that calls the following methods because they throw different exceptions in JMS Client 2.0.

• javax.jms.Session.createDurableSubscriber
• javax.jms.TopicSession.createDurableSubscriber
• javax.jms.Connection.setClientID

Although the method signatures did not change, the method implementations throw different exceptions. These behavior changes do not cause compilation errors because the newly thrown exceptions extend the JMSException class. If you want to migrate your existing applications to use the wasJmsClient-2.0 feature, see JMS messaging (wasJmsClient-2.0) behavior changes for more information.

Note: If your application uses IBM MQ Version 8.0, you can revert the behavior change for the setClientID method by setting the SupportMQExtensions property to True. For more information, see SupportMQExtensions property.