bugzilla | 2 Jul 2008 00:21
Picon
Favicon

DO NOT REPLY [Bug 41980] Log4j stop updating log file- version log4j-1.2. 8 and log4j-1.2.14

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

Thorbjørn Ravn Andersen <thorbjoern <at> gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |thorbjoern <at> gmail.com

--- Comment #3 from Thorbjørn Ravn Andersen <thorbjoern <at> gmail.com>  2008-07-01 15:21:57 PST ---
I also have difficulties of understanding your wording.  If the log file keeps
getting new entries but the modification date in Windows Explorer does not
change, then it is a Windows issue.  If the log file for some reason does not
change at all even if log messages are written steadily and the logging
application works as expected, it could be that the automatic flushing of the
buffers after each write has been disabled.

Can you create a small program with a log4j file which shows this behaviour,
and attach it to this bug?

In the meantime I would suggest marking this bug NEEDINFO.

--

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
bugzilla | 2 Jul 2008 00:25
Picon
Favicon

DO NOT REPLY [Bug 30888] Chainsaw mixes files in same panel

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

Thorbjørn Ravn Andersen <thorbjoern <at> gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |thorbjoern <at> gmail.com

--- Comment #5 from Thorbjørn Ravn Andersen <thorbjoern <at> gmail.com>  2008-07-01 15:25:15 PST ---
Is it correct that the tab label is the one determining where event should go,
even when loaded from different files?  

What would be the appropriate way to deal with this issue now that some time
has passed and other parts of the code has developed too?

--

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
bugzilla | 2 Jul 2008 00:29
Picon
Favicon

DO NOT REPLY [Bug 17887] RollingFileAppender does not work for 10 threads

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

Thorbjørn Ravn Andersen <thorbjoern <at> gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |thorbjoern <at> gmail.com

--- Comment #5 from Thorbjørn Ravn Andersen <thorbjoern <at> gmail.com>  2008-07-01 15:29:58 PST ---
From an initial reading of the bug report this might be that two threads
contend for rolling over the files (i.e. the triggering happens in two threads
so the operations get mixed).

Perhaps a synchronized block around the renaming-bit could help?

Suggestions?

--

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
bugzilla | 2 Jul 2008 00:31
Picon
Favicon

DO NOT REPLY [Bug 30407] Externally rolled file problem

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

Thorbjørn Ravn Andersen <thorbjoern <at> gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |thorbjoern <at> gmail.com

--- Comment #5 from Thorbjørn Ravn Andersen <thorbjoern <at> gmail.com>  2008-07-01 15:31:20 PST ---
Since 1.3 has been discontinued and the current branch is 1.2 would it be
reasonable to close this bug 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.
bugzilla | 2 Jul 2008 00:42
Picon
Favicon

DO NOT REPLY [Bug 23329] <logger> element in XML config should support resourceBundle attribute

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

Thorbjørn Ravn Andersen <thorbjoern <at> gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |thorbjoern <at> gmail.com

--- Comment #4 from Thorbjørn Ravn Andersen <thorbjoern <at> gmail.com>  2008-07-01 15:42:12 PST ---
rev 500752 is not in the history for org.apache.log4j.spi.Configurator in trunk
(i.e. log4j 1.2).

Is this bug still applicable for log4j 1.2, and what is the status?

--

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
bugzilla | 2 Jul 2008 01:15
Picon
Favicon

DO NOT REPLY [Bug 38548] SecurityExceptions when attempting to use in applet in Java 5 Plug-In

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

--- Comment #1 from Thorbjørn Ravn Andersen <thorbjoern <at> gmail.com>  2008-07-01 16:15:51 PST ---
I have now created an applet and tried to view it with log4j-1.2.15.jar.  I did
not see any SecurityExceptions.

If this is a 1.3-only bug, perhaps it could be closed?  Otherwise, please
produce a test case that shows the behaviour with 1.2.15.

--

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
bugzilla | 2 Jul 2008 01:42
Picon
Favicon

DO NOT REPLY [Bug 30888] Chainsaw mixes files in same panel

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

--- Comment #6 from Scott Deboy <sdeboy <at> iname.com>  2008-07-01 16:42:28 PST ---
Fields on the event (along with the tab identifier specified in the
application-wide settings screen) determine which tab events are routed to.  

If a file is loaded (via file/load or through the LogFilePatternReceiver), two
properties are added to each of the file's events.  If the default tab
identifier is in use, these additional properties will cause the file's events
to route to its own tab.

There is also a mechanism by which events can be routed to multiple tabs: via
the 'create custom expression logpanel' menu (essentially creates a 'view' of
events on other tabs in a new tab).

Not sure if this is what you were asking, but I thought I'd try to explain how
the routing works.

--

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
bugzilla | 2 Jul 2008 10:40
Picon
Favicon

DO NOT REPLY [Bug 45236] Wriring output to an out-dated file.

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

Nagireddy Satti <nagireddy9 <at> gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|major                       |critical
           Priority|P2                          |P1

--- Comment #3 from Nagireddy Satti <nagireddy9 <at> gmail.com>  2008-07-02 01:40:37 PST ---
A bulk of output lines have been written to an out-dated log. It's not once,
frequently happening. As I know, writing one line or multiple lines to an 
out-dated log file is not important. Please try to fix this as soon as
possible,as some times we are unable to find out the correct log statements.
Some times it's writing to multiple files(Out-dated).

--

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
bugzilla | 2 Jul 2008 15:32
Picon
Favicon

DO NOT REPLY [Bug 45236] Wriring output to an out-dated file.

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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #22144|0                           |1
        is obsolete|                            |

--- Comment #4 from Curt Arnold <carnold <at> apache.org>  2008-07-02 06:32:31 PST ---
Created an attachment (id=22209)
 --> (https://issues.apache.org/bugzilla/attachment.cgi?id=22209)
PDF version of original Microsoft Word template

The original attachment is a Microsoft Word template file (.dot) which suggests
the presences of a Word Macro virus.

--

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
bugzilla | 2 Jul 2008 15:41
Picon
Favicon

DO NOT REPLY [Bug 45236] Wriring output to an out-dated file.

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

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

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

--- Comment #5 from Curt Arnold <carnold <at> apache.org>  2008-07-02 06:41:22 PST ---
The behavior mentioned is consistent with configuring multiple instances of
log4j writing to the same DailyRollingFileAppender.  The behavior and
attachment suggests that the platform is a Unix and not Windows XP as reported.
 Having multiple instances of any file appender write to the same path name is
known to be error-prone and is strongly discouraged and unsupported.

If multiple instances are writing to the same file names, one instance may
rename a file while another instance continues to write to it.  When the second
instance attempts to roll over its working file, it fails since the target file
already exists.

Unless the problem is not related to multiple instances and additional
information is provided, the report should be marked INVALID.

--

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

Gmane