Wednesday, September 11, 2013

java.sql.SQLTransientException: Request has not completed yet.

Has something changed with Cloud SQL recently -- we seem to be getting these weird exceptions when talking to cloud sql just recently?

Caused by: java.sql.SQLTransientException: Request has not completed yet.
at com.google.cloud.sql.jdbc.internal.Exceptions.newSqlExceptionForApplicationError(Exceptions.java:160)
at com.google.cloud.sql.jdbc.internal.Exceptions.newSqlException(Exceptions.java:204)
at com.google.cloud.sql.jdbc.internal.SqlProtoClient.check(SqlProtoClient.java:198)
at com.google.cloud.sql.jdbc.internal.SqlProtoClient.executeSql(SqlProtoClient.java:87)
at com.google.cloud.sql.jdbc.internal.SqlProtoClient.executeSql(SqlProtoClient.java:76)
at com.google.cloud.sql.jdbc.Connection.executeSql(Connection.java:520)
at com.google.cloud.sql.jdbc.Statement.executeSqlImpl(Statement.java:280)
at com.google.cloud.sql.jdbc.Statement.executeImpl(Statement.java:154)
at com.google.cloud.sql.jdbc.Statement.execute(Statement.java:142)

Should I just retry SQL operations that fail with a SQLTransientException? 

I realize that these problems may be solved in the future with the native MySQL connectivity, but I need to keep a production system up and running......

Philip

--
You received this message because you are subscribed to the Google Groups "Google Cloud SQL discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-sql-discuss+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/91be8af5-7d07-4062-9c5b-7f30bb9d09fa%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

No comments:

Post a Comment