[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=13414784#comment-13414784 ] 

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

[~meetoblivion] The configuration is wrong. You need to use data-source="..." to establish model dependency. Here is an example configuration:

{code:xml}
   <subsystem xmlns="urn:jboss:domain:jgroups:4.1">
            <channels default="ee">
                <channel name="ee" stack="tcp"/>
            </channels>
            <stacks>
                <stack name="tcp">
                    <transport type="TCP" socket-binding="jgroups-tcp"/>
                    <jdbc-protocol type="JDBC_PING" data-source="ExampleDS"/>
                    <protocol type="MERGE3"/>
                    <protocol type="FD_SOCK"/>
                    <protocol type="FD_ALL"/>
                    <protocol type="VERIFY_SUSPECT"/>
                    <protocol type="pbcast.NAKACK2"/>
                    <protocol type="UNICAST3"/>
                    <protocol type="pbcast.STABLE"/>
                    <protocol type="pbcast.GMS"/>
                    <protocol type="MFC"/>
                    <protocol type="FRAG2"/>
                </stack>
            </stacks>
        </subsystem>
{code}

I cannot reproduce the CLI issue with nightly build not 11.0.0.Alpha1. The expected output is:

{noformat}
[standalone at localhost:9990 /] /subsystem=jgroups/stack=tcp/protocol=JDBC_PING:add(data-source=ExampleDS,add-index=0
{
    "outcome" => "success",
    "response-headers" => {
        "operation-requires-reload" => true,
        "process-state" => "reload-required"
    }
}
[standalone at localhost:9990 /] :reload
{
    "outcome" => "success",
    "result" => undefined
}
{noformat}

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