Connections in the database connection pool can be closed for many different reasons. A possible typical cause could be a configured 30 minute connection timeout on a firewall. You can configure database connection validation to be run prior to using a database connection or in the background. The WildFly datasource definition has different settings for configuring how database connection validation occurs.
Scott
any help would be great. --
You received this message because you are subscribed to the Google Groups "WildFly" group.
To unsubscribe from this group and stop receiving emails from it, send an email to wildfly+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/wildfly/09b695e4-6697-4767-88a4-cd7218fdca00n%40googlegroups.com.
thanks for the answer. I think TO is not my case because this behavior is super random...
can you maybe suggest tools you think would help to investigate this further?
I am completely in the dark here...
There are packet tracing tools that can be used but they will
only show the source of the close but not why the connections were
closed. Database connections getting closed occasionally is a
normal thing to happen (e.g. during database restarts or admin
work, connection issues at the network level).
I would try to enable database connection validation (perhaps in
the background) so that the problem is automatically checked for
and addressed by closing the bad connections.
Scott
--On Monday, September 18, 2023 at 3:41:30 PM UTC+3 Scott Marlow wrote:
Connections in the database connection pool can be closed for many different reasons. A possible typical cause could be a configured 30 minute connection timeout on a firewall. You can configure database connection validation to be run prior to using a database connection or in the background. The WildFly datasource definition has different settings for configuring how database connection validation occurs.
Scott
On 9/18/23 1:20 PM, Guy Katz wrote:
Hi Guys;
I have posted in stackoverflow a question and in case there are people who can help here that are not 'listening' on stackoverflow here is the link:
https://stackoverflow.com/questions/77126636/strange-close-wait-connection-behavior-using-wildfly-connection-pool-with-sybase
any help would be great. --
You received this message because you are subscribed to the Google Groups "WildFly" group.
To unsubscribe from this group and stop receiving emails from it, send an email to wildfly+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/wildfly/09b695e4-6697-4767-88a4-cd7218fdca00n%40googlegroups.com.
You received this message because you are subscribed to the Google Groups "WildFly" group.
To unsubscribe from this group and stop receiving emails from it, send an email to wildfly+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/wildfly/0bbb4093-bb25-43a2-bdd9-c590bfb44b14n%40googlegroups.com