Re: newbie questions

GAE makes it very easy to get started with cloud hosted web applications.

Or, even simpler, you could write simple forms in Google Apps Script, store the data in Cloud SQL, then do reports via a Google Spreadsheet

https://developers.google.com/apps-script/uiapp

https://developers.google.com/apps-script/jdbc

On Fri, Jun 28, 2013 at 8:05 AM, David Kern <davekern00@gmail.com> wrote:

Thanks for the info James.  I will look into the tools you suggest.  I do have some level of programming but more of a hack than formal training.  I wrote a homebrew application in the 90's using Borland Delphi and I wrote an iPhone app a few years back to see if I could get it through apple, which I did.  The challenge... I am just confused on the different levels.  What to use for the interface, reporting, etc. with Google as the database.  You gave me some great info, thanks!

Dave

On Friday, June 28, 2013 4:07:58 AM UTC-7, James May wrote:

David,

Unfortunately, you are going to be diving into programming land. Google cloud sql is basically mysql in the cloud. So any book teaching you mysql would work. There are products such as navicat that allow database management with reporting. The problem is that I do not believe that navicat or similar products can connect to google cloud sql because of the driver needed to connect. There are other database management tools such as mysql workbench and dbvisualizer. You should have no problem connecting with squirrel sql and db visualizer because they can be configured with the google java jdbc driver.

The web ui will involve programming. No easy way around that one. I typically use java web development with jsf and primefaces.

My suggestion to you would be to start small. Take the cloud out of it. Cloud is a whole a different beast on top of traditional development. It is a whole different mind shift because of what you can and cannot do. Start with mysql and simple web development on a local server and then branch out from that point.

James May
Co-founding Partner
Bizznetworx Online
http://www.bizznetworxonline.com

On Jun 27, 2013 11:03 PM, "David Kern" <davek...@gmail.com> wrote:

I have a database in MS Access that I wrote about 7 years ago and have been updating to some extent since then.  It has about 30 tables all linked together, many queries and forms and is broken into a front-end and back-end.  I want to migrate this to the web and update the technology in a rewrite.  I am considering Google Cloud SQL as the cloud backend.  I am not a programmer by trade but have been a tinkerer since jr high.  Three big questions as this is new and I don't want to ask too many dumb questions.  Can anyone recommend:

• A good book on creating this type of database in the cloud
• Recommendations on what I should use for my user interface.  Very confused here as I want to to be web based and run in a browser.
• What tool I should use to generate reports?

I know Access sucks but the user interface and reports are easy.  I need to understand this in the context of the cloud and I am a bit confused.

Thanks for any help!

 
 

--
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.
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.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Re: newbie questions

Thanks for the info James.  I will look into the tools you suggest.  I do have some level of programming but more of a hack than formal training.  I wrote a homebrew application in the 90's using Borland Delphi and I wrote an iPhone app a few years back to see if I could get it through apple, which I did.  The challenge... I am just confused on the different levels.  What to use for the interface, reporting, etc. with Google as the database.  You gave me some great info, thanks!

Dave

On Friday, June 28, 2013 4:07:58 AM UTC-7, James May wrote:

David,

Unfortunately, you are going to be diving into programming land. Google cloud sql is basically mysql in the cloud. So any book teaching you mysql would work. There are products such as navicat that allow database management with reporting. The problem is that I do not believe that navicat or similar products can connect to google cloud sql because of the driver needed to connect. There are other database management tools such as mysql workbench and dbvisualizer. You should have no problem connecting with squirrel sql and db visualizer because they can be configured with the google java jdbc driver.

The web ui will involve programming. No easy way around that one. I typically use java web development with jsf and primefaces.

My suggestion to you would be to start small. Take the cloud out of it. Cloud is a whole a different beast on top of traditional development. It is a whole different mind shift because of what you can and cannot do. Start with mysql and simple web development on a local server and then branch out from that point.

James May
Co-founding Partner
Bizznetworx Online
http://www.bizznetworxonline.com

On Jun 27, 2013 11:03 PM, "David Kern" <davek...@gmail.com> wrote:

I have a database in MS Access that I wrote about 7 years ago and have been updating to some extent since then.  It has about 30 tables all linked together, many queries and forms and is broken into a front-end and back-end.  I want to migrate this to the web and update the technology in a rewrite.  I am considering Google Cloud SQL as the cloud backend.  I am not a programmer by trade but have been a tinkerer since jr high.  Three big questions as this is new and I don't want to ask too many dumb questions.  Can anyone recommend:

• A good book on creating this type of database in the cloud
• Recommendations on what I should use for my user interface.  Very confused here as I want to to be web based and run in a browser.
• What tool I should use to generate reports?

I know Access sucks but the user interface and reports are easy.  I need to understand this in the context of the cloud and I am a bit confused.

Thanks for any help!

 
 

--
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.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Re: newbie questions

David,

Unfortunately, you are going to be diving into programming land. Google cloud sql is basically mysql in the cloud. So any book teaching you mysql would work. There are products such as navicat that allow database management with reporting. The problem is that I do not believe that navicat or similar products can connect to google cloud sql because of the driver needed to connect. There are other database management tools such as mysql workbench and dbvisualizer. You should have no problem connecting with squirrel sql and db visualizer because they can be configured with the google java jdbc driver.

The web ui will involve programming. No easy way around that one. I typically use java web development with jsf and primefaces.

My suggestion to you would be to start small. Take the cloud out of it. Cloud is a whole a different beast on top of traditional development. It is a whole different mind shift because of what you can and cannot do. Start with mysql and simple web development on a local server and then branch out from that point.

James May
Co-founding Partner
Bizznetworx Online
http://www.bizznetworxonline.com

On Jun 27, 2013 11:03 PM, "David Kern" <davekern00@gmail.com> wrote:

I have a database in MS Access that I wrote about 7 years ago and have been updating to some extent since then.  It has about 30 tables all linked together, many queries and forms and is broken into a front-end and back-end.  I want to migrate this to the web and update the technology in a rewrite.  I am considering Google Cloud SQL as the cloud backend.  I am not a programmer by trade but have been a tinkerer since jr high.  Three big questions as this is new and I don't want to ask too many dumb questions.  Can anyone recommend:

• A good book on creating this type of database in the cloud
• Recommendations on what I should use for my user interface.  Very confused here as I want to to be web based and run in a browser.
• What tool I should use to generate reports?

I know Access sucks but the user interface and reports are easy.  I need to understand this in the context of the cloud and I am a bit confused.

Thanks for any help!

--
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.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
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.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

newbie questions

I have a database in MS Access that I wrote about 7 years ago and have been updating to some extent since then.  It has about 30 tables all linked together, many queries and forms and is broken into a front-end and back-end.  I want to migrate this to the web and update the technology in a rewrite.  I am considering Google Cloud SQL as the cloud backend.  I am not a programmer by trade but have been a tinkerer since jr high.  Three big questions as this is new and I don't want to ask too many dumb questions.  Can anyone recommend:

• A good book on creating this type of database in the cloud
• Recommendations on what I should use for my user interface.  Very confused here as I want to to be web based and run in a browser.
• What tool I should use to generate reports?

I know Access sucks but the user interface and reports are easy.  I need to understand this in the context of the cloud and I am a bit confused.

Thanks for any help!

--
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.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Re: getGeneratedKey() throws Exception

Yes. using 1 will always work (and is the way I've always done it). Each driver handles the names differently.

Rob

On Wed, Jun 26, 2013 at 9:30 AM, Jonas Gabriel <soli.gabriel@googlemail.com> wrote:

It said "ResultSet doesn't have a column XXX"... I was under the impression that I had to use to column name of my row id, but it seems just using 1 is the better option?

Am Mittwoch, 26. Juni 2013 18:18:42 UTC+2 schrieb Rob:

how does it fail? What's the SQLException or error?

On Wed, Jun 26, 2013 at 9:13 AM, Jonas Gabriel <soli.g...@googlemail.com> wrote:

Hi!

I have a problem with getting the key value after inserting a new row into Google Cloud SQL.

I could have sworn it worked before, but now somehow it doesn't...

String statement = "INSERT INTO xxxx ( xx) VALUES (?)";

PreparedStatement stmt = c.prepareStatement(statement, Statement.RETURN_GENERATED_KEYS);

stmt.setString(1, xx);

int i = 2;

i = stmt.executeUpdate();

if (i == 1) {

ResultSet result = stmt.getGeneratedKeys();

String resultCode = "1";

while (result.next()) {

resultCode = result.getString("xxid");

}

}

I can see the insert in my Database, so that works. And if I delete the stmt.getGeneratedKeys(); Method, everything works fine. But when I add that line, the query fails. What am I doing wrong here? (Makes no difference if I user RETURN_GENERATED_KEYS or 1...)

--
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.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
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.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
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.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Re: getGeneratedKey() throws Exception

It said "ResultSet doesn't have a column XXX"... I was under the impression that I had to use to column name of my row id, but it seems just using 1 is the better option?

Am Mittwoch, 26. Juni 2013 18:18:42 UTC+2 schrieb Rob:

how does it fail? What's the SQLException or error?

On Wed, Jun 26, 2013 at 9:13 AM, Jonas Gabriel <soli.g...@googlemail.com> wrote:

Hi!

I have a problem with getting the key value after inserting a new row into Google Cloud SQL.

I could have sworn it worked before, but now somehow it doesn't...

String statement = "INSERT INTO xxxx ( xx) VALUES (?)";

PreparedStatement stmt = c.prepareStatement(statement, Statement.RETURN_GENERATED_KEYS);

stmt.setString(1, xx);

int i = 2;

i = stmt.executeUpdate();

if (i == 1) {

ResultSet result = stmt.getGeneratedKeys();

String resultCode = "1";

while (result.next()) {

resultCode = result.getString("xxid");

}

}

I can see the insert in my Database, so that works. And if I delete the stmt.getGeneratedKeys(); Method, everything works fine. But when I add that line, the query fails. What am I doing wrong here? (Makes no difference if I user RETURN_GENERATED_KEYS or 1...)

--
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.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
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.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Re: getGeneratedKey() throws Exception

how does it fail? What's the SQLException or error?

On Wed, Jun 26, 2013 at 9:13 AM, Jonas Gabriel <soli.gabriel@googlemail.com> wrote:

Hi!

I have a problem with getting the key value after inserting a new row into Google Cloud SQL.

I could have sworn it worked before, but now somehow it doesn't...

String statement = "INSERT INTO xxxx ( xx) VALUES (?)";

PreparedStatement stmt = c.prepareStatement(statement, Statement.RETURN_GENERATED_KEYS);

stmt.setString(1, xx);

int i = 2;

i = stmt.executeUpdate();

if (i == 1) {

ResultSet result = stmt.getGeneratedKeys();

String resultCode = "1";

while (result.next()) {

resultCode = result.getString("xxid");

}

}

I can see the insert in my Database, so that works. And if I delete the stmt.getGeneratedKeys(); Method, everything works fine. But when I add that line, the query fails. What am I doing wrong here? (Makes no difference if I user RETURN_GENERATED_KEYS or 1...)

--
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.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
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.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Re: Disruption to Google Cloud SQL Service

The problem with Google Cloud SQL affected just a handful of instances, and should be resolved as of 8.50PST.

We apologize for the inconvenience and thank you for your patience and continued support.

J

On Wed, Jun 26, 2013 at 8:08 AM, Joe Faith <joefaith@google.com> wrote:

We're investigating an issue with Google Cloud SQL. We will provide more information shortly.

J

--
Joe Faith | Product Manager | Google Cloud

--
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.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

getGeneratedKey() throws Exception

Hi!

I have a problem with getting the key value after inserting a new row into Google Cloud SQL.

I could have sworn it worked before, but now somehow it doesn't...

String statement = "INSERT INTO xxxx ( xx) VALUES (?)";

PreparedStatement stmt = c.prepareStatement(statement, Statement.RETURN_GENERATED_KEYS);

stmt.setString(1, xx);

int i = 2;

i = stmt.executeUpdate();

if (i == 1) {

ResultSet result = stmt.getGeneratedKeys();

String resultCode = "1";

while (result.next()) {

resultCode = result.getString("xxid");

}

}

I can see the insert in my Database, so that works. And if I delete the stmt.getGeneratedKeys(); Method, everything works fine. But when I add that line, the query fails. What am I doing wrong here? (Makes no difference if I user RETURN_GENERATED_KEYS or 1...)

--
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.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Disruption to Google Cloud SQL Service

We're investigating an issue with Google Cloud SQL. We will provide more information shortly.

J

--
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.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Error in getting access to my instance via Eclipse

Dear all,

I am using a Google Cloud SQL instance as DB for my developments.

Starting from today I am not able to get access to that DB via Eclipse: I always get this error.

(Error: Placement service returned error code 1: /PlacementService.PlaceInstance to 10.182.33.103:8167 : APP_ERROR(1) No speckle data center found.)
Placement service returned error code 1: /PlacementService.PlaceInstance to 10.182.33.103:8167 : APP_ERROR(1) No speckle data center found.
Error creating Google Cloud SQL Connection factory connection to Profile (ACTL-JobOnCloud.GoogleCloudSQL.DevInstance). (Error: Placement service returned error code 1: /PlacementService.PlaceInstance to 10.182.86.73:8164 : APP_ERROR(1) No speckle data center found.)
Placement service returned error code 1: /PlacementService.PlaceInstance to 10.182.86.73:8164 : APP_ERROR(1) No speckle data center found.

Please could you tell me what is going on?

The instance name is "r3vc10udsq1:actl" and it is working well via Google APIs console.

Thank you very much and best Regards,

Marco.

--
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.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Re: Limit Team Access only to the Database

Thanks Amit!

On Sunday, June 23, 2013 10:38:08 PM UTC+2, M2013 wrote:

Hi,
How can I share a database, or an instance with an other user without sharing the information on the APIS admin console? (billing-services-team)

- I tried to create a dbase SQL user, however when running the command line I get following error:
Exiting: Unable to open connection
End user Google Account not authorized.
Is it possible to create an user without adding such usr in the team (admin -console)?

- Alternatively, can I create a database-only access from the sheets to the cloud? No human interaction to the Cloud possible.

thanks.

--
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.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Re: Limit Team Access only to the Database

Sorry for late response.

Currently, the only way is to add the user in the project viewer or editor group using the cloud sql console.

--Amit

On Tue, Jun 25, 2013 at 8:37 AM, M2013 <lorenzo.habicher@gmail.com> wrote:

Hi there, any updates on this front perhaps? :-)

rgards,

On Sunday, June 23, 2013 10:38:08 PM UTC+2, M2013 wrote:

Hi,
How can I share a database, or an instance with an other user without sharing the information on the APIS admin console? (billing-services-team)

- I tried to create a dbase SQL user, however when running the command line I get following error:
Exiting: Unable to open connection
End user Google Account not authorized.
Is it possible to create an user without adding such usr in the team (admin -console)?

- Alternatively, can I create a database-only access from the sheets to the cloud? No human interaction to the Cloud possible.

thanks.

--
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.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
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.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Re: Limit Team Access only to the Database

Hi there, any updates on this front perhaps? :-)

rgards,

On Sunday, June 23, 2013 10:38:08 PM UTC+2, M2013 wrote:

Hi,
How can I share a database, or an instance with an other user without sharing the information on the APIS admin console? (billing-services-team)

- I tried to create a dbase SQL user, however when running the command line I get following error:
Exiting: Unable to open connection
End user Google Account not authorized.
Is it possible to create an user without adding such usr in the team (admin -console)?

- Alternatively, can I create a database-only access from the sheets to the cloud? No human interaction to the Cloud possible.

thanks.

--
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.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Re: Slow insert from AppEngine application

We are in the middle of data center migration. That is most likely the reason.

On Jun 25, 2013 2:33 AM, "Luca Zanconato" <luca.zanconato@gocloud.it> wrote:

Hi Tony,

from this morning (GMT+2) the system started to respond with low latency again.

Thanks

Luca

On Monday, June 24, 2013 11:43:21 PM UTC+2, Tony Tseng wrote:

Hi Luca,

Your instance appears to be co-located with AppEngine. I don't see anything unusual with the connectivity. Are you still experiencing high latency?

On Mon, Jun 24, 2013 at 3:05 AM, Luca Zanconato <luca.za...@gocloud.it> wrote:

Hello,

since friday 21st the Cloud SQL instance has become really slow when bulk inserting records: we tried to remove indexes, to restart the instance and also to drop and recreate the database without success.

Before friday we were able to bulk insert 800 records per time on a single table, and now when trying to insert 400 the instance takes more than 60 seconds to respond and so AppEngine reaches the request timeout limit.

• instance name: workforcegso-pre:workforcegso-pre-db
• application name: workforcegso
• stacktrace:

2013-06-24 10:53:34.500

  it.gocloud.wgso.srv.biz.wfm.AnnotatedActionsWorkflowManager handleWorkflow: null  java.lang.reflect.InvocationTargetException  	at com.google.appengine.runtime.Request.process-017071684c02af59(Request.java)  	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)  	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)  	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)  	at java.lang.reflect.Method.invoke(Method.java:45)  	at it.gocloud.wgso.srv.biz.wfm.AnnotatedActionsWorkflowManager.handleWorkflow(AnnotatedActionsWorkflowManager.java:86)  	at it.gocloud.wgso.srv.res.BulkInterventions.putCsv(BulkInterventions.java:94)  	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)  	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)  	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)  	at java.lang.reflect.Method.invoke(Method.java:45)  	at com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:186)  	at com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:70)  	at com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:279)  	at com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:86)  	at com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:136)  	at com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:74)  	at com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1347)  	at com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1279)  	at com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1229)  	at com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1219)  	at com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:419)  	at com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:537)  	at com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:699)  	at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)  	at com.google.inject.servlet.ServletDefinition.doService(ServletDefinition.java:263)  	at com.google.inject.servlet.ServletDefinition.service(ServletDefinition.java:178)  	at com.google.inject.servlet.ManagedServletPipeline.service(ManagedServletPipeline.java:91)  	at com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:62)  	at org.apache.shiro.guice.web.SimpleFilterChain.doFilter(SimpleFilterChain.java:44)  	at org.apache.shiro.web.servlet.AdviceFilter.executeChain(AdviceFilter.java:108)  	at org.apache.shiro.web.servlet.AdviceFilter.doFilterInternal(AdviceFilter.java:137)  	at org.apache.shiro.web.servlet.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:125)  	at org.apache.shiro.guice.web.SimpleFilterChain.doFilter(SimpleFilterChain.java:41)  	at org.apache.shiro.web.servlet.AdviceFilter.executeChain(AdviceFilter.java:108)  	at org.apache.shiro.web.servlet.AdviceFilter.doFilterInternal(AdviceFilter.java:137)  	at org.apache.shiro.web.servlet.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:125)  	at org.apache.shiro.guice.web.SimpleFilterChain.doFilter(SimpleFilterChain.java:41)  	at org.apache.shiro.web.servlet.AdviceFilter.executeChain(AdviceFilter.java:108)  	at org.apache.shiro.web.servlet.AdviceFilter.doFilterInternal(AdviceFilter.java:137)  	at org.apache.shiro.web.servlet.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:125)  	at org.apache.shiro.guice.web.SimpleFilterChain.doFilter(SimpleFilterChain.java:41)  	at org.apache.shiro.web.servlet.AdviceFilter.executeChain(AdviceFilter.java:108)  	at org.apache.shiro.web.servlet.AdviceFilter.doFilterInternal(AdviceFilter.java:137)  	at org.apache.shiro.web.servlet.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:125)  	at org.apache.shiro.guice.web.SimpleFilterChain.doFilter(SimpleFilterChain.java:41)  	at org.apache.shiro.web.servlet.AbstractShiroFilter.executeChain(AbstractShiroFilter.java:449)  	at org.apache.shiro.web.servlet.AbstractShiroFilter$1.call(AbstractShiroFilter.java:365)  	at org.apache.shiro.subject.support.SubjectCallable.doCall(SubjectCallable.java:90)  	at org.apache.shiro.subject.support.SubjectCallable.call(SubjectCallable.java:83)  	at org.apache.shiro.subject.support.DelegatingSubject.execute(DelegatingSubject.java:380)  	at org.apache.shiro.web.servlet.AbstractShiroFilter.doFilterInternal(AbstractShiroFilter.java:362)  	at org.apache.shiro.web.servlet.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:125)  	at com.google.inject.servlet.FilterDefinition.doFilter(FilterDefinition.java:163)  	at com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:58)  	at com.google.inject.servlet.ManagedFilterPipeline.dispatch(ManagedFilterPipeline.java:118)  	at com.google.inject.servlet.GuiceFilter.doFilter(GuiceFilter.java:113)  	at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)  	at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)  	at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)  	at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)  	at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)  	at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:388)  	at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)  	at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)  	at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765)  	at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:418)  	at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)  	at org.mortbay.jetty.Server.handle(Server.java:326)  	at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542)  	at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:923)  	at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)  	at com.google.tracing.TraceContext$TraceContextRunnable.runInContext(TraceContext.java:483)  	at com.google.tracing.TraceContext$TraceContextRunnable$1.run(TraceContext.java:490)  	at com.google.tracing.TraceContext.runInContext(TraceContext.java:777)  	at com.google.tracing.TraceContext$DoInTraceContext.runInContext(TraceContext.java:754)  	at com.google.tracing.TraceContext$AbstractTraceContextCallback.runInInheritedContextNoUnref(TraceContext.java:345)  	at com.google.tracing.TraceContext$AbstractTraceContextCallback.runInInheritedContext(TraceContext.java:337)  	at com.google.tracing.TraceContext$TraceContextRunnable.run(TraceContext.java:487)  	at java.lang.Thread.run(Thread.java:722)  Caused by: com.google.apphosting.api.DeadlineExceededException: This request (017071684c02af59) started at 2013/06/24 08:52:35.074 UTC and was still executing at 2013/06/24 08:53:34.497 UTC.  	at java.util.regex.Pattern$Curly.match0(Pattern.java:4170)  	at java.util.regex.Pattern$Curly.match(Pattern.java:4132)  	at java.util.regex.Pattern$GroupHead.match(Pattern.java:4556)  	at java.util.regex.Pattern$Start.match(Pattern.java:3408)  	at java.util.regex.Matcher.search(Matcher.java:1318)  	at java.util.regex.Matcher.find(Matcher.java:593)  	at it.gocloud.wgso.srv.data.BaseJpaDao.addDomainFilter(BaseJpaDao.java:102)  	at it.gocloud.wgso.srv.data.BaseJpaDao.query(BaseJpaDao.java:152)  	at it.gocloud.wgso.srv.data.BaseJpaDao.find(BaseJpaDao.java:245)  	at it.gocloud.wgso.srv.data.BaseJpaDao.saveOrUpdate(BaseJpaDao.java:349)  	at it.gocloud.wgso.srv.data.InterventionDaoImpl.addOrUpdate(InterventionDaoImpl.java:211)  	at it.gocloud.wgso.srv.biz.wfm.InterventionWorkflowManagerImpl.insertOrUpdate(InterventionWorkflowManagerImpl.java:72)  	... 79 more

Thanks
Luca Zanconato

Il presente messaggio ed i suoi allegati sono confidenziali in ragione della loro natura professionale e, in ogni caso, non accessibili al pubblico. Nel caso in cui il presente messaggio sia ricevuto da soggetto diverso dal suo diretto destinatario, si prega di darne immediata notizia al n° +390236680761 e di procedere immediatamente alla distruzione dello stesso e dei suoi allegati, da effettuarsi senza copiarne o rivelarne ad alcuno il contenuto. Grazie per la collaborazione.

This e-mail and any  attachments thereto are confidential and may be covered by legal professional privilege or otherwise protected from disclosure. If you are not the intended recipient, please notify us immediately by phone at +390236680761 and then immediately destroy this message and any attachments from your system, without copying or disclosing the contents to any other person. Thank you for your co-operation.

--
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.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Il presente messaggio ed i suoi allegati sono confidenziali in ragione della loro natura professionale e, in ogni caso, non accessibili al pubblico. Nel caso in cui il presente messaggio sia ricevuto da soggetto diverso dal suo diretto destinatario, si prega di darne immediata notizia al n° +390236680761 e di procedere immediatamente alla distruzione dello stesso e dei suoi allegati, da effettuarsi senza copiarne o rivelarne ad alcuno il contenuto. Grazie per la collaborazione.

This e-mail and any  attachments thereto are confidential and may be covered by legal professional privilege or otherwise protected from disclosure. If you are not the intended recipient, please notify us immediately by phone at +390236680761 and then immediately destroy this message and any attachments from your system, without copying or disclosing the contents to any other person. Thank you for your co-operation.

--
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.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
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.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Re: Slow insert from AppEngine application

Hi Tony,

from this morning (GMT+2) the system started to respond with low latency again.

Thanks

Luca

On Monday, June 24, 2013 11:43:21 PM UTC+2, Tony Tseng wrote:

Hi Luca,

Your instance appears to be co-located with AppEngine. I don't see anything unusual with the connectivity. Are you still experiencing high latency?

On Mon, Jun 24, 2013 at 3:05 AM, Luca Zanconato <luca.za...@gocloud.it> wrote:

Hello,

since friday 21st the Cloud SQL instance has become really slow when bulk inserting records: we tried to remove indexes, to restart the instance and also to drop and recreate the database without success.

Before friday we were able to bulk insert 800 records per time on a single table, and now when trying to insert 400 the instance takes more than 60 seconds to respond and so AppEngine reaches the request timeout limit.

• instance name: workforcegso-pre:workforcegso-pre-db
• application name: workforcegso
• stacktrace:

2013-06-24 10:53:34.500

it.gocloud.wgso.srv.biz.wfm.AnnotatedActionsWorkflowManager handleWorkflow: null  java.lang.reflect.InvocationTargetException  	at com.google.appengine.runtime.Request.process-017071684c02af59(Request.java)  	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)  	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)  	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)  	at java.lang.reflect.Method.invoke(Method.java:45)  	at it.gocloud.wgso.srv.biz.wfm.AnnotatedActionsWorkflowManager.handleWorkflow(AnnotatedActionsWorkflowManager.java:86)  	at it.gocloud.wgso.srv.res.BulkInterventions.putCsv(BulkInterventions.java:94)  	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)  	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)  	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)  	at java.lang.reflect.Method.invoke(Method.java:45)  	at com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:186)  	at com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:70)  	at com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:279)  	at com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:86)  	at com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:136)  	at com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:74)  	at com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1347)  	at com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1279)  	at com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1229)  	at com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1219)  	at com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:419)  	at com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:537)  	at com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:699)  	at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)  	at com.google.inject.servlet.ServletDefinition.doService(ServletDefinition.java:263)  	at com.google.inject.servlet.ServletDefinition.service(ServletDefinition.java:178)  	at com.google.inject.servlet.ManagedServletPipeline.service(ManagedServletPipeline.java:91)  	at com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:62)  	at org.apache.shiro.guice.web.SimpleFilterChain.doFilter(SimpleFilterChain.java:44)  	at org.apache.shiro.web.servlet.AdviceFilter.executeChain(AdviceFilter.java:108)  	at org.apache.shiro.web.servlet.AdviceFilter.doFilterInternal(AdviceFilter.java:137)  	at org.apache.shiro.web.servlet.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:125)  	at org.apache.shiro.guice.web.SimpleFilterChain.doFilter(SimpleFilterChain.java:41)  	at org.apache.shiro.web.servlet.AdviceFilter.executeChain(AdviceFilter.java:108)  	at org.apache.shiro.web.servlet.AdviceFilter.doFilterInternal(AdviceFilter.java:137)  	at org.apache.shiro.web.servlet.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:125)  	at org.apache.shiro.guice.web.SimpleFilterChain.doFilter(SimpleFilterChain.java:41)  	at org.apache.shiro.web.servlet.AdviceFilter.executeChain(AdviceFilter.java:108)  	at org.apache.shiro.web.servlet.AdviceFilter.doFilterInternal(AdviceFilter.java:137)  	at org.apache.shiro.web.servlet.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:125)  	at org.apache.shiro.guice.web.SimpleFilterChain.doFilter(SimpleFilterChain.java:41)  	at org.apache.shiro.web.servlet.AdviceFilter.executeChain(AdviceFilter.java:108)  	at org.apache.shiro.web.servlet.AdviceFilter.doFilterInternal(AdviceFilter.java:137)  	at org.apache.shiro.web.servlet.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:125)  	at org.apache.shiro.guice.web.SimpleFilterChain.doFilter(SimpleFilterChain.java:41)  	at org.apache.shiro.web.servlet.AbstractShiroFilter.executeChain(AbstractShiroFilter.java:449)  	at org.apache.shiro.web.servlet.AbstractShiroFilter$1.call(AbstractShiroFilter.java:365)  	at org.apache.shiro.subject.support.SubjectCallable.doCall(SubjectCallable.java:90)  	at org.apache.shiro.subject.support.SubjectCallable.call(SubjectCallable.java:83)  	at org.apache.shiro.subject.support.DelegatingSubject.execute(DelegatingSubject.java:380)  	at org.apache.shiro.web.servlet.AbstractShiroFilter.doFilterInternal(AbstractShiroFilter.java:362)  	at org.apache.shiro.web.servlet.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:125)  	at com.google.inject.servlet.FilterDefinition.doFilter(FilterDefinition.java:163)  	at com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:58)  	at com.google.inject.servlet.ManagedFilterPipeline.dispatch(ManagedFilterPipeline.java:118)  	at com.google.inject.servlet.GuiceFilter.doFilter(GuiceFilter.java:113)  	at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)  	at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)  	at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)  	at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)  	at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)  	at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:388)  	at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)  	at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)  	at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765)  	at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:418)  	at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)  	at org.mortbay.jetty.Server.handle(Server.java:326)  	at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542)  	at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:923)  	at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)  	at com.google.tracing.TraceContext$TraceContextRunnable.runInContext(TraceContext.java:483)  	at com.google.tracing.TraceContext$TraceContextRunnable$1.run(TraceContext.java:490)  	at com.google.tracing.TraceContext.runInContext(TraceContext.java:777)  	at com.google.tracing.TraceContext$DoInTraceContext.runInContext(TraceContext.java:754)  	at com.google.tracing.TraceContext$AbstractTraceContextCallback.runInInheritedContextNoUnref(TraceContext.java:345)  	at com.google.tracing.TraceContext$AbstractTraceContextCallback.runInInheritedContext(TraceContext.java:337)  	at com.google.tracing.TraceContext$TraceContextRunnable.run(TraceContext.java:487)  	at java.lang.Thread.run(Thread.java:722)  Caused by: com.google.apphosting.api.DeadlineExceededException: This request (017071684c02af59) started at 2013/06/24 08:52:35.074 UTC and was still executing at 2013/06/24 08:53:34.497 UTC.  	at java.util.regex.Pattern$Curly.match0(Pattern.java:4170)  	at java.util.regex.Pattern$Curly.match(Pattern.java:4132)  	at java.util.regex.Pattern$GroupHead.match(Pattern.java:4556)  	at java.util.regex.Pattern$Start.match(Pattern.java:3408)  	at java.util.regex.Matcher.search(Matcher.java:1318)  	at java.util.regex.Matcher.find(Matcher.java:593)  	at it.gocloud.wgso.srv.data.BaseJpaDao.addDomainFilter(BaseJpaDao.java:102)  	at it.gocloud.wgso.srv.data.BaseJpaDao.query(BaseJpaDao.java:152)  	at it.gocloud.wgso.srv.data.BaseJpaDao.find(BaseJpaDao.java:245)  	at it.gocloud.wgso.srv.data.BaseJpaDao.saveOrUpdate(BaseJpaDao.java:349)  	at it.gocloud.wgso.srv.data.InterventionDaoImpl.addOrUpdate(InterventionDaoImpl.java:211)  	at it.gocloud.wgso.srv.biz.wfm.InterventionWorkflowManagerImpl.insertOrUpdate(InterventionWorkflowManagerImpl.java:72)  	... 79 more

Thanks
Luca Zanconato

Il presente messaggio ed i suoi allegati sono confidenziali in ragione della loro natura professionale e, in ogni caso, non accessibili al pubblico. Nel caso in cui il presente messaggio sia ricevuto da soggetto diverso dal suo diretto destinatario, si prega di darne immediata notizia al n° +390236680761 e di procedere immediatamente alla distruzione dello stesso e dei suoi allegati, da effettuarsi senza copiarne o rivelarne ad alcuno il contenuto. Grazie per la collaborazione.

This e-mail and any  attachments thereto are confidential and may be covered by legal professional privilege or otherwise protected from disclosure. If you are not the intended recipient, please notify us immediately by phone at +390236680761 and then immediately destroy this message and any attachments from your system, without copying or disclosing the contents to any other person. Thank you for your co-operation.

--
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.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Il presente messaggio ed i suoi allegati sono confidenziali in ragione della loro natura professionale e, in ogni caso, non accessibili al pubblico. Nel caso in cui il presente messaggio sia ricevuto da soggetto diverso dal suo diretto destinatario, si prega di darne immediata notizia al n° +390236680761 e di procedere immediatamente alla distruzione dello stesso e dei suoi allegati, da effettuarsi senza copiarne o rivelarne ad alcuno il contenuto. Grazie per la collaborazione.

This e-mail and any  attachments thereto are confidential and may be covered by legal professional privilege or otherwise protected from disclosure. If you are not the intended recipient, please notify us immediately by phone at +390236680761 and then immediately destroy this message and any attachments from your system, without copying or disclosing the contents to any other person. Thank you for your co-operation.

--
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.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Re: Slow insert from AppEngine application

Hi Luca,

Your instance appears to be co-located with AppEngine. I don't see anything unusual with the connectivity. Are you still experiencing high latency?

On Mon, Jun 24, 2013 at 3:05 AM, Luca Zanconato <luca.zanconato@gocloud.it> wrote:

Hello,

since friday 21st the Cloud SQL instance has become really slow when bulk inserting records: we tried to remove indexes, to restart the instance and also to drop and recreate the database without success.

Before friday we were able to bulk insert 800 records per time on a single table, and now when trying to insert 400 the instance takes more than 60 seconds to respond and so AppEngine reaches the request timeout limit.

• instance name: workforcegso-pre:workforcegso-pre-db
• application name: workforcegso
• stacktrace:

2013-06-24 10:53:34.500

    it.gocloud.wgso.srv.biz.wfm.AnnotatedActionsWorkflowManager handleWorkflow: null  java.lang.reflect.InvocationTargetException  	at com.google.appengine.runtime.Request.process-017071684c02af59(Request.java)  	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)  	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)  	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)  	at java.lang.reflect.Method.invoke(Method.java:45)  	at it.gocloud.wgso.srv.biz.wfm.AnnotatedActionsWorkflowManager.handleWorkflow(AnnotatedActionsWorkflowManager.java:86)  	at it.gocloud.wgso.srv.res.BulkInterventions.putCsv(BulkInterventions.java:94)  	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)  	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)  	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)  	at java.lang.reflect.Method.invoke(Method.java:45)  	at com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:186)  	at com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:70)  	at com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:279)  	at com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:86)  	at com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:136)  	at com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:74)  	at com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1347)  	at com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1279)  	at com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1229)  	at com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1219)  	at com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:419)  	at com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:537)  	at com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:699)  	at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)  	at com.google.inject.servlet.ServletDefinition.doService(ServletDefinition.java:263)  	at com.google.inject.servlet.ServletDefinition.service(ServletDefinition.java:178)  	at com.google.inject.servlet.ManagedServletPipeline.service(ManagedServletPipeline.java:91)  	at com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:62)  	at org.apache.shiro.guice.web.SimpleFilterChain.doFilter(SimpleFilterChain.java:44)  	at org.apache.shiro.web.servlet.AdviceFilter.executeChain(AdviceFilter.java:108)  	at org.apache.shiro.web.servlet.AdviceFilter.doFilterInternal(AdviceFilter.java:137)  	at org.apache.shiro.web.servlet.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:125)  	at org.apache.shiro.guice.web.SimpleFilterChain.doFilter(SimpleFilterChain.java:41)  	at org.apache.shiro.web.servlet.AdviceFilter.executeChain(AdviceFilter.java:108)  	at org.apache.shiro.web.servlet.AdviceFilter.doFilterInternal(AdviceFilter.java:137)  	at org.apache.shiro.web.servlet.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:125)  	at org.apache.shiro.guice.web.SimpleFilterChain.doFilter(SimpleFilterChain.java:41)  	at org.apache.shiro.web.servlet.AdviceFilter.executeChain(AdviceFilter.java:108)  	at org.apache.shiro.web.servlet.AdviceFilter.doFilterInternal(AdviceFilter.java:137)  	at org.apache.shiro.web.servlet.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:125)  	at org.apache.shiro.guice.web.SimpleFilterChain.doFilter(SimpleFilterChain.java:41)  	at org.apache.shiro.web.servlet.AdviceFilter.executeChain(AdviceFilter.java:108)  	at org.apache.shiro.web.servlet.AdviceFilter.doFilterInternal(AdviceFilter.java:137)  	at org.apache.shiro.web.servlet.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:125)  	at org.apache.shiro.guice.web.SimpleFilterChain.doFilter(SimpleFilterChain.java:41)  	at org.apache.shiro.web.servlet.AbstractShiroFilter.executeChain(AbstractShiroFilter.java:449)  	at org.apache.shiro.web.servlet.AbstractShiroFilter$1.call(AbstractShiroFilter.java:365)  	at org.apache.shiro.subject.support.SubjectCallable.doCall(SubjectCallable.java:90)  	at org.apache.shiro.subject.support.SubjectCallable.call(SubjectCallable.java:83)  	at org.apache.shiro.subject.support.DelegatingSubject.execute(DelegatingSubject.java:380)  	at org.apache.shiro.web.servlet.AbstractShiroFilter.doFilterInternal(AbstractShiroFilter.java:362)  	at org.apache.shiro.web.servlet.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:125)  	at com.google.inject.servlet.FilterDefinition.doFilter(FilterDefinition.java:163)  	at com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:58)  	at com.google.inject.servlet.ManagedFilterPipeline.dispatch(ManagedFilterPipeline.java:118)  	at com.google.inject.servlet.GuiceFilter.doFilter(GuiceFilter.java:113)  	at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)  	at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)  	at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)  	at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)  	at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)  	at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:388)  	at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)  	at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)  	at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765)  	at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:418)  	at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)  	at org.mortbay.jetty.Server.handle(Server.java:326)  	at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542)  	at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:923)  	at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)  	at com.google.tracing.TraceContext$TraceContextRunnable.runInContext(TraceContext.java:483)  	at com.google.tracing.TraceContext$TraceContextRunnable$1.run(TraceContext.java:490)  	at com.google.tracing.TraceContext.runInContext(TraceContext.java:777)  	at com.google.tracing.TraceContext$DoInTraceContext.runInContext(TraceContext.java:754)  	at com.google.tracing.TraceContext$AbstractTraceContextCallback.runInInheritedContextNoUnref(TraceContext.java:345)  	at com.google.tracing.TraceContext$AbstractTraceContextCallback.runInInheritedContext(TraceContext.java:337)  	at com.google.tracing.TraceContext$TraceContextRunnable.run(TraceContext.java:487)  	at java.lang.Thread.run(Thread.java:722)  Caused by: com.google.apphosting.api.DeadlineExceededException: This request (017071684c02af59) started at 2013/06/24 08:52:35.074 UTC and was still executing at 2013/06/24 08:53:34.497 UTC.  	at java.util.regex.Pattern$Curly.match0(Pattern.java:4170)  	at java.util.regex.Pattern$Curly.match(Pattern.java:4132)  	at java.util.regex.Pattern$GroupHead.match(Pattern.java:4556)  	at java.util.regex.Pattern$Start.match(Pattern.java:3408)  	at java.util.regex.Matcher.search(Matcher.java:1318)  	at java.util.regex.Matcher.find(Matcher.java:593)  	at it.gocloud.wgso.srv.data.BaseJpaDao.addDomainFilter(BaseJpaDao.java:102)  	at it.gocloud.wgso.srv.data.BaseJpaDao.query(BaseJpaDao.java:152)  	at it.gocloud.wgso.srv.data.BaseJpaDao.find(BaseJpaDao.java:245)  	at it.gocloud.wgso.srv.data.BaseJpaDao.saveOrUpdate(BaseJpaDao.java:349)  	at it.gocloud.wgso.srv.data.InterventionDaoImpl.addOrUpdate(InterventionDaoImpl.java:211)  	at it.gocloud.wgso.srv.biz.wfm.InterventionWorkflowManagerImpl.insertOrUpdate(InterventionWorkflowManagerImpl.java:72)  	... 79 more

Thanks
Luca Zanconato

Il presente messaggio ed i suoi allegati sono confidenziali in ragione della loro natura professionale e, in ogni caso, non accessibili al pubblico. Nel caso in cui il presente messaggio sia ricevuto da soggetto diverso dal suo diretto destinatario, si prega di darne immediata notizia al n° +390236680761 e di procedere immediatamente alla distruzione dello stesso e dei suoi allegati, da effettuarsi senza copiarne o rivelarne ad alcuno il contenuto. Grazie per la collaborazione.

This e-mail and any  attachments thereto are confidential and may be covered by legal professional privilege or otherwise protected from disclosure. If you are not the intended recipient, please notify us immediately by phone at +390236680761 and then immediately destroy this message and any attachments from your system, without copying or disclosing the contents to any other person. Thank you for your co-operation.

--
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.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
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.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Slow insert from AppEngine application

Hello,

since friday 21st the Cloud SQL instance has become really slow when bulk inserting records: we tried to remove indexes, to restart the instance and also to drop and recreate the database without success.

Before friday we were able to bulk insert 800 records per time on a single table, and now when trying to insert 400 the instance takes more than 60 seconds to respond and so AppEngine reaches the request timeout limit.

• instance name: workforcegso-pre:workforcegso-pre-db
• application name: workforcegso
• stacktrace:

2013-06-24 10:53:34.500

