Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: neutral (athena.apache.org: local policy)
Message-ID: <4F1DBAA6.5040409@christopherschultz.net>
Date: Mon, 23 Jan 2012 14:53:10 -0500
From: Christopher Schultz <chris@christopherschultz.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7;
 rv:9.0) Gecko/20111222 Thunderbird/9.0.1
MIME-Version: 1.0
To: Tomcat Users List <users@tomcat.apache.org>
Subject: Re: Connection.close() has already been called during login
References: <1327342897.30710.YahooMailClassic@web181607.mail.ne1.yahoo.com>
In-Reply-To: <1327342897.30710.YahooMailClassic@web181607.mail.ne1.yahoo.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

To whom it may concern,

On 1/23/12 1:21 PM, removeps-code@yahoo.com wrote:
> Initially I thought that my RootJDBCRealm might be the problem,
> but how can that be? RootJDBCRealm extends Tomcat's own JDBCRealm.
> It overrides authenticate to call super.authenticate and if there
> are 3 failures (in that super.authenticate returns null), then it
> locks out the user. So could the user of RootJDBCRealm still be a
> problem?

It obviously depends upon what code is in RootJCBDRealm. Care you share?

As someone else already pointed out, you might want to look at
LockOutRealm.

- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk8duqYACgkQ9CaO5/Lv0PCkAwCfdhqhvv/WR81eJn/GtlZf2ary
wh8An17S8BA/zToMQjLYmHthGBtJRxJy
=LfEC
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org