I think the problem only appears if the server address can be resolved BUT socket connection can not be opened somehow and timeout expires (15s as current configuration).

I confirm that this is just a warning log and it doesn't impact to product at run time as long as there are no gadgets using the features.

These are built-in features of the original shindig 2.0.2 tag version which we forked from. And we should not add these javascript locally as they should be maintained by provider when there are any changes in the service api.

It's possible to configure the path to the default shindig features.txt file in shindig.properties (in shindig server war).

What do you think if we could deactivate the features by default in GateIn ?



On 31 May 2013 21:30, Matt Wringe <mwringe@redhat.com> wrote:
Shindig has some external javascript libraries that it needs to download
when the server starts and when gadgets/dashboards are used. The
external ones seem to only be coming from google to support an analytics
feature.

This can cause problems when a user does not have access external
network access, and it some cases (although I have not been able to
reproduce this situation) causes long delays due to timeouts.

Can one of our Shindig experts please look into this issue?
https://bugzilla.redhat.com/show_bug.cgi?id=893959
https://issues.jboss.org/browse/GTNPORTAL-2518

Is there anyway we can configure the list of services for the feature
after its been built? Or add the javascript locally to the build so we
no longer have to fetch it from an external location?

NB: anyone know if the analytics feature is something we created in our
shindig fork? It doesn't appear to be in the upstream one.
_______________________________________________
gatein-dev mailing list
gatein-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/gatein-dev



--
Trong Tran
(+84) 983841909 | trongtt@gmail.com
Twitter: http://twitter.com/trongtt