activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bruce Snyder (JIRA)" <>
Subject [jira] Updated: (AMQ-968) Store and Forward reconnect failures
Date Fri, 20 Nov 2009 21:07:52 GMT


Bruce Snyder updated AMQ-968:

    Fix Version/s:     (was: AGING_TO_DIE)

> Store and Forward reconnect failures
> ------------------------------------
>                 Key: AMQ-968
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 4.0.2
>         Environment: All
>            Reporter: Andy Piper
>             Fix For: NEED_REVIEWED
>         Attachments:
> For the AMQ reconnection issue, I think it is caused by client can not stop the broker
correctly after server broker is stopped. 
> Attached zip is the test case, it is an IDEA prj, to compile or run it the incubator-activemq-4.0.jar
(download from
) should be involved. In the prj, I added two run configurations: Client, Sever to try all
kinds of connection scenarios below:
> 1. Start client, then start server
> 2. Start server, then start client
> 3. Restart client
> 4. Restart server
> 5. Stop server, then stop client, after that restart server again, then restart client
> All scenarios will be successful if using the run configurations in IDEA, but if we run
the server and client in DOS command line, we will find the #5 is failed. 
> Here is the reason, if the server broker is stopped, the client can not be stopped using
CTL + C, and the interrupt signal is always only captured by the client broker rather than
its JVM. In this time, if we restart the server, no any messages can be received again. But
the messages in client can not be lost, after killing the client and restarting it, the messages
can be still sent to server. 
> So to the scenario in Domain Log, the managed server must be killed by kill-9 shell and
can not be stopped by shutdown.bat (sh) script.
> Uuuuuunfortunately, the scenario #4 is still failed in Domain Log though the codes are
same with above test case's (it IS successful in the test case). I can not get the reason
after I struggled for it the whole day :(. I am not sure if the AMQ network connector is impacted
in Tomcat runtime env.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message