Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 82121 - [Progress] [RCP] Automatic Triggered Jobs in RCP doesnt show progress
Summary: [Progress] [RCP] Automatic Triggered Jobs in RCP doesnt show progress
Status: RESOLVED DUPLICATE of bug 82146
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Runtime (show other bugs)
Version: 3.1   Edit
Hardware: PC Windows 2000
: P2 major (vote)
Target Milestone: ---   Edit
Assignee: John Arthorne CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-01-03 22:38 EST by Ramakrishnan CLA
Modified: 2005-01-05 10:03 EST (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ramakrishnan CLA 2005-01-03 22:38:56 EST
In my RCP, I've added one line to "preWindowOpen(...)" function of
ApplicationAdvisor class to enable the progress indicator
    configurer.setShowProgressIndicator(true);

After that i've no problems executing User Jobs [jobObject.setUser(true)] which
show a progress dialog. But in case of Automatically Trigerred Jobs, which are
to be shown jus in right side in status bar's progress indicator area, progress
is not at all shown.

Same code works when run inside IDE, but not in a RCP :-(.

There were couple of mail threads in Newsgroups, they were discussing the same
problem, but without any result they had closed.
Comment 1 Ramakrishnan CLA 2005-01-03 22:42:28 EST
As a work around, now whenever i'm creating auto triggered jobs for the very
first time before any other job [user / auto-triggered ], i create a dummy very
trivial user job. After this UI shows the progress Auto-triggered jobs too.

I feel this is a ugly thing to do, and need your help asap.

Comment 2 Jean-Michel Lemieux CLA 2005-01-04 11:05:29 EST
Debugged with John this morning and figured out that the problem is related to
job scheduling in runtime. Basically, when a schedule is called within a
listener a new worker thread isn't being created.
Comment 3 John Arthorne CLA 2005-01-04 12:37:11 EST
Although this bug is older, I am marking as a duplicate since I have already
attached a fix to the other bug.

*** This bug has been marked as a duplicate of 82146 ***
Comment 4 Ramakrishnan CLA 2005-01-05 09:27:30 EST
Thanks!! Can u suggest me some way , i can make this code work with my eclipse
3.1 m3. Since i've some deadlines too meet, its very difficult to wait till M5.

Comment 5 Jean-Michel Lemieux CLA 2005-01-05 09:43:50 EST
apply the patch attached in bug 82146.
Comment 6 John Arthorne CLA 2005-01-05 10:03:55 EST
Re: comment #4 - if you don't want to patch Eclipse, the work around you mention
in comment #1 is the only solution I can think of.  This problem doesn't
typically appear in the Eclipse SDK because there are always a few quick jobs
that run on startup, and this "kick starts" the thread pool and prevents this
problem from happening.  It should work as a temporary measure until a build is
available with the proper fix.