[
http://jira.amdatu.org/jira/browse/AMDATUOPENSOCIAL-3?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=11325#comment-11325
]
Ivo Ladage - van Doorn commented on AMDATUOPENSOCIAL-3:
-------------------------------------------------------
Yes, upon the first HTTP request after a restart of Shindig, the
DefaultServiceFetcher verifies that the OSAPI endpoints are available. This
must be a timing issue, when the dashboard is opened or any other Shindig http
call is invoked while Shindig and/or the Shindig servlets are still booting,
this error can occur.
So I believe that if this error appears, it is caused by a HTTP call to Shindig
while Shindig is 'booting'. As such, I don't think that anything should be
fixed.
> Failed to fetch services methods from endpoint logmessage
> ---------------------------------------------------------
>
> Key: AMDATUOPENSOCIAL-3
> URL: http://jira.amdatu.org/jira/browse/AMDATUOPENSOCIAL-3
> Project: Amdatu OpenSocial
> Issue Type: Bug
> Affects Versions: 0.1.0
> Reporter: Dion Meijer
> Fix For: 0.2.0
>
>
> When starting BlueConic on the Amdatu revision in the trunk, the following
> message is displayed in the log:
> Failed to fetch services methods from endpoint http://localhost:3737/rpc.
> Error org.apache.http.client.ClientProtocolException
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
Amdatu-developers mailing list
[email protected]
http://lists.amdatu.org/mailman/listinfo/amdatu-developers