logging-log4j-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jacob Kjome <h...@visi.com>
Subject RE: [BULK] RE: log4j and WSAD 5.0 problems
Date Sat, 03 Jun 2006 22:17:10 GMT

Try forward slashes yourself under Java in Windows.  It works 
fine.  In fact, your single backslashes wouldn't work because "\" is 
a special character and would be ignored.  Your path would end up as 
"c:csslogs".  In order for what you have witten to work you'd need to 
do either...

c:\\css\\logs

OR

c:/css/logs

OR

/css/logs

If that last one surprises you, here's the rule:  the drive 
containing the directory that you start your JVM from will be 
assumed.  So, if you start your JVM from the C: drive, then 
"/css/logs" will translate to "C:/css/logs".  If you start your JVM 
from the D: drive, then "/css/logs" will translate to 
"D:/css/logs".  The nice things about this is that your config file 
can be totally free of platform specifics.  As longs as you use 
equivalent directory paths off the root of the filesystem (or drive 
on Windows), then this technique provides a syntax for using absolute 
system paths without introducing platform specifics.

Of course, this begs the question for the original poster; did you 
actually [partially] understand the technique I just described?  Are 
you using UNIX syntax on Windows, but taking care to make sure that 
the drive you start the JVM from is the C: drive, where you said this 
folder structure exists (eg... "C:/usr/wasapps/css/logs")?  If the 
JVM is being started from another drive, then that drive is going to 
need to have the folder structure.  Clearly the folder structure does 
not exist, according to Log4j, so you must still be making a bad 
assumption somewhere.


Jake

