It was a bug in JBoss Logmanager which has been fixed in a later version https://github.com/jboss-logging/jboss-logmanager/commit/1157ae88ae9da30486fd5a80b9f8b584ccb40861
You could try using the latest released WildFly (previously known as JBoss AS) version Downloads
Thanks. I am not sure if upgrading will be an acceptable solution, I will have to check.
Do you know the related bug ticket (or how I can find out)?
1 of 1 people found this helpful
Looking at the commit, I don't think there was a JIRA created. Let's wait for James who might know whether it's possible to just upgrade certain jars to workaround this issue.
There was no JIRA filed against it. It was just something I spotted and fixed. I'm not sure why it didn't make it into the 1.2 branch. You should be able to switch the jboss-logmanager JAR with a newer version though. The 1.4.3.Final should work, but if you're more comfortable doing a single version jump 1.3.2 has the commit in it as well.
James R. Perkins