[jboss-jira] [JBoss JIRA] (WFLY-8488) Usage of JGroups JDBC_PING attempts to delete row too late

[Radoslav Husar (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-8488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13425140#comment-13425140 ] 

Radoslav Husar commented on WFLY-8488:
--------------------------------------

[~meetoblivion] The stack trace you posted is a stack trace from mod_cluster, not jgroups, which is known harmless log noise on macOS (tracked as MODCLUSTER-460). I will reject the issue now, you can reopen if you manage to reproduce the issue.

> 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.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)