At 05:46 PM 6/2/2006, you wrote:
 >
 >Why do you have a Unix file path on a windows drive? I would think this
 >would cause lots of "unexpected" behaviour. Maybe try changing to
 >something that windows would like more?

 >Say c:\css\logs
 >
 >Cheers,
 >Philip.

 >
 >-----Original Message-----
 >From: Muthukumarasamy, Shanmugam
 >[mailto:shanmugam.muthukumarasamy@21st.com]

 >Sent: Friday, June 02, 2006 2:58 PM
 >To: Log4J Users List
 >Cc: hoju@visi.com
 >Subject: [BULK] RE: log4j and WSAD 5.0 problems
 >Importance: Low
 >
 >Yes I do have this folder structure in my C: drive. Also I have enough
 >permission on these.
 >
 >Thanks,
 >Shan

 >
 >-----Original Message-----
 >From: Jacob Kjome [mailto:hoju@visi.com]
 >Sent: Friday, June 02, 2006 2:26 PM
 >To: Log4J Users List
 >Subject: Re: log4j and WSAD 5.0 problems
 >
 >
 >
 >Does the directory "/usr/wasapps/css/logs/" exist?  Log4j won't attempt
 >to create it if it doesn't already exist.  You must make sure that the
 >full path exists.  If it does, Log4j will write the file there just fine
 >(as long as the user that started the JVM has proper permissions).
 >Otherwise, this error is to be expected.
 >
 >Jake
 >
 >Quoting "Muthukumarasamy, Shanmugam"
 ><shanmugam.muthukumarasamy@21st.com>:
 >
 >>
 >> >    Hi,
 >> >
 >> >    I am getting the following issue, When I try to start my WAS 5.0
 >
 >> > Local
 >> server in WSAD 5.0.1 Integration Edition. Please let me know if you

 >> have any guess on it.
 >> >
 >> >    [6/2/06 10:42:33:542 PDT] 6540e3f1 SystemErr     R log4j:ERROR
 >> setFile(null,true) call failed.
 >> >    [6/2/06 10:42:33:542 PDT] 6540e3f1 SystemErr     R
 >> java.io.FileNotFoundException:

 >> /usr/wasapps/css/logs/fnol-log4j-daily.log
 >> (The system cannot find the path specified)
 >> >    [6/2/06 10:42:33:542 PDT] 6540e3f1 SystemErr     R      at
 >> java.io.FileOutputStream.openAppend(Native Method)
 >> >    [6/2/06 10:42:33:542 PDT] 6540e3f1 SystemErr     R      at
 >> java.io.FileOutputStream.<init>(FileOutputStream.java:114)
 >> >    [6/2/06 10:42:33:542 PDT] 6540e3f1 SystemErr     R      at
 >> org.apache.log4j.FileAppender.setFile(FileAppender.java:272)
 >> >    [6/2/06 10:42:33:542 PDT] 6540e3f1 SystemErr     R      at
 >> org.apache.log4j.FileAppender.activateOptions(FileAppender.java:151)
 >> >    [6/2/06 10:42:33:542 PDT] 6540e3f1 SystemErr     R      at
 >>
 >org.apache.log4j.DailyRollingFileAppender.activateOptions(DailyRollingFi
 >leAppender.java:206)
 >> >    [6/2/06 10:42:33:542 PDT] 6540e3f1 SystemErr     R      at
 >> org.apache.log4j.config.PropertySetter.activate(PropertySetter.java:24
 >> 7)
 >> >    [6/2/06 10:42:33:542 PDT] 6540e3f1 SystemErr     R      at
 >> org.apache.log4j.config.PropertySetter.setProperties(PropertySetter.ja
 >> va:123)
 >> >    [6/2/06 10:42:33:542 PDT] 6540e3f1 SystemErr     R      at
 >> org.apache.log4j.config.PropertySetter.setProperties(PropertySetter.ja
 >> va:87)
 >> >    [6/2/06 10:42:33:542 PDT] 6540e3f1 SystemErr     R      at
 >>
 >org.apache.log4j.PropertyConfigurator.parseAppender(PropertyConfigurator
 >.java:645)
 >> >    [6/2/06 10:42:33:542 PDT] 6540e3f1 SystemErr     R      at
 >>
 >org.apache.log4j.PropertyConfigurator.parseCategory(PropertyConfigurator
 >.java:603)
 >> >    [6/2/06 10:42:33:558 PDT] 6540e3f1 SystemErr     R      at
 >>
 >org.apache.log4j.PropertyConfigurator.configureRootCategory(PropertyConf
 >igurator.java:500)
 >> >    [6/2/06 10:42:33:558 PDT] 6540e3f1 SystemErr     R      at
 >>
 >org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurator.j
 >ava:406)
 >> >    [6/2/06 10:42:33:558 PDT] 6540e3f1 SystemErr     R      at
 >> org.apache.log4j.PropertyConfigurator.configure(PropertyConfigurator.j
 >> ava:340)
 >> >    [6/2/06 10:42:33:558 PDT] 6540e3f1 SystemErr     R      at
 >> com.i21.claims.action.Log4jInitSrvlt.init(Log4jInitSrvlt.java:96)
 >> >    [6/2/06 10:42:33:558 PDT] 6540e3f1 SystemErr     R      at
 >> javax.servlet.GenericServlet.init(GenericServlet.java:258)
 >> >    [6/2/06 10:42:33:558 PDT] 6540e3f1 SystemErr     R      at
 >>
 >com.ibm.ws.webcontainer.servlet.StrictServletInstance.doInit(StrictServl
 >etInstance.java:82)
 >> >    [6/2/06 10:42:33:558 PDT] 6540e3f1 SystemErr     R      at
 >>
 >com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet._init(StrictLifec
 >ycleServlet.java:147)
 >> >    [6/2/06 10:42:33:558 PDT] 6540e3f1 SystemErr     R      at
 >>
 >com.ibm.ws.webcontainer.servlet.PreInitializedServletState.init(StrictLi
 >fecycleServlet.java:270)
 >> >    [6/2/06 10:42:33:558 PDT] 6540e3f1 SystemErr     R      at
 >>
 >com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet.init(StrictLifecy
 >cleServlet.java:113)
 >> >    [6/2/06 10:42:33:558 PDT] 6540e3f1 SystemErr     R      at
 >> com.ibm.ws.webcontainer.servlet.ServletInstance.init(ServletInstance.j
 >> ava:175)
 >> >    [6/2/06 10:42:33:558 PDT] 6540e3f1 SystemErr     R      at
 >> javax.servlet.GenericServlet.init(GenericServlet.java:258)
 >> >    [6/2/06 10:42:33:589 PDT] 6540e3f1 SystemErr     R      at
 >>
 >com.ibm.ws.webcontainer.webapp.WebAppServletManager.addServlet(WebAppSer
 >vletManager.java:761)
 >> >    [6/2/06 10:42:33:589 PDT] 6540e3f1 SystemErr     R      at
 >>
 >com.ibm.ws.webcontainer.webapp.WebAppServletManager.loadServlet(WebAppSe
 >rvletManager.java:257)
 >> >    [6/2/06 10:42:33:589 PDT] 6540e3f1 SystemErr     R      at
 >>
 >com.ibm.ws.webcontainer.webapp.WebAppServletManager.loadAutoLoadServlets
 >(WebAppServletManager.java:453)
 >> >    [6/2/06 10:42:33:589 PDT] 6540e3f1 SystemErr     R      at
 >> com.ibm.ws.webcontainer.webapp.WebApp.loadServletManager(WebApp.java:1
 >> 233)>
 >> >    [6/2/06 10:42:33:589 PDT] 6540e3f1 SystemErr     R      at
 >> com.ibm.ws.webcontainer.webapp.WebApp.init(WebApp.java:273)
 >> >    [6/2/06 10:42:33:589 PDT] 6540e3f1 SystemErr     R      at
 >> com.ibm.ws.webcontainer.srt.WebGroup.loadWebApp(WebGroup.java:317)
 >> >    [6/2/06 10:42:33:589 PDT] 6540e3f1 SystemErr     R      at
 >> com.ibm.ws.webcontainer.srt.WebGroup.init(WebGroup.java:194)
 >> >    [6/2/06 10:42:33:589 PDT] 6540e3f1 SystemErr     R      at
 >> com.ibm.ws.webcontainer.WebContainer.addWebApplication(WebContainer.ja
 >> va:950)
 >> >    [6/2/06 10:42:33:589 PDT] 6540e3f1 SystemErr     R      at
 >>
 >com.ibm.ws.runtime.component.WebContainerImpl.install(WebContainerImpl.j
 >ava:133)
 >> >    [6/2/06 10:42:33:605 PDT] 6540e3f1 SystemErr     R      at
 >> com.ibm.ws.runtime.component.WebContainerImpl.start(WebContainerImpl.j
 >> ava:360)
 >> >    [6/2/06 10:42:33:605 PDT] 6540e3f1 SystemErr     R      at
 >>
 >com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl
 >.java:401)
 >> >    [6/2/06 10:42:33:605 PDT] 6540e3f1 SystemErr     R      at
 >>
 >com.ibm.ws.runtime.component.DeployedApplicationImpl.fireDeployedObjectS
 >tart(DeployedApplicationImpl.java:743)
 >> >    [6/2/06 10:42:33:605 PDT] 6540e3f1 SystemErr     R      at
 >>
 >com.ibm.ws.runtime.component.DeployedModuleImpl.start(DeployedModuleImpl
 >.java:337)
 >> >    [6/2/06 10:42:33:605 PDT] 6540e3f1 SystemErr     R      at
 >>
 >com.ibm.ws.runtime.component.DeployedApplicationImpl.start(DeployedAppli
 >cationImpl.java:531)
 >> >    [6/2/06 10:42:33:605 PDT] 6540e3f1 SystemErr     R      at
 >>
 >com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication(Applica
 >tionMgrImpl.java:254)
 >> >    [6/2/06 10:42:33:605 PDT] 6540e3f1 SystemErr     R      at
 >>
 >com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl
 >.java:232)
 >> >    [6/2/06 10:42:33:605 PDT] 6540e3f1 SystemErr     R      at
 >>
 >com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl
 >.java:343)
 >> >    [6/2/06 10:42:33:605 PDT] 6540e3f1 SystemErr     R      at
 >> com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:23
 >> 4)
 >> >    [6/2/06 10:42:33:605 PDT] 6540e3f1 SystemErr     R      at
 >>
 >com.ibm.ws.runtime.component.ApplicationServerImpl.start(ApplicationServ
 >erImpl.java:117)
 >> >    [6/2/06 10:42:33:605 PDT] 6540e3f1 SystemErr     R      at
 >>
 >com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl
 >.java:343)
 >> >    [6/2/06 10:42:33:605 PDT] 6540e3f1 SystemErr     R      at
 >> com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:23
 >> 4)
 >> >    [6/2/06 10:42:33:605 PDT] 6540e3f1 SystemErr     R      at
 >> com.ibm.ws.runtime.component.ServerImpl.start(ServerImpl.java:182)
 >> >    [6/2/06 10:42:33:605 PDT] 6540e3f1 SystemErr     R      at
 >> com.ibm.ws.runtime.WsServer.start(WsServer.java:135)
 >> >    [6/2/06 10:42:33:605 PDT] 6540e3f1 SystemErr     R      at
 >> com.ibm.ws.runtime.WsServer.main(WsServer.java:232)
 >> >    [6/2/06 10:42:33:620 PDT] 6540e3f1 SystemErr     R      at
 >> java.lang.reflect.Method.invoke(Native Method)
 >> >    [6/2/06 10:42:33:620 PDT] 6540e3f1 SystemErr     R      at
 >> com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:94)
 >> >    [6/2/06 10:42:33:620 PDT] 6540e3f1 SystemErr     R      at
 >>
 >com.ibm.etools.websphere.tools.runner.api.ServerRunnerV5$1.run(ServerRun
 >nerV5.java:97)
 >> >    [6/2/06 10:42:33:620 PDT] 6540e3f1 SystemErr     R log4j:ERROR
 >Either File
 >> or DatePattern options are not set for appender [daily].
 >> >
 >> >
 >> >    Thanks,
 >> >    Shan Muthukumarasamy
 >> >    Information Services
 >> >    Programmer/Analyst Sr.
 >> >    Tel : (818) 715-6581
 >> >    Fax: (818) 715-6123
 >> >    shanmugam.muthukumarasamy@21st.com
 >> >
 >> >
 >> >
 >>
 >> **********************************************************************
 >> * This e-mail and any files transmitted with it are intended solely

 >> for the use of the addressee.  This e-mail may contain confidential

 >> and/or legally privileged information.
 >> Any review, transmission, disclosure, copying, or any action taken or

 >> not taken, by other than the intended recipient, in reliance on the

 >> information, is prohibited.  If you received this e-mail in error,

 >> notify the sender and delete this e-mail (and any accompanying

 >> material) from your computer and network. In addition, please be

 >> advised that 21st Century Insurance Group reserves the right to

 >> monitor, access and review all messages, data and images transmitted

 >> through our electronic mail system. By using our e-mail system, you

 >> consent to this monitoring.
 >> **********************************************************************
 >> *
 >>
 >>
 >>
 >> ---------------------------------------------------------------------
 >> To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
 >> For additional commands, e-mail: log4j-user-help@logging.apache.org
 >>
 >
 >
 >
 >
 >---------------------------------------------------------------------
 >To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
 >For additional commands, e-mail: log4j-user-help@logging.apache.org
 >
 >
 >
 >***********************************************************************
 >This e-mail and any files transmitted with it are intended solely for
 >the use of the addressee.  This e-mail may contain confidential and/or
 >legally privileged information.

 >Any review, transmission, disclosure, copying, or any action taken or
 >not taken, by other than the intended recipient, in reliance on the
 >information, is prohibited.  If you received this e-mail in error,
 >notify the sender and delete this e-mail (and any accompanying material)
 >from your computer and network. In addition, please be advised that 21st
 >Century Insurance Group reserves the right to monitor, access and review
 >all messages, data and images transmitted through our electronic mail
 >system. By using our e-mail system, you consent to this monitoring.

 >***********************************************************************
 >
 >
 >
 >---------------------------------------------------------------------
 >To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
 >For additional commands, e-mail: log4j-user-help@logging.apache.org
 >
 >
 >
 >
 >
 >
 >
 >
 >IMPORTANT NOTICE
 >Email from TSI Terminal Systems Inc. (TSI) is confidential and may be
 >legally privileged. If it is not intended for you, please delete it
 >immediately unread. Under no circumstances should this e-mail be
 >redistributed without prior written consent of TSI.  The internet
 >cannot guarantee that this communication is free of viruses,
 >interception or interference and anyone who communicates with us by
 >email is taken to accept the risks in so doing. Without limitation,
 >TSI and its affiliates accept no liability whatsoever and howsoever
 >arising in connection with the use of this email. Under no
 >circumstances shall this email constitute a binding agreement for
 >provision of services by TSI, which is subject to the terms and
 >conditions of TSI's standard schedule for Terminal Tariffs which is
 >also available at http://www.tsi.bc.ca.
 >
 >---------------------------------------------------------------------
 >To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
 >For additional commands, e-mail: log4j-user-help@logging.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-user-help@logging.apache.org


Mime
View raw message