headers
bugzilla | 1 Oct 2008 16:16
Picon
Favicon

DO NOT REPLY [Bug 45704] Failed to load logging.xml for JRE 1.5.0_16 and Webstart

https://issues.apache.org/bugzilla/show_bug.cgi?id=45704

--- Comment #4 from Nick Ebbutt <nick <at> ebbutt.net>  2008-10-01 07:16:31 PST ---
There is now a bug report relating to this issue on Sun's site
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6753651

--

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
Permalink | Reply | 0 comments |
headers
bugzilla | 1 Oct 2008 22:43
Picon
Favicon

DO NOT REPLY [Bug 45932] New: Log4j JMX MBeans not cleaned up

https://issues.apache.org/bugzilla/show_bug.cgi?id=45932

           Summary: Log4j JMX MBeans not cleaned up
           Product: Log4j
           Version: 1.2
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Other
        AssignedTo: log4j-dev <at> logging.apache.org
        ReportedBy: hmak <at> vaultus.com

LogManager.resetConfiguration() does not drop the JMX MBeans created by
HierarchyDynamicMBean.

When executed twice, the following

        MBeanServer mbs = ...;
        Properties props = ...;
        HierarchyDynamicMBean hdm = new HierarchyDynamicMBean();
        mbs.registerMBean(hdm, new ObjectName("log4j:hiearchy=default"));

        Enumeration<Logger> iter = (Enumeration<Logger>)
