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 159738 - RuntimeManagementService.listServiceAssemblies() returns wrong SA state when the JBI Framework is not ready
Summary: RuntimeManagementService.listServiceAssemblies() returns wrong SA state when ...
Status: NEW
Alias: None
Product: soa
Classification: Unclassified
Component: JBI Manager (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: Jun Qian
URL:
Keywords:
: 134934 151323 (view as bug list)
Depends on:
Blocks:
 
Reported: 2009-03-06 02:17 UTC by Jun Qian
Modified: 2009-03-06 02:22 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 Jun Qian 2009-03-06 02:17:13 UTC 
There are several NetBeans tickets about first-time deployment/undeployment that requires some runtime support.

Use Case: The user tries to deploy/undeploy a CompApp project from within NetBeans when the GlassFish is in stopped state.

This is what happens inside NetBeans:
1. NetBeans starts GlassFish;
2. NetBeans gets blocked until the GlassFish is up and running;
3. NetBeans checks the status of the given CompApp by calling

    com.sun.esb.management.api.runtime.RuntimeManagementService.listServiceAssemblies()

4. Based on the CompApp status, NetBeans does start/stop/shutdown/deploy/undeploy accordingly...

In Step 3, the status returned from the runtime could be wrong because the JBI runtime might not be completely up and
ready to take service request at this point yet. If some delay is put before step 3, then the correct state of the
deployed compapps can be retrieved. Since currently there is no API the client can call to check the JBI framework's
readiness, can we make the RuntimeManagementService.listServiceAssemblies() call blocking, or make it return unknown SA
state so that the client can keep polling for some period of time until the SA state is known or timeout?
Comment 1 Jun Qian 2009-03-06 02:20:12 UTC 
*** Issue 151323 has been marked as a duplicate of this issue. ***
Comment 2 Jun Qian 2009-03-06 02:22:49 UTC 
*** Issue 134934 has been marked as a duplicate of this issue. ***