how do you know it is connection leak? any more data to back that claim?
something in the log?
did you try with connection tracing enabled which would helps identify exact point where leak is happening.
Hi Tomaz, I have tried with debug logs enabled and datasource statistics enabled. Furthermore I monitored the pool with wildfly's console and by JMX (hawtio) too.
At some point, the connection is supplied from the pool but is never closed and a new connection is supplied again. I'm afraid that it could be a lock into the BaseWrapperManagedConnection(LocalManagedConnection).
If you wants, I have some log traces that I can send by email to get another opinion.
Hi Tomaz, I tried but it doesn't generate any file. When there is no connection leak, is this expected? (connections are killed by timeout, maybe this is not considered technically a connection leak)
Well that is odd in any case. But it is not connection leak in app server code anywhere.
But somewhere in code that is deployed on it. So maybe switchyard guys can help here.
Thanks Tomaz, I found a workaround to this problem. Maybe in future versions, doing upgrade of camel or spring to last version can solve the problem.
The only thing that I could see to improve into the switchyard component is the possibility to set a custom entity manager factory to avoid to create one every time, the rest of process is doing by apache camel and spring framework. This was the key of my workaround.
Thanks for your replyTomaz!
Hmm I haven't looked into it deeper yet, but I think connection should not leak even if EntityManagerFactory is created everytime. If it only happens on WildFly10, there would be an issue in hibernate bundled in WF10.