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 182239 - [69cat] GFv3 server log stops outputting after restart
Summary: [69cat] GFv3 server log stops outputting after restart
Status: RESOLVED WORKSFORME
Alias: None
Product: serverplugins
Classification: Unclassified
Component: GlassFish (show other bugs)
Version: 6.x
Hardware: PC Windows XP
: P3 normal (vote)
Assignee: Vince Kraemer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-03-17 16:21 UTC by jpleed3
Modified: 2010-12-21 21:12 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description jpleed3 2010-03-17 16:21:06 UTC
If I have my local server log open while restarting it, it stops outputting after startup is complete. If I then close the log and reopen it by right-clicking the server and selecting View Server Log, two output windows open.

The first window looks to be the server log, but every character is one of those square characters that Notepad shows when it doesn't recognize something. Log level highlighting is still performed and the window is at the top of the log.

The second windows shows the server log, but it takes a few seconds for the log to "download". The log receives a lot of output for a while - as if it started from the beginning - and ends at the last actual log message.

I've noticed this behavior in 6.8 as well.
Comment 1 Vince Kraemer 2010-04-05 20:50:39 UTC
I have not been able to reproduce this yet.

Are you restarting the server with NB?  Which action are you using to do the restrart... Stop, then Start OR Restart?

What local are you using on the system? What is your encoding?
Comment 2 jpleed3 2010-04-09 16:16:15 UTC
Try this: with server log open and GF started, kill the JVM process. Restart GF from the Servers node. For me, the server logs will show the startup process, but nothing after that until I close it and reopen from the Servers node.
Comment 3 Vince Kraemer 2010-05-12 20:05:44 UTC
this is an interesting edge case
Comment 4 Vince Kraemer 2010-12-21 21:12:27 UTC
This appears to be resolved in 7.0 builds...

Please reopen with info on how to reproduce if you can run into this issue with a recent 7.0 build...