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.

Bug 115490

Summary:	Cannot perform dynamic attach, "Error getting running process" message is shown
Product:	profiler	Reporter:	bjb <bjb>
Component:	Base	Assignee:	issues@profiler <issues>
Status:	VERIFIED WONTFIX
Severity:	blocker	Keywords:	RELNOTE
Priority:	P2
Version:	6.x
Hardware:	All
OS:	Windows XP
Issue Type:	DEFECT	Exception Reporter:

Description bjb 2007-09-13 20:04:24 UTC

I am not able to connect 6.0 M10 (running JDK6_2) profiler using local dynamic on a tomcat 5.5 running on JDK 6_2.

The Pickup list is not returning any PID at all (even refreshing).

Message is : "Error getting running process"

I've tried with manual modified and automatic modified .bat as well as both start and run mode.

Additional issue is that when connecting using direct mode, it is extremely slow and we are not able to start a middle
range webapplication.

This issue completely prevent proviling on middle range webapplication using the Tomcat, which is IMHO a major server
used nowaday.

Any workaround is welcomed to make it a P2 and remove the "showstoper" tag.

Rgs,
JB

Comment 1 Jiri Sedlacek 2007-09-13 20:07:56 UTC

This looks like a jps problem on Windows, please delete contents of your Temp folder and try again.

Comment 2 Jiri Sedlacek 2007-09-13 20:20:48 UTC

Related information can be found at http://forum.java.sun.com/thread.jspa?threadID=5133218&tstart=0

Comment 3 bjb 2007-09-14 10:09:51 UTC

Hello,

Thanks for the workaround... this has unabled us to see the PID in netbeans.

But this does not solve the issue as it then crash the Tomcat VM with error dialog box :

MS Visual C++ Runtime Library

assertion failed !
JDK1.6.0_2\bin\java.exe
File : ..\src-jdk15\class_file_cache.c
Line 109
Expression : res == JVMTI_ERROR_NONE

Ignoring will then crash the Tomcat VM with error dump :
#
# An unexpected error has been detected by Java Runtime Environment:
#
#  EXCEPTION_INT_DIVIDE_BY_ZERO (0xc0000094) at pc=0x100030e8, pid=3348, tid=5688
#
# Java VM: Java HotSpot(TM) Client VM (1.6.0_02-b06 mixed mode, sharing)
# Problematic frame:
# C  [profilerinterface.dll+0x30e8]
#
# An error report file with more information is saved as hs_err_pid3348.log

FYI, Accessing with JConsole to the same context&environment is fast and perfectly work.

Direct mode is so slow that after 30 minutes of "launching" netbeans says : "application not responding, do you want to
cancel the profiling". In any cas the profile never get back to live mode.

As a consequence this is a blocking issue that completely prevent Tomcat profiling of an application.

Best Regards,
JB

Comment 4 Tomas Hurka 2007-09-15 07:47:51 UTC

The original problems is solved, so there is no reason to reopen this issue. The 'assertion failed' problem is reported as issue #101815 and issue #100641.
For discussing slow startup please use users@profiler.netbeans.org mailing list. FYI: Profiling tomcat with direct attach works fine for me.

Comment 5 bjb 2007-09-17 09:57:46 UTC

Thanks for this feedback and pointing the assertion failed issue.

Direct tooling is "working" too for me but way too slow to be usable on our application (cf previous posts describing
"timeout issues").
Once I'll confirm "performance issue" on direct tooling with another application, I'll open an issue on this one (making
sure this is not at JDK side too).

Best Rgs,
JB

Comment 6 Jiri Sedlacek 2007-09-17 17:08:44 UTC

Updating summary to better describe original problem with dynamic attach.

Comment 7 Jiri Sedlacek 2007-09-19 14:41:17 UTC

Obtaining list of running Java processes may also fail if temporary directory is on FAT filesystem, see 
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=5042659 for more information which also includes a workaround - 
bypass the file system type check.

Comment 8 babicka_baba 2012-05-24 10:41:00 UTC

The link above is dead, but it is archived at 
http://web.archive.org/web/20080610133848/http://forum.java.sun.com/thread.jspa?threadID=5133218&tstart=0

What helped for me (as written above) was to delete a directory named hsperfdata_<user> where <user> is your login and restart the IDE.