Hi Manuel,
My guess is that the Sequoia driver ping mechanism does not work and
detect that the controller is down and shutdowns the connection.
Unfortunately I don't think there is an option to disable that mechanism
that IMHO is far from being desirable in many scenarios.
One option is to find out why the UDP ping to the controller is not
working. The ugly workaround is to add URL options in the driver to
increase to very large values both pingDelayInMs and controllerTimeoutInMs.
Keep us posted with your findings,
Emmanuel
Hello again,
I tried a little bit more and it seems that the connection is
dropped no matter what. If I am fast enough I am able to send one
select with my application before the connection gets closed.
The Connection seems to be dropped about 5 sec. after tomcat startup
with the comment "Controller /75.101.243.37:25322 down - shutting down
connected sockets".
I tried several Options for the Client JDBC including disabling the
integrated Connection Pooling and enabling commits in autocommit mode
without any changes. Sadly the Server gives no error why the
Connection is dropped.
Best regards
Manuel Rorarius
------------------------------------
mediaskill OHG
Kaiserdamm 100
14057 Berlin
Fon +49 (0)30 - 39 83 572 - 5
Fax +49 (0)30 - 39 83 572 - 3
[EMAIL PROTECTED]
www.mediaskill.de
------------------------------------
Handelsregister: AG Charlottenburg
Nummer: HRA 31638
Ust-IdNr.: DE 238 456 737
------------------------------------
_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia
--
Emmanuel Cecchet
FTO @ Frog Thinker
Open Source Development & Consulting
--
Web: http://www.frogthinker.org
email: [EMAIL PROTECTED]
Skype: emmanuel_cecchet
_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia
