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 40396 - Initial Tomcat deployment fails on debug
Summary: Initial Tomcat deployment fails on debug
Status: VERIFIED FIXED
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Tomcat (show other bugs)
Version: 3.x
Hardware: PC Windows ME/2000
: P3 blocker (vote)
Assignee: Pavel Buzek
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-02-23 23:16 UTC by clever
Modified: 2006-02-28 12:16 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
ide.log from my problematic Tomcat deployment (51.88 KB, text/plain)
2004-02-23 23:18 UTC, clever
Details

Note You need to log in before you can comment on or make changes to this bug.
Description clever 2004-02-23 23:16:40 UTC
After importing an existing project into the
latest dev NetBeans build, I attempted to 'debug'
my webapp.  This is my normal procedure, since I
gain all the benefits of debugging.  Tomcat gave
the appearance of hanging. The deployment dialog
let me close it, but the progress never reached
100%.  As an observation, I noticed the debug UI
did take effect in the IDE.
I attempted a restart of the IDE and could easily
recreate the problem with my current webapp.
I then decided to try an 'execute' the webapp.
This worked. It seemed to have created the context
in Tomcat, and all worked.
Subsequently, I shutdown Tomcat and attempted a
'debug'. This time it worked.

Attached is what I found in the ide.log file after
running into the problem initially.  Subsequently
I undeployed my app (as a test), and attempted to
start Tomcat with a 'debug' session to recreate
the problem. This time it worked. Perhaps the IDE
log info can pinpoint a slight defect.
Comment 1 clever 2004-02-23 23:18:47 UTC
Created attachment 13593 [details]
ide.log from my problematic Tomcat deployment
Comment 2 Petr Jiricka 2004-02-24 07:59:19 UTC
This sounds nasty. Shouldn't this really be a P2? Clever, what build
are you using? Can you please try the latest dev build, if you haven't
done so already? Thanks.

Comment 3 clever 2004-02-24 14:25:08 UTC
I was using a dev build from last week. I am downloading the latest
build and will attempt to recreate the problem in it.  Since my
initial encounter with this problem it's been smooth sailing, which is
good, but I'd hate to have a serious problem slip through the cracks.
I'll try to recreate and update this bug.
Comment 4 Pavel Buzek 2004-02-27 18:11:54 UTC
I think I recall a similar exception from an older build that was then
reported as fixed in a newer build. If you can test with new build and
see the problem again I will change it back to 36 and perhaps rise to
P2. Marking for promo-D for now.
Comment 5 Pavel Buzek 2004-08-06 19:19:21 UTC
looks like it was fixed, if you can still reproduce it please reopen
this issue
Comment 6 Jaroslav Pospisil 2006-02-28 12:16:14 UTC
VERIFIED