Re: Logging - What good is it ?
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 log4j content is expected to be replaced after the completion of the log4j 1.2.15 vote.> Where is the sandbox code kept? https://svn.apache.org/repos/asf/logging/sandbox All the companions that are currently expected to be considered alongside log4j 1.2.15 have now been migrated to https:// svn.apache.org/repos/asf/logging/log4j/companions. Also, will the release you are referring too be available in this link: http://archive.apache.org/dist/logging/log4j/ After the anticipated log4j 1.2.15 vote, all the companions would be available at http://www.apache.org/dist/logging/log4j/companions (and also at the archive site). Release candidates should be at http:// people.apache.org/builds/logging tomorrow. If not what is the proper link to look at the current state of development for the log4j project? The web content typically reflects the state at the last release and in this case is extremely stale since it reflects the expectations at the time of the last log4j 1.3 alpha (since the web content for log4j is generated from the log4j 1.3 source). log4j-dev will always be the place for the latest news, but the web content should be much more current after the switch with the log4j 1.2.15 vote. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Logging - What good is it ?
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 kept? Also, will the release you are referring too be available in this link: http://archive.apache.org/dist/logging/log4j/ If not what is the proper link to look at the current state of development for the log4j project? On 6/4/07, Curt Arnold <[EMAIL PROTECTED]> wrote: > > > 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 released. Are there > > any plans > > on releasing 1.3? Does anyone know if the alpha is stable? > > http://archive.apache.org/dist/logging/log4j/ > > > > 2) Are there any tutorials or documenation on using the new > > SocketReceiver? > > > > log4j 1.3 development is effectively abandoned. Much of the traffic > on the log4j-dev list since early April has dealt with the fate of > log4j 1.3. > > Many features from log4j 1.3 have been backported to work with log4j > 1.2 in the last two months and packaged as "companions" for log4j > 1.2.x and Chainsaw has been rebased to work with log4j 1.2 and a > couple of the companions. SocketReceiver is part of the "receivers" > companion. I'm just in the process of migrating the companions from > the sandbox to the log4j repo and should have a release candidate in > a day or so. As for documentation, I don't know of any other than > the code comments. > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
Re: Logging - What good is it ?
<> 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://archive.apache.org/dist/logging/log4j/ If not what is the proper link to look at the current state of development for the log4j project? On 6/4/07, Curt Arnold <[EMAIL PROTECTED]> wrote: 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 released. Are there > any plans > on releasing 1.3? Does anyone know if the alpha is stable? > http://archive.apache.org/dist/logging/log4j/ > > 2) Are there any tutorials or documenation on using the new > SocketReceiver? > log4j 1.3 development is effectively abandoned. Much of the traffic on the log4j-dev list since early April has dealt with the fate of log4j 1.3. Many features from log4j 1.3 have been backported to work with log4j 1.2 in the last two months and packaged as "companions" for log4j 1.2.x and Chainsaw has been rebased to work with log4j 1.2 and a couple of the companions. SocketReceiver is part of the "receivers" companion. I'm just in the process of migrating the companions from the sandbox to the log4j repo and should have a release candidate in a day or so. As for documentation, I don't know of any other than the code comments. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Logging - What good is it ?
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 released. Are there any plans on releasing 1.3? Does anyone know if the alpha is stable? http://archive.apache.org/dist/logging/log4j/ 2) Are there any tutorials or documenation on using the new SocketReceiver? log4j 1.3 development is effectively abandoned. Much of the traffic on the log4j-dev list since early April has dealt with the fate of log4j 1.3. Many features from log4j 1.3 have been backported to work with log4j 1.2 in the last two months and packaged as "companions" for log4j 1.2.x and Chainsaw has been rebased to work with log4j 1.2 and a couple of the companions. SocketReceiver is part of the "receivers" companion. I'm just in the process of migrating the companions from the sandbox to the log4j repo and should have a release candidate in a day or so. As for documentation, I don't know of any other than the code comments. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Logging - What good is it ?
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 anyone know if the alpha is stable? http://archive.apache.org/dist/logging/log4j/ 2) Are there any tutorials or documenation on using the new SocketReceiver? On 6/4/07, Slaughter, Stan <[EMAIL PROTECTED]> wrote: 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 when ever people join the group or leave). Possible - but time consuming to arrange and maintain - and since they are not the same department responible for setting up the production servers you can run into a the problem of the backup/share no longer working if the production system gets upgraded a year or two from now. A web based answere that migrates with our actual production code is the answere which gives my department the greatest control over our environment. Application Architect [EMAIL PROTECTED] Ext 6418 -Original Message- From: "Scott Deboy" <[EMAIL PROTECTED]>@FDC Sent: Monday, June 04, 2007 9:44 AM To: Log4J Users List Subject: RE: Logging - What good is it ? 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 location if you can get to it using one of VFS's supported file systems (sftp, for example, allows you to get to files only available via ssh) - they could restrict access for the user that's configured to read the log file so it has access to nothing else. http://jakarta.apache.org/commons/vfs/filesystems.html Scott Deboy COMOTIV SYSTEMS 111 SW Columbia Street Ste. 950 Portland, OR 97201 Telephone: 503.224.7496 Cell: 503.997.1367 Fax:503.222.0185 [EMAIL PROTECTED] www.comotivsystems.com -Original Message- From: Slaughter, Stan [mailto:[EMAIL PROTECTED] Sent: Mon 6/4/2007 7:20 AM To: Log4J Users List; [EMAIL PROTECTED] Subject: RE: Logging - What good is it ? 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 an internal network tool. P.S. The way my company breaks down who does what does seem insane - at first glance. The reality is that it's a pretty common seperation of labor in large organizations that are concerned about security. As a developer it is still pretty frustrating though. :) Application Architect [EMAIL PROTECTED] -Original Message- From: Steve Souza [mailto:[EMAIL PROTECTED] Sent: Sunday, June 03, 2007 3:44 PM To: Log4J Users List Subject: Re: Logging - What good is it ? I just released JAMon 2.6 today, and as mentioned in this thread it has a log4j tie-in. The primary focus of this release was to create an Appender that addresses the Original Posters problem. - Allows JAMon to keep realtime aggregate statistics for logs (i.e how many errors are in my log? when did they last occur? how many users have unsuccessfully logged in? and much more) - Allows JAMon to 'tail' different aspects of your log via a web application. With this you will be able to view your logs via web pages. No coding changes are required to take advantage of this new JAMonAppender. Simply modify your log4j xml or property configuration file. Previous releases of JAMon could already keep statistics for all SQL that is executed, and for all page hits that occur. These features also do not require code changes. Here is some more info. I updated the wiki link with more infomation about the JAMonAppender. For full information about this release go to http://jamonapi.sourceforge.net/log4j_jamonappender If you would like to see a live demo of JAMon go to: http://www.ssouza.com/jamon JAMon is an open source performance tuning API, suitable for production environments. See http://www.jamonapi.com for full info. On 6/1/07, Arthur Blake <[EMAIL PROTECTED]> wrote: > > JAMon looks like a pretty neat tool. Almost a full-fledged profiler... > I also noticed it has a lot of cross over with my program log4jdbc (see > http://log4jdbc.sourceforge.net) > actually JAmon does a lot more, but it is interesting to see some of your > ideas because I have some similar > ideas for log4jdbc (ability to generically time interfaces, etc.) > > Speaking of the Wiki... how
RE: Logging - What good is it ?
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 when ever people join the group or leave). Possible - but time consuming to arrange and maintain - and since they are not the same department responible for setting up the production servers you can run into a the problem of the backup/share no longer working if the production system gets upgraded a year or two from now. A web based answere that migrates with our actual production code is the answere which gives my department the greatest control over our environment. Application Architect [EMAIL PROTECTED] Ext 6418 -Original Message- From: "Scott Deboy" <[EMAIL PROTECTED]>@FDC Sent: Monday, June 04, 2007 9:44 AM To: Log4J Users List Subject: RE: Logging - What good is it ? 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 location if you can get to it using one of VFS's supported file systems (sftp, for example, allows you to get to files only available via ssh) - they could restrict access for the user that's configured to read the log file so it has access to nothing else. http://jakarta.apache.org/commons/vfs/filesystems.html Scott Deboy COMOTIV SYSTEMS 111 SW Columbia Street Ste. 950 Portland, OR 97201 Telephone: 503.224.7496 Cell: 503.997.1367 Fax:503.222.0185 [EMAIL PROTECTED] www.comotivsystems.com -Original Message- From: Slaughter, Stan [mailto:[EMAIL PROTECTED] Sent: Mon 6/4/2007 7:20 AM To: Log4J Users List; [EMAIL PROTECTED] Subject: RE: Logging - What good is it ? 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 an internal network tool. P.S. The way my company breaks down who does what does seem insane - at first glance. The reality is that it's a pretty common seperation of labor in large organizations that are concerned about security. As a developer it is still pretty frustrating though. :) Application Architect [EMAIL PROTECTED] -Original Message- From: Steve Souza [mailto:[EMAIL PROTECTED] Sent: Sunday, June 03, 2007 3:44 PM To: Log4J Users List Subject: Re: Logging - What good is it ? I just released JAMon 2.6 today, and as mentioned in this thread it has a log4j tie-in. The primary focus of this release was to create an Appender that addresses the Original Posters problem. - Allows JAMon to keep realtime aggregate statistics for logs (i.e how many errors are in my log? when did they last occur? how many users have unsuccessfully logged in? and much more) - Allows JAMon to 'tail' different aspects of your log via a web application. With this you will be able to view your logs via web pages. No coding changes are required to take advantage of this new JAMonAppender. Simply modify your log4j xml or property configuration file. Previous releases of JAMon could already keep statistics for all SQL that is executed, and for all page hits that occur. These features also do not require code changes. Here is some more info. I updated the wiki link with more infomation about the JAMonAppender. For full information about this release go to http://jamonapi.sourceforge.net/log4j_jamonappender If you would like to see a live demo of JAMon go to: http://www.ssouza.com/jamon JAMon is an open source performance tuning API, suitable for production environments. See http://www.jamonapi.com for full info. On 6/1/07, Arthur Blake <[EMAIL PROTECTED]> wrote: > > JAMon looks like a pretty neat tool. Almost a full-fledged profiler... > I also noticed it has a lot of cross over with my program log4jdbc (see > http://log4jdbc.sourceforge.net) > actually JAmon does a lot more, but it is interesting to see some of your > ideas because I have some similar > ideas for log4jdbc (ability to generically time interfaces, etc.) > > Speaking of the Wiki... how does one get a program added on there? > I tooled around there for a bit and couldn't find any obvious way to add > something to the Wiki... > I would like to get a link to log4jdbc up there... > > Arthur Blake > > - Original Message > From: Jacob Kjome <[EMAIL PROTECTED]> > To: Log4J Users List ; [EMAIL PROTECTED] > Sent: Thursday, May 31, 2007 2:07:45 PM > Subject: Re: Logging - What good is it ? > > > Please add a link to JAMon in the Log4j Wiki. It sounds very useful! > > http://wi
RE: Logging - What good is it ?
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 location if you can get to it using one of VFS's supported file systems (sftp, for example, allows you to get to files only available via ssh) - they could restrict access for the user that's configured to read the log file so it has access to nothing else. http://jakarta.apache.org/commons/vfs/filesystems.html Scott Deboy COMOTIV SYSTEMS 111 SW Columbia Street Ste. 950 Portland, OR 97201 Telephone: 503.224.7496 Cell: 503.997.1367 Fax:503.222.0185 [EMAIL PROTECTED] www.comotivsystems.com -Original Message- From: Slaughter, Stan [mailto:[EMAIL PROTECTED] Sent: Mon 6/4/2007 7:20 AM To: Log4J Users List; [EMAIL PROTECTED] Subject: RE: Logging - What good is it ? 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 an internal network tool. P.S. The way my company breaks down who does what does seem insane - at first glance. The reality is that it's a pretty common seperation of labor in large organizations that are concerned about security. As a developer it is still pretty frustrating though. :) Application Architect [EMAIL PROTECTED] -Original Message- From: Steve Souza [mailto:[EMAIL PROTECTED] Sent: Sunday, June 03, 2007 3:44 PM To: Log4J Users List Subject: Re: Logging - What good is it ? I just released JAMon 2.6 today, and as mentioned in this thread it has a log4j tie-in. The primary focus of this release was to create an Appender that addresses the Original Posters problem. - Allows JAMon to keep realtime aggregate statistics for logs (i.e how many errors are in my log? when did they last occur? how many users have unsuccessfully logged in? and much more) - Allows JAMon to 'tail' different aspects of your log via a web application. With this you will be able to view your logs via web pages. No coding changes are required to take advantage of this new JAMonAppender. Simply modify your log4j xml or property configuration file. Previous releases of JAMon could already keep statistics for all SQL that is executed, and for all page hits that occur. These features also do not require code changes. Here is some more info. I updated the wiki link with more infomation about the JAMonAppender. For full information about this release go to http://jamonapi.sourceforge.net/log4j_jamonappender If you would like to see a live demo of JAMon go to: http://www.ssouza.com/jamon JAMon is an open source performance tuning API, suitable for production environments. See http://www.jamonapi.com for full info. On 6/1/07, Arthur Blake <[EMAIL PROTECTED]> wrote: > > JAMon looks like a pretty neat tool. Almost a full-fledged profiler... > I also noticed it has a lot of cross over with my program log4jdbc (see > http://log4jdbc.sourceforge.net) > actually JAmon does a lot more, but it is interesting to see some of your > ideas because I have some similar > ideas for log4jdbc (ability to generically time interfaces, etc.) > > Speaking of the Wiki... how does one get a program added on there? > I tooled around there for a bit and couldn't find any obvious way to add > something to the Wiki... > I would like to get a link to log4jdbc up there... > > Arthur Blake > > - Original Message > From: Jacob Kjome <[EMAIL PROTECTED]> > To: Log4J Users List ; [EMAIL PROTECTED] > Sent: Thursday, May 31, 2007 2:07:45 PM > Subject: Re: Logging - What good is it ? > > > Please add a link to JAMon in the Log4j Wiki. It sounds very useful! > > http://wiki.apache.org/logging-log4j/Log4JProjectPages > > > Jake > > On Thu, 31 May 2007 12:39:29 -0400 > "Steve Souza" <[EMAIL PROTECTED]> wrote: > > I am the author of the open source monitoring tool JAMon available at > > http://www.jamonapi.com. > > > > I have just written a log4j appender that passes all log messages > through to > > JAMon which allows for a couple nice things to happen. It will allow > you to > > 'tail' your logs in real time and view them from a web page. This gets > > around the problem of not having access to the log. JAMon also will > allow > > aggregation of log4j messages and Levels (How many times was this log > > message called? How many times was error called and when was it last > > called?) > > > > Here is some more info about the appender. If you haven't used jamon > look > > into it as it compliments log4j very nicely. > > > > 1) With the JAMonAppender you will get summary numbers on how many times > the > > log methods of the different levels
RE: Logging - What good is it ?
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 an internal network tool. P.S. The way my company breaks down who does what does seem insane - at first glance. The reality is that it's a pretty common seperation of labor in large organizations that are concerned about security. As a developer it is still pretty frustrating though. :) Application Architect [EMAIL PROTECTED] -Original Message- From: Steve Souza [mailto:[EMAIL PROTECTED] Sent: Sunday, June 03, 2007 3:44 PM To: Log4J Users List Subject: Re: Logging - What good is it ? I just released JAMon 2.6 today, and as mentioned in this thread it has a log4j tie-in. The primary focus of this release was to create an Appender that addresses the Original Posters problem. - Allows JAMon to keep realtime aggregate statistics for logs (i.e how many errors are in my log? when did they last occur? how many users have unsuccessfully logged in? and much more) - Allows JAMon to 'tail' different aspects of your log via a web application. With this you will be able to view your logs via web pages. No coding changes are required to take advantage of this new JAMonAppender. Simply modify your log4j xml or property configuration file. Previous releases of JAMon could already keep statistics for all SQL that is executed, and for all page hits that occur. These features also do not require code changes. Here is some more info. I updated the wiki link with more infomation about the JAMonAppender. For full information about this release go to http://jamonapi.sourceforge.net/log4j_jamonappender If you would like to see a live demo of JAMon go to: http://www.ssouza.com/jamon JAMon is an open source performance tuning API, suitable for production environments. See http://www.jamonapi.com for full info. On 6/1/07, Arthur Blake <[EMAIL PROTECTED]> wrote: > > JAMon looks like a pretty neat tool. Almost a full-fledged profiler... > I also noticed it has a lot of cross over with my program log4jdbc (see > http://log4jdbc.sourceforge.net) > actually JAmon does a lot more, but it is interesting to see some of your > ideas because I have some similar > ideas for log4jdbc (ability to generically time interfaces, etc.) > > Speaking of the Wiki... how does one get a program added on there? > I tooled around there for a bit and couldn't find any obvious way to add > something to the Wiki... > I would like to get a link to log4jdbc up there... > > Arthur Blake > > - Original Message > From: Jacob Kjome <[EMAIL PROTECTED]> > To: Log4J Users List ; [EMAIL PROTECTED] > Sent: Thursday, May 31, 2007 2:07:45 PM > Subject: Re: Logging - What good is it ? > > > Please add a link to JAMon in the Log4j Wiki. It sounds very useful! > > http://wiki.apache.org/logging-log4j/Log4JProjectPages > > > Jake > > On Thu, 31 May 2007 12:39:29 -0400 > "Steve Souza" <[EMAIL PROTECTED]> wrote: > > I am the author of the open source monitoring tool JAMon available at > > http://www.jamonapi.com. > > > > I have just written a log4j appender that passes all log messages > through to > > JAMon which allows for a couple nice things to happen. It will allow > you to > > 'tail' your logs in real time and view them from a web page. This gets > > around the problem of not having access to the log. JAMon also will > allow > > aggregation of log4j messages and Levels (How many times was this log > > message called? How many times was error called and when was it last > > called?) > > > > Here is some more info about the appender. If you haven't used jamon > look > > into it as it compliments log4j very nicely. > > > > 1) With the JAMonAppender you will get summary numbers on how many times > the > > log methods of the different levels have been called (i.e. > > DEBUG/WARN/INFO/ERROR/FATAL), and when they were most recently > called. This > > info is viewable in a sortable report in the jamon.war. > > > > 2) JAMon has buffers that let you via a web page view the last N > > (configurable) log messages that have been sent to the various > Levels. This > > allows you to view the LoggingEvent in a sortable/queriable web > page. This > > works similar to tail in that it doesn't have all rows, but only the > most > > recent. By default this value is set to 100, but it can be increased to > > whatever size is desireable. > > > > 3) You can count how many times messages of a certain format have been > > called. For example say you have a message: Invalid login by 'ssouza'. > > JAMon can generalize this message (Invalid login by ?) and count how > many > > times it has been called, and can put the last N of this message type in > a > > buffer that will allow you to look at the original detailed message. > > > > 4) It is easy to
Re: File and Console Appenders question
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 HttpServlet {
public void init() throws ServletException {
Properties props = new Properties();
try {
props.load(this.getClass().getClassLoader().getResourceAsStream(
"/log4j.properties"));
} catch (IOException e) {
e.printStackTrace();
}
}
}
The log4j.properties file:
log4j.rootLogger=WARN, stdout
log4j.logger.acme.myapp=DEBUG
log4j.appender.stdout=org.apache.log4j.ConsoleAppender
log4j.appender.stdout.layout=org.apache.log4j.PatternLayout
log4j.appender.stdout.layout.ConversionPattern=%d %p [%c] - %m%n
Question(s):
(1)
Let's say I want to use a file appender for logging different parts of
the app's behavior, do I need to create a different properties file?
(2) If not, how would I integrate that with the properties file above?
(3) Is there a way I set the DEBUG warning to just log to the Console and the
LOG warning to just log to specific files (which I specify)?
(4) What if I wanted two separate log files generated for the file appender?
(e.g. one being for cars.log and another one being planes.log)
(5) Do I have to create a different init servlet and different properties file?
Happy programming,
--
James Staufferhttp://www.geocities.com/stauffer_james/
Are you good? Take the test at http://www.livingwaters.com/good/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Threadlogging
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.com/Threadlogging-tf3840256.html#a10873317 Sent from the Log4j - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- James Staufferhttp://www.geocities.com/stauffer_james/ Are you good? Take the test at http://www.livingwaters.com/good/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Proper startup order?
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:
Hi,
I'm rather new to logging and having some trouble pinning down the
proper startup sequence. Current code appears below. If "dosomething"
writes to the log, the output is mingled with the log4j initialization
output. Users find this rather confusing. How can I delay my stuff until
log4j has finished speaking its piece?
DOMConfigurator.configureAndWatch("conf/log4j.xml");
org.apache.commons.logging.Log log =
LogFactory.getFactory().getInstance(Xatanet.class);
dosomething(log);
Rich
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
James Staufferhttp://www.geocities.com/stauffer_james/
Are you good? Take the test at http://www.livingwaters.com/good/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
