Hi Joachim,
You can file this as a bug in the heartbeat implementation.
This was a hack to try to overcome TCP timeouts problems. I hope there
is an option to disable this feature otherwise post a feature request
for it. I don't know when this feature was exactly implemented, you can
try to look in CVS and get an older version that does not use this
heartbeat.
Thanks for the feedback,
Emmanuel
I had this annoying problem with the closed connections during already
working on an open connection. After some debugging I found out that
the problem is that the jdbc driver seems to listen for a connection
on a udp port > 30000 and the controller tries to reach the client
via this port.
If this does not work (e.g. because of a firewall) the controller
thinks (after a timeout of ~20 seconds) the client is not active any
more (not reagarding that it is in constant communication with it)
and so it closes the connection. Very interesting behavior.
My questions:
1. Can I disable this "feature"? I need to work through a firewall!
2. Why is this communication necessary anyway and why is it not
possible to use the already open channel from the driver to the
controller for that?
3. Why is the controller thinking of a client to be dead if it is
constantly chatting with it? It this not a type of headbeat that
should be enough?
Regards
Joachim
_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia
--
Emmanuel Cecchet - Research scientist
EPFL - LABOS/DSLAB - IN.N 317
Phone: +41-21-693-7558
_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia
