Help Desk Ticket Reference: https://na7.salesforce.com/500A0000006kZea Steps to Reproduce: start brms-standalone using the default profile securitylevel_name: Public With a brms standalone install, the following error appears in the server logs -- 16:11:30,691 ERROR [STDERR] SLF4J: Class path contains multiple SLF4J bindings. 16:11:30,691 ERROR [STDERR] SLF4J: Found binding in [vfszip:/opt/jboss/brms-standalone-5.1.0/jboss-as-web/common/lib/slf4j-jboss-logging.jar/org/slf4j/impl/StaticLoggerBinder.class] 16:11:30,691 ERROR [STDERR] SLF4J: Found binding in [vfszip:/opt/jboss/brms-standalone-5.1.0/jboss-as-web/server/default/deploy/jboss-brms.war/WEB-INF/lib/slf4j-log4j12-1.6.0.jar/org/slf4j/impl/StaticLoggerBinder.class] -- SLF4j should not be packaged with jboss-brms.war A similar issue is raised in https://issues.jboss.org/browse/JBAS-8541
Link: Added: This issue duplicates BRMS-432
BRMS-standalone should not include the slf4j jars...agreed. Simple workaround could be to go to /brms-standalone-5.1.0.GA/jboss-as-web/server/default/deploy/jboss-brms.war/WEB-INF/lib and delete slf4j-api-1.6.0.jar and slf4j-log4j12-1.6.0.jar.
GSS prioritizes 'High'.
This issue is no longer existed in BRMS 5.2.0. flag: jboss‑brms‑5.2.0 can be removed.
Ok, moving it to MODIFIED so that we can make sure it is gone.
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: https://bugzilla.redhat.com/show_bug.cgi?id=724672 SLF4j jar files were incorrectly packaged in jboss-brms.war and caused start errors. These jars have been removed and the problem no longer persists.
Technical note updated. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1,3 +1 @@ -https://bugzilla.redhat.com/show_bug.cgi?id=724672 - SLF4j jar files were incorrectly packaged in jboss-brms.war and caused start errors. These jars have been removed and the problem no longer persists.
Technical note updated. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1 +1 @@ -SLF4j jar files were incorrectly packaged in jboss-brms.war and caused start errors. These jars have been removed and the problem no longer persists.+SLF4j jar files were packaged in jboss-brms.war and caused initialization errors. These jars have been removed and the problem no longer persists.
Fix verified in 5.2.0 ER4.
Technical note updated. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1 +1 @@ -SLF4j jar files were packaged in jboss-brms.war and caused initialization errors. These jars have been removed and the problem no longer persists.+SLF4j jar files were incorrectly packaged in jboss-brms.war and caused initialization errors. These jars have been removed and the problem no longer persists.