[jboss-jira] [Red Hat JIRA] (WFLY-13875) Resolve missing dependency jboss.naming.context.java.jboss.DefaultJMSConnectionFactory

[ https://issues.redhat.com/browse/WFLY-13875?page=com.atlassian.jira.plugi... ] Scott Marlow commented on WFLY-13875: ------------------------------------- I'm not currently seeing the "is missing [jboss.naming.context.java.jboss.DefaultJMSConnectionFactory" failure locally but do see a java.lang.UnsatisfiedLinkError: com.sun.ts.lib.util.sec.misc.Unsafe.registerNatives failure: {quote} 2020-10-13 15:14:53,065 INFO [stdout] (MSC service thread 1-2) XXXX: in initializeTSLogger() - about to create JACCLog.txt 2020-10-13 15:14:53,074 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service org.wildfly.security.policy: org.jboss.msc.service.StartException in service org.wildfly.security.policy: Failed to start service at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1731) at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1559) at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1990) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1363) at java.lang.Thread.run(Thread.java:748) 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) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:423) at java.lang.Class.newInstance(Class.java:442) at org.wildfly.extension.elytron.PolicyDefinitions.newPolicy(PolicyDefinitions.java:380) at org.wildfly.extension.elytron.PolicyDefinitions.access$200(PolicyDefinitions.java:87) at org.wildfly.extension.elytron.PolicyDefinitions$5.accept(PolicyDefinitions.java:323) at org.wildfly.extension.elytron.PolicyDefinitions$5.accept(PolicyDefinitions.java:315) at org.wildfly.extension.elytron.PolicyDefinitions$2$1.start(PolicyDefinitions.java:184) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739) at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1701) ... 6 more {quote} I'll look into the cause for the ^ I also reported https://issues.redhat.com/browse/WFLY-13966 from jacc testing which is a likely side effect of the ^ failure. -- This message was sent by Atlassian Jira (v7.13.8#713008)