[
https://issues.apache.org/jira/browse/NIFI-1000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14997392#comment-14997392
]
Oleg Zhurakousky commented on NIFI-1000:
----------------------------------------
Indeed it was a _toString()_ issue. I've fixed it with
{code}
if (message.getJMSDestination() != null) {
String destinationName;
if (message.getJMSDestination() instanceof Queue) {
destinationName = ((Queue)
message.getJMSDestination()).getQueueName();
} else {
destinationName = ((Topic)
message.getJMSDestination()).getTopicName();
}
attributes.put(ATTRIBUTE_PREFIX + JMS_DESTINATION, destinationName);
}
{code}
In the process of re-enabling all the JMS tests that were @Ignore as well as
adding new.
> GetJMSQueue adds wrong value for jms.JMSDestination attribute
> -------------------------------------------------------------
>
> Key: NIFI-1000
> URL: https://issues.apache.org/jira/browse/NIFI-1000
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Reporter: Mark Payne
> Assignee: Oleg Zhurakousky
> Labels: newbie
> Fix For: 0.4.0
>
>
> I used LogAttribute to view the output of messages pulled via GetJMSQueue.
> The Destination's name was the wrong value:
> Key: 'jms.JMSDestination'
> Value: 'org.apache.qpid.amqp_1_0.jms.impl.QueueImpl@1a5bf541'
> It appears that the attribute is being set to the toString() of the
> destination, rather than obtaining the actual name
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
