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.
Syeps to reproduce: - create any sample application project (e.g. SynchronousSample) - add JBI module to the application - deploy the application - debug the application - close debug session - switch to Runtime tab and stop the application - try to shutdown the application Result: Shutdowning takes long time then fails with message in JBI Console: Failed execution of shutdownServiceAssembly. com.sun.jbi.ui.common.JBIRemoteException
I could still reproduce the problem with build 060727_18. (The app server is from build 060724.) After I attached the BPEL debugger and ran a testcase, I noticed that I couldn't stop in the bpel code. I got the following in server.log. (See Attachment DebuggerError.txt) I then detached the debugger, stopped the SA and tried to shutdown the SA. I got a timeout error as originally reported. The following is the error message from server.log. (See Attachment ShutdownError.txt) I think this is some problem in the BPEL runtime/debugger.
Created attachment 32273 [details] DebugError.txt
Created attachment 32274 [details] ShutdownError.txt
With build 060728, when attached to the BPEL debugger, I could hit my breakpoint just fine and I didn't see the debugger error anymore, but I still got timeout on shutting down the SA. I tried the whole process once again (on a fresh JBI installation) except that I didn't attach the BPEL debugger this time. I could stop/shutdown/undeploy the SA without any problem. This leads me to think maybe there are some resources that are not released after attaching/detaching the BPEL debugger? I am reassigning this to the BPEL debugger team for comments.
see also 81280
Bug is reproducible in coke milestone build 17.
Mei Wu has fixed this issue. There was an additional thread that was making a duplicate call to detach the client, this erroneous thread has been removed.
verified in build 060806_1