Its a problem with your database or your network: com.mysql.jdbc.CommunicationsException: The last packet successfully received from the server was56636 milliseconds ago.The last packet sent successfully to the server was 56636 milliseconds ago, which 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.
-Scott -Scott Battaglia PGP Public Key Id: 0x383733AA LinkedIn: http://www.linkedin.com/in/scottbattaglia On Thu, Jan 22, 2009 at 7:27 AM, Mihai <[email protected]> wrote: > Hi, > > I have a problem using the CAS server(tested under glassfish): > > <exception> > > *type* Exception report > > *message* > > *description*The server encountered an internal error () that prevented it > from fulfilling this request. > > *exception* > > org.springframework.web.util.NestedServletException: Request processing > failed; nested exception is > org.springframework.webflow.engine.ActionExecutionException: Exception thrown > executing [annotatedact...@862dc1 targetAction = > org.jasig.cas.web.flow.authenticationviaformact...@4e3801, attributes = > map['method' -> 'submit']] in state 'submit' of flow 'login-webflow' -- > action execution attributes were 'map['method' -> 'submit']'; nested > exception is org.springframework.dao.DataAccessResourceFailureException: > PreparedStatementCallback; SQL [Select count('x') from user Where username = > ? And passwd = ?]; The last packet successfully received from the server > was56636 milliseconds ago.The last packet sent successfully to the server was > 56636 milliseconds ago, which 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.; nested exception is > com.mysql.jdbc.CommunicationsException: The last packet successfully received > from the server was56636 milliseconds ago.The last packet sent successfully > to the server was 56636 milliseconds ago, which 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. > > *root cause* > > org.springframework.webflow.engine.ActionExecutionException: Exception thrown > executing [annotatedact...@862dc1 targetAction = > org.jasig.cas.web.flow.authenticationviaformact...@4e3801, attributes = > map['method' -> 'submit']] in state 'submit' of flow 'login-webflow' -- > action execution attributes were 'map['method' -> 'submit']'; nested > exception is org.springframework.dao.DataAccessResourceFailureException: > PreparedStatementCallback; SQL [Select count('x') from user Where username = > ? And passwd = ?]; The last packet successfully received from the server > was56636 milliseconds ago.The last packet sent successfully to the server was > 56636 milliseconds ago, which 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.; nested exception is > com.mysql.jdbc.CommunicationsException: The last packet successfully received > from the server was56636 milliseconds ago.The last packet sent successfully > to the server was 56636 milliseconds ago, which 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. > > *root cause* > > org.springframework.dao.DataAccessResourceFailureException: > PreparedStatementCallback; SQL [Select count('x') from user Where username = > ? And passwd = ?]; The last packet successfully received from the server > was56636 milliseconds ago.The last packet sent successfully to the server was > 56636 milliseconds ago, which 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.; nested exception is > com.mysql.jdbc.CommunicationsException: The last packet successfully received > from > the > server was56636 milliseconds ago.The last packet sent successfully to the > server was 56636 milliseconds ago, which 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. > > *root cause* > > com.mysql.jdbc.CommunicationsException: The last packet successfully received > from the server was56636 milliseconds ago.The last packet sent successfully > to the server was 56636 milliseconds ago, which 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. > > *root cause* > > java.net <http://java.net.So>.SocketException: Software caused connection > abort: socket write error > > *note* *The full stack traces of the exception and its root causes are > available in the GlassFish/v3 logs.* > </exception> > > This happens most frequently but not always while the user trying to login. > Thanks. > > > > _______________________________________________ > Yale CAS mailing list > [email protected] > http://tp.its.yale.edu/mailman/listinfo/cas > >
_______________________________________________ Yale CAS mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas
