Dear OS Team,
I am currently trying to install yuuvis (core-service, designer, elasticsearch, service-manager, rendition - in that order) using a command line script that I wrote. I have verified that the single steps work by copying them out of the script into PS one by one. However when running the script all at once I come accross the following errors and DMS does not start/register to the service manager.
services.log
....
....
d: ID-DBYUUVIS-1611044449322-0-2). On delivery attempt: 16 caught: java.io.IOException: dms service is not available, cowardly refusing to continue with operations
inboxservice.7231 : 2021-01-19 00:25:04.903 INFO 684 --- [ Thread-23] c.o.services.inbox.service.InboxService : Connection to core-service could not be established - try again ...
inboxservice.7231 : 2021-01-19 00:25:06.903 INFO 684 --- [ Thread-23] c.o.services.inbox.service.InboxService : Connection to core-service could not be established - try again ...
structureservice.7461 : 2021-01-19 09:25:08.308 WARN Trying to reconnect to 127.0.0.1 using try 1 of 20.
structureservice.7461 : 2021-01-19 09:25:08.308 INFO Message state is UP: Stomp messaging connect done. Subscribed to /topic/redServerChanged
inboxservice.7231 : 2021-01-19 00:25:08.965 INFO 684 --- [ Thread-23] c.o.services.inbox.service.InboxService : Connection to core-service could not be established - try again ...
structureservice.7461 : 2021-01-19 09:25:10.684 WARN Unable to retrieve instances for appId: DMS
structureservice.7461 : 2021-01-19 09:25:10.684 ERROR Error during health for component dms : {}
inboxservice.7231 : 2021-01-19 00:25:10.965 INFO 684 --- [ Thread-23] c.o.services.inbox.service.InboxService : Connection to core-service could not be established - try again ...
inboxservice.7231 : 2021-01-19 00:25:12.965 INFO 684 --- [ Thread-23] c.o.services.inbox.service.InboxService : Connection to core-service could not be established - try again ...
indexservice.7291 : 2021-01-19 00:25:14.154 INFO 4304 --- [timer://runOnce] c.os.services.index.service.EcmService : waiting for dms service
indexservice.7291 : 2021-01-19 00:25:14.154 WARN 4304 --- [timer://runOnce] o.a.camel.processor.DefaultErrorHandler : Failed delivery for (MessageId: ID-DBYUUVIS-1611044449322-0-1 on ExchangeI
d: ID-DBYUUVIS-1611044449322-0-2). On delivery attempt: 17 caught: java.io.IOException: dms service is not available, cowardly refusing to continue with operations
inboxservice.7231 : 2021-01-19 00:25:14.966 INFO 684 --- [ Thread-23] c.o.services.inbox.service.InboxService : Connection to core-service could not be established - try again ...
inboxservice.7231 : 2021-01-19 00:25:16.967 INFO 684 --- [ Thread-23] c.o.services.inbox.service.InboxService : Connection to core-service could not be established - try again ...
inboxservice.7231 : 2021-01-19 00:25:18.982 INFO 684 --- [ Thread-23] c.o.services.inbox.service.InboxService : Connection to core-service could not be established - try again ...
inboxservice.7231 : 2021-01-19 00:25:20.982 INFO 684 --- [ Thread-23] c.o.services.inbox.service.InboxService : Connection to core-service could not be established - try again ...
inboxservice.7231 : 2021-01-19 00:25:22.998 INFO 684 --- [ Thread-23] c.o.services.inbox.service.InboxService : Connection to core-service could not be established - try again ...
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.module.application.\\\"dataaccess.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.jasee-ejb.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.\\\"ecm.sar\\\".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.bpm-ejb.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.\\\"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.\\\"jasee.sar\\\".DefaultJMSConnectionFactory is missing [jboss.naming.context.java.jboss.DefaultJMSConnectionFactory]\",
\"jboss.naming.context.java.comp.application.jasee-ejb.TransactedInvocationEjb.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.\\\"jasmonitor.sar\\\".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.\\\"security.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.\\\"visualization.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.\\\"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.\\\"core.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.\\\"srv.sar\\\".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.\\\"scripting.sar\\\".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.bpm-ejb.EngineServiceBean.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]\"
]
}"
rest-ws.war.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.Default
JMSConnectionFactory]\"]
}"
I would appreciate any pointers as to what could cause this problem (race conditions?).
Kind regards,
Tobias