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.
I deployed an EAR to SJSAS 9.1 and got an error: http://www.netbeans.org/issues/show_bug.cgi?id=118603 Shortly after the HTTP Monitor opened. I closed the HTTP Monitor and it opened again. I fought with it for a while, then clicked the Output tab, then went back to the HTTP Monitor tab and finally was able to close it.
It turns out that every time I do an HTTP request on any web app (including admin console) in SJSAS 9.1, the HTTP Monitor opens again. I can close it and it stays close until I click a link or button in one of the web apps.
Confirmed this is indeed the behavior - however I believe there was a reason why we introduced this behavior - at some point you *do* want to see HTTP monitor, and without automatic opening, it would not be discoverable. In the past, we had many people complaining about HTTP monitor not being supported on GlassFish, when in fact it was supported, it only was not turned on by default and users did not know it can be enabled. So discoverability is important. Anyway, there are several easy workarounds: - Just leave the HTTP monitor window open and put another window in the foreground (e.g. the output window). On the next request, the HTTP monitor will stay in the background - Minimize the HTTP monitor window so it appears as an icon in the border on the NetBeans window - disable HTTP monitor for your server in the Server Manager For now I am decreasing the priority to P3.
When I saw this behavior I liked it initially. After deploying to Glassfish and running my app, the HTTP Monitor opened automatically. However, it does not behave exactly as you described. If I leave the HTTP monitor open, and switch to the output tab, the HTTP Monitor forcefully comes back to the foreground every time I click a link in the web app. If I want to watch the output window, I can't. I can't even close the HTTP Monitor because it keeps opening and going to the foreground. This is a real pain in the a**. I wouldn't mind if it opened every time I deploy to glassfish, or every time I started glassfish. But don't force it on me all the time. I can't have any other tab visible, it always forces itself to the top whenever there is any activity.
I have spent some more time playing with this. I was wrong when I said that if I switch tabs, the HTTP Monitor tab pops to the top automatically. However it is impossible to close it without it opening up whenever there is activity. Having it open every time there is activity feels like a bug to me even though it is a feature. I don't want it open. I don't mind if it opens when I start the app server from within NetBeans, but I would like to be able to close it.
Thanks for the evaluation. I acknowledge that this is a valid bug (P3 priority IMO) and should be fixed. The fix is quite tricky though - it requires to recognize and remember whether the window was closed by the user, or whether it was not opened at all before, we need to think about what to do after the IDE restart - should it be opened the next time?, etc. It should be fixed for the next release; it's too late for 6.0, I am afraid.
*** Issue 114543 has been marked as a duplicate of this issue. ***
This bug was reported against NetBeans IDE 6.0 or an older release, or against a non-maintained module. NetBeans team does not have enough resources to get to this issue, therefore we are closing the issue as a WONTFIX. If you are interested in providing a patch for this bug, please see our NetFIX guidelines for how to proceed. We apologize for any inconvenience. Thank you. The NetBeans Team