Re: Tomcat 4.x (Major Problem)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Andy, Andy Moller wrote: >> 1. You are using the array "val2" here instead of "value2". Is that >> intentional? Or, were you somewhat obfuscating your code for publication >> on the list? > > > [Chris]: It is a mistake while changing the variable na

Re: Tomcat 4.x (Major Problem)

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

Re: Tomcat 4.x (Major Problem)

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.getParameterValues("value_1") != null) >? request.getParamete

RE: Tomcat 4.x (Major Problem)

> From: Andy Moller [mailto:[EMAIL PROTECTED] > Subject: Re: Tomcat 4.x (Major Problem) > String[] value1 = (request.getParameterValues("value_1") != null) > ? request.getParameterValues("value_1") > : new String[0]; &g

Re: Tomcat 4.x (Major Problem)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Andy, Andy Moller wrote: > String commonName = (String)session.getAttribute("commonName"); > String[] value1 = (request.getParameterValues("value_1") != null) >? request.getParameterValues("value_1") >: new String[0]; > > String[] val

Re: Tomcat 4.x (Major Problem)

-- 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.

RE: Tomcat 4.x (Major Problem)

> From: Andy Moller [mailto:[EMAIL PROTECTED] > Subject: Tomcat 4.x (Major Problem) > > I have a strange problem that I think Tomcat is causing it, > and I need to confirm if my assumptions are correct. We obviously don't have access to all the data you have available,

Re: Tomcat 4.x (Major Problem)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Andy, Andy Moller wrote: > While debugging the database query logs, the reason was that the > field type is integer, while the passed value was a "string", we went > and inspected the code design and semantics and it was an impossible > case that the

Tomcat 4.x (Major Problem)

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