[
https://issues.apache.org/jira/browse/SLING-506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bertrand Delacretaz closed SLING-506.
-------------------------------------
Resolution: Fixed
Fixed in revision 689045, the ping interval logic was broken.
Ping intervals are now set between the configured min and max values, and
ramped up if the repository is not available, to avoid pinging too often.
Changes to the ping interval are logged at the DEBUG level.
If the repository is available immediately at startup, this is logged:
Repository Pinger interval set to 10000 msec, repository is available
If the repository becomes available about 5 seconds after startup, the interval
sequence is:
14:19:40.865 Repository Pinger interval set to 200 msec, repository is NOT
available
14:19:41.153 Repository Pinger interval set to 400 msec, repository is NOT
available
14:19:41.555 Repository Pinger interval set to 800 msec, repository is NOT
available
14:19:42.356 Repository Pinger interval set to 1600 msec, repository is NOT
available
14:19:43.958 Repository Pinger interval set to 3200 msec, repository is NOT
available
14:19:48.013 Repository Pinger interval set to 10000 msec, repository is
available
> RepositoryPinger pings too often
> --------------------------------
>
> Key: SLING-506
> URL: https://issues.apache.org/jira/browse/SLING-506
> Project: Sling
> Issue Type: Bug
> Components: JCR
> Reporter: Bertrand Delacretaz
> Assignee: Bertrand Delacretaz
> Priority: Minor
>
> SLING-505 reminds me that I've seen the RepositoryPinger ping way too often,
> and a colleague reports seeing two active RepositoryPinger threads in his
> system.
> We need to test this again, and maybe restructure the code to allow for
> automated testing of the ping cycle times.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
