- Original Message -
> From: Hassan Schroeder
> To: Tomcat Users List
> Cc:
> Sent: Wednesday, December 21, 2011 2:40 PM
> Subject: Re: Login fails, then works subsequently (Tomcat 7)
>
> On Wed, Dec 21, 2011 at 2:23 PM, Jerry Malcolm <2ndgenfi...@gmail.com>
On 22/12/2011 04:51, Caldarale, Charles R wrote:
>> From: Hassan Schroeder [mailto:hassan.schroe...@gmail.com]
>> Subject: Re: Login fails, then works subsequently (Tomcat 7)
>
>> No "testWhileIdle" / "validationQuery" settings?
>
>> 10 to 1 you
On 22 Dec 2011, at 02:22, Brian Burch wrote:
> On 22/12/11 06:39, Jerry Malcolm wrote:
>> About a month ago, I upgraded two different servers from TC 5 to TC 7. The
>> migration went cleanly, and everything has been working fine with the
>> exception of one thing. About 50% of the time, when I
On 21 Dec 2011, at 22:52, Chema wrote:
>> 10 to 1 you've got stale connections in your pool; first try fails, second
>> one gets a fresh connection
>
> I thought the same
>
>
> autoReconnect
> Should the driver try to re-establish stale and/or dead connections?
Nope. Like Hassan said, use a vali
> From: Hassan Schroeder [mailto:hassan.schroe...@gmail.com]
> Subject: Re: Login fails, then works subsequently (Tomcat 7)
> No "testWhileIdle" / "validationQuery" settings?
> 10 to 1 you've got stale connections in your pool
Did we just go off on a
On 22/12/11 06:39, Jerry Malcolm wrote:
About a month ago, I upgraded two different servers from TC 5 to TC 7. The
migration went cleanly, and everything has been working fine with the
exception of one thing. About 50% of the time, when I log in to the realm
for my web app (form-based login),
> 10 to 1 you've got stale connections in your pool; first try fails, second
> one gets a fresh connection
I thought the same
autoReconnect
Should the driver try to re-establish stale and/or dead connections?
If enabled the driver will throw an exception for a queries issued on
a stale or dea
On Wed, Dec 21, 2011 at 2:23 PM, Jerry Malcolm <2ndgenfi...@gmail.com> wrote:
> Here is the line from in server.xml:
No "testWhileIdle" / "validationQuery" settings?
10 to 1 you've got stale connections in your pool; first try fails, second
one gets a fresh connection and away you go.
Just a WA
>The http trace would show if the id/pw were different. But that would
>pretty much imply that the browser is messing up what it sends. I guess
>that's always a possibility.
Not necessarily, the browser will send things other than the login and
password like headers and cookies.
>But I hav
Here is the line from in server.xml:
The http trace would show if the id/pw were different. But that would
pretty much imply that the browser is messing up what it sends. I guess
that's always a possibility. But I haven't changed browsers in months.
And it's sending a saved id/pw in all cas
You can try to set traces into the code of your realm class, if it's a
custom realm : to watch the query executed , to watch the
user/password passed from browser, to catch exceptions and print stack
trace ...
If you dont have a custom realm, you can try to create one for testing
Can you paste yo
On Wed, 2011-12-21 at 12:39 -0800, Jerry Malcolm wrote:
> About a month ago, I upgraded two different servers from TC 5 to TC 7. The
> migration went cleanly, and everything has been working fine with the
> exception of one thing. About 50% of the time, when I log in to the realm
> for my web ap
About a month ago, I upgraded two different servers from TC 5 to TC 7. The
migration went cleanly, and everything has been working fine with the
exception of one thing. About 50% of the time, when I log in to the realm
for my web app (form-based login), the login will fail. When I try again
wit
13 matches
Mail list logo
