Re: Address for the Apache Logging Services project

+1 for "http://logging.apache.org";. -Marco - Original Message - From: "Ceki Gülcü" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, December 18, 2003 11:40 AM Subject: Address for the Apache Logging Services project We need to decide on the address of the Apache Logging Ser

Re: NDC

Ceki Gülcü wrote: At 06:58 PM 12/17/2003 -0500, Raymond DeCampo wrote: Before I put any serious effort forward I wanted to make sure that such a change would fit in in terms of the overall vision and that I'm not missing something else that would prevent it being accepted. If one of the commit

[ANNOUNCEMENT] Apache Logging Services project

Good morning to all, The log4j developers are pleased to announce that the Board of Directors of the Apache Software Foundation unanimously passed a resolution for the creation of the Apache Logging Services project. A copy of the resolution can be found at: http://nagoya.apache.org/wiki/apachewik

Re: NDC

Ceki Gülcü wrote: Please do. You can take the MDC code as example. (For MDC code, use the latest from CVS not the code from 1.2.8). Test cases would be highly welcome. Ceki, Where's the best place to look to get up to speed on how the test cases work? Thanks, Ray -

cvs commit: jakarta-log4j/src/java/org/apache/log4j/plugins Receiver.java

psmith 2003/12/18 19:19:06 Modified:src/java/org/apache/log4j/plugins Receiver.java Log: Now fires a PropertyChangeEvent if the level changes. Revision ChangesPath 1.6 +2 -0 jakarta-log4j/src/java/org/apache/log4j/plugins/Receiver.java Index: Receiver.jav

cvs commit: jakarta-log4j/src/java/org/apache/log4j/net SocketHubReceiver.java

psmith 2003/12/18 19:19:41 Modified:src/java/org/apache/log4j/net SocketHubReceiver.java Log: now fires a PropertyChangeEvent if the Reconnection delay changes. Revision ChangesPath 1.9 +2 -0 jakarta-log4j/src/java/org/apache/log4j/net/SocketHubReceiver.jav

cvs commit: jakarta-log4j/src/java/org/apache/log4j/chainsaw/helper - New directory

psmith 2003/12/18 19:20:27 jakarta-log4j/src/java/org/apache/log4j/chainsaw/helper - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: jakarta-log4j/src/java/org/apache/log4j/chainsaw/helper TableCellEditorFactory.java

psmith 2003/12/18 19:20:31 Added: src/java/org/apache/log4j/chainsaw/helper TableCellEditorFactory.java Log: Added a helper package, and added a helper class to assist with editing tables. Revision ChangesPath 1.1 jakarta-log

cvs commit: jakarta-log4j/src/java/org/apache/log4j/chainsaw/receivers ReceiversTreeModel.java PluginPropertyEditorPanel.java ReceiversPanel.java

psmith 2003/12/18 19:21:36 Modified:src/java/org/apache/log4j/chainsaw/receivers ReceiversTreeModel.java PluginPropertyEditorPanel.java ReceiversPanel.java Log: Plugin Property editor now getting close to being pretty usable. Can

cvs commit: jakarta-log4j/src/java/org/apache/log4j/chainsaw GeneratorBeanInfo.java

psmith 2003/12/18 20:19:14 Modified:.build.xml Added: src/java/org/apache/log4j/net SocketHubReceiverBeanInfo.java src/java/org/apache/log4j/chainsaw GeneratorBeanInfo.java Log: Added 2 example BeanInfo classes for everyone to review. I have delib

cvs commit: jakarta-log4j/src/java/org/apache/log4j/chainsaw/help HelpManager.java

psmith 2003/12/18 22:50:35 Added: src/java/org/apache/log4j/chainsaw/help HelpManager.java Log: Added a singleton HelpManager so that the Help system is a little more decoupled from the implementation of the help viewer. Revision ChangesPath 1.1 jak

cvs commit: jakarta-log4j/src/java/org/apache/log4j/chainsaw WelcomePanel.java ChainsawConstants.java

psmith 2003/12/18 22:50:57 Modified:src/java/org/apache/log4j/chainsaw WelcomePanel.java ChainsawConstants.java Log: Moved out some constants into the Constants class. Revision ChangesPath 1.7 +6 -20 jakarta-log4j/src/java/org/apache/lo

cvs commit: jakarta-log4j/src/java/org/apache/log4j/chainsaw LogUI.java

psmith 2003/12/18 22:51:59 Modified:src/java/org/apache/log4j/chainsaw LogUI.java Log: GUI now registers a PropertyChangeListener on the HelpManager and sets the new URL on the Welcome panel. Revision ChangesPath 1.58 +18 -1 jakarta-log4j/src/java/org/apache/l

cvs commit: jakarta-log4j/src/java/org/apache/log4j/chainsaw/receivers ReceiversPanel.java

psmith 2003/12/18 22:54:28 Modified:src/java/org/apache/log4j/chainsaw/receivers ReceiversPanel.java Log: Start of the context sensitive help for the Plugins. You can right click on a Plugin within the Receivers panel and choose the Help menu item. Th

Plugins: BeanInfo

