[
https://issues.apache.org/activemq/browse/AMQ-1763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=52748#action_52748
]
Mark Gellings commented on AMQ-1763:
------------------------------------
Hey Gary.
Thanks for helping out on this issue. I looked at your code and it looks like
it should be replicating the problem and failing.
Since it isn't, do you think you could try running the code the reporter
attached. I'm thinking if you run the producer once and then the consumer
messages will come through as expected. Then if you stop and run the consumer
a second time the same messages will be redelivered. This forsurely replicates
the problem when using the ActiveMQ NMS framework.
If you could do this that would be great because maybe we are missing something
in the unit test.
I think if you run the reporters producer/consumer and everything works
correctly then it's safe to assume this is an issue with the ActiveMQ NMS
framework.
-Regards
PS Sorry about the previous comments. Looks like auto-reply can be a nuisance.
Especially if you aren't aware of it.
> Acknowledgment of Messages consumed from VirtualTopic consumer queues fails
> ---------------------------------------------------------------------------
>
> Key: AMQ-1763
> URL: https://issues.apache.org/activemq/browse/AMQ-1763
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.1.0
> Environment: Windows XP, Java(TM) SE Runtime Environment (build
> 1.6.0_06-b02)
> Reporter: Konrad Podloucky
> Fix For: 5.4.0
>
> Attachments: test.xml, TestConsumer.java, testPatch.patch,
> TestProducer.java
>
>
> The Message Broker throws an exception each time a client tries to
> acknowledge a message consumed from a VirtualTopic consumer queue:
> ERROR Service - Async error occurred:
> java.lang.IllegalArgumentException: The subscription does not exist:
> ID:seautpc271-1314-1212495185267-0:0:1:1
> java.lang.IllegalArgumentException: The subscription does not exist:
> ID:seautpc271-1314-1212495185267-0:0:1:1
> at
> org.apache.activemq.broker.region.AbstractRegion.acknowledge(AbstractRegion.java:357)
> at
> org.apache.activemq.broker.region.RegionBroker.acknowledge(RegionBroker.java:470)
> at
> org.apache.activemq.broker.TransactionBroker.acknowledge(TransactionBroker.java:194)
> at
> org.apache.activemq.broker.BrokerFilter.acknowledge(BrokerFilter.java:73)
> at
> org.apache.activemq.broker.BrokerFilter.acknowledge(BrokerFilter.java:73)
> at
> org.apache.activemq.broker.MutableBrokerFilter.acknowledge(MutableBrokerFilter.java:84)
> at
> org.apache.activemq.broker.TransportConnection.processMessageAck(TransportConnection.java:443)
> at org.apache.activemq.command.MessageAck.visit(MessageAck.java:196)
> at
> org.apache.activemq.broker.TransportConnection.service(TransportConnection.java:292)
> at
> org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:180)
> at
> org.apache.activemq.transport.TransportFilter.onCommand(TransportFilter.java:68)
> at
> org.apache.activemq.transport.WireFormatNegotiator.onCommand(WireFormatNegotiator.java:143)
> at
> org.apache.activemq.transport.InactivityMonitor.onCommand(InactivityMonitor.java:206)
> at
> org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:84)
> at
> org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:196)
> at
> org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:183)
> at java.lang.Thread.run(Thread.java:619)
> Consequently the message gets re-delivered as soon as the client connects to
> the queue again (and fails again on aknowledgement). Strangely enough the
> subscription mentioned in the exception is visible in the JMX console. I can
> reproduce this error every time I try to consume from VirtualTopic consumer
> queues.
> I have attached the broker configuration (which is rather minimal) and the
> test classes I used to trigger this error.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
