Comments - Aborted connections
Content reproduced on this site is the property of its respective owners,
and this content is not reviewed in advance by MariaDB. The views, information and opinions
expressed by this content do not necessarily represent those of MariaDB or any other party.
Vladislav, thanks for your answer!
Our applikations use MYSql Connector/NET and DbConnection.Open() to create a connection to the database and suddently this method fails and cause the error in the error log. (By the way: By default we use connection pooling).
What is the reason why the method DbConnection.Open() fails?
You can ask the developers of MySQL Connector/NET about that (Its been a decade since I worked on that connector last time). If this fails this way, you're not opening a pooled connection obviously. I'd generally prefer and recommend the community .NET driver to the one of Oracle , exactly because I've seen Oracle's one from inside.
ok, I think I need to test the community .NET driver. But something else must have happened regarding the server environment. A few years the system worked fine. And suddenly problems with the connections and this only after a few weeks of trouble-free runtime ...
Thanks Peter
can you monitor NETSTAT -A on both sides and see if something is leaking over some TCP system limits
Thanks Stephane,
probably this is the solution. I can see many TCP connection on port 8080 with status "waiting..." and one of our processes (java/ActiveMQ) has over 80000 handles.
I will monitor this...