Problem in killing jboss with hornetq using kill or kill -9

[arunpmohan]

Scenario Description

1. 2 Nodes in cluster, running under load test environment

2. issue shutdown command to one of the servers.

3. Some of the services stops while MDB's and JMS continues sending  un processed messages and so jboss never actually stops.

4. issue kill command and still it doesn't stop

5. issue kill -9  and then  it stops but corrupts Messaging files

   which results in loss of messages and server restart.

Thread dumps attached and logs attached

Any body have experienced this please help?

[clebert.suconic]

What version of HornetQ have you been using?

There was an issue with hornetQ 2.1.2 on the journal. What do you mean by corrupts Messaging Files? a Kill -9 won't corrupt the files.

[clebert.suconic]

BTW: this is the Dev forum, I will move this to the user's forum.

[arunpmohan]

i am using hornetq 2.1.1 final and kill -9 on load shows that journals are corrupted.

Restart of server further doesnt work.The only way is to delete those journals and then start the server to get going

[clebert.suconic]

You should use 2.2.2. There was a bug on 2.1.1 and 2.1.2 that would lead to journal corruption.

[jbenninger]

Clebert,

  Twice I've had the journal go corrupt on clean shutdown. I'm running 2.1.2. Can you point me to which bug would cause this issue. I would just like to understand the problem before upgrading.

[clebert.suconic]

https://issues.jboss.org/browse/HORNETQ-440

2.1.2 had some improvements.

2.2.5 is much better now. there was another possible race condition on 2.2.2 if you killed the server while compacting. It was a rare condition but it's been fixed on 2.2.5