I do see this in the logs INFO: https://myserver/opensocial/rpc?method=system.listMethods&st=oclc:LXcpXCAPLyrVfHlxPmnSKYEU59aEt45_3VZPKNuPdSwMGnYaNSLikIGUaET_SEaVN70w-W7jQybrDLUoopvyxVbq8cs has timed out because of the following exception: org.apache.shindig.gadgets.http.BasicHttpFetcher - connect timed out - 30,012 ms. Jun 02, 2015 9:05:04 AM org.apache.shindig.gadgets.render.DefaultServiceFetcher retrieveServices SEVERE: An HTTP 504 error occurred when fetching service methods from the https://myserver/opensocial/rpc endpoint.
Interesting that the server tries to fetch the endpoints by calling through the rpc endpoint on the target server, rather than just internally introspecting? I guess I could just define the osapi.servcies to prevent the rpc call by removing the osapi.endPoints configuration. doug On Jun 2, 2015, at 9:50 AM, Davies,Douglas <davi...@oclc.org<mailto:davi...@oclc.org>> wrote: Has anyone ever seen the osapi endpoints missing from the request for the shindig js? I occasionally get back javascript that is missing the endpoints and all my osapi calls fail (undefined). For example here is a good response "osapi.services":{"gadgets.rpc":["container.listMethods"],"//%host%/opensocial/rpc":"spaces.update spaces.delete albums.create http.head gadgets.token activitystreams.supportedFields messages.modify userprefs.create activities.create permissions.hasPermission containersecuritytoken.refresh userprefs.get applications.get http.get spaces.supportedFields mediaItems.delete spaces.get people.get gadgets.supportedFields gadgets.cajaSupportedFields mediaItems.update http.put appdata.create activitystreams.delete http.delete cache.invalidate albums.delete userprefs.delete applications.create messages.delete appdata.update people.update activities.supportedFields applications.update http.post albums.get gadgets.cajole gadgets.proxySupportedFields applications.delete people.supportedFields gadgets.metadata albums.supportedFields albums.update spaces.create activities.delete mediaItems.get groups.get applications.supportedFields mediaItems.supportedFields gadgets.proxy activities.update gadgetContext.get activitystreams.create activitystreams.get messages.get activitystreams.update mediaItems.create messages.create gadgets.jsSupportedFields gadgets.tokenSupportedFields activities.get gadgets.js appdata.get appdata.delete userprefs.update system.listMethods".split(" “)} and a bad one "osapi.services":{"gadgets.rpc":["container.listMethods”]} It seems to be a timing issue and MAY have been introduced when I started using updateContainerSecurityToken refreshing (but I can’t say that for sure — I only started seeing this when I implemented the refresh logic). Ideas what to look for? doug
