Hi,

First of all, let me say thanks to all the developers for making such a
great product available.  I am currently trying to resolve an issue related
to reading the log4j configuration from an xml file contained in a WAR.  I
have browsed through the archives and found some seemly related issues but
not a specific answer.

When I call DOMConfigurator.doConfigure(url, hierarchy), I get the stack
trace included below.  I have the log4j jars placed in the lib dir of the
WAR, and the xml config file in the WEB-INF/classes dir.  Here is the code
snippet that fails:

    URL file = this.getClass().getResource("/log4j-config.xml");

    DOMConfigurator config = new DOMConfigurator();
    config.doConfigure(file, Category.getDefaultHierarchy());

The file URL resolves to:

zip:C:/bea/wlserver6.0sp1/config/mydomain/applications/.wl_temp_do_not_delet
e/wl_local_comp63005.war#WEB-INF/classes/log-config.xml

I have a suspicion this is related to classloaders or permissions.  When I
put the log4j jars in the weblogic startup classpath, everything works
great.

TIA,
Anthony


Stack trace:

log4j:ERROR Could not parse input stream
[weblogic.utils.zip.SafeZipFileInputStream@6f3a22].
java.util.zip.ZipException: The system cannot find the file specified
        at java.util.zip.ZipFile.open(Native Method)
        at java.util.zip.ZipFile.<init>(ZipFile.java:110)
        at java.util.zip.ZipFile.<init>(ZipFile.java:125)
        at
weblogic.utils.zip.ZipURLConnection.getInputStream(Handler.java:49)
        at java.net.URL.openStream(URL.java:798)
        at
weblogic.apache.xerces.readers.DefaultReaderFactory.createReader(DefaultRead
erFactory.java:149)
        at
weblogic.apache.xerces.readers.DefaultEntityHandler.startReadingFromExternal
Entity(DefaultEntityHandler.java:
775)
        at
weblogic.apache.xerces.readers.DefaultEntityHandler.startReadingFromExternal
Subset(DefaultEntityHandler.java:
570)
        at
weblogic.apache.xerces.framework.XMLDTDScanner.scanDoctypeDecl(XMLDTDScanner
java:1131)
        at
weblogic.apache.xerces.framework.XMLDocumentScanner.scanDoctypeDecl(XMLDocum
entScanner.java:2177)
        at
weblogic.apache.xerces.framework.XMLDocumentScanner.access$0(XMLDocumentScan
ner.java:2133)
        at
weblogic.apache.xerces.framework.XMLDocumentScanner$PrologDispatcher.dispatc
h(XMLDocumentScanner.java:882)
        at
weblogic.apache.xerces.framework.XMLDocumentScanner.parseSome(XMLDocumentSca
nner.java:380)
        at
weblogic.apache.xerces.framework.XMLParser.parse(XMLParser.java:900)
        at
weblogic.apache.xerces.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImplja
va:123)
        at
weblogic.xml.jaxp.RegistryDocumentBuilder.parse(RegistryDocumentBuilder.java
:98)
        at
org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:572)
        at com.qwest.cplus.util.Logger.configure(Logger.java:61)
        at
com.qwest.cplus.web.ControllerServlet.init(ControllerServlet.java:127)
        at javax.servlet.GenericServlet.init(GenericServlet.java:258)
        at
weblogic.servlet.internal.ServletStubImpl.createServlet(ServletStubImpl.java
:638)
        at
weblogic.servlet.internal.ServletStubImpl.createInstances(ServletStubImplja
va:581)
        at
weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.jav
a:526)
        at
weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java:30
6)
        at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:208)
        at
weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletCo
ntext.java:1265)
        at
weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java
:1622)
        at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
        at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
log4j:ERROR No appenders could be found for category
(com.qwest.cplus.web.ControllerServlet).
log4j:ERROR Please initialize the log4j system properly.


-----
Anthony Baker, [EMAIL PROTECTED]
503.748.8197 

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to