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

["Michael Moser (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/NIFI-3672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Moser updated NIFI-3672:
--------------------------------
    Status: Patch Available  (was: Open)

> Older versions of IBM MQ allowed integer value to be set as String
> ------------------------------------------------------------------
>
>                 Key: NIFI-3672
>                 URL: https://issues.apache.org/jira/browse/NIFI-3672
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Extensions
>    Affects Versions: 1.1.1
>            Reporter: Andy LoPresto
>            Assignee: Michael Moser
>            Priority: Minor
>              Labels: beginner, jms, third-party
>
> As reported in this [Stack Overflow question|https://stackoverflow.com/questions/43213416/publishjms-processor-failing-for-writing-message-to-ibm-websphere-mq], 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|https://www-01.ibm.com/support/docview.wss?uid=swg1IT02814] 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. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)