[jboss-jira] [JBoss JIRA] (AS7-3354) HornetQ backup server won't start when live server is killed

[Miroslav Novak (JIRA)]

     [ https://issues.jboss.org/browse/AS7-3354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Miroslav Novak updated AS7-3354:
--------------------------------

    Attachment: console-log-serverB.txt
                console-log-serverA.txt

    
> HornetQ backup server won't start when live server is killed
> ------------------------------------------------------------
>
>                 Key: AS7-3354
>                 URL: https://issues.jboss.org/browse/AS7-3354
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: JMS
>    Affects Versions: 7.1.0.CR1
>            Reporter: Miroslav Novak
>            Assignee: Clebert Suconic
>             Fix For: 7.1.0.Final
>
>         Attachments: console-log-serverA.txt, console-log-serverB.txt, reproducer.zip
>
>
> Test scenario:
> 1. Start two AS7/EAP6 servers in (hornetq) cluster with HornetQ in colocated topology - server A contains backup for server B and server B contains backup for server A 
> 2. Kill AS7/EAP6 server A using "kill -9 ..." 
> I see following to happen after step 2.:
> a) HornetQ backup server on server B won't start/come live.
> b) Server B is not able to update its cluster view.
> a) and b) -> c) JMS clients on server A are not able to failover to bakcup
> I've attached reproducer with configuration - reproducer.zip. (logging is set to DEBUG level for "org.hornetq")
> How to use the reproducer (there are necessary two machines):
> 1. Download and unzip attached reproducer.zip
> 2. prepare servers A and B using - "sh prepare.sh"
> 3. start server A - "sh start-server1.sh serverA_hostname" - on server serverA_hostname
> 4. start server B - "sh start-server2.sh serverB_hostname" - on server serverB_hostname
> 5. Kill server A using "kill -9 ..."
> I've attached JMS client to reproducer (it's using HornetQ core api to create connection factory a queue "testQueue"):
> 1. Start producer - "sh start-producer.sh server_hostname"
> 2. Start consumer - "sh start-consumer.sh server_hostname"
> This could be configuration issue. For this reason I set major priority. Please re-check standalone-ha-A.xml and standalone-ha-B.xml. I could not find a bug in it. 
> Thank you,
> Mirek

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira