Issue Details (XML | Word | Printable)

Key: GLASSFISH-12033
Type: New Feature New Feature
Status: Resolved Resolved
Resolution: Fixed
Priority: Blocker Blocker
Assignee: martin.mares
Reporter: Tom Mueller
Votes: 0
Watchers: 1

If you were logged in you would be able to see more operations.

DYREC-007: progress status implementation

Created: 25/May/10 11:48 AM   Updated: 13/Dec/12 08:19 PM  Due: 15/Aug/11   Resolved: 13/Dec/12 08:19 PM
Component/s: admin
Affects Version/s: 3.1
Fix Version/s: 4.0_b60

Time Tracking:
Not Specified


Operating System: All
Platform: All

Issue Links:

Issuezilla Id: 12,033
Participants: Alexis MP, martin.mares, Tom Mueller and vijaysr

 Description  « Hide


This feature is to provide a mechanism to get progress status for long running
operations (ex. deploy). This issue is for the implementation of the feature.

vijaysr added a comment - 08/Jun/10 03:14 PM

Since some resources were moved out, this feature has been given a lower priority. This may be dropped
from 3.1 itself - not decided as yet.

Alexis MP added a comment - 29/Jun/10 11:43 AM


vijaysr added a comment - 03/Aug/10 02:43 PM

Dropped for 3.1

vijaysr added a comment - 28/Oct/10 10:34 AM

Transferring requested / planned enhancements for 3.2 to Tom to be reassigned to appropriate engineers

Tom Mueller added a comment - 06/Apr/11 08:29 AM

Must have for 3.2.

Tom Mueller added a comment - 05/Jul/11 01:31 PM

The implementation of this progress framework should also include changes to the start-instance and start-cluster commands to use it.