Configuring Docker insecure repository ( server gave HTTP response to HTTPS client)

If docker gives the error “server gave HTTP response to HTTPS client” when starting a container, you can fix it by adding the following configuration: for never Docker releases, create or update the file /etc/docker/daemon.json as: { “insecure-registries”:[“MY_INSECURE_ADDRESS:5000”] } Replace MY_INSECURE_ADDRESS with your own address. for older Docker releases, create or update the file  /etc/init.d/docker as: DOCKER_OPTS=–insecure-registry MY_INSECURE_ADDRESS:5000 … More Configuring Docker insecure repository ( server gave HTTP response to HTTPS client)

JBOSS Wildfly XADataSourceClass is undefined

Sometimes, the server gives the following error after configuring the driver for the database: ERROR [org.jboss.jca.core.tx.jbossts.XAResourceRecoveryImpl] (Periodic Recovery) IJ000906: Error during crash recovery: java:/PostgresXADS (IJ031084: Unable to create connection): javax.resource.ResourceException: IJ031084: Unable to create connection at org.jboss.jca.adapters.jdbc.xa.XAManagedConnectionFactory.getXAManagedConnection(XAManagedConnectionFactory.java:509) at org.jboss.jca.adapters.jdbc.xa.XAManagedConnectionFactory$1$1.run(XAManagedConnectionFactory.java:395) at org.jboss.jca.adapters.jdbc.xa.XAManagedConnectionFactory$1$1.run(XAManagedConnectionFactory.java:392) at java.security.AccessController.doPrivileged(Native Method) at javax.security.auth.Subject.doAs(Subject.java:422) at org.jboss.jca.adapters.jdbc.xa.XAManagedConnectionFactory$1.run(XAManagedConnectionFactory.java:391) at org.jboss.jca.adapters.jdbc.xa.XAManagedConnectionFactory$1.run(XAManagedConnectionFactory.java:388) at java.security.AccessController.doPrivileged(Native Method) at org.jboss.jca.adapters.jdbc.xa.XAManagedConnectionFactory.createManagedConnection(XAManagedConnectionFactory.java:387) … More JBOSS Wildfly XADataSourceClass is undefined