-
Enhancement
-
Resolution: Done
-
Major
-
None
wildfly-config.xml parsing error is being logged at trace only :
10:31:02,439 TRACE [org.jboss.remoting.remote] Failed to parse endpoint XML definition: org.wildfly.client.config.ConfigXMLParseException: CONF0005: Unexpected element "connection" in namespace "urn:jboss-remoting:5.0" encountered at file:/home/jboss/client.jar/wildfly-config.xml:21:7 at org.wildfly.client.config.ConfigurationXMLStreamReader.unexpectedElement(ConfigurationXMLStreamReader.java:291) [wildfly-client-config-1.0.1.Final-redhat-00001.jar:1.0.1.Final-redhat-00001] at org.jboss.remoting3.RemotingXmlParser.parseEndpointElement(RemotingXmlParser.java:100) [jboss-remoting-5.0.8.Final-redhat-1.jar:5.0.9.Final-SNAPSHOT]
It looks like wildfly-client-config is logging the message, but I think remoting is controlling the logging level in this instance.
- is cloned by
-
REM3-330 Log wildfly-config.xml parsing issue at WARN
- Resolved
- is incorporated by
-
JBEAP-16670 [GSS](7.2.z) Upgrade JBoss Remoting from 5.0.8 to 5.0.9.Final-redhat-00001
- Closed