Re: Connection.close() has already been called during login

2012-01-23 Thread removeps-code
--- On Mon, 1/23/12, Christopher Schultz wrote: > From: Christopher Schultz > Subject: Re: Connection.close() has already been called during login > To: "Tomcat Users List" > Date: Monday, January 23, 2012, 2:42 PM > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1

Re: Connection.close() has already been called during login

2012-01-23 Thread Christopher Schultz
tomatically, and maybe > FileLock will do the job for the files. But anyway, it sounds > complicated. memcached. Cassandra. Whatever. > As for my my authenticate it was as follows, although I don't see > this should cause the failure in the subject of this email -- > &quo

Re: Connection.close() has already been called during login

2012-01-23 Thread removeps-code
authenticate it was as follows, although I don't see this should cause the failure in the subject of this email -- "Connection.close() has already been called during login": public Principal authenticate(String username, String credentials) { threadUserLockedOut.remov

Re: Connection.close() has already been called during login

2012-01-23 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 To whom it may concern, On 1/23/12 2:54 PM, removeps-c...@yahoo.com wrote: > Sorry, I did not know about [LockOutRealm]. Will this class work > if you have many Tomcats on different machines (possibly load > balancing) so regardless of which exact ma

Re: Connection.close() has already been called during login

2012-01-23 Thread removeps-code
--- On Mon, 1/23/12, Daniel Mikusa wrote: > From: Daniel Mikusa > Subject: Re: Connection.close() has already been called during login > To: "Tomcat Users List" > Date: Monday, January 23, 2012, 10:55 AM > On Mon, 2012-01-23 at 10:21 -0800, removeps-c...@yahoo.com

Re: Connection.close() has already been called during login

2012-01-23 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 To whom it may concern, On 1/23/12 1:21 PM, removeps-c...@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

Re: Connection.close() has already been called during login

2012-01-23 Thread Daniel Mikusa
l be a problem? Thanks. > > --- On Mon, 1/23/12, Mark Thomas wrote: > > > From: Mark Thomas > > Subject: Re: Connection.close() has already been called during login > > To: "Tomcat Users List" > > Date: Monday, January 23, 2012, 12:49 AM > > On 23/01/2012

Re: Connection.close() has already been called during login

2012-01-23 Thread Chema
>2012/1/23 : > 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 ou

Re: Connection.close() has already been called during login

2012-01-23 Thread removeps-code
could the user of RootJDBCRealm still be a problem? Thanks. --- On Mon, 1/23/12, Mark Thomas wrote: > From: Mark Thomas > Subject: Re: Connection.close() has already been called during login > To: "Tomcat Users List" > Date: Monday, January 23, 2012, 12:49 AM > O

Re: Connection.close() has already been called during login

2012-01-23 Thread Mark Thomas
On 23/01/2012 03:49, removeps-c...@yahoo.com wrote: > Am running Tomcat 7 and see this in the logs: > > SEVERE: Exception performing authentication > com.mysql.jdbc.exceptions.jdbc4.MySQLNonTransientConnectionException: > Connection.close() has already been called. Invalid operation in this state

Connection.close() has already been called during login

2012-01-22 Thread removeps-code
Am running Tomcat 7 and see this in the logs: SEVERE: Exception performing authentication com.mysql.jdbc.exceptions.jdbc4.MySQLNonTransientConnectionException: Connection.close() has already been called. Invalid operation in this state. at sun.reflect.NativeConstructorAccessorImpl.newInst