[
https://issues.apache.org/jira/browse/CELIX-170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14175086#comment-14175086
]
Daniel Parker commented on CELIX-170:
-------------------------------------
celix Remote Service messages after restarting felix:
-> ERROR: ENDPOINT_POLLER: unable to read endpoints, reason: Couldn't connect
to server
at
endpointDiscoveryPoller_getEndpoints(/home/dparker/yocto/poky/build-jetway/tmp/work/core2-elp-linux/celix/1.0.0-r2/trunk/remote_services/discovery/private/src/endpoint_discovery_poller.c:314)
INFO: Removing service
(org.syntech.unit.message.embedded.RemoteMessageLogService)
INFO: TOPOLOGY_MANAGER: Remove imported service
(org.syntech.unit.message.embedded.RemoteMessageLogService;
cd0f1086-39c1-4bb7-87d2-91389c1a7a52).
INFO: RSA: closing proxy
INFO: TOPOLOGY_MANAGER: listener with filter
"(&(objectClass=remote_proxy_factory)(proxy.interface=org.syntech.unit.message.embedded.RemoteMessageLogService))"
removed.
LogWriter: BUNDLE_EVENT_STOPPED from
org.syntech.unit.message.embedded.RemoteMessageLogService_proxy
LogWriter: BUNDLE_EVENT_UNRESOLVED from
org.syntech.unit.message.embedded.RemoteMessageLogService_proxy
LogWriter: BUNDLE_EVENT_UNINSTALLED from
org.syntech.unit.message.embedded.RemoteMessageLogService_proxy
INFO: Removing service
(org.syntech.transaction.embedded.RemoteTransactionLogService)
INFO: TOPOLOGY_MANAGER: Remove imported service
(org.syntech.transaction.embedded.RemoteTransactionLogService;
dd1762bd-c3ea-4aaa-943a-48c904223471).
INFO: RSA: closing proxy
INFO: TOPOLOGY_MANAGER: listener with filter
"(&(objectClass=remote_proxy_factory)(proxy.interface=org.syntech.transaction.embedded.RemoteTransactionLogService))"
removed.
LogWriter: BUNDLE_EVENT_STOPPED from
org.syntech.transaction.embedded.RemoteTransactionLogService_proxy
LogWriter: BUNDLE_EVENT_UNRESOLVED from
org.syntech.transaction.embedded.RemoteTransactionLogService_proxy
LogWriter: BUNDLE_EVENT_UNINSTALLED from
org.syntech.transaction.embedded.RemoteTransactionLogService_proxy
INFO: Removing service
(org.syntech.mainboard.configuration.MainboardConfigurator)
INFO: TOPOLOGY_MANAGER: Remove imported service
(org.syntech.mainboard.configuration.MainboardConfigurator;
f2f67b38-a959-4d0e-a261-842793931b90).
ERROR: ENDPOINT_POLLER: unable to read endpoints, reason: Couldn't connect to
server
at
endpointDiscoveryPoller_getEndpoints(/home/dparker/yocto/poky/build-jetway/tmp/work/core2-elp-linux/celix/1.0.0-r2/trunk/remote_services/discovery/private/src/endpoint_discovery_poller.c:314)
WARNING: ENDPOINT_DESCRIPTOR_READER: Only single-valued string supported for
service.id
WARNING: ENDPOINT_DESCRIPTOR_READER: Only single-valued string supported for
service.id
WARNING: ENDPOINT_DESCRIPTOR_READER: Only single-valued string supported for
service.id
INFO: Adding service (org.syntech.unit.message.embedded.RemoteMessageLogService)
INFO: TOPOLOGY_MANAGER: Add imported service
(org.syntech.unit.message.embedded.RemoteMessageLogService;
7d4e1613-da8c-4052-b5ed-ddebffbc9957).
INFO: RSA: Import service
org.syntech.unit.message.embedded.RemoteMessageLogService
INFO: TOPOLOGY_MANAGER: listener with filter
"(&(objectClass=remote_proxy_factory)(proxy.interface=org.syntech.unit.message.embedded.RemoteMessageLogService))"
added
INFO: remoteServiceAdmin_importService: new registration_factory added for
org.syntech.unit.message.embedded.RemoteMessageLogService at 0xb5422938
LogWriter: BUNDLE_EVENT_INSTALLED from
org.syntech.unit.message.embedded.RemoteMessageLogService_proxy
LogWriter: BUNDLE_EVENT_RESOLVED from
org.syntech.unit.message.embedded.RemoteMessageLogService_proxy
INFO:
endpoints/org.syntech.unit.message.embedded.RemoteMessageLogService_proxy.zip
successfully started.
LogWriter: BUNDLE_EVENT_STARTED from
org.syntech.unit.message.embedded.RemoteMessageLogService_proxy
INFO: Adding service (org.syntech.mainboard.configuration.MainboardConfigurator)
INFO: TOPOLOGY_MANAGER: Add imported service
(org.syntech.mainboard.configuration.MainboardConfigurator;
7592f9ad-86b8-401a-8828-5ac7118734d4).
INFO: RSA: Import service
org.syntech.mainboard.configuration.MainboardConfigurator
INFO: TOPOLOGY_MANAGER: listener with filter
"(&(objectClass=remote_proxy_factory)(proxy.interface=org.syntech.mainboard.configuration.MainboardConfigurator))"
added
INFO: remoteServiceAdmin_importService: new registration_factory added for
org.syntech.mainboard.configuration.MainboardConfigurator at 0xb541dc00
ps
ID State Name
0 Active framework
1 Active apache_celix_rsa_discovery_configured
2 Active apache_celix_rs_topology_manager
3 Active apache_celix_remote_service_admin_http
4 Active org.syntech.unit.atmapp.embedded.ATMapp
5 Active apache_celix_shell
6 Active apache_celix_shell_tui
7 Active apache_celix_log_service
8 Active apache_celix_log_writer
9 Active org.syntech.authorizationComponent
10 Active org.syntech.configurationhandler
11 Active org.syntech.configurationhandler.shell
16 Active
org.syntech.unit.message.embedded.RemoteMessageLogService_proxy
> Remote services can fail to restart when felix restarts
> -------------------------------------------------------
>
> Key: CELIX-170
> URL: https://issues.apache.org/jira/browse/CELIX-170
> Project: Celix
> Issue Type: Bug
> Components: Remote Service Admin
> Reporter: Daniel Parker
>
> If you have a number of services which are offered remotely from felix, but
> only some of them actually have proxies installed on the celix side, then the
> system works fine the first time, but it can get confused if felix restarts.
> In this case, some of the remote services which do have proxies installed may
> not restart properly in celix.
> Example: at Syntech, the felix side provides an Authorization Service, a
> Configuration Service, a Transaction Service, and a Message service. The
> Authorization Service and the Configuration Service are still being worked
> on, so they don't have endpoints installed in celix. The first time the
> system starts, the installed services are loaded correctly. If the felix
> side is restarted, the Message service starts correctly, but the Transaction
> Service does not start.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
