On Jun 4, 2007, at 7:44 PM, Steve Souza wrote:
<>
Not sure who controls the website, but that direction should be
updated on
the site as currently it indicates log4j 1.3 is the future. Not
everyone is
on this mailing list.
A total reworking of the online content is in-progress. All the
Thanks for you help by the way :)
On 6/4/07, Steve Souza <[EMAIL PROTECTED]> wrote:
<>
Not sure who controls the website, but that direction should be updated on
the site as currently it indicates log4j 1.3 is the future. Not everyone
is on this mailing list.
<>
Where is the sandbox code kep
<>
Not sure who controls the website, but that direction should be updated on
the site as currently it indicates log4j 1.3 is the future. Not everyone is
on this mailing list.
<>
Where is the sandbox code kept? Also, will the release you are referring
too be available in this link:
http://archi
On Jun 4, 2007, at 5:44 PM, Steve Souza wrote:
I am interested in using a Log4j 1.3 SocketReceiver for JAMon to
receive
LoggingEvents. I have a couple questions
1) Per the following link I see the first release of log4j 1.3 was
in 2004,
and it still hasn't had a beta let alone been releas
I am interested in using a Log4j 1.3 SocketReceiver for JAMon to receive
LoggingEvents. I have a couple questions
1) Per the following link I see the first release of log4j 1.3 was in 2004,
and it still hasn't had a beta let alone been released. Are there any plans
on releasing 1.3? Does anyon
Yep - but
1 - Time Synched backups are pain when you need to see what is going on
in production "right now"
And
2 - That means getting different departments involved inorder to create
backups and/or network shares and all the attendent securing of the
shares (adding and removing allowed users
You could have your IT folks rsync the log file regularly to a location that
you have access to , and then use whatever tools you want for slicing & dicing
the log file (including Chainsaw).
You can also use VFSLogFilePatternReceiver with Chainsaw to access the log file
from its original locati
Looks Nice. I'll be out of pocket this week - but I'll be giving it a
run when I get back.
I have never understand the sparcity of web enabled tools for log4j. A
project that is sponsored by an organization that also produces TOMCAT.
I guess all the effort has gone into Chainsaw, which is really
1. No.
2,3. http://logging.apache.org/log4j/docs/manual.html
4. Attach two appenders to the one logger.
5. No.
On 6/1/07, untz <[EMAIL PROTECTED]> wrote:
Hello there,
I am using an init servlet to load my log4j.properties file during app start
up...
public class Log4jInitServlet extends Http
This was just discussed. See
http://www.nabble.com/DailyRollingFileAppender-for-multiple-threads-tf3752882.html#a1084
On 5/30/07, Daniel Abrecht <[EMAIL PROTECTED]> wrote:
Can i configure Log4j that i get for eacht java-thread a log file?
--
View this message in context:
http://www.nabble.
Is it possible that log4j is being configured twice because AFAIK
configuration doesn't happen in the background?
Also log4j config messages aren't generally sent to your logs unless
you have log4j debugging turned on and use a ConsoleAppender.
On 5/26/07, Rich Adili <[EMAIL PROTECTED]> wrote:
11 matches
Mail list logo
