Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 346967 - ECF Hello Service DS Host (zeroconf,generic).product gives errors on startup
Summary: ECF Hello Service DS Host (zeroconf,generic).product gives errors on startup
Status: RESOLVED INVALID
Alias: None
Product: ECF
Classification: RT
Component: ecf.examples (show other bugs)
Version: unspecified   Edit
Hardware: PC All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: ecf.examples-inbox CLA
QA Contact:
URL: http://git.eclipse.org/c/ecf/org.ecli...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-24 07:13 EDT by Alex Blewitt CLA
Modified: 2011-05-24 10:33 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alex Blewitt CLA 2011-05-24 07:13:46 EDT
I checked out the ECF Remote Services DS Host (and consumer), but when I run the Host I get the following error:


osgi> [log;+0100 2011.05.24 12:06:21:435;WARNING;org.eclipse.ecf.osgi.services.remoteserviceadmin;org.eclipse.core.runtime.Status[plugin=org.eclipse.ecf.osgi.services.remoteserviceadmin;code=2;message=org.eclipse.ecf.osgi.services.remoteserviceadmin.RemoteServiceAdmin:exportService:No containers found for serviceReference={org.eclipse.ecf.examples.remoteservices.hello.IHello}={ecf.exported.containerfactoryargs=ecftcp://localhost:3787/server, component.name=org.eclipse.ecf.examples.remoteservices.hello.ds.host, component.id=0, service.exported.configs=ecf.generic.server, service.exported.interfaces=*, service.id=52} properties={component.id=0, component.name=org.eclipse.ecf.examples.remoteservices.hello.ds.host, ecf.exported.containerfactoryargs=ecftcp://localhost:3787/server, objectClass=[Ljava.lang.String;@1b273cc, service.exported.configs=ecf.generic.server, service.exported.interfaces=[Ljava.lang.String;@1f2cea2, service.id=52}. Remote service NOT EXPORTED;severity2;exception=null;children=[]]]
[log;+0100 2011.05.24 12:06:21:435;ERROR;org.eclipse.ecf.osgi.services.remoteserviceadmin;org.eclipse.core.runtime.Status[plugin=org.eclipse.ecf.osgi.services.remoteserviceadmin;code=4;message=org.eclipse.ecf.internal.osgi.services.distribution.BasicTopologyManager:handleServiceRegistered:No export registrations created by RemoteServiceAdmin=org.eclipse.ecf.osgi.services.remoteserviceadmin.RemoteServiceAdmin@77eaf8.  ServiceReference={org.eclipse.ecf.examples.remoteservices.hello.IHello}={ecf.exported.containerfactoryargs=ecftcp://localhost:3787/server, component.name=org.eclipse.ecf.examples.remoteservices.hello.ds.host, component.id=0, service.exported.configs=ecf.generic.server, service.exported.interfaces=*, service.id=52} NOT EXPORTED;severity4;exception=null;children=[]]]

Here's what my runtime looks like:

Framework is launched.

id	State       Bundle
0	ACTIVE      org.eclipse.osgi_3.6.2.R36x_v20110210
1	ACTIVE      org.eclipse.equinox.common_3.6.0.v20100503
2	ACTIVE      org.eclipse.core.runtime_3.6.0.v20100505
3	<<LAZY>>    org.eclipse.ecf.provider_4.2.0.v20110518-0313
4	ACTIVE      org.eclipse.ecf.osgi.services.distribution_2.0.100.v20110518-0313
5	RESOLVED    org.eclipse.osgi.services.remoteserviceadmin_1.0.0.v20110518-0228
6	ACTIVE      org.eclipse.ecf.discovery_4.0.0.v20110518-0313
7	<<LAZY>>    org.eclipse.ecf.sharedobject_2.2.100.v20110518-0313
9	RESOLVED    org.eclipse.osgi.services_3.2.100.v20100503
10	<<LAZY>>    org.eclipse.ecf.provider.remoteservice_4.0.0.v20110518-0313
11	ACTIVE      org.eclipse.ecf.osgi.services.remoteserviceadmin.proxy_1.0.0.v20110518-0313
12	ACTIVE      org.eclipse.equinox.app_1.3.1.R36x_v20100803
13	<<LAZY>>    org.eclipse.ecf.provider.jmdns_4.1.0.v20110518-0313
14	ACTIVE      org.eclipse.equinox.util_1.0.200.v20100503
15	ACTIVE      org.eclipse.equinox.ds_1.2.1.R36x_v20100803
16	ACTIVE      org.eclipse.equinox.preferences_3.3.0.v20100503
17	ACTIVE      org.eclipse.ecf.remoteservice_6.0.0.v20110518-0313
18	ACTIVE      org.eclipse.ecf_3.1.0.v20100906-1425
19	ACTIVE      org.eclipse.equinox.registry_3.5.0.v20100503
20	ACTIVE      org.eclipse.ecf.identity_3.1.0.v20100906-1425
21	ACTIVE      org.eclipse.ecf.osgi.services.remoteserviceadmin_2.0.100.v20110518-0313
22	ACTIVE      org.eclipse.equinox.concurrent_1.0.100.v20100503
23	ACTIVE      org.eclipse.core.jobs_3.5.1.R36x_v20100824
25	ACTIVE      org.eclipse.ecf.examples.remoteservices.hello_3.0.100.v20110518-0313
26	<<LAZY>>    org.eclipse.core.contenttype_3.4.100.v20100505-1235
27	ACTIVE      org.eclipse.ecf.examples.remoteservices.hello.ds.host_3.0.0.v20110518-0313

Note that I previously installed the ECF SDK 3.5.1 into my Eclipse 3.6 host, so there may be some error on my part here. The remoteservices example came from git master.
A few are shown as lazy or resolved, but if I start them all, I still get the same error message when starting/stopping bundle 27.
Comment 1 Alex Blewitt CLA 2011-05-24 07:27:37 EDT
As an update; I installed this into an Eclipse 3.6 install (from master) and it didn't work as it said it was missing org.eclipse.ecf.osgi.services.discovery (which seems to have disappeared in master?)

I rolled back to the 3.4 maintenance branch of ECF and the demo worked OK.

I interpret this to mean the link on the page only works against the latest release, and that org.eclipse.ecf.osgi.services.discovery has gone or been replaced with remoteservicesadmin. If so this bug can probably be closed as invalid.
Comment 2 Scott Lewis CLA 2011-05-24 10:33:15 EDT
(In reply to comment #1)
> As an update; I installed this into an Eclipse 3.6 install (from master) and it
> didn't work as it said it was missing org.eclipse.ecf.osgi.services.discovery
> (which seems to have disappeared in master?)
> 
> I rolled back to the 3.4 maintenance branch of ECF and the demo worked OK.
> 
> I interpret this to mean the link on the page only works against the latest
> release, and that org.eclipse.ecf.osgi.services.discovery has gone or been
> replaced with remoteservicesadmin. 

That's right...it's been removed/replaced with RSA impl (which standardizes endpoint description meta-data and discovery).  Apologies that this hasn't been made clearer in the docs.  I will try to do something about that.

>If so this bug can probably be closed as
> invalid.

Right...I think that's what I will do.  If you still have troubles, please reopen.

In any event, thanks for the report.