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 74538

Summary: System.err is not immediately flushed
Product: platform Reporter: Martin Krauskopf <mkrauskopf>
Component: -- Other --Assignee: Jaroslav Tulach <jtulach>
Status: VERIFIED DUPLICATE    
Severity: blocker Keywords: REGRESSION
Priority: P2    
Version: 6.x   
Hardware: All   
OS: All   
Issue Type: DEFECT Exception Reporter:

Description Martin Krauskopf 2006-04-06 19:21:25 UTC
1) Create module by New Module Wizard
2) Register new CallableSystemAction into menu (by Action Wizard - always
   enabled)
3) Put into generate action.performAction() method's body e.g.

     System.err.println("I'm not flushed immediatelly");

4) Run Module
5) Invoke action from the menu

You will not see "I'm not flushed immediatelly" immediatelly in the output
window of the main IDE (the one where you created a module). Then close the IDE,
the message is flushed.

Might be caused by new logging implementaion (CCing Yarda). It is regression.
Comment 1 Martin Krauskopf 2006-04-07 06:25:49 UTC
It is the problem of the loggin infrastructure, since it happened this time with
Eclipse Importer. Log of the main IDE (dev build) did not appear immediately in
the underlaying console.
Easily reproducible with module described in the initial comment. Just install
it in the running IDE instance, run the Action -> nothing on the console -> exit
the IDE, System.err is flushed.

Also got this randomly, not sure if it is related:

WARNING [null]: Do not call reset() on the error io, only on the output IO. 
Reset on the error io does nothing.
Comment 2 Martin Krauskopf 2006-04-07 07:39:18 UTC

*** This issue has been marked as a duplicate of 74526 ***
Comment 3 Marian Mirilovic 2006-04-07 07:58:39 UTC
verified duplicate