Stefan Egli created SLING-3446:
----------------------------------
Summary: [discovery] stale connector - improve osgi dependencies
of ConnectorRegistryImpl to avoid IllegalArgumentException on bundle
de/activation
Key: SLING-3446
URL: https://issues.apache.org/jira/browse/SLING-3446
Project: Sling
Issue Type: Bug
Components: Extensions
Affects Versions: Discovery Impl 1.0.4
Reporter: Stefan Egli
Assignee: Stefan Egli
The following warning shows up every 30 sec when deploying a bundle which
results in loads of bundle restart:
10.03.2014 18:27:31.107 *WARN* [pool-8-thread-3]
org.apache.sling.discovery.impl.topology.connector.TopologyConnectorClient
ping: got RuntimeException: java.lang.IllegalArgumentException: ownerId must
not be null or empty
java.lang.IllegalArgumentException: ownerId must not be null or empty
at
org.apache.sling.discovery.impl.topology.announcement.Announcement.<init>(Announcement.java:88)
at
org.apache.sling.discovery.impl.topology.announcement.Announcement.<init>(Announcement.java:83)
at
org.apache.sling.discovery.impl.topology.connector.TopologyConnectorClient.ping(TopologyConnectorClient.java:169)
at
org.apache.sling.discovery.impl.topology.connector.ConnectorRegistryImpl.pingOutgoingConnectors(ConnectorRegistryImpl.java:138)
at
org.apache.sling.discovery.impl.common.heartbeat.HeartbeatHandler.issueRemoteHeartbeats(HeartbeatHandler.java:269)
at
org.apache.sling.discovery.impl.common.heartbeat.HeartbeatHandler.issueHeartbeat(HeartbeatHandler.java:256)
at
org.apache.sling.discovery.impl.common.heartbeat.HeartbeatHandler.run(HeartbeatHandler.java:209)
at
org.apache.sling.commons.scheduler.impl.QuartzJobExecutor.execute(QuartzJobExecutor.java:105)
at org.quartz.core.JobRunShell.run(JobRunShell.java:207)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
at java.lang.Thread.run(Thread.java:662)
Even though TopologyConnectorClient is managed by ConnectorRegistryImpl (which
is a service), it seems there are cases where ClusterViewServiceImpl can get
deactivated but ConnectorRegistryImpl not.
Note that restarting discovery.impl fixes the warning from above stale
connector.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
