You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Gary Tully (Created) (JIRA)" <ji...@apache.org> on 2012/02/03 14:39:53 UTC
[jira] [Created] (AMQ-3695) Failover using a JDBC Message Store and
Virtual Topic can result in a lost message if queue is empty
Failover using a JDBC Message Store and Virtual Topic can result in a lost message if queue is empty
----------------------------------------------------------------------------------------------------
Key: AMQ-3695
URL: https://issues.apache.org/jira/browse/AMQ-3695
Project: ActiveMQ
Issue Type: Bug
Components: Message Store
Affects Versions: 5.5.1
Environment: jdbc store, virtual topics, failover, master/slave shared store
Reporter: Gary Tully
Assignee: Gary Tully
Fix For: 5.6.0
*Description:*
A consumer connects to the broker and expresses interest in the virtual topic and the queue is created and empty
The consumer then disconnects
The broker is killed and the producer fails over to the next broker
The producer sends the message to the topic
The consumer reconnects to the broker, however it has no message waiting the virtual topic's queue
*Symptom*
The queue for the virtual topic is not automatically created during the failover.
*Work around*
A work around for this issue is to use startup destinations on the slave brokers if the destination is known.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (AMQ-3695) Failover using a JDBC Message Store
and Virtual Topic can result in a lost message if queue is empty
Posted by "Gary Tully (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQ-3695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gary Tully resolved AMQ-3695.
-----------------------------
Resolution: Fixed
fix in: http://svn.apache.org/viewvc?rev=1240162&view=rev
For new queues that match the virtual interceptor prefixes configured, an entry is added to the ack table and the get destinations query unions distinct on ack and messages table. This allows them to be found and loaded on start.
> Failover using a JDBC Message Store and Virtual Topic can result in a lost message if queue is empty
> ----------------------------------------------------------------------------------------------------
>
> Key: AMQ-3695
> URL: https://issues.apache.org/jira/browse/AMQ-3695
> Project: ActiveMQ
> Issue Type: Bug
> Components: Message Store
> Affects Versions: 5.5.1
> Environment: jdbc store, virtual topics, failover, master/slave shared store
> Reporter: Gary Tully
> Assignee: Gary Tully
> Labels: failover, jdbc, masterslave, virtualtopic
> Fix For: 5.6.0
>
>
> *Description:*
> A consumer connects to the broker and expresses interest in the virtual topic and the queue is created and empty
> The consumer then disconnects
> The broker is killed and the producer fails over to the next broker
> The producer sends the message to the topic
> The consumer reconnects to the broker, however it has no message waiting the virtual topic's queue
> *Symptom*
> The queue for the virtual topic is not automatically created during the failover.
> *Work around*
> A work around for this issue is to use startup destinations on the slave brokers if the destination is known.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira