[ http://issues.apache.org/jira/browse/JCR-477?page=all ]
Edgar Poce resolved JCR-477:
----------------------------
Resolution: Fixed
Hi Darren,
IMO these are unrelated problems.
1)
13:20:48,857 INFO [STDOUT] log4j:ERROR A
"org.jboss.logging.util.OnlyOnceErrorHandler" object is not assignable to a "o
rg.apache.log4j.spi.ErrorHandler" variable.
I think this is caused by a duplicated jar in your deployment, we should
probably update the instructions at
http://wiki.apache.org/jackrabbit/JackrabbitOnJBoss.
A quick fix would be to remove log4j from the war and remove all the lines in
the log4j.xml descriptor.
e.g.
WEB-INF/log4j.xml:
<?xml version="1.0" encoding="UTF-8" ?>
<!DOCTYPE log4j:configuration SYSTEM "log4j.dtd">
<log4j:configuration xmlns:log4j="http://jakarta.apache.org/log4j/";>
</log4j:configuration>
2)
java.lang.IllegalStateException: Inactive logical session handle called
at
org.apache.jackrabbit.jca.JCAManagedConnection.getSession(JCAManagedConnection.java:214)
This problem is caused by a problem in a logging call which afaik shouldn't
affect the servlet normal behaviour. it's fixed in rev. 421405
br,
edgar
> Deployment of webdav servlet on Jboss problem - logging
> -------------------------------------------------------
>
> Key: JCR-477
> URL: http://issues.apache.org/jira/browse/JCR-477
> Project: Jackrabbit
> Type: Bug
> Components: webdav
> Environment: SVN build of JCR-Server (post version 1.0.1/pre 1.1), Win2000,
> Sun JDK 1.5_06, Jboss 4.0.4.GA/4.0.3SP1
> Reporter: Darren Hartford
>
> Tested two different installs of JBoss to verify problem is not related to a
> specific version. There is a problem with the jackrabbit-server.war when
> deploying on jboss. Here are the details during deployment:
> =======================
> 13:20:48,654 INFO [TomcatDeployer] deploy, ctxPath=/jackrabbit-server,
> warUrl=.../deploy/jackrabbit-server.war/
> 13:20:48,857 INFO [STDOUT] log4j:ERROR A
> "org.jboss.logging.util.OnlyOnceErrorHandler" object is not assignable to a
> "o rg.apache.log4j.spi.ErrorHandler" variable.
> 13:20:48,857 INFO [STDOUT] log4j:ERROR The class
> "org.apache.log4j.spi.ErrorHandler" was loaded by
> 13:20:48,857 INFO [STDOUT] log4j:ERROR [WebappClassLoader
> delegate: false
> repositories:
> /WEB-INF/classes/
> ----------> Parent Classloader:
> [EMAIL PROTECTED]
> ] whereas object of type
> 13:20:48,857 INFO [STDOUT] log4j:ERROR
> "org.jboss.logging.util.OnlyOnceErrorHandler" was loaded by
> [org.jboss.system.se [EMAIL PROTECTED]
> 13:20:48,904 INFO [STDOUT] log4j:ERROR Could not create an Appender.
> Reported error follows.
> 13:20:48,904 INFO [STDOUT] java.lang.ClassCastException:
> org.jboss.logging.appender.DailyRollingFileAppender
> 13:20:48,904 INFO [STDOUT] at
> org.apache.log4j.xml.DOMConfigurator.parseAppender(DOMConfigurator.java:165)
> 13:20:48,904 INFO [STDOUT] at
> org.apache.log4j.xml.DOMConfigurator.findAppenderByName(DOMConfigurator.java:140)
> 13:20:48,904 INFO [STDOUT] at
> org.apache.log4j.xml.DOMConfigurator.findAppenderByReference(DOMConfigurator.java:153
> )
> 13:20:48,904 INFO [STDOUT] at
> org.apache.log4j.xml.DOMConfigurator.parseChildrenOfLoggerElement(DOMConfigurator.jav
> a:415)
> 13:20:48,904 INFO [STDOUT] at
> org.apache.log4j.xml.DOMConfigurator.parseRoot(DOMConfigurator.java:384)
> 13:20:48,904 INFO [STDOUT] at
> org.apache.log4j.xml.DOMConfigurator.parse(DOMConfigurator.java:783)
> 13:20:48,904 INFO [STDOUT] at
> org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:666)
> 13:20:48,904 INFO [STDOUT] at
> org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:616)
> 13:20:48,904 INFO [STDOUT] at
> org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:602)
> 13:20:48,904 INFO [STDOUT] at
> org.apache.log4j.helpers.OptionConverter.selectAndConfigure(OptionConverter.java:460)
> 13:20:48,904 INFO [STDOUT] at
> org.apache.log4j.LogManager.<clinit>(LogManager.java:113)
> 13:20:48,904 INFO [STDOUT] at
> org.apache.log4j.xml.DOMConfigurator.configure(DOMConfigurator.java:543)
> 13:20:48,904 INFO [STDOUT] at
> org.apache.jackrabbit.j2ee.LoggingServlet.configureXML(LoggingServlet.java:148)
> 13:20:48,904 INFO [STDOUT] at
> org.apache.jackrabbit.j2ee.LoggingServlet.configure(LoggingServlet.java:115)
> 13:20:48,904 INFO [STDOUT] at
> org.apache.jackrabbit.j2ee.LoggingServlet.init(LoggingServlet.java:86)
> ======================
>
> Unlike most logging problems, this is having an impact during runtime - when
> trying to do DASL searches, will return a 500 error as the server was unable
> to log correctly.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
