]
Emmanuel Hugonnet commented on WFLY-13875:
------------------------------------------
I think this is the cause of the embedded broker not starting:
{noformat}
15:55:52,362 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC000001: Failed
to start service jboss.security.bootstrap: org.jboss.msc.service.StartException in service
jboss.security.bootstrap: Failed to start service
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1731)
[jboss-msc-1.4.11.Final.jar:1.4.11.Final]
at
org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1559)
[jboss-msc-1.4.11.Final.jar:1.4.11.Final]
at
org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
[jboss-threads-2.4.0.Final.jar:2.4.0.Final]
at
org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1990)
[jboss-threads-2.4.0.Final.jar:2.4.0.Final]
at
org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
[jboss-threads-2.4.0.Final.jar:2.4.0.Final]
at
org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
[jboss-threads-2.4.0.Final.jar:2.4.0.Final]
at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_265]
Caused by: java.lang.UnsatisfiedLinkError:
com.sun.ts.lib.util.sec.misc.Unsafe.registerNatives()V
at com.sun.ts.lib.util.sec.misc.Unsafe.registerNatives(Native Method)
at com.sun.ts.lib.util.sec.misc.Unsafe.<clinit>(Unsafe.java:36)
at
com.sun.ts.lib.util.sec.misc.SharedSecrets.<clinit>(SharedSecrets.java:38)
at
com.sun.ts.lib.util.sec.security.provider.PolicyFile$PolicyInfo.<init>(PolicyFile.java:2408)
at com.sun.ts.lib.util.sec.security.provider.PolicyFile.init(PolicyFile.java:472)
at
com.sun.ts.lib.util.sec.security.provider.PolicyFile.<init>(PolicyFile.java:324)
at com.sun.ts.tests.jacc.provider.TSPolicy.loadPolicy(TSPolicy.java:206)
at com.sun.ts.tests.jacc.provider.TSPolicy.<init>(TSPolicy.java:72)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
[rt.jar:1.8.0_265]
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
[rt.jar:1.8.0_265]
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
[rt.jar:1.8.0_265]
at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
[rt.jar:1.8.0_265]
at java.lang.Class.newInstance(Class.java:442) [rt.jar:1.8.0_265]
at
org.jboss.as.security.service.SecurityBootstrapService.initializeJacc(SecurityBootstrapService.java:128)
at
org.jboss.as.security.service.SecurityBootstrapService.start(SecurityBootstrapService.java:102)
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739)
[jboss-msc-1.4.11.Final.jar:1.4.11.Final]
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1701)
[jboss-msc-1.4.11.Final.jar:1.4.11.Final]
... 6 more{noformat}
Resolve missing dependency
jboss.naming.context.java.jboss.DefaultJMSConnectionFactory
--------------------------------------------------------------------------------------
Key: WFLY-13875
URL:
https://issues.redhat.com/browse/WFLY-13875
Project: WildFly
Issue Type: Sub-task
Components: JMS
Reporter: Scott Marlow
Assignee: Emmanuel Hugonnet
Priority: Major
Labels: EE9
server.log output from running Jakarta EE 9 Platform TCK JACC tests against Brian's
WildFly ee-9 branch:
{code}
020-09-15 15:48:46,120 ERROR [org.jboss.as.controller.management-operation] (Controller
Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address:
([("deployment" => "greenmail-jboss-service.sar")]) - failure
description: {
"WFLYCTL0412: Required services that are not installed:" =>
["jboss.naming.context.java.jboss.DefaultJMSConnectionFactory"],
"WFLYCTL0180: Services with missing/unavailable dependencies" =>
["jboss.naming.context.java.module.\"greenmail-jboss-service.sar\".\"greenmail-jboss-service.sar\".DefaultJMSConnectionFactory
is missing [jboss.naming.context.java.jboss.DefaultJMSConnectionFactory]"]
}
...
2020-09-15 15:49:21,610 ERROR [org.jboss.as.controller.management-operation]
(DeploymentScanner-threads - 2) WFLYCTL0013: Operation ("deploy") failed -
address: ([("deployment" => "jacc_util.ear")]) - failure
description: {
"WFLYCTL0412: Required services that are not installed:" =>
["jboss.naming.context.java.jboss.DefaultJMSConnectionFactory"],
"WFLYCTL0180: Services with missing/unavailable dependencies" =>
["jboss.naming.context.java.module.jacc_util.jacc_util_web.DefaultJMSConnectionFactory
is missing [jboss.naming.context.java.jboss.DefaultJMSConnectionFactory]"]
}
...
2020-09-15 15:49:27,418 ERROR [org.jboss.as.controller.management-operation]
(DeploymentScanner-threads - 2) WFLYCTL0013: Operation ("deploy") failed -
address: ([("deployment" => "jacc_ejb_methodperm.ear")]) - failure
description: {
"WFLYCTL0412: Required services that are not installed:" =>
["jboss.naming.context.java.jboss.DefaultJMSConnectionFactory"],
"WFLYCTL0180: Services with missing/unavailable dependencies" => [
"jboss.naming.context.java.module.jacc_ejb_methodperm.jacc_ejb_methodperm_ejb.DefaultJMSConnectionFactory
is missing [jboss.naming.context.java.jboss.DefaultJMSConnectionFactory]",
"jboss.naming.context.java.module.jacc_ejb_methodperm.jacc_ejb_methodperm_client.DefaultJMSConnectionFactory
is missing [jboss.naming.context.java.jboss.DefaultJMSConnectionFactory]",
"jboss.naming.context.java.comp.jacc_ejb_methodperm.jacc_ejb_methodperm_ejb.jacc_ejb_methodperm_MethodPermBean.DefaultJMSConnectionFactory
is missing [jboss.naming.context.java.jboss.DefaultJMSConnectionFactory]"
]
}
{code}