Hi,
Am Mittwoch, 18. November 2009 schrieb conrad-tomcat.users.2...@tivano.de:
>
> When a HTTP/1.0 client requests a dynamically generated page over SSL,
> most of the response is returned immediately. Then, we see a 5-second
> timeout (this is *not* Apache's KeepAliveTimeout), then the rest of th
Hi,
On Thu, Nov 19, 2009 at 12:50:44AM +0100, Rainer Jung wrote:
>
> On 18.11.2009 17:01, conrad-tomcat.users.2...@tivano.de wrote:
> >
> > As you can see, 24552 (=3 * 8184) bytes are received almost immediately,
>
> 8184 looks like the body size of one full AJP packet (protocol used by
> mod_j
Hi,
we're seeing a strange problem here that is only partially reproducible.
Our customer is running a cluster of Tomcat 5.5.26 servers (several cluster
domains) behind several load-balanced Apache-2.2.11 (for SSL termination +
sticky sessions). The application consists of an unencrypted part and
Hi,
for completeness: the issue seems to have been resolved.
The problems were apparently caused by a misconfigured
router between the webservers and the appservers.
Am Mittwoch, 14. Oktober 2009 schrieb Mark Thomas:
>
> > Any idea how to gain more information?
>
> Jk debug logs
> wireshark
> com
Hi,
On Thu, Oct 15, 2009 at 08:53:03AM -0500, sharda k wrote:
> I was under the impression that restarting webserver would kill all user
> sessions. But with my tomcat install, restarting Tomcat does not kill user
> sessions. I am still able to continue with the initially started sessions.
> Is th
Hi,
Am Mittwoch, 14. Oktober 2009 schrieb Christopher Schultz:
>
> Although those threads say "runnable", they're really blocked at the OS
> level waiting to receive data from the mod_jk connector. These threads
> are actually idle, waiting for requests from httpd to come through the
> pipe.
>
> Y
Hi,
our customer is running a cluster of tomcat servlet engines. On these,
our web application is running. The basic setup is
Loadbalancer <---> Apache 1.3.x with mod_jk <---> Tomcat
with 2-3 Apache servers and >30 Tomcat instances bundled into clusters
of 3-5 instances each. Apache + Tomcat ser