LogManager.getLoggerRepository().getCurrentLoggers();
        while (iter.hasMoreElements()) {
                hdm.addLoggerMBean(iter
                          .nextElement()
                          .getName());
(Continue reading)

Permalink | Reply | 0 comments |
headers
bugzilla | 2 Oct 2008 13:40
Picon
Favicon

DO NOT REPLY [Bug 45934] New: FileAppender should use virtual-machine shutdown hook that flushes buffer automatically

https://issues.apache.org/bugzilla/show_bug.cgi?id=45934

           Summary: FileAppender should use virtual-machine shutdown hook
                    that flushes buffer automatically
           Product: Log4j
           Version: 1.2
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: Appender
        AssignedTo: log4j-dev <at> logging.apache.org
        ReportedBy: m <at> rtin-burger.de

If org.apache.log4j.FileAppender buffers output (option BufferedIO set to
true), then the underlying WriterAppender's field immediateFlush will set to
false.

So, the FileAppender will skip flushing and it is very likely that the last few
log events will not be recorded on disk when the application exits.

To avoid the loss of these events, an optional virtual-machine shutdown that
flushes automatically at the end should be used.

--

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
(Continue reading)

Permalink | Reply | 1 comment |
headers
bugzilla | 2 Oct 2008 13:51
Picon
Favicon

DO NOT REPLY [Bug 45934] FileAppender should use virtual-machine shutdown hook that flushes buffer automatically

https://issues.apache.org/bugzilla/show_bug.cgi?id=45934

--- Comment #1 from Martin Burger <m <at> rtin-burger.de>  2008-10-02 04:51:20 PST ---
Created an attachment (id=22667)
 --> (https://issues.apache.org/bugzilla/attachment.cgi?id=22667)
Patch to FileAppender.java that produces implementation of proposed feature.

The attached patch implements the proposed feature using a shutdown thread. It
adds a new optional option "ShutdownHook" (default: false). If this option is
set to true and option "BufferedIO" is set to true as well, the shutdown hook
will be registered in method setFile(...).

Note: The test suite runs without any error after applying the patch, at least
on my system.

--

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
Permalink | Reply | 0 comments |
headers
bugzilla | 2 Oct 2008 18:43
Picon
Favicon

DO NOT REPLY [Bug 45939] New: Cannot drop HierarchyDynamicMBean from LoggerRepository

https://issues.apache.org/bugzilla/show_bug.cgi?id=45939

           Summary: Cannot drop HierarchyDynamicMBean from LoggerRepository
           Product: Log4j
           Version: 1.2
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Other
        AssignedTo: log4j-dev <at> logging.apache.org
        ReportedBy: hmak <at> vaultus.com

HierarchyDynamicMBean registered too many times w/ LoggerRepository.  This can
occur when:

1. start MBeanServer
2. register new HierarchyDynamicMBean (HDMBean) to MBeanServer
3. unregister HDMBean from MBeanServer
4. stop MBeanServer
5. repeat (1) - (3)

LoggerReposity will still broadcast to old HDMBean [in addition to new
HDMBean].  There is no API to unregister the MBean.

--

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
(Continue reading)

Permalink | Reply | 0 comments |
headers
bugzilla | 3 Oct 2008 11:58
Picon
Favicon

DO NOT REPLY [Bug 45941] New: Custom PatternLayout

https://issues.apache.org/bugzilla/show_bug.cgi?id=45941

           Summary: Custom PatternLayout
           Product: Log4j
           Version: unspecified
          Platform: PC
               URL: http://logging.apache.org/log4j/1.2/apidocs/org/apache/l
                    og4j/PatternLayout.html
        OS/Version: All
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: Layout
        AssignedTo: log4j-dev <at> logging.apache.org
        ReportedBy: spamadore <at> gmail.com

For the moment, you can only use predefined patternLayout here

http://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/PatternLayout.html

An evolution could be to add a system to define our own layout

basically a custom layout could be

---------------------------------------------------------
public class MyPidLayout implements CustomConversionLayout{

     char getConversionCharacter(){
            return 'y';
      }
(Continue reading)

Permalink | Reply | 2 comments |
headers
bugzilla | 3 Oct 2008 15:15
Picon
Favicon

DO NOT REPLY [Bug 45941] Custom PatternLayout

https://issues.apache.org/bugzilla/show_bug.cgi?id=45941

Curt Arnold <carnold <at> apache.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |NEEDINFO

--- Comment #1 from Curt Arnold <carnold <at> apache.org>  2008-10-03 06:15:52 PST ---
Please look at EnhancedPatternLayout in the extras companion.  That is a back
port of the PatternLayout from the abandoned log4j 1.3 development and supports
user supplied conversion patterns and see if it does what you are wanting to
do.  If not, please describe what you want to do more concretely.

--

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
Permalink | Reply | 0 comments |
headers
bugzilla | 6 Oct 2008 08:08
Picon
Favicon

Bug report for Log4j [2008/10/05]

+---------------------------------------------------------------------------+
| Bugzilla Bug ID                                                           |
|     +---------------------------------------------------------------------+
|     | Status: UNC=Unconfirmed NEW=New         ASS=Assigned                |
|     |         OPN=Reopened    VER=Verified    (Skipped Closed/Resolved)   |
|     |   +-----------------------------------------------------------------+
|     |   | Severity: BLK=Blocker CRI=Critical  REG=Regression  MAJ=Major   |
|     |   |           MIN=Minor   NOR=Normal    ENH=Enhancement TRV=Trivial |
|     |   |   +-------------------------------------------------------------+
|     |   |   | Date Posted                                                 |
|     |   |   |          +--------------------------------------------------+
|     |   |   |          | Description                                      |
|     |   |   |          |                                                  |
|13099|Opn|Nor|2002-09-27|DOMConfigurator ignores category factory setting  |
|17887|Opn|Maj|2003-03-11|RollingFileAppender does not work for 10 threads  |
|20395|Inf|Enh|2003-06-01|PreparedStatementAppender Enhancement             |
|23329|Ass|Enh|2003-09-22|<logger> element in XML config should support reso|
|25355|Ass|Enh|2003-12-09|allow to require "TLS/SSL only" for outgoing mails|
|26084|Inf|Nor|2004-01-13|Log Event detail panel does not show special chara|
|27363|Inf|Enh|2004-03-02|JNI based SyslogAppender                          |
|27367|Inf|Enh|2004-03-02|NetSendAppender                                   |
|28647|Ass|Enh|2004-04-28|Add "Flush on Level" capability to FileAppender   |
|29244|Inf|Nor|2004-05-27|Preserve XML content in log messages when using XM|
|29304|New|Nor|2004-05-30|Starting XMLSocketAppender from config file       |
|29305|New|Nor|2004-05-30|Chainsaw doesn't see locationinfo from XMLSocketRe|
|29735|New|Nor|2004-06-22|Receiver list display error  when receiver has no |
|30055|New|Nor|2004-07-12|Problem with registering Appenders with the same n|
|30407|Inf|Maj|2004-07-30|Externally rolled file problem                    |
|30888|New|Maj|2004-08-27|Chainsaw mixes files in same panel                |
|30890|New|Min|2004-08-27|Newly opened log file should get focus            |
(Continue reading)

Permalink | Reply | 0 comments |
headers
bugzilla | 7 Oct 2008 21:01
Picon
Favicon

DO NOT REPLY [Bug 42213] log4j causing threads to stuck in weblogic

https://issues.apache.org/bugzilla/show_bug.cgi?id=42213

Sachin <sachinlohe <at> gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |sachinlohe <at> gmail.com
             Status|RESOLVED                    |REOPENED
         Resolution|DUPLICATE                   |

--- Comment #5 from Sachin <sachinlohe <at> gmail.com>  2008-10-07 12:01:29 PST ---
We have same environment and same issue. 
Sudhanshu/Anyone who want to answer : How was this issue resolved finally.
Duplicate bug(41214) comment 22 mentioned that this may be jre1.5 solaris bug.

"[STUCK] ExecuteThread: '93' for queue: 'weblogic.kernel.Default
(self-tuning)'" daemon prio=3 tid=0x00000001071bbea0 nid=0x5a0 runnable
[0xfffffffe9a3fd000..0xfffffffe9a3ff6a8]

        at java.io.FileOutputStream.writeBytes(Native Method)

        at java.io.FileOutputStream.write(FileOutputStream.java:260)

        at
sun.nio.cs.StreamEncoder$CharsetSE.writeBytes(StreamEncoder.java:336)

        at
sun.nio.cs.StreamEncoder$CharsetSE.implFlushBuffer(StreamEncoder.java:404)

        at sun.nio.cs.StreamEncoder$CharsetSE.implFlush(StreamEncoder.java:408)
(Continue reading)

Permalink | Reply | 0 comments |
headers
Johan Sandgren | 8 Oct 2008 10:19
Picon

Dual logging problem - outofmemoryerror... heap space

Hi,

 

Need advice from professionals here… I’m stuck! L

 

I’m using log4j, and my logs are rotating quite fast, so if an error occurs, for example in the middle of the night, it will not be present in the log in the morning when I arrive to check for errors.

 

So I decided to extract the errors live, when they occur, and make them go to another file.

But since errors just on their own does not say much of where the program were and what was the variables right then, I’d also like to attach some history before the error in the error.log-file.

 

So I wrote a class to support this feature. It’s a spy really. It’s attaching to an existing logger, and adding another appender, which I use to create history and outputting to another error.log-file when I need to.

 

 

A little more details on the spyclass are:

 

I’m calling my usual logger X, and I’ve created another loggerclass Y, which attaches another appender on my X.

 

For each logger call with X, I also call my Y which is getting the string too, because it’s snooping on X, via this appender I added. Y is also keeping a circularbuffer of history of all logging it gets.

When Y is called with error, fatal or warn, it will do a dump of the history and lastly, the erranous line, and all this to another file, error.log.

 

That way I will get my usual log in blabla.log, and for each warn, error /fatal, I get a few lines of history + the error/warn/fatal-line that is to be noticed.

 

 

My problem:

BUT, I get out of heapmemory when using it after a while.

I cannot find the error causing it. Mayber I’m misusing the appender or log4j?

 

I’ve attached the historymaking class “ErrorLogger.java”, and an example (test.java) of how the calls are made.

 

 

 

Exception in thread "Thread-5" java.lang.OutOfMemoryError: Java heap space

        at java.lang.AbstractStringBuilder.expandCapacity(AbstractStringBuilder.java:99)

        at java.lang.AbstractStringBuilder.append(AbstractStringBuilder.java:393)

        at java.lang.StringBuffer.append(StringBuffer.java:225)

        at java.io.StringWriter.write(StringWriter.java:79)

        at org.apache.log4j.helpers.QuietWriter.write(QuietWriter.java:47)

        at org.apache.log4j.WriterAppender.subAppend(WriterAppender.java:301)

        at org.apache.log4j.WriterAppender.append(WriterAppender.java:159)

        at org.apache.log4j.AppenderSkeleton.doAppend(AppenderSkeleton.java:230)

        at org.apache.log4j.helpers.AppenderAttachableImpl.appendLoopOnAppenders(AppenderAttachableImpl.java:65)

        at org.apache.log4j.Category.callAppenders(Category.java:203)

        at org.apache.log4j.Category.forcedLog(Category.java:388)

        at org.apache.log4j.Category.debug(Category.java:257)

 

        at com.sttcare.alarmSwitch.JmsTester.activeMqIsUp(JmsTester.java:88) calls connection.stop(); So it really has nothing with log4j, I guess the heap is just ended right then.

 

        at com.sttcare.alarmSwitch.systemWatch.ProgramChecker.activeMQWorks(ProgramChecker.java:143)

        at com.sttcare.alarmSwitch.systemWatch.ProgramChecker.run(ProgramChecker.java:119)

        at java.lang.Thread.run(Thread.java:595)

 

 

Seems to me something is exandCapacity too much…

 

/Johan

 

_______________

Johan Sandgren   

Svep Design Center AB                                

Phone +46 46 192 722

Mobile +46 70 173 4152

Box 1233, 221 05 Lund, Sweden                                 

E-mail   jsa <at> svep.se

Website www.svep.se

 

Attachment (ErrorLogger.java): application/octet-stream, 5605 bytes
Attachment (test.java): application/octet-stream, 1711 bytes
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe <at> logging.apache.org
For additional commands, e-mail: log4j-dev-help <at> logging.apache.org
Permalink | Reply | 2 comments |

Gmane