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.
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.
*** Issue 173298 has been marked as a duplicate of this issue. ***
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.
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.
where is GF installed?
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.
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.
Now I can not reproduce with the latest build - closing as INVALID. I will reopen if I find reproducible steps.
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).
Peter, do you have some time to check if this issue still exists in 7.3?
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
Report from old NetBeans version. Due to code changes since it was reported likely not reproducible now. Feel free to reopen if happens in 8.0.2 or 8.1.