Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 333852 - ch.ethz.iks.r_osgi.RemoteOSGiException: Channel is closed
Summary: ch.ethz.iks.r_osgi.RemoteOSGiException: Channel is closed
Status: CLOSED WORKSFORME
Alias: None
Product: ECF
Classification: RT
Component: ecf.providers (show other bugs)
Version: 3.4.0   Edit
Hardware: PC Windows Vista
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: ecf.core-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-10 06:06 EST by Martin Petzold CLA
Modified: 2011-01-12 08:30 EST (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 Martin Petzold CLA 2011-01-10 06:06:14 EST
Environment: JmDNS, R-OSGi

Provider and Consumer Application (OSGi instance) on the same machine. If I close a provider and then reopen it (short time after each other) this exception occured.

ENTRY org.eclipse.osgi 4 0 2011-01-10 11:57:32.439
!MESSAGE An unexpected runtime error has occurred.
!STACK 0
ch.ethz.iks.r_osgi.RemoteOSGiException: Channel is closed
	at ch.ethz.iks.r_osgi.impl.ChannelEndpointImpl.send(ChannelEndpointImpl.java:974)
	at ch.ethz.iks.r_osgi.impl.ChannelEndpointImpl.sendLeaseUpdate(ChannelEndpointImpl.java:755)
	at ch.ethz.iks.r_osgi.impl.RemoteOSGiServiceImpl.updateLeases(RemoteOSGiServiceImpl.java:1052)
	at ch.ethz.iks.r_osgi.impl.RemoteOSGiServiceImpl$3.addingService(RemoteOSGiServiceImpl.java:533)
	at org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:896)
	at org.osgi.util.tracker.AbstractTracked.trackAdding(AbstractTracked.java:261)
	at org.osgi.util.tracker.AbstractTracked.track(AbstractTracked.java:233)
	at org.osgi.util.tracker.ServiceTracker$Tracked.serviceChanged(ServiceTracker.java:840)
	at org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:104)
	at org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:933)
	at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:227)
	at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:149)
	at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:756)
	at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:711)
	at org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
	at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:206)
	at org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:507)
	at proxy.jumper_jchjhb.devsosgi.event.IEventHandlerImpl.start(Unknown Source)
	at org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(BundleContextImpl.java:783)
	at java.security.AccessController.doPrivileged(Native Method)
	at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:774)
	at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:755)
	at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:370)
	at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:284)
	at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:276)
	at ch.ethz.iks.r_osgi.impl.ChannelEndpointImpl.installResolveAndStartBundle(ChannelEndpointImpl.java:819)
	at ch.ethz.iks.r_osgi.impl.ChannelEndpointImpl.getProxyBundle(ChannelEndpointImpl.java:799)
	at ch.ethz.iks.r_osgi.impl.RemoteOSGiServiceImpl.fetchService(RemoteOSGiServiceImpl.java:867)
	at ch.ethz.iks.r_osgi.impl.RemoteOSGiServiceImpl.getRemoteService(RemoteOSGiServiceImpl.java:788)
	at org.eclipse.ecf.internal.provider.r_osgi.R_OSGiRemoteServiceContainer.getRemoteService(R_OSGiRemoteServiceContainer.java:198)
	at org.eclipse.ecf.internal.osgi.services.distribution.DiscoveredServiceTrackerImpl.registerRemoteServiceReferences(DiscoveredServiceTrackerImpl.java:575)
	at org.eclipse.ecf.internal.osgi.services.distribution.DiscoveredServiceTrackerImpl.handleDiscoveredServiceAvailable(DiscoveredServiceTrackerImpl.java:273)
	at org.eclipse.ecf.internal.osgi.services.distribution.DiscoveredServiceTrackerImpl.access$4(DiscoveredServiceTrackerImpl.java:206)
	at org.eclipse.ecf.internal.osgi.services.distribution.DiscoveredServiceTrackerImpl$1.dispatchEvent(DiscoveredServiceTrackerImpl.java:101)
	at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:227)
	at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:337)
Comment 1 Markus Kuppe CLA 2011-01-10 06:16:22 EST
Can you provide a test case that reproduces this behavior?
Comment 2 Martin Petzold CLA 2011-01-12 08:30:21 EST
I think this problem only occurs if a remote service is registered before r-osgi is completely started (e.g. set start levels).