-
1. Re: jboss-as-7.1.0.Final Stack Trace not being logged from SLF4J
jamezp May 14, 2013 12:31 PM (in response to steine_locus)This was fixed in the available EAP 6.1.Alpha and Beta. There is an upgrade to slf4j and the JBoss slf4j bridge. Essentially the formatter in slf4j wasn't checking for exception parameters.
--
James R. Perkins
-
2. Re: jboss-as-7.1.0.Final Stack Trace not being logged from SLF4J
steine_locus May 14, 2013 12:36 PM (in response to jamezp)Thanks. What is an EAP 6.1 and where do I get it?
Eric
-
3. Re: jboss-as-7.1.0.Final Stack Trace not being logged from SLF4J
jamezp May 14, 2013 12:40 PM (in response to steine_locus)Sorry about that. I totally meant to add the link and sent the reply before I did You can download it at http://www.jboss.org/jbossas/downloads/ and get more information at http://www.redhat.com/products/jbossenterprisemiddleware/community-enterprise/. Also a good read is http://www.jboss.org/jbossas/faq
--
James R. Perkins
-
4. Re: jboss-as-7.1.0.Final Stack Trace not being logged from SLF4J
steine_locus May 14, 2013 12:57 PM (in response to jamezp)Oh, wait. Is this a matter of copying a new jar file into an existing installation, or do I have to migrate my entire development team and all our servers?
Eric
-
5. Re: jboss-as-7.1.0.Final Stack Trace not being logged from SLF4J
jamezp May 14, 2013 1:27 PM (in response to steine_locus)You could try just changing the JAR's. You would need to update the root resources in the module.xml. The org.slf4j, org.slf4j.impl, org.slf4j.ext, org.slf4j.jcl-over-slf4j and org.jboss.logging.jul-to-slf4j-stub modules would need to be upgraded. It's probably easiest to download EAP 6.1.Beta and copy the module.xml and the dependencies to their respective places.
There are quite a few bug fixes in JBoss EAP 6.1 FWIW.
--
James R. Perkins