yuuvis® RAD Q&A

Ask

DMS won't start in Docker Container

0 votes
by (140 points)

I'm trying to install yuuvis inside of a Docker Container, but somehow the DMS microservice won't keep running (Registers to service manager and then stops and deregisters a couple of seconds later). Since I'm attempting to install inside a Docker Container (Windows Server Core) I am restricted to using powershell. The Wildfly server is running in Standalone mode.

application.ear.failed:

  "WFLYCTL0412: Required services that are not installed:" => ["jboss.naming.context.java.jboss.DefaultJMSConnectionFactory"],
        "WFLYCTL0180: Services with missing/unavailable dependencies" => [
            "jboss.naming.context.java.comp.application.jasee-ejb.TransactedInvocationEjb.DefaultJMSConnectionFactory is missing [jboss.naming.context.java.jboss.DefaultJMSConnectionFactory]",
            "jboss.naming.context.java.module.application.\"fulltext.sar\".DefaultJMSConnectionFactory is missing [jboss.naming.context.java.jboss.DefaultJMSConnectionFactory]",
            "jboss.naming.context.java.module.application.\"security.sar\".DefaultJMSConnectionFactory is missing [jboss.naming.context.java.jboss.DefaultJMSConnectionFactory]",
            "jboss.naming.context.java.comp.application.bpm-ejb.EngineServiceBean.DefaultJMSConnectionFactory is missing [jboss.naming.context.java.jboss.DefaultJMSConnectionFactory]",
            "jboss.naming.context.java.comp.application.jasee-ejb.ApplicationDeployerEjb.DefaultJMSConnectionFactory is missing [jboss.naming.context.java.jboss.DefaultJMSConnectionFactory]",
            "jboss.naming.context.java.comp.application.core-ejb.IsolatedTransactionRunnerBean.DefaultJMSConnectionFactory is missing [jboss.naming.context.java.jboss.DefaultJMSConnectionFactory]",
            "jboss.naming.context.java.module.application.\"jasmonitor.sar\".DefaultJMSConnectionFactory is missing [jboss.naming.context.java.jboss.DefaultJMSConnectionFactory]",
            "jboss.naming.context.java.module.application.\"bpm.sar\".DefaultJMSConnectionFactory is missing [jboss.naming.context.java.jboss.DefaultJMSConnectionFactory]",
            "jboss.naming.context.java.module.application.\"etl.sar\".DefaultJMSConnectionFactory is missing [jboss.naming.context.java.jboss.DefaultJMSConnectionFactory]",
            "jboss.naming.context.java.module.application.\"operations.sar\".DefaultJMSConnectionFactory is missing [jboss.naming.context.java.jboss.DefaultJMSConnectionFactory]",
            "jboss.naming.context.java.module.application.\"ecm.sar\".DefaultJMSConnectionFactory is missing [jboss.naming.context.java.jboss.DefaultJMSConnectionFactory]",
            "jboss.naming.context.java.module.application.\"depository.sar\".DefaultJMSConnectionFactory is missing [jboss.naming.context.java.jboss.DefaultJMSConnectionFactory]",
            "jboss.naming.context.java.module.application.\"scripting.sar\".DefaultJMSConnectionFactory is missing [jboss.naming.context.java.jboss.DefaultJMSConnectionFactory]",
            "jboss.naming.context.java.module.application.\"repository.sar\".DefaultJMSConnectionFactory is missing [jboss.naming.context.java.jboss.DefaultJMSConnectionFactory]",
            "jboss.naming.context.java.comp.application.jasee-ejb.JndiContextBinderEjb.DefaultJMSConnectionFactory is missing [jboss.naming.context.java.jboss.DefaultJMSConnectionFactory]",
            "jboss.naming.context.java.module.application.\"messaging.sar\".DefaultJMSConnectionFactory is missing [jboss.naming.context.java.jboss.DefaultJMSConnectionFactory]",
            "jboss.naming.context.java.module.application.\"core.sar\".DefaultJMSConnectionFactory is missing [jboss.naming.context.java.jboss.DefaultJMSConnectionFactory]",
            "jboss.naming.context.java.module.application.core-ejb.DefaultJMSConnectionFactory is missing [jboss.naming.context.java.jboss.DefaultJMSConnectionFactory]",
            "jboss.naming.context.java.module.application.\"dms.sar\".DefaultJMSConnectionFactory is missing [jboss.naming.context.java.jboss.DefaultJMSConnectionFactory]",
            "jboss.naming.context.java.module.application.\"ldapsync.sar\".DefaultJMSConnectionFactory is missing [jboss.naming.context.java.jboss.DefaultJMSConnectionFactory]",
            "jboss.naming.context.java.module.application.\"rendition.sar\".DefaultJMSConnectionFactory is missing [jboss.naming.context.java.jboss.DefaultJMSConnectionFactory]",
            "jboss.naming.context.java.module.application.\"organisation.sar\".DefaultJMSConnectionFactory is missing [jboss.naming.context.java.jboss.DefaultJMSConnectionFactory]",
            "jboss.naming.context.java.module.application.\"typesystem.sar\".DefaultJMSConnectionFactory is missing [jboss.naming.context.java.jboss.DefaultJMSConnectionFactory]",
            "jboss.naming.context.java.module.application.\"jasee.sar\".DefaultJMSConnectionFactory is missing [jboss.naming.context.java.jboss.DefaultJMSConnectionFactory]",
            "jboss.naming.context.java.module.application.jasee-ejb.DefaultJMSConnectionFactory is missing [jboss.naming.context.java.jboss.DefaultJMSConnectionFactory]",
            "jboss.naming.context.java.module.application.\"srv.sar\".DefaultJMSConnectionFactory is missing [jboss.naming.context.java.jboss.DefaultJMSConnectionFactory]",
            "jboss.naming.context.java.module.application.\"dataaccess.sar\".DefaultJMSConnectionFactory is missing [jboss.naming.context.java.jboss.DefaultJMSConnectionFactory]",
            "jboss.naming.context.java.module.application.bpm-ejb.DefaultJMSConnectionFactory is missing [jboss.naming.context.java.jboss.DefaultJMSConnectionFactory]",
            "jboss.naming.context.java.module.application.\"visualization.sar\".DefaultJMSConnectionFactory is missing [jboss.naming.context.java.jboss.DefaultJMSConnectionFactory]"
        ]

