Bug 175460 - HTTP monitor is not enabled in some situations
HTTP monitor is not enabled in some situations
Status: REOPENED
Product: serverplugins
Classification: Unclassified
Component: GlassFish
6.x
All All
: P3 (vote)
: 7.4
Assigned To: Vince Kraemer
issues@serverplugins
NB_ONLY
:
: 173298 (view as bug list)
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-10-26 17:39 UTC by Petr Jiricka
Modified: 2013-07-19 23:26 UTC (History)
0 users

See Also:
Issue Type: DEFECT
:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Petr Jiricka 2009-10-26 17:39:29 UTC
1. Add v3 instance and enable HTTP monitor in properties
2. Create a WebApp with v3 as target and run it
3. Go to Window -> Debugging -> HTTP Server Monitor

No HTTP transactions are shown. For v2, it works well.
Comment 1 Vince Kraemer 2009-10-26 18:00:00 UTC
*** Issue 173298 has been marked as a duplicate of this issue. ***
Comment 2 Vince Kraemer 2009-10-26 18:53:42 UTC
OS? JDK? NB build?

I used Mac OS X 10.5.8, jdk 6 update 15, recent pull from web-main.

I followed your steps and was not able to  replicate the issue.

Please provide more details so I will be able to replicate the issue and fix it.
Comment 3 Petr Jiricka 2009-10-27 09:55:18 UTC
Hi Vince,

sorry I forgot I filed this issue already. Here is my system information:

Product Version: NetBeans IDE Dev (Build web-main-1925-on-091024)
Java: 1.5.0_20; Java HotSpot(TM) Client VM 1.5.0_20-141
System: Mac OS X version 10.5.8 running on i386; MacRoman; en_US (nb)

I am using GlassFish b69 (unpacked zip file) registered manually in the IDE. It looks like the jar files were not copied
to the GF installation dir.
Comment 4 Vince Kraemer 2009-10-27 15:44:22 UTC
where is GF installed?
Comment 5 Petr Jiricka 2009-10-27 15:53:50 UTC
Under my homedir /Users/petrjiricka/glassfish_b69. Now I tried to reproduce under the debugger, and everything works
fine suddenly :-( Weird. 
When I do ls -l under the domains dir, I get the following:
drwxr-xr-x  12 petrjiricka  staff  408 Oct 26 15:51 domain1

Which should be enough.

BTW, I suspect HttpMonitorHelper.copy() is quite inefficient - under the debugger it took >10 seconds to copy the file.
Wouldn't it be more efficient to use FileUtil.copyFile()?

I will keep trying to debug by adding some debug messages instead of the debugger.
Comment 6 Vince Kraemer 2009-10-27 19:33:30 UTC
Thanks for the additional info.

I usually start the iDE under the debugger... though I do not attach...

I just start the IDE 'normally' and could not replicate the issue, though.

I will keep looking.
Comment 7 Petr Jiricka 2009-10-29 14:53:24 UTC
Now I can not reproduce with the latest build - closing as INVALID. I will reopen if I find reproducible steps.
Comment 8 Petr Jiricka 2009-10-30 11:59:39 UTC
Now I think I have a better idea how to reproduce:

1. Add v3 instance
2. Create a WebApp with v3 as target and run it
3. Enable HTTP monitor in the v3 instance properties
4. Run the application again
5. Go to Window -> Debugging -> HTTP Server Monitor

It seems that the monitor setup code is only called if deployment (either initial, or incremental) actually happens. In
this case, there were no changes in the application between the two runs, so the deployment code was not called. When I
create a new class (which triggers deploy-on-save), HTTP monitor starts working (as the monitor configuration is added
and the server is restarted automatically).
Comment 9 TomasKraus 2012-11-22 16:07:47 UTC
Peter, do you have some time to check if this issue still exists in 7.3?
Comment 10 lianhwang 2013-03-26 07:09:04 UTC
Also happens with Tomcat 7 and IDE 7.2.1.
No http Monitor logs except Tomcat Manager activities.

Used to work in IDE 6.5


By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2012, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo