- This topic has 1 reply, 2 voices, and was last updated 17 years, 9 months ago by Riyad Kalla.
-
AuthorPosts
-
nalbionMemberI’m trying to deploy a web app on JBoss 4.0.5.GA, but get the following error.
What’s frustrating is that I’m not even exporting log4j.jar. I’m also using JBoss’ version (see .classpath below)11:14:43,484 INFO [TomcatDeployer] deploy, ctxPath=/mojoWeb, warUrl=…/deploy/mojoWeb.war/
11:14:43,625 INFO [WebappClassLoader] validateJarFile(C:\sw_dev\java\jboss-4.0.5.GA\server\default\.\deploy\mojoWeb.war\WEB-INF\lib\selenium-server.jar) – jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class: javax/servlet/Servlet.class
11:14:43,765 ERROR [STDERR] log4j:ERROR A “org.jboss.logging.util.OnlyOnceErrorHandler” object is not assignable to a “org.apache.log4j.spi.ErrorHandler” variable.
11:14:43,765 ERROR [STDERR] log4j:ERROR The class “org.apache.log4j.spi.ErrorHandler” was loaded by
11:14:43,765 ERROR [STDERR] log4j:ERROR [WebappClassLoader
delegate: false
repositories:
/WEB-INF/classes/
———-> Parent Classloader:
java.net.FactoryURLClassLoader@5c775d
] whereas object of type
11:14:43,765 ERROR [STDERR] log4j:ERROR “org.jboss.logging.util.OnlyOnceErrorHandler” was loaded by [org.jboss.system.server.NoAnnotationURLClassLoader@1c92535].
11:14:43,843 ERROR [STDERR] log4j:ERROR Could not create an Appender. Reported error follows.
11:14:43,843 ERROR [STDERR] java.lang.ClassCastException: org.jboss.logging.appender.DailyRollingFileAppender cannot be cast to org.apache.log4j.Appender
11:14:43,843 ERROR [STDERR] at org.apache.log4j.xml.DOMConfigurator.parseAppender(DOMConfigurator.java:165)———- .classpath ———-
<?xml version=”1.0″ encoding=”UTF-8″?>
<classpath>
<classpathentry excluding=”net/sourceforge/wurfl/|net/sourceforge/wurfl/wall/” kind=”src” output=”WebRoot/WEB-INF/classes” path=”src”/>
<classpathentry kind=”src” output=”build” path=”test”/>
<classpathentry kind=”con” path=”org.eclipse.jdt.launching.JRE_CONTAINER”/>
<classpathentry kind=”con” path=”com.genuitec.eclipse.j2eedt.core.J2EE14_CONTAINER”/>
<classpathentry kind=”lib” path=”WebRoot/WEB-INF/lib/tomahawk.jar”/>
<classpathentry kind=”lib” path=”WebRoot/WEB-INF/lib/jsf-impl.jar”/>
<classpathentry kind=”lib” path=”WebRoot/WEB-INF/lib/myfaces-all.jar”/>
<classpathentry exported=”true” kind=”lib” path=”WebRoot/WEB-INF/lib/struts.jar”/>
<classpathentry kind=”lib” path=”WebRoot/WEB-INF/lib/jstl.jar”/>
<classpathentry kind=”lib” path=”WebRoot/WEB-INF/lib/standard.jar”/>
<classpathentry kind=”lib” path=”WebRoot/WEB-INF/lib/xom-1.0.jar”/>
<classpathentry combineaccessrules=”false” kind=”src” path=”/mojoWebEJB”/>
<classpathentry exported=”true” kind=”lib” path=”/mojoWebEJB/lib/oscache-2.3.2.jar”/>
<classpathentry kind=”con” path=”org.eclipse.jdt.USER_LIBRARY/HtmlUnit”/>
<classpathentry kind=”var” path=”JUNIT_HOME/junit.jar” sourcepath=”ECLIPSE_HOME/plugins/org.eclipse.jdt.source_3.1.0/src/org.junit_3.8.1/junitsrc.zip”/>
<classpathentry kind=”lib” path=”C:/sw_dev/java/j2ee/lib/testng/testng-5.1-jdk15.jar”/>
<classpathentry kind=”lib” path=”C:/sw_dev/java/j2ee/lib/selenium-remote-control-0.8.1/server/selenium-server.jar”/>
<classpathentry exported=”true” kind=”lib” path=”C:/Documents and Settings/nick/workspace/tools/java/wurflapi-xom/antbuild/wurfltags.jar” sourcepath=”/Wurfl Java API/src”/>
<classpathentry kind=”lib” path=”WebRoot/WEB-INF/lib/switcher.jar”/>
<classpathentry kind=”lib” path=”lib/wapunit0.9.5.jar” sourcepath=”/WapStack”/>
<classpathentry kind=”con” path=”org.eclipse.jdt.USER_LIBRARY/JBoss 4.0.5″/>
<classpathentry kind=”output” path=”WebRoot/WEB-INF/classes”/>
</classpath>
Riyad KallaMember<classpathentry kind=”lib” path=”C:/sw_dev/java/j2ee/lib/selenium-remote-control-0.8.1/server/selenium-server.jar”/>
This is your offending entry (read your error, higher up). It looks like for build purposes you are including a server-JAR in your build path. The only problem is that when you then deploy the project, you are re-deploying this server JAR back to itself, and causing the load violation. You will either need to not include this in your path, or adjust the deployment rules under your project properties then MyEclipse > Web> Deployment, to not deploy that *type* of JAR.
-
AuthorPosts