rest-ws.ear.failed:

"WFLYCTL0412: Required services that are not installed:" => ["jboss.naming.context.java.jboss.DefaultJMSConnectionFactory"],
    "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.naming.context.java.module.rest-ws.rest-ws.DefaultJMSConnectionFactory is missing [jboss.naming.context.java.jboss.DefaultJMS
ConnectionFactory]"]

../service_manager/logs/services.log:

gateway.80                : 2020-12-22 01:33:16.733  WARN 4748 --- [ qtp25943839-19] c.o.e.r.g.e.EnaioAuthenticationProvider  : Authentication failed! Reason: UnknownHostException: This is usually a tem
porary error during hostname resolution and means that the local server did not receive a response from an authoritative server (http)]
structureservice.7461     : 2020-12-22 09:33:17.624 WARN  Unable to retrieve instances for appId: DMS
structureservice.7461     : 2020-12-22 09:33:17.624 ERROR Error during health for component dms : {}
inboxservice.7231         : 2020-12-22 01:33:17.764  INFO 1164 --- [      Thread-23] c.o.services.inbox.service.InboxService  : Connection to core-service could not be established - try again ...
inboxservice.7231         : 2020-12-22 01:33:19.780  INFO 1164 --- [      Thread-23] c.o.services.inbox.service.InboxService  : Connection to core-service could not be established - try again ...
gateway.80                : 2020-12-22 01:33:21.764  WARN 4748 --- [ qtp25943839-41] c.o.e.r.g.e.EnaioAuthenticationProvider  : Authentication failed! Reason: UnknownHostException: http]
inboxservice.7231         : 2020-12-22 01:33:21.795  INFO 1164 --- [      Thread-23] c.o.services.inbox.service.InboxService  : Connection to core-service could not be established - try again ...
inboxservice.7231         : 2020-12-22 01:33:23.796  INFO 1164 --- [      Thread-23] c.o.services.inbox.service.InboxService  : Connection to core-service could not be established - try again ...
inboxservice.7231         : 2020-12-22 01:33:25.811  INFO 1164 --- [      Thread-23] c.o.services.inbox.service.InboxService  : Connection to core-service could not be established - try again ...
structureservice.7461     : 2020-12-22 09:33:27.624 WARN  Unable to retrieve instances for appId: DMS
structureservice.7461     : 2020-12-22 09:33:27.624 ERROR Error during health for component dms : {}
inboxservice.7231         : 2020-12-22 01:33:27.858  INFO 1164 --- [      Thread-23] c.o.services.inbox.service.InboxService  : Connection to core-service could not be established - try again ...
inboxservice.7231         : 2020-12-22 01:33:29.858  INFO 1164 --- [      Thread-23] c.o.services.inbox.service.InboxService  : Connection to core-service could not be established - try again ...
inboxservice.7231         : 2020-12-22 01:33:31.858  INFO 1164 --- [      Thread-23] c.o.services.inbox.service.InboxService  : Connection to core-service could not be established - try again ...
inboxservice.7231         : 2020-12-22 01:33:33.874  INFO 1164 --- [      Thread-23] c.o.services.inbox.service.InboxService  : Connection to core-service could not be established - try again ...
inboxservice.7231         : 2020-12-22 01:33:35.889  INFO 1164 --- [      Thread-23] c.o.services.inbox.service.InboxService  : Connection to core-service could not be established - try again ...
gateway.80                : 2020-12-22 01:33:36.670  WARN 4748 --- [ qtp25943839-41] c.o.e.r.g.e.EnaioAuthenticationProvider  : Authentication failed! Reason: UnknownHostException: This is usually a tem
porary error during hostname resolution and means that the local server did not receive a response from an authoritative server (http)]
inboxservice.7231         : 2020-12-22 01:33:37.905  INFO 1164 --- [      Thread-23] c.o.services.inbox.service.InboxService  : Connection to core-service could not be established - try again ...
inboxservice.7231         : 2020-12-22 01:33:39.905  INFO 1164 --- [      Thread-23] c.o.services.inbox.service.InboxService  : Connection to core-service could not be established - try again ...
gateway.80                : 2020-12-22 01:33:41.702  WARN 4748 --- [ qtp25943839-41] c.o.e.r.g.e.EnaioAuthenticationProvider  : Authentication failed! Reason: UnknownHostException: http]
inboxservice.7231         : 2020-12-22 01:33:41.920  INFO 1164 --- [      Thread-23] c.o.services.inbox.service.InboxService  : Connection to core-service could not be established - try again ...
inboxservice.7231         : 2020-12-22 01:33:43.920  INFO 1164 --- [      Thread-23] c.o.services.inbox.service.InboxService  : Connection to core-service could not be established - try again ...
inboxservice.7231         : 2020-12-22 01:33:45.920  INFO 1164 --- [      Thread-23] c.o.services.inbox.service.InboxService  : Connection to core-service could not be established - try again ...
structureservice.7461     : 2020-12-22 09:33:47.624 WARN  Unable to retrieve instances for appId: DMS
structureservice.7461     : 2020-12-22 09:33:47.624 ERROR Error during health for component dms : {}
inboxservice.7231         : 2020-12-22 01:33:47.936  INFO 1164 --- [      Thread-23] c.o.services.inbox.service.InboxService  : Connection to core-service could not be established - try again ...
inboxservice.7231         : 2020-12-22 01:33:49.952  INFO 1164 --- [      Thread-23] c.o.services.inbox.service.InboxService  : Connection to core-service could not be established - try again ...

