| Summary: | Problem starting host.ds example | ||
|---|---|---|---|
| Product: | [RT] ECF | Reporter: | Wim Jongman <wim.jongman> |
| Component: | ecf.remoteservices | Assignee: | ecf.core-inbox <ecf.core-inbox> |
| Status: | CLOSED INVALID | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | bugs.eclipse.org, slewis |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | |||
|
Description
Wim Jongman
This patch solved it for me:
### Eclipse Workspace Patch 1.0
#P org.eclipse.ecf.examples.remoteservices.hello.ds.host
Index: products/Hello Service DS Host (zeroconf,generic).product
===================================================================
RCS file: /cvsroot/rt/org.eclipse.ecf/examples/bundles/org.eclipse.ecf.examples.remoteservices.hello.ds.host/products/Hello Service DS Host (zeroconf,generic).product,v
retrieving revision 1.1
diff -u -r1.1 Hello Service DS Host (zeroconf,generic).product
--- products/Hello Service DS Host (zeroconf,generic).product 12 May 2010 04:27:07 -0000 1.1
+++ products/Hello Service DS Host (zeroconf,generic).product 2 Jun 2010 22:22:30 -0000
@@ -49,10 +49,13 @@
</plugins>
<configurations>
- <plugin id="org.eclipse.ecf.examples.remoteservices.hello.ds.host" autoStart="true" startLevel="0" />
- <plugin id="org.eclipse.ecf.osgi.services.distribution" autoStart="true" startLevel="0" />
- <plugin id="org.eclipse.equinox.common" autoStart="true" startLevel="2" />
+ <plugin id="org.eclipse.ecf.examples.remoteservices.hello.ds.host" autoStart="false" startLevel="0" />
+ <plugin id="org.eclipse.ecf.osgi.services.discovery" autoStart="true" startLevel="0" />
+ <plugin id="org.eclipse.ecf.osgi.services.distribution" autoStart="true" startLevel="3" />
+ <plugin id="org.eclipse.ecf.provider.remoteservice" autoStart="true" startLevel="1" />
+ <plugin id="org.eclipse.equinox.common" autoStart="true" startLevel="1" />
<plugin id="org.eclipse.equinox.ds" autoStart="true" startLevel="2" />
+ <plugin id="org.eclipse.osgi.services" autoStart="true" startLevel="0" />
</configurations>
</product>
Hi Wim. I've never seen this in my own running of the ds example (host I guess). Is this easily reproducible? Any conditions that particularly affect it? The only reason I ask is that in general...and to the extent possible...I would like to avoid fussing with start levels of the example bundles...since I don't think it will be obvious/clear to people why such start levels are set the way that they are. Maybe for ECF 3.4 we can add a plan item and work on making the bundles/examples start level unaware. Hi, I agree. But fiddling with start levels is the biggest time consumer so far in working the ECF 3.3 and Zookeeper. I am sure it must be something in the ZK bundle but it is still pretty annoying. Could it be somebody's hardware being fast or slow that causes timing problems? When I start the DS straight out of the CVS repository in my workspace i get: "Thread[JMDNS Discovery Thread,5,main]" timed out waiting (5000ms) for thread "Thread[Start Level Event Dispatcher,5,main]" to finish starting bundle "org.eclipse.ecf.osgi.services.distribution_1.2.0.qualifier [17]" every time. Is there any more evidence about what's going on with this problem?...or is it still a problem for you Wim? I am still unable to reproduce. Haven't seen it for a while. |