Am Freitag, 16. November 2007 schrieb [EMAIL PROTECTED]:
> My investigations showed, that it seems to be the Driver, who pings
> the Controllers the whole time.
This seems to be the udp connection I discovered recently and that is
discussed in thread "[Sequoia] jdbc driver acts as a udp server?"?
> In my eyes the current implementation uses one ControllerPinger
> Thread for every Controller. Additional every new JDBC Connection
> uses its own ControllerPinger.
> In our case, we have multiple connections from one machine (using
> myosotis) to the cluster. So we have an enormous amount of
> Connections between the cluster and the "proxy" server only for
> this pinging. In my eyes, it would be helpful to implement a kind
> of synchronization to use only one connection to each controller.
> What to all you others think? Best regards,
I thing that it would be helpful to be able to disable this ping in
the driver via a connection string parameter. UDP connections are
mostly not compatible with firewalls and are not very secure to be
handled there anyway.
Regards
Joachim von Thadden
_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia
