Re: Missing cached payload in retry response.

Hi Philip

I'll get in touch off-list

j

On Mon, Sep 9, 2013 at 12:35 PM, Philip Gladstone <philip.j.s.gladstone@gmail.com> wrote:

It runs in AWS. 

I could try upgrading to the newer version of the google_sql.jar that comes in the current version of the SDK (0.9.8). Is that the new native one? How would I tell?

Philip

On Monday, September 9, 2013 2:08:58 PM UTC-4, Rob wrote:

where does your backend app run?

On Mon, Sep 9, 2013 at 10:47 AM, Philip Gladstone <philip.j.s...@gmail.com> wrote:

Doe this work when you are accessing the cloud SQL from outside app engine? This particular case is my backend app uploading data (which is then displayed by the appengine app).

Philip

On Monday, September 9, 2013 10:54:17 AM UTC-4, Razvan Musaloiu-E. wrote:

Can you please switch to using native MySQL Connection from Google App Engine [1]? The error you are seeing is generated only on the old connectivity. The errors on the new path should be closer to what MySQL generates.

[1] https://developers.google.com/cloud-sql/docs/native-mysql-gae

-- Razvan ME

On Mon, Sep 9, 2013 at 6:55 AM, Philip Gladstone <philip.j.s...@gmail.com> wrote:

Does anybody know what this error means: Missing cached payload in retry response.

It happened to me over the weekend when running a statement of the form:

INSERT INTO table1(fields) SELECT fields FROM table2 ON DUPLICATE KEY UPDATE f1=VALUES(f1)

This can be slow if there is a lot of data to move, but in this case, it couldn't have taken longer than about 400 seconds..... This was being done from a Java program using the cloud sql JDBC driver.

Has anybody else seen this error (it only appears in one distinct search result)? 

Is there anything that I can do (apart from retrying) to make this go away?

Thanks, Philip

The full traceback is

Caused by: java.sql.SQLException: Missing cached payload in retry response.

#011at com.google.cloud.sql.jdbc.internal.Exceptions.newSqlException(Exceptions.java:129)

#011at com.google.cloud.sql.jdbc.internal.SqlProtoClient.toCachedExecResponse(SqlProtoClient.java:288)

#011at com.google.cloud.sql.jdbc.internal.SqlProtoClient.access$700(SqlProtoClient.java:34)

#011at com.google.cloud.sql.jdbc.internal.SqlProtoClient$ExecHelper.retry(SqlProtoClient.java:364)

#011at com.google.cloud.sql.jdbc.internal.SqlProtoClient$ExecHelper.run(SqlProtoClient.java:324)

#011at com.google.cloud.sql.jdbc.internal.SqlProtoClient.executeSql(SqlProtoClient.java:85)

#011at com.google.cloud.sql.jdbc.internal.SqlProtoClient.executeSql(SqlProtoClient.java:76)

#011at com.google.cloud.sql.jdbc.Connection.executeSql(Connection.java:520)

#011at com.google.cloud.sql.jdbc.Statement.executeSqlImpl(Statement.java:280)

#011at com.google.cloud.sql.jdbc.Statement.executeImpl(Statement.java:154)

#011at com.google.cloud.sql.jdbc.Statement.execute(Statement.java:142)

--
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/9cd2e243-5498-48d8-950c-16babd3e2ab7%40googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.

--
Joe Faith | Product Manager | Google Cloud

--
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/CAHNz2%3D9qMSp5LPchcnrx3B79%2BGmEfM%2Bhf_Gi-W%3DXC5kY4Bphfg%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.