[
https://issues.jboss.org/browse/WFLY-8488?page=com.atlassian.jira.plugin....
]
John Ament commented on WFLY-8488:
----------------------------------
unfortunately, while testing in 11 Alpha1, I get the following error:
{code}
stener=https' is deprecated, and may be removed in future version. See the attribute
description in the output of the read-resource-description operation to learn more about
the deprecation.
22:31:33,478 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread
Pool -- 9) WFLYCTL0013: Operation ("add") failed - address: ([
("subsystem" => "jgroups"),
("stack" => "tcp"),
("protocol" => "JDBC_PING")
]) - failure description: "WFLYCTL0155: 'data-source' may not be null"
22:31:33,545 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread)
"WFLYCTL0193: Failed executing subsystem jgroups boot operations"
22:31:33,546 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread)
WFLYCTL0013: Operation ("parallel-subsystem-boot") failed - address: ([]) -
failure description: "\"WFLYCTL0193: Failed executing subsystem jgroups boot
operations\""
22:31:33,549 FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot
has failed in an unrecoverable manner; exiting. See previous messages for details.
22:31:33,564 INFO [org.jboss.as] (MSC service thread 1-3) WFLYSRV0050: WildFly Full
11.0.0.Alpha1 (WildFly Core 3.0.0.Beta11) stopped in 9ms
{code}
This is what my stack looks like
{code}
<stack name="tcp">
<transport type="TCP"
socket-binding="jgroups-tcp"/>
<!-- socket-protocol type="MPING"
socket-binding="jgroups-mping" -->
<protocol type="JDBC_PING">
<property
name="datasource_jndi_name">java:jboss/datasources/ExampleDS</property>
</protocol>
<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>
{code}
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)