Starting wildfly 11 with activemq in arquillian fails
phantumas Mar 23, 2018 9:18 AMI have testet arquillian with wildfly 11 in standalone-configuration without any problems. But when i start the server with standalone-full.xml I can't get it to work.
I test it with a very simple war-project without any external dependencies, only arquillian and junit.
I can't solve the LogManager-problem:
10:16:31,506 ERROR [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0002: Error booting the container: java.lang.ExceptionInInitializerError
at org.apache.commons.logging.LogFactory.getFactory(LogFactory.java:316)
at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:329)
at org.apache.commons.beanutils.ConvertUtilsBean.<init>(ConvertUtilsBean.java:154)
at org.apache.commons.beanutils.BeanUtilsBean.<init>(BeanUtilsBean.java:113)
at org.apache.activemq.artemis.utils.uri.BeanSupport.<clinit>(BeanSupport.java:35)
at org.apache.activemq.artemis.core.server.cluster.impl.MessageLoadBalancingType.<clinit>(MessageLoadBalancingType.java:27)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at java.lang.Class.getEnumConstantsShared(Class.java:3320)
at java.lang.System$2.getEnumConstantsShared(System.java:1249)
at java.util.EnumSet.getUniverse(EnumSet.java:407)
at java.util.EnumSet.noneOf(EnumSet.java:110)
at java.util.EnumSet.allOf(EnumSet.java:131)
at org.jboss.as.controller.operations.validation.EnumValidator.<init>(EnumValidator.java:107)
at org.wildfly.extension.messaging.activemq.ClusterConnectionDefinition.<clinit>(ClusterConnectionDefinition.java:125)
at org.wildfly.extension.messaging.activemq.MessagingSubsystemParser_2_0.getParserDescription(MessagingSubsystemParser_2_0.java:358)
at org.jboss.as.controller.PersistentResourceXMLParser.readElement(PersistentResourceXMLParser.java:41)
at org.jboss.as.controller.PersistentResourceXMLParser.readElement(PersistentResourceXMLParser.java:35)
at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:122)
at org.jboss.staxmapper.XMLExtendedStreamReaderImpl.handleAny(XMLExtendedStreamReaderImpl.java:69)
at org.jboss.as.server.parsing.StandaloneXml_5.parseServerProfile(StandaloneXml_5.java:610)
at org.jboss.as.server.parsing.StandaloneXml_5.readServerElement(StandaloneXml_5.java:243)
at org.jboss.as.server.parsing.StandaloneXml_5.readElement(StandaloneXml_5.java:142)
at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:107)
at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:49)
at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:122)
at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:76)
at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:126)
at org.jboss.as.server.ServerService.boot(ServerService.java:387)
at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:370)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.IllegalStateException: The LogManager was not properly installed (you must set the "java.util.logging.manager" system property to "org.jboss.logmanager.LogManager")
at org.jboss.logmanager.Logger.getLogger(Logger.java:57)
at org.apache.commons.logging.JBossLogFactory.<init>(JBossLogFactory.java:48)
at org.apache.commons.logging.LogFactory$Holder.<clinit>(LogFactory.java:42)
... 33 more
The problem starts when i activate the subsystem "urn:jboss:domain:messaging-activemq:2.0"
I have testet this: https://inspectit-performance.atlassian.net/wiki/spaces/DOC14/pages/5018025/JBoss+7.x and many other suggested solutions which works in previous wildfly-versions.
Has anyone managed to start the wildfly 11 with the standalone-full-configuration under Arquillian?
Many thanks for everey sulotion or idea to resolve this problem!