Once again thanks jake,
upgraded to 1.2.14 version and good thing is I did not encounter any
weblogic errors and my log is rolling too.
To set file name for the log dynamically, I do..
logProperties.setProperty("webApp.name", webAppName);
Is there anything similar to this for xml formatted proper
At 04:56 PM 4/13/2007, you wrote:
>
>Thanks Jake, Changing from Servlet to ServletContextListener helped,
>accordingly I changed web.xml and applications are now logging to
>independent log files.
>
>I have hit another block though with DailyRollingFileAppender, I changed one
>applications propert
Thanks Jake, Changing from Servlet to ServletContextListener helped,
accordingly I changed web.xml and applications are now logging to
independent log files.
I have hit another block though with DailyRollingFileAppender, I changed one
applications properties to use DailyRollingFileAppender to ro
At 05:13 PM 4/12/2007, you wrote:
>
>I have tried many ways to get this to work..partly successful but overall
>can't this to work. I even purchased the manual and reviewed it.
>
>Tried Log4j 1.3, It was like opening a can of worms..weblogic 8.1.6 internal
>logging complained, had to revert back t
I have tried many ways to get this to work..partly successful but overall
can't this to work. I even purchased the manual and reviewed it.
Tried Log4j 1.3, It was like opening a can of worms..weblogic 8.1.6 internal
logging complained, had to revert back to Log4j 1.2 version.
Earlier I was able
Looks mostly correct. You could change jakarta.apache.org or
logging.apache.org, but that's inconsequential. Also, you should apply a level
to the root logger, such as , or maybe set it to DEBUG for
testing.
See the Log4j Wiki [1] for links to WizardForge (look at the bottom of the
page), which
Hi jake,
Before I start using Log4j-1.3, I want to confirm if my Log4j.xml is valid
for my requirements
Below is the xml..I removed SYSTEM entry as I was getting log4j.dtd file not
found error during weblogic startup.
In this xml do I need to specify logger entry? Am I missing anything!
thanks,
Have you tried using the JNDI repository selector solution, such as
in Log4j-1.3? To test this out quickly, you could just try using
Log4j-1.3 and its ContextJNDISelector class to perform the repository
selection. I know it works. I'm not sure why you are seeing odd
results with the classl
"What do you mean "'pcs' is the log file name"? That would be the logger
name,
not the file name."
My mistake, I meant to say that it is both the logger name as well as I
named the log file name same too after the application name.
I tried with both LogFactory of commons-logging as well as direc
Quoting sohan <[EMAIL PROTECTED]>:
>
> I changed to use Log4j.xml from Log4j.properties and also changed to
> non-static loggers and with in the static methods followed the link
> examples. Now the logging is taking place only for the loggers mentioned in
> the static methods, Log log = LogFactory
I changed to use Log4j.xml from Log4j.properties and also changed to
non-static loggers and with in the static methods followed the link
examples. Now the logging is taking place only for the loggers mentioned in
the static methods, Log log = LogFactory.getLog("pcs"); pcs is the log file
name.
A
1. Use non-static loggers (for Serializable classes, you'll need to
mark these as transient)
2. Avoid Classloader-based repository selectors. Use JNDI-base
selectors. There's already one written for Log4j-1.3alpha. Even if
you don't care to use 1.3, you can use it to get an idea of how to
I followed some examples on the web to use RepositorySelector to implement
separate logging for 2 applications deployed on the same instance of
weblogic server. I have the Lgo4j.properties file under Web-Inf/ folder,
This is loaded through web.xml file through a startup servlet. Problem is
logging
13 matches
Mail list logo
