DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25386.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25386.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
At 02:40 AM 12/10/2003 +, [EMAIL PROTECTED] wrote:
psmith 2003/12/09 18:40:47
Modified:src/java/org/apache/log4j/pattern PatternParser.java
Added: src/java/org/apache/log4j/pattern
PropertiesPatternConverter.java
Log:
Added a Properties pattern
ceki2003/12/10 03:13:47
Modified:..cvsignore
Log:
Ignore class files
Revision ChangesPath
1.4 +1 -0 jakarta-log4j-sandbox/.cvsignore
Index: .cvsignore
===
RCS file:
ceki2003/12/10 03:15:11
Modified:..cvsignore
Log:
ignore chainsaw.jar and build.chainsaw.properties file
Revision ChangesPath
1.5 +2 -0 jakarta-log4j-sandbox/.cvsignore
Index: .cvsignore
I can't speak for Ceki, but here's my 2 cents. Some applications try
very hard to control the number of threads and other resources for
efficiency purposes. For example, application servers are usually
written in this way. In fact, the EJB specification prohibits EJB from
creating their
Hi ,
I need help as i am new in using log4j.xml .
My requirement is
1)When application uses INFO level , all the logs of the application should go into 1
log file ( say a.log)
2)when application uses DEBUG, ERROR ,FATAL level all logs of the application should
go into another log file ( say
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25386.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
At 12:22 PM 12/10/2003 +0100, Walid Joseph Gedeon wrote:
I can't speak for Ceki, but here's my 2 cents. Some applications try
very hard to control the number of threads and other resources for
efficiency purposes. For example, application servers are usually
written in this way. In fact,
This is probably something trivial but here I go.
I'd like to have two distinct web-applications running on the same
servlet container to log to different chainsaw panels.
(I am using the latest code from CVS head.)
1st attempt)
The servlet container is started with the following
At 02:02 PM 12/9/2003 -0800, Scott Deboy wrote:
Is there a reason why JDBCReceiver couldn't be moved from sandbox to
core? I recently made some fixes that improve it's performance pretty
dramatically (it was re-appending events it had previously seen)..
For folks who have no way to send events
Please post this to the use list, not the dev list. You, most likely, will
not get a valuable response here.
Jake
At 05:25 PM 12/10/2003 +0530, you wrote:
Hi ,
I need help as i am new in using log4j.xml .
My requirement is
1)When application uses INFO level , all the logs of the application
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25386.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
The version of SocketAppender that supported log4jApp was reverted...
See
http://cvs.apache.org/viewcvs.cgi/jakarta-log4j/src/java/org/apache/log4j/net/SocketAppender.java?r1=1.16r2=1.17diff_format=h
If you use another appender (multicastappender or udpappender), the properties are set.
Thanks Scott. It seems that I was too quick to revert the changes. Do you
think they are still valid?
Paul suggested that I look at the property name. He was right, the property
name should
have been be 'log4japp'.
How about if these property name were set as constants in a file, say
Sounds good..the only reason I added 'log4j' to the front of the property name was to
scope the properties to log4j-generated, not application-generated.
-Original Message-
From: Ceki Gülcü [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 10, 2003 12:31 PM
To: Log4J Developers List
I think something's wrong Chainsaw's routing..I can't get the log4japp property to
make a difference..
Time to look into it.
-Original Message-
From: Scott Deboy
Sent: Wednesday, December 10, 2003 12:34 PM
To: Log4J Developers List
Subject: RE: chainsaw with multiple tabs...
Sounds
Hey, it works for me!
At 12:40 PM 12/10/2003 -0800, you wrote:
I think something's wrong Chainsaw's routing..I can't get the log4japp
property to make a difference..
Time to look into it.
--
Ceki Gülcü
For log4j documentation consider The complete log4j manual
ISBN: 2970036908
Last evening before leaving the office, I made a note to myself to
remind me to solicit log4j-dev@ in order to add a
PropertiesPatternConverter. Imagine my surprise this morning when I
saw it just sitting in our CVS repository. :-)
We try to mind read where we can Ceki! :)
There are days
The other day I created an Ant-based install script that automatically
gets and configures everything you need to run Chainsaw v2. (see
attached script)
Does anyone think this might be useful for the -user list?
To run it, you need:
* Ant (duh...)
* CVS
It just checks out the latest
ceki2003/12/10 13:35:06
Modified:src/java/org/apache/log4j/net SocketAppender.java
UDPAppender.java SocketHubAppender.java
MulticastAppender.java XMLSocketNode.java
src/java/org/apache/log4j/chainsaw FileLoadAction.java
With the changes I just comitted, I observe a slightly different behavior.
The hostname and application name get concatenated in the tabs, which is
nice. However, there are cases when I could imagine a developer wanting to
put all logging events in the same application tab regardless of host.
This is script is a great way to circumvent the fact that there is no
official release... I feel the pressure mounting. :-)
At 08:22 AM 12/11/2003 +1100, Paul Smith wrote:
The other day I created an Ant-based install script that automatically
gets and configures everything you need to run
Scott and I have been discussing this offline over the last couple of
days. Perhaps we should forward our email thread.
this begs the question about whether Scott and I should keep our
discussions online on the list, my only concern is that we are doing a
decent amount of discussion, and I'm
On Thu, 2003-12-11 at 08:48, Ceki Glc wrote:
This is script is a great way to circumvent the fact that there is no
official release... I feel the pressure mounting. :-)
Do you think it's a bad idea to release this script? I was just
thinking it might make it more attractive for people to help
Paul Smith wrote:
What do people think? I would love everyone to participate in the
discussions, but I also don't want to saturate people either.
Saturate us! If we don't have time to read, we can always hit delete.
--
Toby Butzon [EMAIL PROTECTED]
ILC RD Co-op / Georgia Tech CS / KKPsi Iota
At 08:53 AM 12/11/2003 +1100, Paul Smith wrote:
Scott and I have been discussing this offline over the last couple of
days. Perhaps we should forward our email thread.
this begs the question about whether Scott and I should keep our
discussions online on the list, my only concern is that we are
psmith 2003/12/10 14:06:51
Modified:src/java/org/apache/log4j/pattern PatternParser.java
src/java/org/apache/log4j PatternLayout.java
Added: src/java/org/apache/log4j/pattern
ThrowableInformationPatternConverter.java
Log:
Added a
psmith 2003/12/10 14:07:16
Modified:src/java/org/apache/log4j/chainsaw/layout
DefaultDetailLayout.html
Log:
Default event detail layout can now show the stack trace.
Revision ChangesPath
1.3 +1 -1
Ok, I think we should prefix the subject line for Chainsaw related
discussions with '[Chainsaw]' so people can filter out with their mail
client as required.
Scott, you happy with this?
Paul
On Thu, 2003-12-11 at 09:06, Ceki Glc wrote:
At 08:53 AM 12/11/2003 +1100, Paul Smith wrote:
Scott and
ok
-Original Message-
From: Paul Smith [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 10, 2003 2:09 PM
To: Log4J Developers List
Subject: RE: chainsaw with multiple tabs...
Ok, I think we should prefix the subject line for Chainsaw related discussions with
'[Chainsaw]' so people
Here's my current thoughts on multiple tabs (mostly initialization time definition of
tabs):
We have the ability to look up logging event fields by keyword, using the
LoggingEventFieldResolver class.
This allows us to define expressions that can be resolved when an event shows up,
which can
For example, for the way Chainsaw currently works, the only expression
it's supporting is:
PROP.log4jmachinename-PROP.log4japp
At a minimum we should at least convert over the ChainsawAppenderHandler
code so that it is configurable, rather than how we have it now (it's a
bunch of if()'s with
We need to be able to parse the identifier, which either requires
everything to be separated by spaces (like the expressionrule requires)
or we need to delimit keywords with some character, like single quote.
Examples: Both would resolve to something like 'mybox-appname':
(spaces are removed
(spaces are removed after the event's values are retrieved)
PROP.log4jmachinename - PROP.log4japp
I like this one. We can always work out a way to make spaces not
mandatory at latter stage if it's a pain right now.
We could be smarter about it but that would require more complicated
I'll add a method to LoggingEventFieldResolver:
String applyFields(String) that returns the identifier.
Now the question of how to get chainsawappenderhandler to use the saved
property via settingsManager. That looks a little more complicated.
-Original Message-
From: Paul
On Thu, 2003-12-11 at 12:49, Scott Deboy wrote:
Now the question of how to get chainsawappenderhandler to use the saved
property via settingsManager. That looks a little more complicated.
Easy. We don't.
We can modify the Handler to have a getIdentifierExpression() + a setter
to make it a
psmith 2003/12/10 18:56:08
Modified:src/java/org/apache/log4j/chainsaw/prefs
SaveSettingsEvent.java
Log:
added support for saving a boolean property
Revision ChangesPath
1.2 +9 -0
psmith 2003/12/10 18:56:35
Added: src/java/org/apache/log4j/chainsaw
ApplicationPreferenceModel.java
Log:
added a new Application wide settings model.
Revision ChangesPath
1.1
psmith 2003/12/10 18:59:01
Modified:src/java/org/apache/log4j/chainsaw LogUI.java
NoReceiversWarningPanel.java
Log:
Modified so LogUI (the 'app') uses an ApplicationPreferenceModel
which will load and save it-' own settings. We can
add new properties to
sdeboy 2003/12/10 21:45:59
Modified:src/java/org/apache/log4j/chainsaw LogUI.java
ChainsawAppenderHandler.java
ApplicationPreferenceModel.java
LoggingEventFieldResolver.java
On Thu, 2003-12-11 at 08:44, Ceki Glc wrote:
With the changes I just comitted, I observe a slightly different behavior.
The hostname and application name get concatenated in the tabs, which is
nice. However, there are cases when I could imagine a developer wanting to
put all logging events
sdeboy 2003/12/10 22:10:27
Modified:src/java/org/apache/log4j/chainsaw
LoggingEventFieldResolver.java
Log:
removed debug msgs
Revision ChangesPath
1.15 +0 -3
sdeboy 2003/12/10 22:30:56
Modified:src/java/org/apache/log4j/chainsaw/rule NotRule.java
ExistsRule.java InequalityRule.java LikeRule.java
PartialTextMatchRule.java
Log:
Added assertions to rules to prevent problems during parsing of
44 matches
Mail list logo