I would like to add a matching BeanInfo class for each of the Plugins that have been created so far. See: BeanInfo: http://java.sun.com/j2se/1.4.2/docs/api/java/beans/BeanInfo.html Introspector: http://java.sun.com/j2se/1.4.2/docs/api/java/beans/Introspector.html A BeanInfo class forms Meta-

RE: [PROPOSAL] Logging services top level project

At 02:14 PM 12/14/2003 +1100, Paul Smith wrote: I am still new to all the 'legals' side of things, and how PMC's work etc. If a sister project was unable, or unwilling to donate the code base to Apache and come under the Apache umbrella, I would still recommend that they have a role within the Logg

DO NOT REPLY [Bug 25556] - Unimplemented interface

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 25556] - Unimplemented interface

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

Re: [Chainsaw]: Proposed new LogPanel preference saving structure

At 03:03 PM 12/16/2003 +1100, Paul Smith wrote: At the end of the day I have to create a text file (.properties or .xml), is there anything within the Joran package to help with the _creating_ of the XML? (Something like Betwixt but I would rather not have another dep.) Joran should be able to do

Address for the Apache Logging Services project

We need to decide on the address of the Apache Logging Services project. Possible choices are "http://logging.apache.org"; and "http://ls.apache.org";. My preference goes with "http://logging.apache.org";. What do you think? -- Ceki Gülcü For log4j documentation consider "The complete log4j m

Re: Address for the Apache Logging Services project

or http://log.apache.org ?? Regards Siva - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

RE: Address for the Apache Logging Services project

> http://logging.apache.org +1 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

RE: Address for the Apache Logging Services project

+1 for http://logging.apache.org -Original Message- From: Ceki Gülcü [mailto:[EMAIL PROTECTED] Sent: Thursday, December 18, 2003 11:41 AM To: [EMAIL PROTECTED] Subject: Address for the Apache Logging Services project We need to decide on the address of the Apache Logging Services projec

RE: Deadlock Issue with log4J 1.2.8?

Howdy, There's no "patch" for this "issue" and AFAIK no one is actively working in this area. That's because it's not really a log4j bug. Yoav Shapira Millennium ChemInformatics -Original Message- From: Prithi [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 17, 2003 10:23 PM To: Lo

RE: Address for the Apache Logging Services project

Howdy, Definitely logging.apache.org. Yoav Shapira Millennium ChemInformatics >-Original Message- >From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] >Sent: Thursday, December 18, 2003 5:57 AM >To: [EMAIL PROTECTED] >Subject: RE: Address for the Apache Logging Services project > >+1 for

RE: Address for the Apache Logging Services project

I agree. logging.apache.org sounds good to me. +1 Jake At 08:44 AM 12/18/2003 -0500, you wrote: Howdy, Definitely logging.apache.org. Yoav Shapira Millennium ChemInformatics >-Original Message- >From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] >Sent: Thursday, December 18, 2003 5:57 A

Re: Address for the Apache Logging Services project

http://logging.apache.org for me ! Michael Selon Ceki Gülcü <[EMAIL PROTECTED]>: > > We need to decide on the address of the Apache Logging Services project. > Possible choices are "http://logging.apache.org"; and "http://ls.apache.org";. > > My preference goes with "http://logging.apache.org"

Re: Address for the Apache Logging Services project

> http://logging.apache.org +1 guilllaume moulardCeki Gülcü <[EMAIL PROTECTED]> wrote: We need to decide on the address of the Apache Logging Services project.Possible choices are "http://logging.apache.org" and "http://ls.apache.org".My preference goes with "http://logging.apache.org". What d

Re: Deadlock Issue with log4J 1.2.8?

Which version of log4j are you using? JDK? OS? Could you supply the whole stack trace? Are you redirecting System.out or System.err? At 01:04 PM 12/17/2003 -0800, Prithi wrote: We are seeing a dead lock problem with log4j, during load test. Has anyone seen this before. I have attached a sample l

Re: Deadlock Issue with log4J 1.2.8?

At 03:58 PM 12/17/2003 -0800, Elias Ross wrote: Refer to this: http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24159 If any of your objects look like this, and if you log it from one thread, and call set in another, you can deadlock. I suggest you don't do any sort of logging while holding any

Re: C++ ports was: [PROPOSAL] Logging Services

At 12:19 AM 12/16/2003 +0100, Michael CATANZARITI wrote: This summer, my company asked me to look for a logging framework in order to ingrate it into our product. I needed a logging framework in C++, so I took a look at log4cpp and log4cplus. Log4cpp is licensed under the LGPL, which was not sui

Re: NDC

At 06:58 PM 12/17/2003 -0500, Raymond DeCampo wrote: All, I was recently thinking about adding some NDC logging to my servlet, but I was concerned (perhaps unnecessarily) by some of the things I read in the docs and the source code. Since I am in a servlet container I am not in control of my th

RE: Address for the Apache Logging Services project

http://logging.apache.org +1 > -Original Message- > From: Ceki Gülcü [mailto:[EMAIL PROTECTED] > Sent: Thursday, December 18, 2003 2:41 AM > To: [EMAIL PROTECTED] > Subject: Address for the Apache Logging Services project > > > We need to decide on the address of the Apache Logging Se

