1:20 a.m.
On Sat 08 Jun 2013 09:19:47 AM EDT, Trong Tran wrote:
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).
Since the war is compressed, is there anyway we can move this to an
external configuration file?
What I have found is that if I modify the features.txt in the
shindig-features.jar to remove features/analytics/features.xml and
features/com.google.gadgets.analytics/features.xml then I no longer run
into the issue.
Ideally I would like to see something along the lines of moving the
features that require online access to a online features set. Removing
them from the features.txt file and adding it instead to the
shindig.properties features list (where shindig.properties would be an
external configuration file). Or maybe just a flag to set for offline
access?
What are people's thoughts on this? I don't know if a couple of minutes
delay at server startup for a user who is using the server offline and
explicitly set the timeout to be much longer than default is really
worth the extra effort.
What do you think if we could deactivate the features by default in
GateIn ?
But if someone is currently using those gadget features, it will appear
broken in an update. I would assume most people are using GateIn with
web access and only a small minority are using it without.
On 31 May 2013 21:30, Matt Wringe <mwringe(a)redhat.com
<mailto: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(a)lists.jboss.org <mailto:gatein-dev@lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/gatein-dev
--
*Trong Tran*
/(+84) 983841909 | /trongtt(a)gmail.com <mailto:trongtt@gmail.com>
Twitter: http://twitter.com/trongtt//