This is due to Logger implementation conflict of aribaweb and JBoss AS7.
JBoss AS7 supports Log4J implementation by default. But in the case of JBoss AS7 server org.apache.log4j.Logger
class is wrapped by its own implementation which is org.jboss.logmanager.log4j.BridgeLogger
. In the case of aribaweb org.apache.log4j.Logger
class is wrapped by aribas implementation (ariba.util.log.Logger
). For resolving this issue you need to remove the JBoss AS7's log4j module dependency from your war file. For that you need to create a jboss-deployment-structure.xml
file with following lines of codes
<?xml version="1.0" encoding="UTF-8"?>
<jboss-deployment-structure>
<deployment>
<exclusions>
<module name="org.apache.log4j" />
</exclusions>
</deployment>
</jboss-deployment-structure>
and you need to deploy this file in META-INF folder of your war file.