Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 336200 - Hot-deployment of atomic plans produces two "starting" plan event log entries
Summary: Hot-deployment of atomic plans produces two "starting" plan event log entries
Status: CLOSED FIXED
Alias: None
Product: Virgo
Classification: RT
Component: runtime (show other bugs)
Version: 3.0.0.M01   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: 3.0.0.M01   Edit
Assignee: Borislav Kapukaranov CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-02-03 04:14 EST by Borislav Kapukaranov CLA
Modified: 2011-02-28 10:53 EST (History)
1 user (show)

See Also:

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 Borislav Kapukaranov CLA 2011-02-03 04:14:44 EST 
When deploying atomic plan both on kernel and web-server distributions the "starting" plan trace is printed twice. The "started" bundle trace is also printed twice. It seems for the moment that the plan is being started two times.

Steps to reproduce:
1. Copy an atomic plan in pickup
2. Check the console traces
Comment 1 Borislav Kapukaranov CLA 2011-02-03 04:21:04 EST 
After a bit of debugging i found that the plan bundles are installed, starting and started already on the install step. This proves that the plan is being started twice. It seems there is a bug somewhere in the install phase.
Comment 2 Borislav Kapukaranov CLA 2011-02-16 08:12:40 EST 
Fixed and pushed. Now deploying atomic plans containing lazy bundles produce one starting event log, as expected. A test case is also provided.