Do I manually need to install some additional dependencies for JBoss or is this a configuration problem?

1 Answer

0 votes
by (5.4k points)

Hi,

Running RAD in Docker is not supported: https://help.optimal-systems.com/yuuvisRAD/v60/admin/en/index.html

Could you please give us a bit more info, why you are running core in Docker, in which environement and in which project? (if you do not wish to discuss the details openly, please contact us per email)

best regards,
Bratislav

by (140 points)
So I tried setting up a reference installation on my normal Windows OS to verify that the issue persists, I also reinstalled the Docker installation, which was now behaving a bit differently. DMS didnt show up in the service manager journal (localhost:7273) anymore at all. The Windows OS installation behaved the same way, though the errors were slightly different.

The status right after finishing the installation with the same scripts used to install in Docker is as follows:

rest-ws.war.failed
"WFLYCTL0063: Composite operation was rolled back"

application.ear.failed
"{
    \"WFLYCTL0412: Required services that are not installed:\" => [
        \"jboss.security.security-domain.jas\",
        \"jboss.naming.context.java.JASDB\"
    ],
    \"WFLYCTL0180: Services with missing/unavailable dependencies\" => [
        \"jboss.deployment.subunit.\\\"application.ear\\\".\\\"jasee-ejb.jar\\\".component.JndiContextBinderEjb.CREATE is missing [jboss.security.security-domain.jas]\",
        \"jboss.deployment.subunit.\\\"application.ear\\\".\\\"jasee-ejb.jar\\\".component.ApplicationDeployerEjb.CREATE is missing [jboss.security.security-domain.jas]\",
        \"jboss.deployment.subunit.\\\"application.ear\\\".\\\"core-ejb.jar\\\".component.IsolatedTransactionRunnerBean.CREATE is missing [jboss.security.security-domain.jas]\",
        \"jboss.naming.context.java.comp.application.jasee-ejb.ApplicationDeployerEjb.env.\\\"com.os.ee.deployment.ApplicationDeployerEjb\\\".ds is missing [jboss.naming.context.java.JASDB]\",
        \"jboss.deployment.subunit.\\\"application.ear\\\".\\\"jasee-ejb.jar\\\".component.TransactedInvocationEjb.CREATE is missing [jboss.security.security-domain.jas]\",
        \"jboss.deployment.subunit.\\\"application.ear\\\".\\\"bpm-ejb.jar\\\".component.EngineServiceBean.CREATE is missing [jboss.security.security-domain.jas]\"
    ]
}"


