3 Replies Latest reply on Mar 12, 2010 9:42 AM by clebert.suconic

HornetQ, Dead sessions, connections

chrisp. Mar 11, 2010 4:08 AM

Hi!

I'm new with HornetQ and there are still some questions:

Is there any possibilty to be notified if a client (ClientSession!) is closed or dead ? I'm working on a media application and it is very important to know if a session is dead or not (MultiChat for example...). I'm using the Core API.

I noticed the multiplex technique used for sessions. So it would be great if I could register a listener or handler anywhere to be notified if a session or the physical connection (Which could handle a lot of multiplexed sessions) is closed or dead. I hope someone could me !

Greetings from Germany !

Chris P.

1. Re: HornetQ, Dead sessions, connections

clebert.suconic Mar 11, 2010 6:18 PM (in response to chrisp.)

Look at addFailureListener on ClientSession.

If you need it on the server side, Maybe you could use Interceptor to capture the connections established and add a FailureListener to the Connection.
Actions
2. Re: HornetQ, Dead sessions, connections

chrisp. Mar 12, 2010 3:12 AM (in response to clebert.suconic)

Hi!

Thanks for your reply! That was a good idea. But if a client disconnects without calling close, neither the FailureListener nor the InterceptorListener is called. I think these client are kicked after a timeout. Is there any possibility to become notified in such a situation ?

Greetings,
Chris
Actions
3. Re: HornetQ, Dead sessions, connections

clebert.suconic Mar 12, 2010 9:42 AM (in response to chrisp.)

The FailureListener should be called after TTL. (Time to live)
1 of 1 people found this helpful
Actions

Go to original post