On 1/22/07, Caldarale, Charles R <[EMAIL PROTECTED]> wrote:
> From: Andy Moller [mailto:[EMAIL PROTECTED]
> Subject: Re: Tomcat 4.x (Major Problem)
> String[] value1 = (request.getParameterValues("value_1") != null)
> ? request.getParameterValues("v
On 1/22/07, Christopher Schultz <[EMAIL PROTECTED]> wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andy,
Andy Moller wrote:
> String commonName = (String)session.getAttribute("commonName");
> String[] value1 = (request.getParameterVal
--
The code is simple, and the query is printed on the stdout before it is
executed, that was the reason I suspected Tomcat as the reason for the
problem having a session leak somehow.
The application assumes about 25 concurrent sessions with heavy use of
session variables.
I hope this can help.
Hi All,
I have a strange problem that I think Tomcat is causing it, and I need to
confirm if my assumptions are correct.
We have a Tomcat-Standalone (Apache Tomcat/4.0.3) running as a service, we
have been working with that version of tomcat for quite sometime with
different applications. Most
