Looks like the application is not working properly , it was working couple of months back, we are using this sample application for Kubernetes demo purposes and havent been able to use it recently. I'm using this image - arungupta/wildfly-mysql-javaee7:k8s

Running the container in Kubernetes or Docker standalone gives this exception in logs

Caused by: java.sql.SQLException: Must specify port after ':' in connection string
        at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1094)
        at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:997)
        at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:983)


0:36:39,164 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 10) MSC000001: Failed to start service jboss.persistenceunit."employees.war#MyPU": org.jboss.msc.service.StartException in service jboss.persistenceunit."employees.war#MyPU": org.hibernate.HibernateException: Access to DialectResolutionInfo cannot be null when 'hibernate.dialect' not set

Hello Arun,
your image arungupta/couchbase looks a little bit old. What install steps or commands are used by you before commited the image? Thank you!

Hi,
running a master + replicas, give the opportunity to have a failover system. In my cluster i've tried to remove and recreate the master and i was expecting to see that it came back in the cluster and recover it's data, but this not happen. Can you help me to understand if it is doable?

this is my compose

version: '3.3'

networks:
  traefik-net:
    external: true
  couchdb:
    external: true

services:

  master:
    image: arungupta/couchbase
    networks:
      - traefik-net
      - couchdb
    environment:
      TYPE: MASTER
    deploy:
      labels:
        - traefik.port=11211
        - traefik.frontend.rule=Host:couchdb.XXXXXX
        - traefik.docker.network=traefik-net
        - traefik.cluster.port=8091
        - traefik.cluster.frontend.rule=Host:couchadmin.XXXXX
        - traefik.cluster.docker.network=traefik-net
      mode: replicated
      replicas: 1
      endpoint_mode: dnsrr
      restart_policy:
        condition: any
        delay: 5s
        max_attempts: 0
        window: 5s

  replicas:
    image: arungupta/couchbase
    networks:
      - couchdb
    environment:
      TYPE: WORKER
      COUCHBASE_MASTER: couchdb_master
      AUTO_REBALANCE: 'true'
    deploy:
      mode: global
      endpoint_mode: dnsrr
      restart_policy:
        condition: any
        delay: 5s
        max_attempts: 0
        window: 5s

the example here:
wildfly-mysql-javaee7/docker-compose.yml

relies on:
docker-compose --x-networking up -d

which works well in: docker-compose version 1.5.2, build 7240ff3

but in current versions of docker-compose (since docker-compose 1.6) the --x-networking option has been deprecated in favour of docker-compose.yml in version:2 format.

I would be very interested to see a similar example to 'wildfly-mysql-javaee7' but working with a recent version of docker-compose and possibile in the version:2 format.

Thanks.

Hello,when i am trying to build a docker image from the dockerfile provided,I am unable to get the login portal and getting only one port exposed.But meanwhile when i use the docker image stored in docker hub i get the two exact ports exposed and also an accessible login portal...So,can you please let me know what additional steps needs to be done...

docker run -p 8080:8080 -t 770727c11311
Error: Invalid or corrupt jarfile /app.jar

I am using the following sample app to make my own docker image
https://github.com/spring-guides/gs-spring-boot-docker.git

docker image builds successfully. and working fine with my laptop with docker terminal for windows 10.
but the same image pushed to gitlab docker registry. and using my VPS Centos server. it is getting the same error. Please help me. Or even pulling to same docker image to docker terminal for windows 10. getting the same error.

docker build -t chanezon/wildfly-couchbase-javaee7 .
Sending build context to Docker daemon 5.207 MB
Step 1 : FROM jboss/wildfly:latest
---> 4c99bd2cd264
Step 2 : RUN sudo yum install -y jq
---> Running in bf2c81e2ed81
/bin/sh: sudo: command not found
The command '/bin/sh -c sudo yum install -y jq' returned a non-zero code: 127

If I pull ur image from docker hub directly.. how can I configure all the parameters that are there in docker-compose.yml?

With the following stack trace:

org.jboss.as.cli.CliInitializationException: Failed to connect to the controller
at org.jboss.as.cli.impl.CliLauncher.initCommandContext(CliLauncher.java:278)
at org.jboss.as.cli.impl.CliLauncher.main(CliLauncher.java:241)
at org.jboss.as.cli.CommandLineMain.main(CommandLineMain.java:34)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.jboss.modules.Module.run(Module.java:312)
at org.jboss.modules.Main.main(Main.java:460)
Caused by: org.jboss.as.cli.CommandLineException: The controller is not available at localhost:9990
at org.jboss.as.cli.impl.CommandContextImpl.tryConnection(CommandContextImpl.java:1028)
at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:840)
at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:819)
at org.jboss.as.cli.impl.CliLauncher.initCommandContext(CliLauncher.java:276)
... 8 more
Caused by: java.io.IOException: java.net.ConnectException: JBAS012174: Could not connect to http-remoting://localhost:9990. The connection failed
at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:129)
at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:71)
at org.jboss.as.cli.impl.CommandContextImpl.tryConnection(CommandContextImpl.java:1005)
... 11 more
Caused by: java.net.ConnectException: JBAS012174: Could not connect to http-remoting://localhost:9990. The connection failed
at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:117)
at org.jboss.as.protocol.ProtocolConnectionManager$EstablishingConnection.connect(ProtocolConnectionManager.java:256)
at org.jboss.as.pr