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.
Created attachment 119023 [details] IDE log. It is not possible to profile web application. To reproduce: - install 7.2 beta (http://smetiste.cz.oracle.com/builds/netbeans/7.2/beta/2012-05-02_15-16-04/ml/start.html?platform=windows&lang=en&option=javaee) to default location on Windows 7 64 - create web project with GlassFish (C:\Program Files\glassfish-3.1.2) - right-click project node and choose Profile - click Run in dialog - it fails and progress dialog "Connecting to the target VM..." stays opened (see attached logs) Product Version: NetBeans IDE 7.2 Beta (Build 201205021516) Java: 1.7.0_04; Java HotSpot(TM) 64-Bit Server VM 23.0-b21 System: Windows 7 version 6.1 running on amd64; Cp1250; en_US (nb) User directory: C:\Users\jskrivanek\AppData\Roaming\NetBeans\7.2beta
Created attachment 119024 [details] Server and Ant logs.
tomas: please investigate this
could not replicate with recent pull on Mac OS X
(In reply to comment #3) > could not replicate with recent pull on Mac OS X Note: this is just an FYI. I am not actively working this issue. Just trying to make sure it isn't a P1
looks like a space-in-path issue to me.
I was also unable to reproduce this with NB 7.2 build on Linux with local GlassFish configured. Will give it another try on Windows this afternoon.
Targeting to 7.2. If Vince is true, this fix won't take long.
Reproduced on Windows machine with glassfish in C:\Program files\gf-312 directory. Application was deployed and opened in Firefox (http://localhost:8080/WebApplicationTest/). In NetBeans 'Connecting to the target VM...' window stays opened.
Any progress with this bug? Probably not only space-in-path issue. Reproduced also with GlassFish in C:\Users\jskrivanek\GlassFish_Server the following way: - create Java EE 6 web project with GlassFish server - right-click project node and choose Profile - wait until profiling is started and browser is opened - stop profiling (menu item "Profile|Stop Profiling Session") - again right-click project node and choose Profile - server is not started and it fails with message compile-jsps: In-place deployment at D:\Development\builds\nbUserdir-20120604145844\WebApplication2\build\web deploy?DEFAULT=D:\Development\builds\nbUserdir-20120604145844\WebApplication2\build\web&name=WebApplication2&contextroot=/WebApplication2&force=true failed. Instance is not GlassFish Server 3+. Product Version: NetBeans IDE Dev (Build 201206050001) Java: 1.7.0_04; Java HotSpot(TM) 64-Bit Server VM 23.0-b21 System: Windows 7 version 6.1 running on amd64; Cp1250; en_US (nb)
This looks and reads like a different bug to me. I opened http://netbeans.org/bugzilla/show_bug.cgi?id=213640 to track it instead of mixing multiple bugs into this one issue. (In reply to comment #9) > Any progress with this bug? Probably not only space-in-path issue. Reproduced > also with GlassFish in C:\Users\jskrivanek\GlassFish_Server the following way: > > - create Java EE 6 web project with GlassFish server > - right-click project node and choose Profile > - wait until profiling is started and browser is opened > - stop profiling (menu item "Profile|Stop Profiling Session") > - again right-click project node and choose Profile > - server is not started and it fails with message > > compile-jsps: > In-place deployment at > D:\Development\builds\nbUserdir-20120604145844\WebApplication2\build\web > deploy?DEFAULT=D:\Development\builds\nbUserdir-20120604145844\WebApplication2\build\web&name=WebApplication2&contextroot=/WebApplication2&force=true > failed. Instance is not GlassFish Server 3+. > > Product Version: NetBeans IDE Dev (Build 201206050001) > Java: 1.7.0_04; Java HotSpot(TM) 64-Bit Server VM 23.0-b21 > System: Windows 7 version 6.1 running on amd64; Cp1250; en_US (nb)
I tested this scenario again today and I'm unable to reproduce this issue with last 7.2 build. Jiri, can you please re-test it again to see if it's still freezes after 'run'?
I believe this issue and issue #213640 have a common cause. So the patch attached in #213640 should hopefully solve this as well.
Jirko, can you also verify this one? It should be fixed by 74f26d341f9b done for issue #213640.
Still reproducible in dev build 201206250002 and 7.2rc1.
Created attachment 121286 [details] New stack trace.
Looks like the agent path is not properly escaped. So the problem is space in path of NB location. Error occurred during initialization of VM agent library failed to init: C:\Program Files\NetBeans Dev 201206250002\profiler\lib\deployed\jdk16\windows-amd64\profilerinterface.dll Profiler Agent: Initializing... Profiler Agent: Options: >C:\Program< Profiler Agent: -agentpath:<PATH>/profilerinterface should be called with two parameters: Profiler Agent: path to Profiler agent libraries and port number, separated by comma, for example: Profiler Agent: java -agentpath:/mypath/profilerinterface=/home/me/nb-profiler-server/profiler-ea-libs,5140 INFO: Running GlassFish Version: GlassFish Server Open Source Edition 3.1.2 (build 23) INFO: Grizzly Framework 1.9.46 started in: 109ms - bound to [0.0.0.0:3700] INFO: Grizzly Framework 1.9.46 started in: 78ms - bound to [0.0.0.0:7676] INFO: Grizzly Framework 1.9.46 started in: 109ms - bound to [0.0.0.0:4848] INFO: Grizzly Framework 1.9.46 started in: 140ms - bound to [0.0.0.0:8181] INFO: Grizzly Framework 1.9.46 started in: 218ms - bound to [0.0.0.0:8080] INFO: Registered org.glassfish.ha.store.adapter.cache.ShoalBackingStoreProxy for persistence-type = replicated in BackingStoreFactoryRegistry INFO: GlassFish Server Open Source Edition 3.1.2 (23) startup time : Felix (16 860ms), startup services(3 015ms), total(19 875ms) INFO: JMX005: JMXStartupService had Started JMXConnector on JMXService URL service:jmx:rmi://PHEJL-CZ.cz.oracle.com:8686/jndi/rmi://PHEJL-CZ.cz.oracle.com:8686/jmxrmi INFO: Hibernate Validator 4.2.0.Final INFO: Grizzly Framework 1.9.46 started in: 15ms - bound to [0.0.0.0:8080] INFO: unable to read instance state file C:\Users\phejl\AppData\Roaming\NetBeans\dev\config\GF3\domain1\config\.instancestate, recreating INFO: Grizzly Framework 1.9.46 started in: 16ms - bound to [0.0.0.0:8181]
Yes, I can replicate the problem when NetBeans is installed in folder with space in path.
This issue is glassfish specific. Tomcat, JBoss and Weblogic can process the profiler jvm args in its current form.
fixed in http://hg.netbeans.org/profiler-main/rev/05a657e0a8d5
Verified in patched trunk build 201206270002. Please, transplant to release72 branch till COB today.
The patch looks OK. It can be integrated into release72 branch.
Transplanted to release72 branch, changeset: 232332:c40e68474b18 branch: release72 user: Jaroslav Bachorik <yardus@netbeans.org> date: Wed Jun 27 10:00:15 2012 +0200 summary: #212011: Changing escaping the profiler jvm agent arg to make glassfish happy
Integrated into 'releases', will be available in build *201206272359* or newer. Wait for official and publicly available build. Changeset: http://hg.netbeans.org/releases/rev/c40e68474b18 User: Jaroslav Bachorik <yardus@netbeans.org> Log: #212011: Changing escaping the profiler jvm agent arg to make glassfish happy (transplanted from 05a657e0a8d5137a290676fe98b5ff3afd7e1b80)
Verified in NetBeans IDE 7.2 RC1 (Build 201206272359).
Integrated into 'main-golden', will be available in build *201207020907* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-golden/rev/05a657e0a8d5 User: Jaroslav Bachorik <yardus@netbeans.org> Log: #212011: Changing escaping the profiler jvm agent arg to make glassfish happy