On 04/03/2016 13:19, Tullio Bettinazzi wrote:
> Done and nothing changed.
What has changed is that you have now provided a test case that someone
else can run easily and confirm, or not, your findings.
> Any suggestion ?
Before anyone spends time looking at this the other question I don't see
an
Am 05.03.2016 um 12:34 schrieb Tullio Bettinazzi:
This is not a memory problem because, otherwise, I'll have the same problem on
all client systems.
It's a communication related problem between server and clients but not
strictly a network problem because, otherwise, two clients, connected to t
This is not a memory problem because, otherwise, I'll have the same problem on
all client systems.
It's a communication related problem between server and clients but not
strictly a network problem because, otherwise, two clients, connected to the
same cable would perform in the same way.
Tks
Tu
Am 04.03.2016 um 10:11 schrieb Chanchal Kariwala:
I tries what you asked and I have observed the following
1. Browser sends a request for the resource
Server replies with HTTP 401 and WWW-Authenticate: Negotiate in Response
Headers
2. Browser sends a new request with the following in Request He
Am 04.03.2016 um 14:19 schrieb Tullio Bettinazzi:
Done and nothing changed.
Any suggestion ?
It could be related to memory usage.
Tomcat 8 can use more memory than tomcat 7 (See
https://mail-archives.apache.org/mod_mbox/tomcat-users/201602.mbox/%3ccacbju2wmw7mntevb6hwjqdfzsjpmfiuw6k_dn1u0ufh0h