it.gocloud.wgso.srv.biz.wfm.AnnotatedActionsWorkflowManager handleWorkflow: null  java.lang.reflect.InvocationTargetException  	at com.google.appengine.runtime.Request.process-017071684c02af59(Request.java)  	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)  	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)  	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)  	at java.lang.reflect.Method.invoke(Method.java:45)  	at it.gocloud.wgso.srv.biz.wfm.AnnotatedActionsWorkflowManager.handleWorkflow(AnnotatedActionsWorkflowManager.java:86)  	at it.gocloud.wgso.srv.res.BulkInterventions.putCsv(BulkInterventions.java:94)  	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)  	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)  	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)  	at java.lang.reflect.Method.invoke(Method.java:45)  	at com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:186)  	at com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:70)  	at com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:279)  	at com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:86)  	at com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:136)  	at com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:74)  	at com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1347)  	at com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1279)  	at com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1229)  	at com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1219)  	at com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:419)  	at com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:537)  	at com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:699)  	at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)  	at com.google.inject.servlet.ServletDefinition.doService(ServletDefinition.java:263)  	at com.google.inject.servlet.ServletDefinition.service(ServletDefinition.java:178)  	at com.google.inject.servlet.ManagedServletPipeline.service(ManagedServletPipeline.java:91)  	at com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:62)  	at org.apache.shiro.guice.web.SimpleFilterChain.doFilter(SimpleFilterChain.java:44)  	at org.apache.shiro.web.servlet.AdviceFilter.executeChain(AdviceFilter.java:108)  	at org.apache.shiro.web.servlet.AdviceFilter.doFilterInternal(AdviceFilter.java:137)  	at org.apache.shiro.web.servlet.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:125)  	at org.apache.shiro.guice.web.SimpleFilterChain.doFilter(SimpleFilterChain.java:41)  	at org.apache.shiro.web.servlet.AdviceFilter.executeChain(AdviceFilter.java:108)  	at org.apache.shiro.web.servlet.AdviceFilter.doFilterInternal(AdviceFilter.java:137)  	at org.apache.shiro.web.servlet.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:125)  	at org.apache.shiro.guice.web.SimpleFilterChain.doFilter(SimpleFilterChain.java:41)  	at org.apache.shiro.web.servlet.AdviceFilter.executeChain(AdviceFilter.java:108)  	at org.apache.shiro.web.servlet.AdviceFilter.doFilterInternal(AdviceFilter.java:137)  	at org.apache.shiro.web.servlet.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:125)  	at org.apache.shiro.guice.web.SimpleFilterChain.doFilter(SimpleFilterChain.java:41)  	at org.apache.shiro.web.servlet.AdviceFilter.executeChain(AdviceFilter.java:108)  	at org.apache.shiro.web.servlet.AdviceFilter.doFilterInternal(AdviceFilter.java:137)  	at org.apache.shiro.web.servlet.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:125)  	at org.apache.shiro.guice.web.SimpleFilterChain.doFilter(SimpleFilterChain.java:41)  	at org.apache.shiro.web.servlet.AbstractShiroFilter.executeChain(AbstractShiroFilter.java:449)  	at org.apache.shiro.web.servlet.AbstractShiroFilter$1.call(AbstractShiroFilter.java:365)  	at org.apache.shiro.subject.support.SubjectCallable.doCall(SubjectCallable.java:90)  	at org.apache.shiro.subject.support.SubjectCallable.call(SubjectCallable.java:83)  	at org.apache.shiro.subject.support.DelegatingSubject.execute(DelegatingSubject.java:380)  	at org.apache.shiro.web.servlet.AbstractShiroFilter.doFilterInternal(AbstractShiroFilter.java:362)  	at org.apache.shiro.web.servlet.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:125)  	at com.google.inject.servlet.FilterDefinition.doFilter(FilterDefinition.java:163)  	at com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:58)  	at com.google.inject.servlet.ManagedFilterPipeline.dispatch(ManagedFilterPipeline.java:118)  	at com.google.inject.servlet.GuiceFilter.doFilter(GuiceFilter.java:113)  	at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)  	at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)  	at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)  	at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)  	at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)  	at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:388)  	at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)  	at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)  	at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765)  	at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:418)  	at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)  	at org.mortbay.jetty.Server.handle(Server.java:326)  	at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542)  	at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:923)  	at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)  	at com.google.tracing.TraceContext$TraceContextRunnable.runInContext(TraceContext.java:483)  	at com.google.tracing.TraceContext$TraceContextRunnable$1.run(TraceContext.java:490)  	at com.google.tracing.TraceContext.runInContext(TraceContext.java:777)  	at com.google.tracing.TraceContext$DoInTraceContext.runInContext(TraceContext.java:754)  	at com.google.tracing.TraceContext$AbstractTraceContextCallback.runInInheritedContextNoUnref(TraceContext.java:345)  	at com.google.tracing.TraceContext$AbstractTraceContextCallback.runInInheritedContext(TraceContext.java:337)  	at com.google.tracing.TraceContext$TraceContextRunnable.run(TraceContext.java:487)  	at java.lang.Thread.run(Thread.java:722)  Caused by: com.google.apphosting.api.DeadlineExceededException: This request (017071684c02af59) started at 2013/06/24 08:52:35.074 UTC and was still executing at 2013/06/24 08:53:34.497 UTC.  	at java.util.regex.Pattern$Curly.match0(Pattern.java:4170)  	at java.util.regex.Pattern$Curly.match(Pattern.java:4132)  	at java.util.regex.Pattern$GroupHead.match(Pattern.java:4556)  	at java.util.regex.Pattern$Start.match(Pattern.java:3408)  	at java.util.regex.Matcher.search(Matcher.java:1318)  	at java.util.regex.Matcher.find(Matcher.java:593)  	at it.gocloud.wgso.srv.data.BaseJpaDao.addDomainFilter(BaseJpaDao.java:102)  	at it.gocloud.wgso.srv.data.BaseJpaDao.query(BaseJpaDao.java:152)  	at it.gocloud.wgso.srv.data.BaseJpaDao.find(BaseJpaDao.java:245)  	at it.gocloud.wgso.srv.data.BaseJpaDao.saveOrUpdate(BaseJpaDao.java:349)  	at it.gocloud.wgso.srv.data.InterventionDaoImpl.addOrUpdate(InterventionDaoImpl.java:211)  	at it.gocloud.wgso.srv.biz.wfm.InterventionWorkflowManagerImpl.insertOrUpdate(InterventionWorkflowManagerImpl.java:72)  	... 79 more

Thanks
Luca Zanconato

Il presente messaggio ed i suoi allegati sono confidenziali in ragione della loro natura professionale e, in ogni caso, non accessibili al pubblico. Nel caso in cui il presente messaggio sia ricevuto da soggetto diverso dal suo diretto destinatario, si prega di darne immediata notizia al n° +390236680761 e di procedere immediatamente alla distruzione dello stesso e dei suoi allegati, da effettuarsi senza copiarne o rivelarne ad alcuno il contenuto. Grazie per la collaborazione.

This e-mail and any  attachments thereto are confidential and may be covered by legal professional privilege or otherwise protected from disclosure. If you are not the intended recipient, please notify us immediately by phone at +390236680761 and then immediately destroy this message and any attachments from your system, without copying or disclosing the contents to any other person. Thank you for your co-operation.

--
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.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Limit Team Access only to the Database

Hi,
How can I share a database, or an instance with an other user without sharing the information on the APIS admin console? (billing-services-team)

- I tried to create a dbase SQL user, however when running the command line I get following error:
Exiting: Unable to open connection
End user Google Account not authorized.
Is it possible to create an user without adding such usr in the team (admin -console)?

- Alternatively, can I create a database-only access from the sheets to the cloud? No human interaction to the Cloud possible.

thanks.

--
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.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Re: Connection setup time >700ms on a google compute engine instance

As Joe said earlier, we are working hard on improving the connectivity between GCE and Cloud SQL.  Yes, latency is very high between them right now, but we're going to fix that.

It looks like you are still the in the development phase of your project.  I suggest that you simply run a mysqld in a GCE VM for purposes of development.  When you are ready for something more robust, please check in with us.

Thanks for your patience,

Ken

