Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Message-ID: <335895597.1247071447188.JavaMail.jira@brutus>
Date: Wed, 8 Jul 2009 09:44:07 -0700 (PDT)
From: "Gary Tully (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Subject: [jira] Commented: (AMQ-1763) Acknowledgment of Messages consumed
 from VirtualTopic consumer queues fails
In-Reply-To: <1875403644.1212496320332.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/activemq/browse/AMQ-1763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=52743#action_52743 ] 

Gary Tully commented on AMQ-1763:
---------------------------------

mark, i applied ur changes and refactored a bit more to use separate connections for each consumer, but to no avail. the test still works. Cannot do much with this till we get a failing test case. I cannot see any real difference between the test classes from the original reporter and the current test case on trunk.
latest test is in r792220


> 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.