cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 6224] New: - Logging not reloading properly with reloadable=true on servlet context
Date Mon, 04 Feb 2002 16:17:59 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6224>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6224

Logging not reloading properly with reloadable=true on servlet context

           Summary: Logging not reloading properly with reloadable=true on
                    servlet context
           Product: Cocoon 2
           Version: Current CVS
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: core
        AssignedTo: cocoon-dev@xml.apache.org
        ReportedBy: proyal@managingpartners.com


Cocoon works fine until I recompile a class which causes tomcat (3.2.1) to
reload the servlet context. I get the following error on the tomcat console:

Logging Error: Could not set up Cocoon Logger, will use screen instead
java.lang.ClassCastException: org.apache.avalon.excalibur.logger.factory.Priorit
                                                         yFilterTargetFactory
        at org.apache.avalon.excalibur.logger.DefaultLogTargetFactoryManager.con
                                                        
figure(DefaultLogTargetFactoryManager.java:102)
        at org.apache.avalon.excalibur.logger.DefaultLogKitManager.setupTargetFa
                                                        
ctoryManager(DefaultLogKitManager.java:194)
        at org.apache.avalon.excalibur.logger.DefaultLogKitManager.configure(Def
                                                         aultLogKitManager.java:157)
        at org.apache.cocoon.servlet.CocoonServlet.initLogger(CocoonServlet.java
                                                         :587)
        at org.apache.cocoon.servlet.CocoonServlet.init(CocoonServlet.java:168)
        at org.apache.tomcat.core.ServletWrapper.doInit(ServletWrapper.java:317)
        at org.apache.tomcat.core.Handler.init(Handler.java:215)
        at org.apache.tomcat.core.ServletWrapper.init(ServletWrapper.java:296)
        at org.apache.tomcat.core.Handler.service(Handler.java:254)
        at org.apache.tomcat.core.ServletWrapper.service(ServletWrapper.java:372
                                                         )
        at org.apache.tomcat.core.ContextManager.internalService(ContextManager.
                                                         java:797)
        at org.apache.tomcat.core.ContextManager.service(ContextManager.java:743
                                                         )
        at org.apache.tomcat.service.http.HttpConnectionHandler.processConnectio
                                                        
n(HttpConnectionHandler.java:210)
        at org.apache.tomcat.service.TcpWorkerThread.runIt(PoolTcpEndpoint.java:
                                                         416)
        at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java
                                                         :498)
        at java.lang.Thread.run(Thread.java:484)


If this rings a bell with someone, go for it, otherwise it hasn't quite yet
reached my annoyance level to drop and fix it. (Getting close though :)

---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Mime
View raw message