cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christian Schneider (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (DOSGI-16) Exception when Remoting Service with Single-Bundle Distro w/o Discovery Server
Date Wed, 14 Sep 2016 09:51:20 GMT

     [ https://issues.apache.org/jira/browse/DOSGI-16?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Christian Schneider resolved DOSGI-16.
--------------------------------------
    Resolution: Won't Fix
      Assignee: Christian Schneider

The single bundle distro is not supported anymore.

> Exception when Remoting Service with Single-Bundle Distro w/o Discovery Server
> ------------------------------------------------------------------------------
>
>                 Key: DOSGI-16
>                 URL: https://issues.apache.org/jira/browse/DOSGI-16
>             Project: CXF Distributed OSGi
>          Issue Type: Bug
>            Reporter: David Bosschaert
>            Assignee: Christian Schneider
>            Priority: Minor
>
> When using the Single Bundle Distribution you may get the following exception when remoting
a service:
> SEVERE: Exception while processing the addition of a ServicePublication.
> org.apache.zookeeper.KeeperException$ConnectionLossException: KeeperErrorCode = ConnectionLoss
> 	at org.apache.zookeeper.KeeperException.create(KeeperException.java:59)
> 	at org.apache.zookeeper.ZooKeeper.exists(ZooKeeper.java:593)
> 	at org.apache.zookeeper.ZooKeeper.exists(ZooKeeper.java:620)
> 	at org.apache.cxf.dosgi.discovery.zookeeper.PublishToZooKeeperCustomizer.ensurePath(PublishToZooKeeperCustomizer.java:112)
> 	at org.apache.cxf.dosgi.discovery.zookeeper.PublishToZooKeeperCustomizer.addingService(PublishToZooKeeperCustomizer.java:68)
> 	at org.osgi.util.tracker.ServiceTracker$Tracked.trackAdding(ServiceTracker.java:1021)
> 	at org.osgi.util.tracker.ServiceTracker$Tracked.track(ServiceTracker.java:999)
> 	at org.osgi.util.tracker.ServiceTracker$Tracked.serviceChanged(ServiceTracker.java:924)
> 	at org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:124)
> 	at org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:930)
> 	at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:220)
> 	at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:149)
> 	at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:757)
> 	at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:712)
> 	at org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:129)
> 	at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:206)
> 	at org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:506)
> 	at org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:524)
> 	at org.apache.cxf.dosgi.dsw.hooks.ServiceHookUtils.publish(ServiceHookUtils.java:55)
> 	at org.apache.cxf.dosgi.dsw.hooks.CxfPublishHook.publishEndpoint(CxfPublishHook.java:82)
> 	at org.apache.cxf.dosgi.dsw.Activator$1.run(Activator.java:164)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
> 	at java.lang.Thread.run(Unknown Source)
> This happens when you don't have a Zookeeper Discovery Server running.
> The exception is harmless and everything still works but it should be changed into an
INFO log message as running without Discovery is a perfectly valid use case.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message