I have noticed in my experience that when I send a new update to the Tomcat server software for ODK Aggregate or install a new version of ODK Aggregate, it can take up to 2 hours for web servers to recognize this (I'm running Aggregate on a local server using Tomcat and SSL). The end result is that some phones will connect without problem to ODK Aggregate while others will display various connection errors. Similarly, some web sites will recognize my security certificate while others will not find the security certificate there. This has often driven me slightly crazy trying to sort out - but now I have realized sometimes I simply need to wait for a few hours and the problem sorts itself out.
Maybe it would be helpful to add a note about this on your trouble-shooting page?
I have noticed in my experience that when I send a new update to the
Tomcat server software for ODK Aggregate or install a new version of ODK
Aggregate, it can take up to 2 hours for web servers to recognize this (I'm
running Aggregate on a local server using Tomcat and SSL). The end result
is that some phones will connect without problem to ODK Aggregate while
others will display various connection errors. Similarly, some web sites
will recognize my security certificate while others will not find the
security certificate there. This has often driven me slightly crazy trying
to sort out - but now I have realized sometimes I simply need to wait for a
few hours and the problem sorts itself out.
Maybe it would be helpful to add a note about this on your
trouble-shooting page?
I am doing 3 - how do I clear the caching for the session cookies?
Best wishes,
Lu
···
On Tuesday, December 9, 2014 12:29:27 AM UTC, Mitch Sundt wrote:
> Are you:
> (1) updating the CNAME ref for the server?
> (2) updating the SSL cert of the server?
> (3) copying a new WAR onto the server?
>
>
> A propagation delay is certainly needed for (1) and maybe for (2).
>
>
>
> If you are just doing (3), do you have any caching set up for the JSESSIONID (session cookie)?
>
> Depending upon how you manage your instance and generate the WAR file, you might need to clear these session cookies.
>
> --
>
> Mitch Sundt
> Software Engineer
> University of Washington
> mitche...@gmail.com
>
>
>
> On Sat, Dec 6, 2014 at 5:28 AM, wrote:
> Hi there,
>
>
>
> I have noticed in my experience that when I send a new update to the Tomcat server software for ODK Aggregate or install a new version of ODK Aggregate, it can take up to 2 hours for web servers to recognize this (I'm running Aggregate on a local server using Tomcat and SSL). The end result is that some phones will connect without problem to ODK Aggregate while others will display various connection errors. Similarly, some web sites will recognize my security certificate while others will not find the security certificate there. This has often driven me slightly crazy trying to sort out - but now I have realized sometimes I simply need to wait for a few hours and the problem sorts itself out.
>
>
>
> Maybe it would be helpful to add a note about this on your trouble-shooting page?
>
>
>
> https://code.google.com/p/opendatakit/wiki/AggregateTroubleshooting
>
>
>
> Best wishes,
>
>
>
> Lu
>
>
>
> --
>
> --
>
> Post: opend...@googlegroups.com
>
> Unsubscribe: opendatakit...@googlegroups.com
>
> Options: http://groups.google.com/group/opendatakit?hl=en
>
>
>
> ---
>
> You received this message because you are subscribed to the Google Groups "ODK Community" group.
>
> To unsubscribe from this group and stop receiving emails from it, send an email to opendatakit...@googlegroups.com.
>
> For more options, visit https://groups.google.com/d/optout.
>
>
>
>
> --
>
> Mitch Sundt
> Software Engineer
> University of Washington
> mitche...@gmail.com
A quick test: if session cookies are the problem, opening an incognito or
private browsing window should work immediately, but accessing the site
through your standard browser windows should fail until those cookies
expire.
The management of session cookies depends upon the server and any proxy
configurations, so it is site specific. I don't have any suggestions for
this.
···
On Tue, Dec 9, 2014 at 3:26 AM, wrote:
Hi Mitch,
I am doing 3 - how do I clear the caching for the session cookies?
Best wishes,
Lu
On Tuesday, December 9, 2014 12:29:27 AM UTC, Mitch Sundt wrote:
Are you:
(1) updating the CNAME ref for the server?
(2) updating the SSL cert of the server?
(3) copying a new WAR onto the server?
A propagation delay is certainly needed for (1) and maybe for (2).
If you are just doing (3), do you have any caching set up for the
JSESSIONID (session cookie)?
Depending upon how you manage your instance and generate the WAR file,
you might need to clear these session cookies.
I have noticed in my experience that when I send a new update to the
Tomcat server software for ODK Aggregate or install a new version of ODK
Aggregate, it can take up to 2 hours for web servers to recognize this (I'm
running Aggregate on a local server using Tomcat and SSL). The end result
is that some phones will connect without problem to ODK Aggregate while
others will display various connection errors. Similarly, some web sites
will recognize my security certificate while others will not find the
security certificate there. This has often driven me slightly crazy trying
to sort out - but now I have realized sometimes I simply need to wait for a
few hours and the problem sorts itself out.
Maybe it would be helpful to add a note about this on your
trouble-shooting page?