RE: Address for the Apache Logging Services project

+1 -Original Message- From: Ceki Gülcü [mailto:[EMAIL PROTECTED] Sent: Thursday, December 18, 2003 2:41 AM To: [EMAIL PROTECTED] Subject: Address for the Apache Logging Services project We need to decide on the address of the Apache Logging Services project. Possible choices are "http

Re: Deadlock Issue with log4J 1.2.8?

On Thu, 2003-12-18 at 07:56, Ceki GÃlcà wrote: > >class State { > >Logger log; > > > >synchronized void setState() { > > // Something takes a long time here > > log.debug("hello world"); > >} > > > >synchronized Object getState() { > >} > > > >public String toStri

Re: Deadlock Issue with log4J 1.2.8?

At 10:04 AM 12/18/2003 -0800, Elias Ross wrote: On Thu, 2003-12-18 at 07:56, Ceki Gülcü wrote: > >class State { > >Logger log; > > > >synchronized void setState() { > > // Something takes a long time here > > log.debug("hello world"); > >} > > > >synchronized Object get

DO NOT REPLY [Bug 24159] - Log4J can create deadlock conditions

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 24159] - Log4J can create deadlock conditions

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

cvs commit: jakarta-log4j/src/java/org/apache/log4j/chainsaw ApplicationPreferenceModel.java

psmith 2003/12/18 13:33:07 Modified:src/java/org/apache/log4j/chainsaw ApplicationPreferenceModel.java Log: As part of some general package reshuffling, made this class public. Revision ChangesPath 1.8 +1 -1 jakarta-log4j/src/java/or

cvs commit: jakarta-log4j/src/java/org/apache/log4j/chainsaw ChainsawStatusBar.java

psmith 2003/12/18 13:33:30 Modified:src/java/org/apache/log4j/chainsaw ChainsawStatusBar.java Log: As part of some general package reshuffling, made this class public. Revision ChangesPath 1.7 +3 -3 jakarta-log4j/src/java/org/apache/log4j/chainsaw/ChainsawS

cvs commit: jakarta-log4j/src/java/org/apache/log4j/chainsaw Generator.java

psmith 2003/12/18 13:34:32 Modified:src/java/org/apache/log4j/chainsaw Generator.java Log: This took a LONG time to track down, but having a thread running forever while holding the syncronization lock is clearly not a good idea!! :) Revision ChangesPath 1.7 +1

cvs commit: jakarta-log4j/src/java/org/apache/log4j/chainsaw PopupListener.java

psmith 2003/12/18 13:34:58 Modified:src/java/org/apache/log4j/chainsaw PopupListener.java Log: addressed some compatibility issues with JDK 1.3.1. Thanks to Raymond DeCampo for keeping us in check. Revision ChangesPath 1.2 +2 -2 jakarta-log4j/src/java/or

Re: cvs commit: jakarta-log4j/src/java/org/apache/log4j/chainsaw PopupListener.java

Whoops, incorrect commit msg, should have been "part of the general package reshuffle". On Fri, 2003-12-19 at 08:34, [EMAIL PROTECTED] wrote: > psmith 2003/12/18 13:34:58 > > Modified:src/java/org/apache/log4j/chainsaw PopupListener.java > Log: > addressed some compatibility issues

cvs commit: jakarta-log4j/src/java/org/apache/log4j/chainsaw LogUI.java

psmith 2003/12/18 13:36:59 Modified:src/java/org/apache/log4j/chainsaw LogUI.java Log: As part of some general package reshuffling, made this some methods public. Revision ChangesPath 1.57 +2 -1 jakarta-log4j/src/java/org/apache/log4j/chainsaw/LogUI.java

cvs commit: jakarta-log4j/src/java/org/apache/log4j/chainsaw LogPanel.java

psmith 2003/12/18 13:37:38 Modified:src/java/org/apache/log4j/chainsaw LogPanel.java Log: This class no longer needed to extend Thread. Revision ChangesPath 1.42 +1 -1 jakarta-log4j/src/java/org/apache/log4j/chainsaw/LogPanel.java Index: LogPanel.java ==

cvs commit: jakarta-log4j/src/java/org/apache/log4j/chainsaw ReceiverTreeCellRenderer.java ReceiversPanel.java ReceiversTreeModel.java

psmith 2003/12/18 13:39:56 Removed: src/java/org/apache/log4j/chainsaw ReceiverTreeCellRenderer.java ReceiversPanel.java ReceiversTreeModel.java Log: These classes are being moved into a sub package in an effort to reduce the number

cvs commit: jakarta-log4j/src/java/org/apache/log4j/chainsaw/receivers - New directory

psmith 2003/12/18 13:41:40 jakarta-log4j/src/java/org/apache/log4j/chainsaw/receivers - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

DO NOT REPLY [Bug 24159] - Log4J can create deadlock conditions

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 24159] - Log4J can create deadlock conditions

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 24159] - Log4J can create deadlock conditions

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu