DO NOT REPLY [Bug 45304] using log4j with OAS for some reasone all the logging activty hangs from all the applications deployed
https://issues.apache.org/bugzilla/show_bug.cgi?id=45304 --- Comment #2 from Amgad Muhammad [EMAIL PROTECTED] 2008-07-03 00:49:09 PST --- (In reply to comment #1) Please provide additional information on this issue. Can you provide a small example which behaves like you describe? I'm using log4j on Oracle Application Server.and i'm configuring the log4j from a property file not on runtime, and am using category instead of logger. everything is working fine but suddenly all the logging activity hangs. to restore the logging activity i have to restart the OC4j. non from the applications deployed on the OC4J configure the log4j on runtime so it's configured only once on startup. i need to know what is causing this. --- example of loading the log4j: private org.apache.log4j.Category logger; logger = org.apache.log4j.Category.getInstance(ZainKSABilling); --- does the deprecated method getinstance could have something to do with this issue? -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 45304] using log4j with OAS for some reasone all the logging activty hangs from all the applications deployed
https://issues.apache.org/bugzilla/show_bug.cgi?id=45304 --- Comment #3 from Thorbjørn Ravn Andersen [EMAIL PROTECTED] 2008-07-03 03:53:43 PST --- Please provide the property file you use, and a thread dump (JVM and OS dependant) of OC4J of the situation where logging has stopped. My guess is that this is a resource deadlock. How many web applications do you run in OC4J? -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 42171] SocketHubReceiver duplicates messages
https://issues.apache.org/bugzilla/show_bug.cgi?id=42171 Thorbjørn Ravn Andersen [EMAIL PROTECTED] changed: What|Removed |Added CC||[EMAIL PROTECTED] --- Comment #3 from Thorbjørn Ravn Andersen [EMAIL PROTECTED] 2008-07-03 03:57:12 PST --- I have seen this behaviour in ChainSaw within the last month, and as the original poster indicated after some use. I am using ZeroConf to configure, and rerunning the programs doing the logging. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 45304] using log4j with OAS for some reasone all the logging activty hangs from all the applications deployed
https://issues.apache.org/bugzilla/show_bug.cgi?id=45304 Amgad Muhammad [EMAIL PROTECTED] changed: What|Removed |Added Attachment #22212|application/octet-stream|text/plain mime type|| -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 45304] using log4j with OAS for some reasone all the logging activty hangs from all the applications deployed
https://issues.apache.org/bugzilla/show_bug.cgi?id=45304 --- Comment #5 from Amgad Muhammad [EMAIL PROTECTED] 2008-07-03 04:33:08 PST --- I'll provide the thread dump as soon as the hanging starts -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r673744 - /logging/log4j/companions/receivers/trunk/src/main/java/org/apache/log4j/db/CustomSQLDBReceiver.java
Author: sdeboy
Date: Thu Jul 3 10:49:08 2008
New Revision: 673744
URL: http://svn.apache.org/viewvc?rev=673744view=rev
Log:
Update the customsqldbreceiver javadoc to make it even more clear that the
user's db columns don't have to have the same name/contain all of the same
columns (can be ALIASed).
Modified:
logging/log4j/companions/receivers/trunk/src/main/java/org/apache/log4j/db/CustomSQLDBReceiver.java
Modified:
logging/log4j/companions/receivers/trunk/src/main/java/org/apache/log4j/db/CustomSQLDBReceiver.java
URL:
http://svn.apache.org/viewvc/logging/log4j/companions/receivers/trunk/src/main/java/org/apache/log4j/db/CustomSQLDBReceiver.java?rev=673744r1=673743r2=673744view=diff
==
---
logging/log4j/companions/receivers/trunk/src/main/java/org/apache/log4j/db/CustomSQLDBReceiver.java
(original)
+++
logging/log4j/companions/receivers/trunk/src/main/java/org/apache/log4j/db/CustomSQLDBReceiver.java
Thu Jul 3 10:49:08 2008
@@ -119,11 +119,12 @@
* or save the events to XML for later analysis.
* p
* Here is a complete MySQL SQL statement which can be used to provide events
to
- * Chainsaw:
+ * Chainsaw (note how in the example below, there is no column in logtable
representing the throwable, so an
+ * empty string is passed in and an ALIAS is still defined):
* p
- * select logger as LOGGER, timestamp as TIMESTAMP, level as LEVEL, thread as
- * THREAD, message as MESSAGE, ndc as NDC, mdc as MDC, class as CLASS, method
as
- * METHOD, file as FILE, line as LINE,
+ * select myloggercolumn as LOGGER, mytimestampcolumn as TIMESTAMP,
mylevelcolumn as LEVEL, mythreadcolumn as
+ * THREAD, mymessagecolumn as MESSAGE, myndccolumn as NDC, mymdccolumn as MDC,
myclasscolumn as CLASS, mymethodcolumn as
+ * METHOD, myfilecolumn as FILE, mylinecolumn as LINE,
* concat({{application,databaselogs,hostname,mymachine, log4jid,,
* COUNTER,}}) as PROPERTIES, as THROWABLE from logtable
* p
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 40990] Cannot bind port or ip address for outgoing UDP socket when using SysLogAppender
https://issues.apache.org/bugzilla/show_bug.cgi?id=40990 Thorbjørn Ravn Andersen [EMAIL PROTECTED] changed: What|Removed |Added CC||[EMAIL PROTECTED] --- Comment #2 from Thorbjørn Ravn Andersen [EMAIL PROTECTED] 2008-07-03 12:28:03 PST --- (In reply to comment #0) I suggest that a fix should be implemented to use a parameterized constructor instead such that users may set configurations such that the socket can be bounded to a user-defined port and/or local address. Is it possible to write a testcase for this? If so, would you do so? What would be reasonable names for these parameters? port and inetaddress? -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 42851] Adding Goto Line feature to Chainsaw log panel
https://issues.apache.org/bugzilla/show_bug.cgi?id=42851 --- Comment #4 from Thorbjørn Ravn Andersen [EMAIL PROTECTED] 2008-07-03 12:45:00 PST --- Is there any pending actions on this bug report? I understand that the patch correcting the original issue has been applied, so it might be reasonable to change this from NEW to CLOSED/FIXED. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 39691] DBAppender doesn't log long events
https://issues.apache.org/bugzilla/show_bug.cgi?id=39691 --- Comment #2 from Thorbjørn Ravn Andersen [EMAIL PROTECTED] 2008-07-03 12:50:23 PST --- (In reply to comment #1) Truncation should be the resposibility of the appender, since it has the domain knowledge on the length to trim at. It should be expected that the logger logs as much as it can of the data it gets, so I disagree with this. The suggested code contains magical constants - 3800, 254 and 230 - which should be better documented. Best would be if the creation scripts use the same values to create the needed tables, otherwise they may get out of synchronization later. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 45335] New: NDC.remove NullPointerException
https://issues.apache.org/bugzilla/show_bug.cgi?id=45335 Summary: NDC.remove NullPointerException Product: Log4j Version: 1.2 Platform: PC OS/Version: Linux Status: NEW Severity: major Priority: P2 Component: Other AssignedTo: log4j-dev@logging.apache.org ReportedBy: [EMAIL PROTECTED] calling NDC.remove during tomcat shutdown results in a NullPointerException Jul 3, 2008 1:09:51 PM org.apache.coyote.http11.Http11BaseProtocol destroy INFO: Stopping Coyote HTTP/1.1 on http-8080 Jul 3, 2008 1:09:51 PM org.apache.catalina.core.AprLifecycleListener lifecycleEvent INFO: Failed shutdown of Apache Portable Runtime Exception in thread error java.lang.NullPointerException at org.apache.log4j.NDC.remove(NDC.java:377) at ProcessMonitor$1.run(ProcessMonitor.java:44) at java.lang.Thread.run(Thread.java:619) Exception in thread exit java.lang.NullPointerException Exception in thread response at org.apache.log4j.NDC.remove(NDC.java:377) at ProcessMonitor$2.run(ProcessMonitor.java:83) at java.lang.Thread.run(Thread.java:619) java.lang.NullPointerException at org.apache.log4j.NDC.remove(NDC.java:377) at ProcessMonitor$3.run(ProcessMonitor.java:114) at java.lang.Thread.run(Thread.java:619) Glancing at the source for NDC.java it appears the the ht hashtable variable is null at this point in the tomcat shutdown sequence. I notice that some of the other places in NDC that refer to ht check that it is not null. Two other minor things I notice in NDC: 1. bogus comment // The synchronized keyword is not used in this class. This may seem // dangerous, especially since the class will be used by // multiple-threads. In particular, all threads share the same // hashtable (the ht variable). This is OK since java hashtables // are thread safe. Same goes for Stacks. However the lazyRemove method synchronizes on ht while checking the pushCounter. 2. another bogus comment // The number of times we allow push to be called before we call lazyRemove // 5 is a relatively small number. As such, lazyRemove is not called too // frequently. We thus avoid the cost of creating an Enumeration too often. // The higher this number, the longer is the avarage period for which all // logging calls in all threads are blocked. static final int REAP_THRESHOLD = 5; The lazyRemove method is NOT called by push, it is only called by remove. Cheers, Derek -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 42851] Adding Goto Line feature to Chainsaw log panel
https://issues.apache.org/bugzilla/show_bug.cgi?id=42851 Scott Deboy [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 44700] Log4J locks rolled log files
https://issues.apache.org/bugzilla/show_bug.cgi?id=44700 Thorbjørn Ravn Andersen [EMAIL PROTECTED] changed: What|Removed |Added CC||[EMAIL PROTECTED] --- Comment #1 from Thorbjørn Ravn Andersen [EMAIL PROTECTED] 2008-07-03 12:56:34 PST --- Can you please provide the log4j.xml file as an attachment for the issue reported? Also please describe the applications running in the WAS6 server. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 44765] SyslogAppender should not attempt to remove inital tabs from stack trace lines
https://issues.apache.org/bugzilla/show_bug.cgi?id=44765 Thorbjørn Ravn Andersen [EMAIL PROTECTED] changed: What|Removed |Added CC||[EMAIL PROTECTED] --- Comment #1 from Thorbjørn Ravn Andersen [EMAIL PROTECTED] 2008-07-03 12:59:07 PST --- Is there any reason why this behaviour should NOT be changed to include all characters logged? Does the first character have special meaning in syslog messages? -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 37182] Exception from exception toString() causes log4j to fail
https://issues.apache.org/bugzilla/show_bug.cgi?id=37182 Thorbjørn Ravn Andersen [EMAIL PROTECTED] changed: What|Removed |Added CC||[EMAIL PROTECTED] --- Comment #4 from Thorbjørn Ravn Andersen [EMAIL PROTECTED] 2008-07-03 13:09:05 PST --- This is an issue with those classes which implement ObjectRenderer. The DefaultRenderer (which is called here) just do a return o.toString(); and it would be reasonable to return some dummy value if o was null. Just return null or null perhaps? AttributesRenderer and ThreadGroupRenderer do an instanceof, UTObjectRenderer just returns a parmeters, so this should be the only location which need patching. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 43403] PatternLayout: new format modifer: prefix if non-empty
https://issues.apache.org/bugzilla/show_bug.cgi?id=43403 --- Comment #2 from Thorbjørn Ravn Andersen [EMAIL PROTECTED] 2008-07-03 13:12:06 PST --- If the functionality is available with other layouts, and the original poster has not pursued this further, perhaps it would be reasonable to close this issue? -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 41547] PropertyConfigurator and layout.contentType
https://issues.apache.org/bugzilla/show_bug.cgi?id=41547 --- Comment #1 from Thorbjørn Ravn Andersen [EMAIL PROTECTED] 2008-07-03 13:14:18 PST --- Could you please provide sample code demonstrating the issue you are reporting? Preferrably as an attached zipfile -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 45231] Clear appenders call on logger calls a helper which calls close on the appenders
https://issues.apache.org/bugzilla/show_bug.cgi?id=45231 --- Comment #1 from Thorbjørn Ravn Andersen [EMAIL PROTECTED] 2008-07-03 13:37:24 PST --- Please attach a testcase demonstrating the behaviour you are reporting. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 44765] SyslogAppender should not attempt to remove inital tabs from stack trace lines
https://issues.apache.org/bugzilla/show_bug.cgi?id=44765 Morten Hattesen [EMAIL PROTECTED] changed: What|Removed |Added CC||[EMAIL PROTECTED] --- Comment #2 from Morten Hattesen [EMAIL PROTECTED] 2008-07-03 13:38:51 PST --- (In reply to comment #1) Is there any reason why this behaviour should NOT be changed to include all characters logged? Does the first character have special meaning in syslog messages? No, the first character has no special meaning. But since stack-traces are indented using a leading TAB character, it is generally a good idea to expand this to a number (4) of spaces to ensure consistent rendering of the stack-trace. But the TAB character should definitely NOT be truncated as part of the Syslog appender, as is the case today. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 43867] NOPLoggerRepository error during shutdown
https://issues.apache.org/bugzilla/show_bug.cgi?id=43867 --- Comment #14 from Thorbjørn Ravn Andersen [EMAIL PROTECTED] 2008-07-03 13:40:25 PST --- From what I understand from the comments this is basically a Tomcat issue, and will not be circumvented in log4j 1.2? Would it be reasonable to resolve with a WONTFIX then? -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 42189] Add simple bridge for java.util.logging, with basic Configurator support
https://issues.apache.org/bugzilla/show_bug.cgi?id=42189 --- Comment #13 from Thorbjørn Ravn Andersen [EMAIL PROTECTED] 2008-07-03 13:45:33 PST --- I don't think it is a good idea to replicate the work that has been done with slf4j regarding gluing logging frameworks together. I believe they have functional log4j and j.u.l bridges, and that log4j should only concentrate on log4j stuff. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 38590] no space on device fails another instance
https://issues.apache.org/bugzilla/show_bug.cgi?id=38590 --- Comment #1 from Thorbjørn Ravn Andersen [EMAIL PROTECTED] 2008-07-03 13:53:06 PST --- Please provide log4j configuration file for your scenario plus the disk layout provoking this issue. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 36384] Configuring triggering/ rolling policies should be supported through properties
https://issues.apache.org/bugzilla/show_bug.cgi?id=36384 Thorbjørn Ravn Andersen [EMAIL PROTECTED] changed: What|Removed |Added CC||[EMAIL PROTECTED] --- Comment #3 from Thorbjørn Ravn Andersen [EMAIL PROTECTED] 2008-07-03 14:08:26 PST --- This is reported against 1.3alpha which has been discontinued. Is this behaviour backported to 1.2 or should this be closed with WONTFIX? -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 43874] SocketHubAppender should expose actual port in use to extending classes
https://issues.apache.org/bugzilla/show_bug.cgi?id=43874 --- Comment #2 from Thorbjørn Ravn Andersen [EMAIL PROTECTED] 2008-07-03 14:32:05 PST --- Is the issue still present, or can this issue be closed? -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 45231] Clear appenders call on logger calls a helper which calls close on the appenders
https://issues.apache.org/bugzilla/show_bug.cgi?id=45231
--- Comment #2 from David Berkman [EMAIL PROTECTED] 2008-07-03 14:32:48 PST
---
(In reply to comment #1)
Please attach a testcase demonstrating the behaviour you are reporting.
You've got to be kidding. It's directly in your code. Here's the stack trace...
at
org.apache.log4j.helpers.AppenderAttachableImpl.removeAllAppenders(AppenderAttachableImpl.java:141)
at org.apache.log4j.Category.removeAllAppenders(Category.java:891)
Calling Category.removeAllAppenders() results in a call to
AppenderAttachableImpl.removeAllAppenders(), probably because this is set as
the default listener for the remove event internally. Looking at the code fro
the removeAllAppenders method in AppenderAttachableImpl, we see...
public
void removeAllAppenders() {
if(appenderList != null) {
int len = appenderList.size();
for(int i = 0; i len; i++) {
Appender a = (Appender) appenderList.elementAt(i);
a.close();
}
appenderList.removeAllElements();
appenderList = null;
}
}
Look at that a.close(). Why is this method calling close on an Appender simply
because it has been removed from a logger? Appenders are shared objects. I
wonder how the other loggers that Appender is attached to will feel about it
being closed underneath them? What happens when I re-use this Appender?
In my opinion this is incorrect behavior.
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 40068] Add support for attach-on-demand API to chainsaw
https://issues.apache.org/bugzilla/show_bug.cgi?id=40068 --- Comment #2 from Curt Cox [EMAIL PROTECTED] 2008-07-03 15:32:44 PST --- The basic idea is that the decision to use ChainSaw could be after-the-fact. JConsole currently supports this sort of usage. The API has changed since I filed the RFE. I don't have any experience with it, but the API looks pretty straightforward. http://java.sun.com/javase/6/docs/jdk/api/attach/spec/com/sun/tools/attach/VirtualMachine.html#list() Let me know if there is any further clarification I could provide or otherwise lend a hand. Thanks, Curt -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Receivers artifacts and Chainsaw
One of the last tasks to complete before a potential 'release' to the Webstart version of Chainsaw is building a custom Receiver artifact output that does not include the JMSReceiver DBReceiver, both of which require dependent jars that we obviously can't ship (because we don't know what provider they'll need). I plan to add a new output artifact in log4j-receivers that contains this, and have it with a classifier of 'chainsaw-receivers', and have it attached via buildhelper plugin so that it is pushed out as an artifact. A similar approach would be to produce an artifact just containing JMS+DB receivers. There would still be a 'non-classified' binary containing all Receivers as standard. That way Chainsaw can mark a dependency on it's relevant classifier. This would mean that both the Webstart and standalone versions of Chainsaw would require an end-user who wished to use JMSReceiver or DBReceiver could download the 'extras' pack of Receivers, and drop it into the plugins folder together with their provider jars. thoughts? Paul - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 43874] SocketHubAppender should expose actual port in use to extending classes
https://issues.apache.org/bugzilla/show_bug.cgi?id=43874 Paul Smith [EMAIL PROTECTED] changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution||FIXED --- Comment #3 from Paul Smith [EMAIL PROTECTED] 2008-07-03 15:51:27 PST --- I believe we knocked this off recently and is part of the 1.2.16-SNAPSHOT (it's in the change.xml). -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Receivers artifacts and Chainsaw
+1 Not sure about the name chainsaw-receivers (they can be used outside Chainsaw). 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: Paul Smith [mailto:[EMAIL PROTECTED] Sent: Thu 7/3/2008 3:46 PM To: Log4J Developers List Subject: Receivers artifacts and Chainsaw One of the last tasks to complete before a potential 'release' to the Webstart version of Chainsaw is building a custom Receiver artifact output that does not include the JMSReceiver DBReceiver, both of which require dependent jars that we obviously can't ship (because we don't know what provider they'll need). I plan to add a new output artifact in log4j-receivers that contains this, and have it with a classifier of 'chainsaw-receivers', and have it attached via buildhelper plugin so that it is pushed out as an artifact. A similar approach would be to produce an artifact just containing JMS+DB receivers. There would still be a 'non-classified' binary containing all Receivers as standard. That way Chainsaw can mark a dependency on it's relevant classifier. This would mean that both the Webstart and standalone versions of Chainsaw would require an end-user who wished to use JMSReceiver or DBReceiver could download the 'extras' pack of Receivers, and drop it into the plugins folder together with their provider jars. thoughts? Paul - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] winmail.dat- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 40068] Add support for attach-on-demand API to chainsaw
https://issues.apache.org/bugzilla/show_bug.cgi?id=40068 --- Comment #3 from Paul Smith [EMAIL PROTECTED] 2008-07-03 15:55:48 PST --- Listing the running VM's on the local box is easy, it would mean a change to Chainsaw to depend on Java 6, but +1000 from me. Then what does one do with it? Chainsaw needs to be able to bind a receiver to soak events from it, so I can't see anyway to use the VirtualMachine object to inspect the running VM to discover what appenders it has running (so that it could create a matching Receiver if a compatible one is found). Have I missed something? (great idea if it can be done) -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Receivers artifacts and Chainsaw
On 04/07/2008, at 8:54 AM, Scott Deboy wrote: +1 Not sure about the name chainsaw-receivers (they can be used outside Chainsaw). I'm all ears on suggestions! :) I think it blows too, but my brain is tired this morning. Paul - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 42189] Add simple bridge for java.util.logging, with basic Configurator support
https://issues.apache.org/bugzilla/show_bug.cgi?id=42189 --- Comment #14 from Paul Smith [EMAIL PROTECTED] 2008-07-03 16:04:55 PST --- (In reply to comment #13) I don't think it is a good idea to replicate the work that has been done with slf4j regarding gluing logging frameworks together. I believe they have functional log4j and j.u.l bridges, and that log4j should only concentrate on log4j stuff. That's a pretty fair point actually! -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 40068] Add support for attach-on-demand API to chainsaw
https://issues.apache.org/bugzilla/show_bug.cgi?id=40068 --- Comment #4 from Scott Deboy [EMAIL PROTECTED] 2008-07-03 16:05:43 PST --- JMX for that part? -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Receivers artifacts and Chainsaw
log4j-receivers-3rdpartydeps? pretty hokey but a bit more accurate 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: Paul Smith [mailto:[EMAIL PROTECTED] Sent: Thu 7/3/2008 4:03 PM To: Log4J Developers List Subject: Re: Receivers artifacts and Chainsaw On 04/07/2008, at 8:54 AM, Scott Deboy wrote: +1 Not sure about the name chainsaw-receivers (they can be used outside Chainsaw). I'm all ears on suggestions! :) I think it blows too, but my brain is tired this morning. Paul - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] winmail.dat- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 40068] Add support for attach-on-demand API to chainsaw
https://issues.apache.org/bugzilla/show_bug.cgi?id=40068 --- Comment #5 from Paul Smith [EMAIL PROTECTED] 2008-07-03 16:07:27 PST --- (In reply to comment #4) JMX for that part? That would mean the Appenders would have to be exposed as managed objects in the JMX namespace, which might work (if our JMX support was better). Hrm, sounds possible! -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 39691] DBAppender doesn't log long events
https://issues.apache.org/bugzilla/show_bug.cgi?id=39691 --- Comment #3 from Thorbjørn Ravn Andersen [EMAIL PROTECTED] 2008-07-03 16:40:30 PST --- (In reply to comment #2) (In reply to comment #1) Truncation should be the resposibility of the appender, since it has the domain knowledge on the length to trim at. It should be expected that the logger logs as much as it can of the data it gets, so I disagree with this. I was apparently thinking of the logger and not the appender when writing the above. Please disregard. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 45231] Clear appenders call on logger calls a helper which calls close on the appenders
https://issues.apache.org/bugzilla/show_bug.cgi?id=45231 Thorbjørn Ravn Andersen [EMAIL PROTECTED] changed: What|Removed |Added CC||[EMAIL PROTECTED] --- Comment #3 from Thorbjørn Ravn Andersen [EMAIL PROTECTED] 2008-07-03 16:47:35 PST --- (In reply to comment #2) You've got to be kidding. It's directly in your code. Here's the stack trace... I am not kidding, and it is not my code (you can see that in the Subversion history). By providing a testcase it can be demonstrated that the bug exists, and that the patch removed the bug. Otherwise we can only guess what caused the bug and if the handwaving code introduced fixed it in the way you expected. Hence, please provide a testcase. In my opinion this is incorrect behavior. Most likely. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Receivers artifacts and Chainsaw
Paul Smith skrev den 04-07-2008 00:46: One of the last tasks to complete before a potential 'release' to the Webstart version of Chainsaw is building a custom Receiver artifact output that does not include the JMSReceiver DBReceiver, both of which require dependent jars that we obviously can't ship (because we don't know what provider they'll need). I plan to add a new output artifact in log4j-receivers that contains this, and have it with a classifier of 'chainsaw-receivers', and have it attached via buildhelper plugin so that it is pushed out as an artifact. A similar approach would be to produce an artifact just containing JMS+DB receivers. There would still be a 'non-classified' binary containing all Receivers as standard. That way Chainsaw can mark a dependency on it's relevant classifier. This would mean that both the Webstart and standalone versions of Chainsaw would require an end-user who wished to use JMSReceiver or DBReceiver could download the 'extras' pack of Receivers, and drop it into the plugins folder together with their provider jars. I think that there should be a core log4j which should cover those classes described in the printed manual, and that all the other stuff which has come up since then should go in one or more extras packages which may have a different release cycle than the core. The reason is the simple that log4j-core for 1.2 is mature code which should get few updates, where the auxillary libraries appears still to be rough here and there, so I think it would be beneficial to have two seperate release tracks. -- Thorbjørn - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Receivers artifacts and Chainsaw
On 04/07/2008, at 9:59 AM, Thorbjørn Ravn Andersen wrote: Paul Smith skrev den 04-07-2008 00:46: One of the last tasks to complete before a potential 'release' to the Webstart version of Chainsaw is building a custom Receiver artifact output that does not include the JMSReceiver DBReceiver, both of which require dependent jars that we obviously can't ship (because we don't know what provider they'll need). I plan to add a new output artifact in log4j-receivers that contains this, and have it with a classifier of 'chainsaw- receivers', and have it attached via buildhelper plugin so that it is pushed out as an artifact. A similar approach would be to produce an artifact just containing JMS+DB receivers. There would still be a 'non-classified' binary containing all Receivers as standard. That way Chainsaw can mark a dependency on it's relevant classifier. This would mean that both the Webstart and standalone versions of Chainsaw would require an end-user who wished to use JMSReceiver or DBReceiver could download the 'extras' pack of Receivers, and drop it into the plugins folder together with their provider jars. I think that there should be a core log4j which should cover those classes described in the printed manual, and that all the other stuff which has come up since then should go in one or more extras packages which may have a different release cycle than the core. But there is.. log4j-receivers is a separate maven module with an independent release cycle. There's also log4j-extras. Paul - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