On Fri, Jun 21, 2013 at 3:49 PM, Vladimir Ralev <vladimir.ralev@gmail.com> wrote:

To expand on this issue. Even a single SET_AUTO_COMMIT or manual COMMIT statement takes 70-80 ms. I am not sure at this point if this is hibernate issue, but if the driver has any opportunity to batch such statements into a single request together with the real SQL that would decrease the response time by 50% on many queries.

Here is one instance:

21:47:49,648 FINE  [com.google.cloud.sql.jdbc.internal.SqlProtoClient] (Threadpool-6) Executing Operation: SET_AUTO_COMMIT

21:47:49,648 FINE  [com.google.cloud.sql.jdbc.internal.googleapi.RpcGoogleApi.DefaultGoogleApi] (Threadpool-6) Sending request to https://www.googleapis.com/sql/v1/jdbc/execOp?alt=proto

21:47:49,649 CONFIG [com.google.api.client.http.HttpTransport] (Threadpool-6) -------------- REQUEST  --------------

POST https://www.googleapis.com/sql/v1/jdbc/execOp?alt=proto

Accept-Encoding: gzip

Authorization: <Not Logged>

User-Agent: Google SQL Service/1.0 Google-HTTP-Java-Client/1.9.0-beta-SNAPSHOT (gzip)

X-Upload-Content-Length: 0

Content-Type: application/x-protobuf

Content-Length: 99

21:47:49,649 CONFIG [com.google.api.client.http.HttpTransport] (Threadpool-6)

^Nprod-ef2f:ef2f^RI^@d^_^M?S???bv???|b'???C??^S~?1???3w,??^P?r?{???^C^\?????6?U?_??8}?????]i^Z^D^H^D(^@@^_

21:47:49,722 CONFIG [com.google.api.client.http.HttpTransport] (Threadpool-6) -------------- RESPONSE --------------

HTTP/1.1 200 OK

X-Frame-Options: SAMEORIGIN

ETag: "_7wYyDbWr4n6mUP0M5ioyTuAIh4/0PoMTV1GP9GOFogpVgbpFNZgA7o"

Date: Fri, 21 Jun 2013 21:47:49 GMT

Transfer-Encoding: chunked

Expires: Fri, 01 Jan 1990 00:00:00 GMT

X-XSS-Protection: 1; mode=block

Content-Type: application/x-protobuf

Server: GSE

Cache-Control: no-cache, no-store, max-age=0, must-revalidate

Pragma: no-cache

X-Content-Type-Options: nosniff

On Saturday, June 22, 2013 12:21:20 AM UTC+3, Sergio Garcia Murillo wrote:

Hi Joe,

Cloud SQL with HA/redundancy is a killer functionality for us, in fact that was the reason for choosing GCE over AWS, so any improvement would be really appreciated.

We were already investigating the connection pooling with somewhat mixed results. The mayor blocker for now is the latency of single queries, even a "SELECT 1" takes 70-80ms to execute.

We were using the SELECT 1 as a validity query, so each request time is doubled. Also we have seen in some situations in which some estrange metadata is been fetched, adding an extra 160ms. So a request where only 3 queries are performed can take up to (3+1)*2*80=640 ms.

Now we are trying to move the validity query to background but we get some errors from time to time. I will be able to provide more information in the following days. Do you have any recommendation on keepalives and any setting that may increase performance?

Best regards
Sergio

El 21/06/2013 19:46, Joe Faith escribió:

Hi Sergio

Sorry to hear about the problems you've been having.

We realize that the latency of the external JDBC connection is quite large (including from GCE), and we are working very hard to improve the connectivity.

We hope to have more news for you real soon, but in the meantime it looks like connection pooling would help

The recommendation against using connection pooling in the FAQ [1] was intended to apply to connections from GAE, where the time to create a new connection is similar to that to test the liveness of an existing one.

We'll clarify it.

J

[1] https://developers.google.com/cloud-sql/faq#connections

On Fri, Jun 21, 2013 at 4:22 AM, Sergio Garcia Murillo <sergio.gar...@gmail.com> wrote:

Hi all

I am trying to connect to my Cloud SQL instance inside a Google compute engine server instance, and we are observing that the setup time for a DB connection is always bigger than 700ms.

Given that not connection pooling is recommend, this makes our REST based app unusable as each request needs to open a new connection to the database and get's the 700ms minimum lag.

Below are the traces of a simple app running on the server instance showing the connection setup phase with the timestamps.

1371812704338 FINE Using cached Access token.

1371812704354 FINE Created client for instance: xxxxx

1371812704359 FINE Executing OpenConnection: null at xxxxx

1371812704377 FINE Sending request to https://www.googleapis.com/sql/v1/jdbc/openConnection?alt=proto

1371812704513 CONFIG -------------- REQUEST  --------------

1371812704516 FINEST ProxySelector Request for https://www.googleapis.com/sql/v1/jdbc/openConnection?alt=proto

1371812704828 FINEST Proxy used: DIRECT

1371812704936 FINEST sun.net.www.MessageHeader@2a9cfec112 pairs: {POST /sql/v1/jdbc/openConnection?alt=proto HTTP/1.1: null}{Accept-Encoding: gzip}{Authorization: Bearer ya29.AHES6ZQrijCM7aJRY5jzsWayAIDp7lwoVFzHbFsVoWr2L2bY9FuYDNs}{User-Agent: Google SQL Service/1.0 Google-HTTP-Java-Client/1.9.0-beta-SNAPSHOT (gzip)}{X-Upload-Content-Length: 0}{Content-Type: application/x-protobuf}{Cache-Control: no-cache}{Pragma: no-cache}{Host: www.googleapis.com}{Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2}{Connection: keep-alive}{Content-Length: 66}

1371812704936 FINEST HttpClient.writeRequests() streaming=true

1371812704938 CONFIG

1371812705039 FINEST sun.net.www.MessageHeader@3e018c7412 pairs: {null: HTTP/1.1 200 OK}{Cache-Control: no-cache, no-store, max-age=0, must-revalidate}{Pragma: no-cache}{Expires: Fri, 01 Jan 1990 00:00:00 GMT}{Date: Fri, 21 Jun 2013 11:05:05 GMT}{ETag: "_7wYyDbWr4n6mUP0M5ioyTuAIh4/78JYOhpfkickmRL0KbO9P7pOgNI"}{Content-Type: application/x-protobuf}{Transfer-Encoding: chunked}{X-Content-Type-Options: nosniff}{X-Frame-Options: SAMEORIGIN}{X-XSS-Protection: 1; mode=block}{Server: GSE}

1371812705041 CONFIG -------------- RESPONSE --------------

1371812705042 CONFIG Response size: 75 bytes

1371812705043 CONFIG

1371812705048 FINEST RPC response: connection_id: "\000d\037\r\370x\331\2428\272t\267P\030\340K[\263P\262c\205\260.Vb\262*}\027\314r\305\341;\310\024\306\\\030\323\324Q\003Tp\355\303\242\352\003!\v3^\203/\030`I*\236\030U=\322>x\027;\302$\211"

1371812705122 FINEST Connection: {instance=xxxxx, database=xxxxx}

Is there any way to enhance the connection setup or enable the connection pooling reliably?

Best regards

Sergio

--
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.
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.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
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.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
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.
For more options, visit https://groups.google.com/groups/opt_out.