]
Radoslav Husar commented on WFLY-8488:
--------------------------------------
[~meetoblivion] Can you reproduce on master? Did you set the datasource reference on
JDBC_PING protocol resource? e.g.
/subsystem=jgroups/stack=tcp/protocol=JDBC_PING:add(data-source=ExampleDS) If that still
fails, can you post configuration and stack trace?
Usage of JGroups JDBC_PING attempts to delete row too late
----------------------------------------------------------
Key: WFLY-8488
URL:
https://issues.jboss.org/browse/WFLY-8488
Project: WildFly
Issue Type: Bug
Components: Clustering
Affects Versions: 10.1.0.Final
Reporter: John Ament
Assignee: Paul Ferraro
I was recently working on spinning up a Keycloak cluster. We're deployed to AWS,
can't leverage UDP and wanted to have a discovery mechanism that was easy to use, so
tried out JDBC_PING. While I got the cluster running, when shutting down a node I would
receive an exception on the console when attempting to remove the node from the cluster.
It attempts to do a delete on the row in the database after the DataSource has been shut
down.
In my setup, I'm pointing JGroups at the same DataSource as Keycloak, I'm not
using the properties approach. I can switch to the properties approach, but I would
prefer a single pool rather than multiple connections.