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 42811 - JPDAConnect blocks for a long time
Summary: JPDAConnect blocks for a long time
Status: CLOSED WORKSFORME
Alias: None
Product: debugger
Classification: Unclassified
Component: Java (show other bugs)
Version: 4.x
Hardware: PC Linux
: P2 blocker (vote)
Assignee: Jan Jancura
URL:
Keywords: PERFORMANCE, REGRESSION
Depends on:
Blocks:
 
Reported: 2004-05-05 09:31 UTC by Martin Grebac
Modified: 2006-03-24 10:15 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
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 Martin Grebac 2004-05-05 09:31:35 UTC 
1.Create web project
2.Run main project in debugger

When JPDAConect task is invoked from ant, it takes
about 10-15 seconds to finish, but it just waits
for something (there's no cpu usage).
Comment 1 Martin Grebac 2004-05-05 09:41:46 UTC 
The actual time is 27 seconds to execute JPDAConnect. Used to be about 1s.
Comment 2 Martin Grebac 2004-05-05 16:55:20 UTC 
Seems to be a problem with my computer only, but it doesn't look like
a a problem with dns resolution.
Comment 3 Martin Grebac 2004-05-06 13:32:42 UTC 
Hmm, does not happen anymore even on my machine. Don't know what was
wrong. Silly.
Comment 4 Martin Grebac 2004-05-26 17:08:03 UTC 
We've seen this today on Hanz's machine and I still was not able to
resolve the problem on my machine, so reopening and raising priority.
Can be JDK specific - I'll check it out.
Comment 5 Maros Sandor 2004-06-22 09:41:11 UTC 
I'm unable to reproduce it on WXP JDK 1.4.2_04, will try on Fedora 
later.
Comment 6 Maros Sandor 2004-06-28 15:09:34 UTC 
I cannot reproduce it in Fedora either.
Comment 7 Maros Sandor 2004-07-20 09:09:57 UTC 
Does it still block that long? I cannot examine this issue directly 
because I cannot reproduce it. I may be that you network config is 
broken (long time without CPU activity).
Comment 8 Martin Grebac 2004-07-20 09:48:16 UTC 
No, I didn't see this for some time.
Comment 9 Martin Grebac 2004-07-21 16:39:51 UTC 
verified in 200407201800