Thanks.
This is a trace from the sending client - with the logging set to DEBUG. I've
not yet managed to get a trace from the receiver
as I can't repeat the problem at will.
I can see where the client thinks that the connection to the server has gone
away and where it reconnects.
Where can we
Hi,
For completeness I've managed to get a receiver client-side log where it stops
picking up messages.
The first set of messages are from a successful receipt, then next set of
messages are from the next message on after which it stops receiving.
If you need more logs then I've got the whole
I'm giving this one a nudge - to see if anyone has experience similar issues.
It appears that I'm more likely to get messages stuck if the receiver client
attempts to fail-over and then times out after 60 seconds.
It is a though something loses track of the correct node IDs to use when
pulling
There is a FAQ somewhere about killing versus stopping the server.
You could set a flag to start failover after a clean shutdown, but usually
failover will take place after a kill -9.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4211669#4211669
Reply to the
anonymous wrote :
| 11:08:13,730 INFO @Thread-10
failureDetected(FailoverCommandCenter.java:117) [FailoverCommandCenter
|
] JBoss Messaging server failure detected - waiting for failover to complete...
Can you turn on 'trace' log level and post more logs around this line? Thanks.
View
