Simon,
On 11/25/15 12:55 PM, Simon Callan wrote:
> The different versions of tomcat all show the same issue. We have this issue
> on two systems, and only two systems. We have not been able to reproduce this
> on any other system we have access to.
>
> Having investigated further, I appear to
>>> Then, after the user logs-out (from the either completely responsive
>>> or completely non-responsive web application), the web application becomes
>>> (or remains) unresponsive?
>>
>> What I mean by this is:
>> 1. User starts web-app, and uses it normally.
>Do you mean that the user starts
Simon,
On 11/20/15 11:13 AM, Simon Callan wrote:
> We are running GWT 2.5.1, Tomcat 7.0.56 and 7.0.65 on windows server
> 2008, IE 10, configured to serve web pages over SSL.
>
> The user can run our web-app and it will happily run until the user
> closes the web-browser, or logs out from the
Christopher,
Hopefully some useful answers.
> From: Christopher Schultz [mailto:ch...@christopherschultz.net]
> Sent: 20 November 2015 16:22
> On 11/20/15 11:13 AM, Simon Callan wrote:
> > We are running GWT 2.5.1, Tomcat 7.0.56 and 7.0.65 on windows server
> > 2008, IE 10, configured to serve
Simon,
On 11/20/15 11:43 AM, Simon Callan wrote:
> Christopher,
>
> Hopefully some useful answers.
>
>> From: Christopher Schultz [mailto:ch...@christopherschultz.net]
>> Sent: 20 November 2015 16:22
>
>> On 11/20/15 11:13 AM, Simon Callan wrote:
>>> We are running GWT 2.5.1, Tomcat 7.0.56 and
Some additional information.
If we configure Tomcat to accept both HTTP and HTTPs connections, the HTTP
connection remains working, even after the HTTPS one has broken.
Simon
Infoshare is registered in England and Wales.
Registered Office: Infoshare Ltd,