activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "zachary.zhang (JIRA)" <>
Subject [jira] [Commented] (AMQ-4619) lose messages in Shared File System Master/Slave while swich master to slave quickly and many times
Date Tue, 09 Jul 2013 01:26:47 GMT


zachary.zhang commented on AMQ-4619:

In our scenario, there are many consumers to receive messages,if we send duplicate messages
 or losing messages,there isn't a good way to make consumers to know which message is duplicate
or losing.
I noticed there is a rollback methed in session.I plan to use it when producer throw exception,then
resend message ,so the consumer can receive messages perfectly neither more or less. However,
after I tested, the rollback methed can't destroy the message ,it worked not  as JDBC rollback.
Is there something wrong in this solution? 
Thanks for your help.
> lose messages in  Shared File System Master/Slave while swich master to slave quickly
and many times
> ----------------------------------------------------------------------------------------------------
>                 Key: AMQ-4619
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: JMS client, Message Store
>    Affects Versions: 5.8.0
>         Environment: pc(computer), windows 7(os), Shared File System Master/Slave
>            Reporter: zachary.zhang
>              Labels: security
>             Fix For: 5.x
>   Original Estimate: 72h
>  Remaining Estimate: 72h
>  There are two activemq instance in my pc, they are in  Shared File System Master/Slave
with kahaDB model. 
> 1 set up the consumer listener and  receive message use failover protocol .
> 2 set up the producer to send message use failover protocol. the message total is 6000.
> 3 close the master actviemq , so the slave can replace the master to work.
> repeat the step 3 many times (more than 5) and quickly.
> result:
> 1 the producer will throw exception several times:
> javax.jms.TransactionRolledBackException: Transaction completion in doubt due to failover.
Forcing rollback of TX:ID:wcmis175-55198-1372489851858-1:1:643
>                 at org.apache.activemq.state.ConnectionStateTracker.restoreTransactions(
>                 at org.apache.activemq.state.ConnectionStateTracker.restore(
>                 at org.apache.activemq.transport.failover.FailoverTransport.restoreTransport(
>                 at org.apache.activemq.transport.failover.FailoverTransport.doReconnect(
>                 at org.apache.activemq.transport.failover.FailoverTransport$2.iterate(
>                 at org.apache.activemq.thread.PooledTaskRunner.runTask(
>                 at org.apache.activemq.thread.PooledTaskRunner$
>                 at java.util.concurrent.ThreadPoolExecutor.runWorker(
>                 at java.util.concurrent.ThreadPoolExecutor$
>                 at
> 2 sometimes it will lose messages in consumer side (for example producer send 6000 messages
,throw 8 exceptions , the consumer will receive 5998 messages).I don't know where the lost
messages going.
> So ,I think this bug is dangerous if it was really exsit. Sometimes we must use failover
switch the master and slave,and we don't want to face losing messages.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message