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 subversion and git services (Jira)" <ji...@apache.org> on 2019/10/14 18:09:00 UTC

[jira] [Commented] (ARTEMIS-2519) ActiveMQUnexpectedRoutingTypeForAddress uses wrong enum type

    [ https://issues.apache.org/jira/browse/ARTEMIS-2519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16951210#comment-16951210 ] 

ASF subversion and git services commented on ARTEMIS-2519:
----------------------------------------------------------

Commit a74036361d51c2c2f77063a0c0fa00523ed082a0 in activemq-artemis's branch refs/heads/master from Christopher L. Shannon (cshannon)
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=a740363 ]

ARTEMIS-2519: Use proper enum type inside ActiveMQUnexpectedRoutingTypeForAddress


> ActiveMQUnexpectedRoutingTypeForAddress uses wrong enum type
> ------------------------------------------------------------
>
>                 Key: ARTEMIS-2519
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-2519
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 2.10.1
>            Reporter: Christopher L. Shannon
>            Assignee: Christopher L. Shannon
>            Priority: Minor
>             Fix For: 2.11.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> I was browsing the ActiveMQException types to see what was available to be used for some custom processing I'm doing in a plugin and I noticed that the exception type ActiveMQUnexpectedRoutingTypeForAddress uses the wrong enum type.  It currently is setup to use ActiveMQExceptionType.MAX_CONSUMER_LIMIT_EXCEEDED but this should be ActiveMQExceptionType.UNEXPECTED_ROUTING_TYPE_FOR_ADDRESS.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)