Skip to content

Instantly share code, notes, and snippets.

@hlucasfranca

hlucasfranca/gist:56b20951825971a650e7369b874185c2

Forked from rkbalgi/gist:183a113e946dd9f8360e774dcf17a3db
Created March 2, 2022 19:12
Show Gist options
  • Save hlucasfranca/56b20951825971a650e7369b874185c2 to your computer and use it in GitHub Desktop.
Save hlucasfranca/56b20951825971a650e7369b874185c2 to your computer and use it in GitHub Desktop.
Download ZIP
JDBC_PING with keycloak and postgresql on AWS Fargate
Raw
gistfile1.txt
In your effort of implementing standalone-ha with keycloak postgresql using JDBC_PING you will stumble upon many sites that define
the table structure for jgroupsping and the right one goes like this -
CREATE TABLE IF NOT EXISTS JGROUPSPING (
own_addr varchar(200) NOT NULL,
cluster_name varchar(200) NOT NULL,
ping_data BYTEA,
constraint PK_JGROUPSPING PRIMARY KEY (own_addr, cluster_name)
);
In some links, you will see additional columns like bind_addr and created. These can be included, but will have supplied
as java system properties (especially bind_addr)
The errors occuring because of these will look like - "null value in column "created" or "bind_addr" violates not-null constraint"
' Links
https://developer.jboss.org/wiki/JDBCPING
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment