You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2019/03/27 16:31:00 UTC
[jira] [Work logged] (ARTEMIS-2286) AMQP to Core Conversion doesn't
map routing type always.
[ https://issues.apache.org/jira/browse/ARTEMIS-2286?focusedWorklogId=219420&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-219420 ]
ASF GitHub Bot logged work on ARTEMIS-2286:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 27/Mar/19 16:30
Start Date: 27/Mar/19 16:30
Worklog Time Spent: 10m
Work Description: michaelandrepearce commented on pull request #2594: ARTEMIS-2286 AMQP to Core Conversion doesn't map routing type always
URL: https://github.com/apache/activemq-artemis/pull/2594
Add test that exhibits the issue when sending AMQP (non JMS) to Artemis that one mapping to Core JMS the destination is not resolving as the RoutingType can be missing.
Add fix
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 219420)
Time Spent: 10m
Remaining Estimate: 0h
> AMQP to Core Conversion doesn't map routing type always.
> --------------------------------------------------------
>
> Key: ARTEMIS-2286
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2286
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Reporter: Michael Andre Pearce
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> This can cause issues where sender is AMQP but consumer is CORE JMS, as the JMSDestination is not either Queue or Topic because the routing type in CoreMessage is null.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)