Hi,
option (b):
File configFile = ...
Properties properties = new Properties();
properties.load(new FileInputStream(configFile));
properties.setProperty("webapp.name", webappName);
PropertyConfigurator.configure(properties);
=> haven't
Did you ever try setting log4j.debug=true in your property file? What does it
spit out to the console? I don't recall if you can set this as a system
property or not? Look at LogManager.java for something like "log4j.debug". In
that case, you could do -Dlog4j.debug=true.
If you see no output
I think log4j.properties is being read by the application. I verified this in
the same way you mentioned.
1. Wrote a method in my Struts Action to read the "log4j.configuration" from
system variables. Using the value read by this variable, I did a
fileinputstream and loaded into Properties. The
It's probably that the config file never gets put in the classpath when you run
as a service. I think you've claimed previously that you verified that it was
in the classpath, but that's hard to believe.
Why don't you do this. In some class (or a JSP), try to load up the config file
as an input
Jacob,
So, I got 1.2.14 version of log4j and ran the application as a service and
manually. I plugged in eclipse debugger to see where the problem was. I found
that when I run manually, the appenders are getting created. Specifically,
variable 'aai' has an instance of AppenderAttachableImpl for
Quoting Henning Sprang <[EMAIL PROTECTED]>:
> Hi,
> I want to use the JMSAppender class in a simple environment, where we
> don't have a jndi service running. Because I have not so much
> knowledge about JNDI and we simply don't need it.
>
You should look into Spring's Mock classes. Specifically
Hi,
I want to use the JMSAppender class in a simple environment, where we
don't have a jndi service running. Because I have not so much
knowledge about JNDI and we simply don't need it.
I tried a lot and searched the docs for hours now, but could not find
how this can simply be accomplished - any
That's an intersting idea. You can post an enhancement report in bugzilla along
with your implementation. However, I'm not sure if this would be something that
would go into Log4j-1.2.xx because it is pretty much in bugfix mode. New
development is on the trunk for the 1.3.xx releases.
The way
Hello,
I know that PropertyConfigurator support placeholders
and will resolve them using System properties or properties in the
configuration file
being parsed.
But what if I would like to supply properties (for the placeholders)
at runtime ?
suppose I have this in my config file:
log4j.appende
