[jira] [Resolved] (SLING-3506) [discovery] very misleading: webconsole shows "loop-connector" as error

["Stefan Egli (JIRA)" <ji...@apache.org>]

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

Stefan Egli resolved SLING-3506.
--------------------------------

    Resolution: Fixed

fixed - loop-connectors are again shown as OK instead of not ok

> [discovery] very misleading: webconsole shows "loop-connector" as error
> -----------------------------------------------------------------------
>
>                 Key: SLING-3506
>                 URL: https://issues.apache.org/jira/browse/SLING-3506
>             Project: Sling
>          Issue Type: Bug
>          Components: Extensions
>    Affects Versions: Discovery Impl 1.0.6
>            Reporter: Stefan Egli
>            Assignee: Stefan Egli
>            Priority: Critical
>             Fix For: Discovery Impl 1.0.8
>
>
> Consider the following steps:
>  * create a connector to 'self', eg localhost:8080/libs/sling/topology/connector
>  * go to the webconsole, eg http://localhost:8080/system/console/topology
>  * notice that the above created connector is showing the following message, instead of just 'ok, loop':
> {code}not connected 	not ok (HTTP Status-Code: 200, received announcement has expired (it was last renewed Tue Apr 22 09:14:14 CEST 2014) - consider increasing heartbeat timeout){code}
> This wrong status message is very confusing as it gets people to start debugging in the wrong direction on a system which is doing just fine.



--
This message was sent by Atlassian JIRA
(v6.2#6252)