tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mark Thomas <ma...@apache.org>
Subject Re: Why am I Getting org.apache.catalina.realm.JDBCRealm getPassword SEVERE: Exception performing authentication?
Date Wed, 08 Feb 2012 19:40:28 GMT
On 08/02/2012 19:15, Jonathan Rosenberg wrote:
> On Wed, Feb 8, 2012 at 1:41 PM, Mark Thomas <markt@apache.org> wrote:
>> On 08/02/2012 18:23, Jonathan Rosenberg wrote:
>>> Caused by: com.mysql.jdbc.exceptions.jdbc4.CommunicationsException:
>>> The last packet successfully received from the server was 58,153,867
>>> milliseconds ago.  The last packet sent successfully to the server was
>>> 58,153,867 milliseconds ago. is longer than the server configured
>>> value of 'wait_timeout'. You should consider either expiring and/or
>>> testing connection validity before use in your application, increasing
>>> the server configured values for client timeouts, or using the
>>> Connector/J connection property 'autoReconnect=true' to avoid this
>>> problem.
>>
>> Which part of this is unclear?
> 
> The message is, indeed, perfectly clear. Did you read my post?
> 
> I don't understand why Tomcat is involved in the authentication  (the
> exception happens in org.apache.catalina.realm.JDBCRealm getPassword)
> at this point.  As far as I know, the only authentication going on
> should be the CAS authentication used by my app.

> SEVERE: Exception performing authentication
> com.mysql.jdbc.exceptions.jdbc4.MySQLNonTransientConnectionException:
> No operations allowed after connection closed.Connection was
> implicitly closed by the driver.
>        at
sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
>        at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
>        at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
>        at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
>        at com.mysql.jdbc.Util.handleNewInstance(Util.java:409)
>        at com.mysql.jdbc.Util.getInstance(Util.java:384)
>        at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1015)
>        at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:989)
>        at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:984)
>        at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:929)
>        at
com.mysql.jdbc.ConnectionImpl.throwConnectionClosedException(ConnectionImpl.java:1193)
>        at com.mysql.jdbc.ConnectionImpl.getMutex(ConnectionImpl.java:3035)
>        at com.mysql.jdbc.ConnectionImpl.commit(ConnectionImpl.java:1612)
>        at
org.apache.catalina.realm.JDBCRealm.getPassword(JDBCRealm.java:579)
>        at
org.apache.catalina.realm.JDBCRealm.authenticate(JDBCRealm.java:408)
>        at
org.apache.catalina.realm.JDBCRealm.authenticate(JDBCRealm.java:355)
>        at
org.apache.catalina.realm.CombinedRealm.authenticate(CombinedRealm.java:146)
>        at
org.apache.catalina.realm.LockOutRealm.authenticate(LockOutRealm.java:180)
>        at
org.apache.catalina.authenticator.BasicAuthenticator.authenticate(BasicAuthenticator.java:157)

This means you are using Tomcat's BASIC authentication.

It appears you do not have CAS configured correctly. Check your web.xml.

Mark

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


Mime
View raw message