[NIFI-3672] Older versions of IBM MQ allowed integer value to be set as String

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 1.1.1
• Fix Version/s: 1.8.0
• Component/s: Extensions
• Labels: beginner jms third-party
• Assignee: Michael W Moser
• Reporter: Andy LoPresto
• Created: 05/Apr/17 04:23
• Updated: 02/Oct/18 13:45
• Resolved: 02/Oct/18 13:45

Description

As reported in this Stack Overflow question, the PublishJMS processor was failing to connect to an IBM MQ JMS server with the exception com.ibm.msg.client.jms.DetailedMessageFormatException: JMSCC0051: The property 'JMS_IBM_MsgType' should be set using type 'java.lang.Integer', not 'java.lang.String'. As noted in the answer, this is a known IBM issue IT02814 in which older (pre-7.0) versions allowed integer properties to be set as a java.lang.String but new versions require it to be a java.lang.Integer. The property descriptor should be changed to validate an integer value and return it with the correct type when setting the configuration.

Issue Links

• links to: GitHub Pull Request #2949