Log4j2中的JMS Appender转到Wildfly 14时出错

Question

  topicConnFacName: com.rsc.mmpl.TopicConnectionFactory
  initialContextFacName: org.jboss.naming.remote.client.InitialContextFactory
  URL: http-remoting://JDEVDWS166:9090
  Topic name: com.rsc.mmpl.MsgHndlrTopic

我的log4j2.xml配置如下：

<?xml version="1.0" encoding="UTF-8"?>
<Configuration status="INFO">
  <Appenders>
    <Console name="Console" target="SYSTEM_OUT">
      <PatternLayout pattern="%p %d{yyyy-MMM-dd HH:mm:ss.SSS} %c{3}[line %L] - %m%n"/>
    </Console>
    <JMS name="jmsQueue" destinationBindingName="com.rsc.mmpl.MsgHndlrTopic"
         factoryName="org.jboss.naming.remote.client.InitialContextFactory"
         factoryBindingName="com.rsc.mmpl.TopicConnectionFactory"
         ignoreExceptions="false"
         providerURL="http-remoting://JDEVDWS166:9090">
         <JsonLayout properties="true" complete="true"/>
    </JMS>
  </Appenders>
  <Loggers>
    <Root level="info">
      <AppenderRef ref="Console"/>
      <AppenderRef ref="jmsQueue"/>
    </Root>
  </Loggers>
</Configuration>

如果我注释掉我的JMS Appender，它工作得很好，所以我知道从类路径的角度来看，我的log4j设置是正确的(log4j核心和api jar，以及jackson jars和jboss-client.jar都在整个类路径上）。

但是，当使用JMS Appender运行客户端应用程序时，我会出现以下错误：

[stderr] Caused by: java.lang.NoClassDefFoundError: Could not initialize class org.jboss.remoting3.ConfigurationEndpointSupplier$Holder
[stderr]    at org.jboss.remoting3.ConfigurationEndpointSupplier.get(ConfigurationEndpointSupplier.java:84)
[stderr]    at org.jboss.remoting3.ConfigurationEndpointSupplier.get(ConfigurationEndpointSupplier.java:40)
[stderr]    at org.wildfly.common.context.ContextManager.getPrivileged(ContextManager.java:286)
[stderr]    at org.jboss.remoting3.Endpoint.getCurrent(Endpoint.java:81)
[stderr]    at org.wildfly.naming.client.remote.RemoteNamingProviderFactory.getEndpoint(RemoteNamingProviderFactory.java:49)
[stderr]    at org.wildfly.naming.client.remote.RemoteNamingProviderFactory.supportsUriScheme(RemoteNamingProviderFactory.java:40)
[stderr]    at org.wildfly.naming.client.WildFlyRootContext.getProviderContext(WildFlyRootContext.java:784)
[stderr]    at org.wildfly.naming.client.WildFlyRootContext.lookup(WildFlyRootContext.java:140)
[stderr]    at java.naming/javax.naming.InitialContext.lookup(InitialContext.java:409)
[stderr]    at org.apache.logging.log4j.core.net.JndiManager.lookup(JndiManager.java:172)
[stderr]    at org.apache.logging.log4j.core.appender.mom.JmsManager.createConnection(JmsManager.java:323)
[stderr]    at org.apache.logging.log4j.core.appender.mom.JmsManager.<init>(JmsManager.java:250)
[stderr]    at org.apache.logging.log4j.core.appender.mom.JmsManager.<init>(JmsManager.java:54)
[stderr]    at org.apache.logging.log4j.core.appender.mom.JmsManager$JmsManagerFactory.createManager(JmsManager.java:130)
[stderr]    at org.apache.logging.log4j.core.appender.mom.JmsManager$JmsManagerFactory.createManager(JmsManager.java:125)
[stderr]    at org.apache.logging.log4j.core.appender.AbstractManager.getManager(AbstractManager.java:113)
[stderr]    at org.apache.logging.log4j.core.appender.mom.JmsAppender$Builder.build(JmsAppender.java:118)
[stderr]    at org.apache.logging.log4j.core.appender.mom.JmsAppender$Builder.build(JmsAppender.java:50)
[stderr]    at org.apache.logging.log4j.core.config.plugins.util.PluginBuilder.build(PluginBuilder.java:123)
[stderr]    at org.apache.logging.log4j.core.config.AbstractConfiguration.createPluginObject(AbstractConfiguration.java:959)
[stderr]    at org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:899)
[stderr]    at org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:891)
[stderr]    at org.apache.logging.log4j.core.config.AbstractConfiguration.doConfigure(AbstractConfiguration.java:514)
[stderr]    at org.apache.logging.log4j.core.config.AbstractConfiguration.initialize(AbstractConfiguration.java:238)
[stderr]    at org.apache.logging.log4j.core.config.AbstractConfiguration.start(AbstractConfiguration.java:250)
[stderr]    at org.apache.logging.log4j.core.LoggerContext.setConfiguration(LoggerContext.java:547)
[stderr]    at org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:619)
[stderr]    at org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:636)
[stderr]    at org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:231)
[stderr]    at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:243)
[stderr]    at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:45)
[stderr]    at org.apache.logging.log4j.LogManager.getContext(LogManager.java:174)
[stderr]    at org.apache.logging.log4j.LogManager.getLogger(LogManager.java:648)
[stderr]    at com.rsc.delphi.logger.log4j.Log4jLogger.<init>(Unknown Source)
[stderr]    ... 20 more

有没有办法获得更多的信息来弄清楚这里的失败是什么？同样，以编程方式连接到我的Wildfly JMS是很好的，只是Log4J2出现了一个问题。

提前谢了。

Answer 1

看着它，我的第一个猜测是问题不在堆栈跟踪的顶部。类加载问题可能源于log4j2获得到wildfly命名接口的连接。

看起来现在提供了一个新的InitialContextFactory（子类）模块。这意味着你必须改变：

org.jboss.naming.remote.client.InitialContextFactory

致：

org.wildfly.naming.client.WildFlyInitialContextFactory