[prev in list] [next in list] [prev in thread] [next in thread] 

List:       activemq-dev
Subject:    [jira] Issue Comment Edited: (AMQ-1763) Acknowledgment of Messages
From:       "Mark Gellings (JIRA)" <jira () apache ! org>
Date:       2009-06-30 13:36:07
Message-ID: 1294127777.1246368967168.JavaMail.jira () brutus
[Download RAW message or body]


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

Mark Gellings edited comment on AMQ-1763 at 6/30/09 6:34 AM:
-------------------------------------------------------------

Any reason why this issue can't get resolved in version 5.3?  Virtual Topics are a \
documented feature of ActiveMQ.

http://activemq.apache.org/virtual-destinations.html 

The broker receives the same error with a transactional session on commit.  Here's a \
thread further discussing the problem:

http://www.nabble.com/uses-virtual-topic---and-ClientAcknowledge-to-submit-the-message-occured-probem-ts22486742.html#a24260251


      was (Author: magellings):
    Any reason why this issue can't get resolved in version 5.3?  Virtual Topics are \
a documented feature of ActiveMQ.

http://activemq.apache.org/virtual-destinations.html 
  
> 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, 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.


[prev in list] [next in list] [prev in thread] [next in thread]