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 168695 - Deployment progress never stopped when Deploy on Save option is enabled
Summary: Deployment progress never stopped when Deploy on Save option is enabled
Status: RESOLVED DUPLICATE of bug 186898
Alias: None
Product: platform
Classification: Unclassified
Component: Progress (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: Jan Peska
URL:
Keywords: RANDOM
Depends on:
Blocks:
 
Reported: 2009-07-16 16:08 UTC by Masaki Katakai
Modified: 2011-08-11 14:39 UTC (History)
0 users

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 Masaki Katakai 2009-07-16 16:08:49 UTC 
Product Version: NetBeans IDE 6.7.1 RC (Build 200907150227)
Java: 1.6.0_13; Java HotSpot(TM) 64-Bit Server VM 11.3-b02-83
System: Mac OS X version 10.5.7 running on x86_64; SJIS; en (nb)

I got a report from community member in Japan. It was reported about
NetBeans 6.7 FCS but it seems that it's still happening on 6.7.1 RC.

It seems that deployment process will not stop with Deploy on Save option.

1. Start NetBeans with bundled tomcat
2. Create web application and set tomcat as server
   Make sure Deploy on Save is ON
3. Run
   default page will be displayed on browser
4. Modify index.jsp then Ctrl+S to save
   It will succeed first time
5. Try step 4 several times
   It looks deployment itself is finished but
   progress window is still running and showing
   "Deploying WebApplicato1..." is still displayed.
  
   There is no way to stop.
Comment 1 Petr Hejl 2009-10-27 15:25:34 UTC 
The progress is properly finished. Looks like there is some kind of race condition in progress api - I saw this rarely
under different circumstances.
Comment 2 Jan Peska 2011-08-11 14:39:55 UTC 

*** This bug has been marked as a duplicate of bug 186898 ***