geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vamsavardhana Reddy (JIRA)" <...@geronimo.apache.org>
Subject [jira] Created: (GERONIMO-1746) Updates to Logger through Log Manager portlet under Console are not reflected in the server
Date Thu, 16 Mar 2006 06:35:05 GMT
Updates to Logger through Log Manager portlet under Console are not reflected in the server
-------------------------------------------------------------------------------------------

         Key: GERONIMO-1746
         URL: http://issues.apache.org/jira/browse/GERONIMO-1746
     Project: Geronimo
        Type: Bug
  Components: console, Logging  
    Versions: 1.0    
 Environment: Win XP, Sun JDK 1.4.2_08
    Reporter: Vamsavardhana Reddy
     Fix For: 1.2


Changes made to the logger through Log Manager portlet are not reflected in the server.  Through
the admin console, I have changed the Config File from server-log4j.properties to a different
file.  The change is written to config.xml .  Inspite of this new file name in config.xml,
upon restart, the server still uses server-log4j.properties  .

Restarting the server after deleting server-log4j.properties logged the following error to
console window.

log4j:ERROR Could not read configuration file from URL [file:/C:/geronimo-1.0/va
r/log/server-log4j.properties].
java.io.FileNotFoundException: C:\geronimo-1.0\var\log\server-log4j.properties (
The system cannot find the file specified)
        at java.io.FileInputStream.open(Native Method)
        at java.io.FileInputStream.<init>(Unknown Source)
        at java.io.FileInputStream.<init>(Unknown Source)
        at sun.net.www.protocol.file.FileURLConnection.connect(Unknown Source)
        at sun.net.www.protocol.file.FileURLConnection.getInputStream(Unknown So
urce)
        at java.net.URL.openStream(Unknown Source)
        at org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurato
r.java:424)
        at org.apache.geronimo.system.logging.log4j.URLConfigurator.doConfigure(
URLConfigurator.java:117)
        at org.apache.geronimo.system.logging.log4j.URLConfigurator.configure(UR
LConfigurator.java:44)
        at org.apache.geronimo.system.logging.log4j.Log4jService.reconfigure(Log
4jService.java:518)
        at org.apache.geronimo.system.logging.log4j.Log4jService.doStart(Log4jSe
rvice.java:561)
        at org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanI
nstance.java:936)
        at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart
(GBeanInstanceState.java:325)
        at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInsta
nceState.java:110)
        at org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(G
BeanInstanceState.java:132)
        at org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanI
nstance.java:537)
        at org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(Basi
cKernel.java:208)
        at org.apache.geronimo.kernel.config.Configuration.startRecursiveGBeans(
Configuration.java:315)
        at org.apache.geronimo.kernel.config.Configuration$$FastClassByCGLIB$$7f
4b4a9b.invoke(<generated>)
        at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53)
        at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethod
Invoker.java:38)
        at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperatio
n.java:118)
        at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.
java:835)
        at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:
178)
        at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:
173)
        at org.apache.geronimo.system.main.Daemon.doStartup(Daemon.java:286)
        at org.apache.geronimo.system.main.Daemon.<init>(Daemon.java:82)
        at org.apache.geronimo.system.main.Daemon.main(Daemon.java:404)
log4j:ERROR Ignoring configuration file [file:/C:/geronimo-1.0/var/log/server-lo
g4j.properties].

-- 
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


Mime
View raw message