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 97710 - JBoss process is not fully stopped on Stop Profiling Session action
Summary: JBoss process is not fully stopped on Stop Profiling Session action
Status: RESOLVED WORKSFORME
Alias: None
Product: profiler
Classification: Unclassified
Component: Base (show other bugs)
Version: 5.x
Hardware: PC Windows XP
: P3 blocker (vote)
Assignee: J Bachorik
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-03-13 09:58 UTC by Alexander Kouznetsov
Modified: 2008-07-07 10:20 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
JBoss 2nd profiling attempt output (538 bytes, text/plain)
2007-11-06 19:06 UTC, Alexander Kouznetsov 		Details
Profiler output and thread dump (18.44 KB, text/plain)
2007-11-06 19:06 UTC, Alexander Kouznetsov 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander Kouznetsov 2007-03-13 09:58:06 UTC 
Profiler 070309
NetBeans IDE Dev (Build 200703111900)
1.6.0; Java HotSpot(TM) Client VM 1.6.0-b105
Windows XP version 5.1 running on x86
ru_RU (nb); Cp1251
JBoss (MX MicroKernel) [4.0.5.GA (build: CVSTag=Branch_4_0 date=200610162339)]
JBoss (MX MicroKernel) [4.0.4.GA (build: CVSTag=JBoss_4_0_4_GA date=200605151000)]

This issue is reproducible in 5.5.1 as well.

Steps to reproduce:
- Start Profiling Project on JBoss server
(http://www.netbeans.org/nonav/issues/showattachment.cgi/38685/jboss_test.zip)
- Do some profiling
- Stop Profiler with server
- RESULT: Even server is shown as stopped (and logs say the same), its process
is still running and is preventing server to be started again (due to some ports
occupation).
Comment 1 J Bachorik 2007-09-20 09:11:56 UTC 
can not reproduce it. the threaddumps of profiler IDE and the server process would help in resolving this issue
thanks
Comment 2 Alexander Kouznetsov 2007-11-06 19:05:17 UTC 
No thread dump is available for hanging JBoss process since jps, jconsole and jstack don't show it. However, it is still
shown in Task Manager and netstat also shows that 2390, 2391, 2393 and 1098 are occupied. On the second attempt to
perform JBoss project profiling it outputs the following:
JBoss Application Server Start Failed. RMI naming service port 1098 is already in use.

Once this hanging process is killed manually the JBoss profiling is possible again.
Comment 3 Alexander Kouznetsov 2007-11-06 19:06:01 UTC 
Created attachment 52619 [details]
JBoss 2nd profiling attempt output
Comment 4 Alexander Kouznetsov 2007-11-06 19:06:28 UTC 
Created attachment 52620 [details]
Profiler output and thread dump
Comment 5 Alexander Kouznetsov 2007-11-06 19:08:50 UTC 
Reproduced with
Product Version: NetBeans IDE Dev (Build 200711060000)
Java: 1.6.0_03; Java HotSpot(TM) Client VM 1.6.0_03-b05
System: Windows XP version 5.1 running on x86; Cp1251; ru_RU (nb)
JBoss 4.2.2.GA
Comment 6 J Bachorik 2008-07-07 10:20:54 UTC 
This works flawlessly for me with the current dev build:

Product Version: NetBeans IDE Dev (Build 080703)
Java: 1.6.0_10-beta; Java HotSpot(TM) Client VM 11.0-b12
System: Linux version 2.6.24-19-generic running on i386; UTF-8; en_US (nb)