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 39499 - Deployment thread lock
Summary: Deployment thread lock
Status: CLOSED WORKSFORME
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Tomcat (show other bugs)
Version: 3.x
Hardware: PC Windows ME/2000
: P3 blocker (vote)
Assignee: Martin Grebac
URL:
Keywords: RANDOM
Depends on:
Blocks:
 
Reported: 2004-02-02 15:46 UTC by zikmund
Modified: 2004-06-08 16:06 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
thread dump (12.25 KB, text/plain)
2004-02-02 15:47 UTC, zikmund
Details

Note You need to log in before you can comment on or make changes to this bug.
Description zikmund 2004-02-02 15:46:43 UTC
Build: 200402011900
It happend to me once and I can't reproduce it again.
1) I had 2 filesystems with several HTML files (4)
and 1 JSP file (just generated).
2) I run it using "Run to cursor" or "Execute"
(I'm not sure) ... but it was the first time of
tomcat using.
3) ERROR: Deployment window stopped.
IDE was still running, no deadlock.
For more see attached thread dump.
Comment 1 zikmund 2004-02-02 15:47:52 UTC
Created attachment 13199 [details]
thread dump
Comment 2 Marek Fukala 2004-02-02 22:59:48 UTC
Just a short note Karle: You run the webmodule in a debugger mode (see
the JDI threads in the threaddump)
Comment 3 Petr Jiricka 2004-02-04 13:57:38 UTC
Martine, is this a debugger issue, or a j2eeserver API issue?

Comment 4 Martin Grebac 2004-02-05 16:23:41 UTC
These are interesting lines:

Terminate batch job (Y/N)? "Thread-17" daemon prio=5 tid=0x1ec341c8 
id=0x648 runnable [2389f000..2389fd8c]
at java.lang.Win32Process.waitFor(Native Method)

I'm curious how is this possible.
Comment 5 zikmund 2004-02-05 16:36:13 UTC
AFAIK it's Win console reaction on Ctrl-Break, which is mixed with
thread dump (don't ask me why).
Comment 6 Martin Grebac 2004-02-12 16:13:48 UTC
Hmm, works for me, too. I never encountered this and from the thread
dump it's not obvious where could be a problem, so closing as
WORKSFORME. Please reopen if you encounter the same again (and don't
forget the new dump then, too).