This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 74507 - Logging output is buffered
Summary: Logging output is buffered
Status: RESOLVED FIXED
Alias: None
Product: platform
Classification: Unclassified
Component: -- Other -- (show other bugs)
Version: 6.x
Hardware: All All
: P2 blocker (vote)
Assignee: Jaroslav Tulach
URL:
Keywords: REGRESSION
: 74526 (view as bug list)
Depends on:
Blocks:
 
Reported: 2006-04-06 13:31 UTC by mslama
Modified: 2008-12-22 20:51 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description mslama 2006-04-06 13:31:31 UTC 
There is no flush in logging. I do not know if it should be automatic or on
request. I would prefer some automatic flushing if possible. It is important
when logging is sent to console. Probably not so important when logging is going
to file but I think it should be flushed regardless where output is sent to.
Comment 1 Jaroslav Tulach 2006-04-07 08:39:25 UTC 
*** Issue 74526 has been marked as a duplicate of this issue. ***
Comment 2 Jaroslav Tulach 2006-04-07 08:41:22 UTC 
The flush is currently set to 5s:

/shared/data/ccvs/repository/core/startup/test/unit/src/org/netbeans/core/startup/TopLoggingTest.java,v  
<--  TopLoggingTest.java
new revision: 1.4; previous revision: 1.3
done
Checking in src/org/netbeans/core/startup/TopLogging.java;
/shared/data/ccvs/repository/core/startup/src/org/netbeans/core/startup/TopLogging.java,v  
<--  TopLogging.java
new revision: 1.8; previous revision: 1.7
Comment 3 Martin Krauskopf 2006-04-09 17:56:52 UTC 
I'm reopening this issue. I think the fix is not too good. 5s is too long delay.
I believe that System.err is used a lot by a lot of developers. They perform
some action which writes something to System.err and still "nothing" happens
when they switch to console, so they switch back to IDE - they just do not stay
on the console for 5s if they do not know this, kind of annoyance. IMHO feedback
have to be "immediate".
Would it be a performance problem if you flush out the buffer every, let's say,
500ms? Also maybe that flushing buffer when it is empty - 95%(?) of cases;
should not be a performance problem at all? If yes would it be possible to check
if it is empty and do nothing then?
Comment 4 Jaroslav Tulach 2006-04-10 07:56:36 UTC 
/shared/data/ccvs/repository/core/startup/src/org/netbeans/core/startup/TopLogging.java,v  
<--  TopLogging.java
new revision: 1.9; previous revision: 1.8
done
Checking in 
test/unit/src/org/netbeans/core/startup/TopLoggingNbLoggerConsoleTest.java;
/shared/data/ccvs/repository/core/startup/test/unit/src/org/netbeans/core/startup/TopLoggingNbLoggerConsoleTest.java,v  
<--  TopLoggingNbLoggerConsoleTest.java
new revision: 1.2; previous revision: 1.1


If you want more, please write a test.