service_manager/service.log
dmssidecar.7301           : com.netflix.zuul.exception.ZuulException: Filter threw Exception
dmssidecar.7301           :     at com.netflix.zuul.FilterProcessor.processZuulFilter(FilterProcessor.java:227)
dmssidecar.7301           :     at com.netflix.zuul.FilterProcessor.runFilters(FilterProcessor.java:157)
dmssidecar.7301           :     at com.netflix.zuul.FilterProcessor.preRoute(FilterProcessor.java:133)
dmssidecar.7301           :     at com.netflix.zuul.ZuulRunner.preRoute(ZuulRunner.java:105)
dmssidecar.7301           :     at com.netflix.zuul.http.ZuulServlet.preRoute(ZuulServlet.java:125)
dmssidecar.7301           :     at com.netflix.zuul.http.ZuulServlet.service(ZuulServlet.java:74)
dmssidecar.7301           :     at org.springframework.web.servlet.mvc.ServletWrappingController.handleRequestInternal(ServletWrappingController.java:157)
dmssidecar.7301           :     at org.springframework.cloud.netflix.zuul.web.ZuulController.handleRequest(ZuulController.java:44)
dmssidecar.7301           :     at org.springframework.web.servlet.mvc.SimpleControllerHandlerAdapter.handle(SimpleControllerHandlerAdapter.java:50)
dmssidecar.7301           :     at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:967)
dmssidecar.7301           :     at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:901)
dmssidecar.7301           :     at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:970)
dmssidecar.7301           :     at org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:861)
dmssidecar.7301           :     at javax.servlet.http.HttpServlet.service(HttpServlet.java:687)
dmssidecar.7301           :     at org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:846)
dmssidecar.7301           :     at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
dmssidecar.7301           :     at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:865)
dmssidecar.7301           :     at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1655)
dmssidecar.7301           :     at org.eclipse.jetty.websocket.server.WebSocketUpgradeFilter.doFilter(WebSocketUpgradeFilter.java:215)
dmssidecar.7301           :     at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1642)
dmssidecar.7301           :     at org.springframework.boot.web.filter.ApplicationContextHeaderFilter.doFilterInternal(ApplicationContextHeaderFilter.java:55)
dmssidecar.7301           :     at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107)
dmssidecar.7301           :     at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1642)
dmssidecar.7301           :     at com.os.services.dms.IpWhiteListFilter.doFilter(IpWhiteListFilter.java:45)
dmssidecar.7301           :     at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1642)
dmssidecar.7301           :     at com.os.services.core.audit.tracing.CorrelationHeaderFilter.doFilter(CorrelationHeaderFilter.java:45)
dmssidecar.7301           :     at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1642)
dmssidecar.7301           :     at org.springframework.boot.actuate.trace.WebRequestTraceFilter.doFilterInternal(WebRequestTraceFilter.java:111)
dmssidecar.7301           :     at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107)
dmssidecar.7301           :     at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1642)
dmssidecar.7301           :     at com.os.services.core.logging.PerformanceFilter.doFilter(PerformanceFilter.java:84)
dmssidecar.7301           :     at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1642)
dmssidecar.7301           :     at org.springframework.security.web.FilterChainProxy.doFilterInternal(FilterChainProxy.java:208)
dmssidecar.7301           :     ...
dmssidecar.7301           :     at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:683)
dmssidecar.7301           :     at java.lang.Thread.run(Thread.java:748)
dmssidecar.7301           : Caused by: java.lang.IllegalStateException: Target URL is malformed
dmssidecar.7301           :     at org.springframework.cloud.netflix.zuul.filters.pre.PreDecorationFilter.getUrl(PreDecorationFilter.java:269)
dmssidecar.7301           :     at org.springframework.cloud.netflix.zuul.filters.pre.PreDecorationFilter.run(PreDecorationFilter.java:132)
dmssidecar.7301           :     at com.netflix.zuul.ZuulFilter.runFilter(ZuulFilter.java:117)
dmssidecar.7301           :     at com.netflix.zuul.FilterProcessor.processZuulFilter(FilterProcessor.java:193)
dmssidecar.7301           :     ... 80 common frames omitted
dmssidecar.7301           : Caused by: java.net.MalformedURLException: For input string: "7301:8080"
dmssidecar.7301           :     at java.net.URL.<init>(URL.java:627)
dmssidecar.7301           :     at java.net.URL.<init>(URL.java:490)
dmssidecar.7301           :     at java.net.URL.<init>(URL.java:439)
dmssidecar.7301           :     at org.springframework.cloud.netflix.zuul.filters.pre.PreDecorationFilter.getUrl(PreDecorationFilter.java:266)
dmssidecar.7301           :     ... 83 common frames omitted
dmssidecar.7301           : Caused by: java.lang.NumberFormatException: For input string: "7301:8080"
dmssidecar.7301           :     at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
dmssidecar.7301           :     at java.lang.Integer.parseInt(Integer.java:580)
dmssidecar.7301           :     at java.lang.Integer.parseInt(Integer.java:615)
dmssidecar.7301           :     at java.net.URLStreamHandler.parseURL(URLStreamHandler.java:222)
dmssidecar.7301           :     at java.net.URL.<init>(URL.java:622)
dmssidecar.7301           :     ... 86 common frames omitted

Then after attempting to start the services in the order: core-service, rendition, service_manager all are running for a moment before core-service goes down again, this behaviour persists. Then 15 services register to the service manager, they are all 'up'. DMS does not make contact with the service manager.
by (5.4k points)
edited by
Hi,

as said, yuuvis RAD does not support installation via Docker (for various reasons). In case that this is necessary in a project, please contact us via email so that we can get in touch, discuss the need and requirement, and see how to proceed.

As for the installation in Windows - do you use our standard installers? In our test instances, the installation works without a problem. If this does not work, please contact our support and they will help you with the installation, or if necessary, they will create a ticket for development.

If you are trying to do the same as in Docker (deploy .ear in jboss), this cannot work and is not a supported way of installing yuuvis RAD.

best regards,
Bratislav

Related questions

0 votes
1 answer
Cache-Control DMS Content possible?
asked Jan 26, 2021 by Martin Januschke (660 points)
0 votes
2 answers
DMS Service does not start up
asked Jan 2, 2019 by Mathias Keller (1.9k points)
0 votes
1 answer
Change DMS sidecar URL after the installation
asked Feb 19, 2019 by Umar Chikobava (790 points)
© Copyright OPTIMAL SYSTEMS 2023 | Legal & Data Privacy
...