I am developing a web application using Glassfish v2.  A continual source of irritation is the fact that whenever I run the application, the entire historical 
Glassfish log is dumped into the output window.

I am interested in log messages from the current run of my web app - I don't care about the multiple megabytes of old logging, stack traces, exceptions 
from runs I did two days ago, and miscellaneous noise in the log file - it makes it much harder to find the beginning of the current run and the info I'm 
really interested in.  Also, if there is a stack trace with highlights in the log file, the output window will stop scrolling on that, no matter how old it is.  Of 
course, I can right-click the output window and clear it, but I will get it all again the next time I restart the server.

In short, the full server log is just annoying noise - I want an easy way to see what's being logged *now*.

Suggested solution:  The output window allows you to provide Actions for toolbar buttons on the left of the window.  The default behavior should be only 
to show the current session's output, and not dump the full log into the output window.  Provide an action "Show full log" or something on the output 
window toolbar, so you can get the full log if you need it.  Perhaps even clear the server log output pane on deployment (although this could be 
problematic in the case that multiple apps are simultaneously being developed - but I don't know how real a use case that is).