activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ARTEMIS-1576) Anonymous producer with AMQP auto-creates address with wrong routing-type
Date Thu, 11 Jan 2018 15:40:00 GMT

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

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

Commit efec2d3464ef57c50c1104c7c980d2511a3858ee in activemq-artemis's branch refs/heads/master
from [~tabish121]
[ https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;h=efec2d3 ]

ARTEMIS-1576 Fix test that was broken with changes on this issue

The test is using the wrong indices for the destinations it uses so they
don't match the one's created in the test support class.  Because the
code is now using the default routing type the test fails when it tries
to send a message on a JMS Queue when the auto created address default
to the multicast routing type.

> Anonymous producer with AMQP auto-creates address with wrong routing-type
> -------------------------------------------------------------------------
>
>                 Key: ARTEMIS-1576
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-1576
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>          Components: AMQP
>    Affects Versions: 2.4.0
>            Reporter: Johan Stenberg
>            Assignee: Justin Bertram
>             Fix For: 2.5.0
>
>         Attachments: ArtemisTest.java, pom.xml
>
>
> When publishing a message to an autocreated multicast address where no consumer is subscribed
to yet, an anycast address is created. Resulting in "Address XYZ is not configured for topic
support"
> I tested this with the latest QPID JMS Client 0.2.8 and the latest Artemis 2.5.0-SNAPSHOT.
> I attached a test class that reproduces the issue.
> {noformat}
> Exception in thread "main" javax.jms.JMSRuntimeException: Address topics.myTopic is not
configured for topic support [condition = amqp:illegal-state]
> 	at org.apache.qpid.jms.exceptions.JmsExceptionSupport.createRuntimeException(JmsExceptionSupport.java:207)
> 	at org.apache.qpid.jms.JmsContext.createConsumer(JmsContext.java:314)
> 	at ArtemisTest.main(ArtemisTest.java:93)
> Caused by: javax.jms.JMSException: Address topics.myTopic is not configured for topic
support [condition = amqp:illegal-state]
> 	at org.apache.qpid.jms.provider.amqp.AmqpSupport.convertToException(AmqpSupport.java:164)
> 	at org.apache.qpid.jms.provider.amqp.AmqpSupport.convertToException(AmqpSupport.java:117)
> 	at org.apache.qpid.jms.provider.amqp.builders.AmqpResourceBuilder.handleClosed(AmqpResourceBuilder.java:185)
> 	at org.apache.qpid.jms.provider.amqp.builders.AmqpResourceBuilder.processRemoteClose(AmqpResourceBuilder.java:129)
> 	at org.apache.qpid.jms.provider.amqp.AmqpProvider.processUpdates(AmqpProvider.java:906)
> 	at org.apache.qpid.jms.provider.amqp.AmqpProvider.access$1800(AmqpProvider.java:102)
> 	at org.apache.qpid.jms.provider.amqp.AmqpProvider$17.run(AmqpProvider.java:792)
> 	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> 	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> 	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
> 	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
> 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> 	at java.lang.Thread.run(Thread.java:748)
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message