March 2013

Sunday, March 31, 2013

Re: Are backups occurring for you? (not for me)

The cloudsqladmin user is expected to not show up in mysql.user. The fact that the backups did not run is indeed a bug. We recently fixed it and the fix will be deployed in prod later this week.

-- Razvan ME

On Sun, Mar 31, 2013 at 11:53 AM, Luca de Alfaro <luca.de.alfaro@gmail.com> wrote:

On my D0 instance, backups are scheduled, but they never occur.
There is no message as to why.
I read that there should be a cloudsqladmin user, which is used to do backups.

Yet, on my D0 instance, and also on a D1 instance I created just for testing this, the command "select * from mysql.user" generates only the following users:

Host User

localhost root
127.0.0.1 root

::1 root
localhost

So I have two questions:

Do backups work for you?

Do you see the cloudsqladmin user listed?

Any suggestion on how to get backups to run would be appreciated.

Luca

--
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.

Desain perubahan warna pada objek

pada file ini menggunakan efek dari Skect yang akan merubah objek akan menjadi skect yang kita ingin kan dan pada warna campuran CMYK yang mempengaruhi objek perubahan warna dari skect menjadi warna putih ,,,. yang kita gunakan sofware photoshop yang mudah merubah objeck yang kita inginkan ..... dan pada kalian harus banyak mencoba sofware yang akan kalian coba seperti photoshop ini..

GAE No connectivity to local dev MySQL instance with data nucleus

I am trying to get a Development Google App Engine app working with JPA, Google Cloud SQL, and a local MySQL database. I am using the GAE eclipse plugin. I have signed up for a Google cloud SQL instance. Configured the app engine settings on the project to use Google Cloud SQL and put in the connectivity info for the local MySQL database and for the cloud SQL instance.

The data nucleus enhancers picks up my 57 classes and I see the log with the classes successfully optimized. I run my application within Eclipse and the dev environment fires up successfully and I can get to my app through the browser. I copied the mysql driver jar file to the lib of the app engine sdk.

The issue is that the data in the database cannot be retrieved through from the JPA calls. I don't see any errors in the application output. I run through the debugger and the JPA calls run successfully without throwing an exception in my app source code. I get an empty list from retrieval. Checked the datanucleus.log file. The only thing I see is the optimization output.

My guess is that there is something failing but the error could be swallowed or maybe a restriction. I also tried changing the JPA calls by using criteria builder and then using straight up JPQL. Still get the same results.

Checked the arguments to the local GAE dev server and I see the arguments that are being used from the configuration that I typed in for the local mysql server. I did some digging around and enabled the mysql general logging and I don't see anything written to the log for queries that should be created from datanucleus. I also do not see a connection when I connect with MySQL workbench and look at the active connections in the administration section. I know the connectivity information that I entered for the google cloud sql local mysql instance is correct, because I went back and changed the port and I got an error when I applied the changes. I changed back to the right port and the changes accepted successfully.

Any help would be appreciated. Not sure where to go from here. I have researched online for quite some time and I am tired and frustrated.

Persistence.xml - (with only 2 classes for testing)

<persistence-unit name="iberis-jpa">      <provider>org.datanucleus.api.jpa.PersistenceProviderImpl</provider>      <class>com.bizznetworxonline.iberis.core.SystemArea</class>      <class>com.bizznetworxonline.iberis.core.SystemUnit</class>        <exclude-unlisted-classes>true</exclude-unlisted-classes>        <properties>          <property name="datanucleus.NontransactionalRead" value="true"/>          <property name="datanucleus.NontransactionalWrite" value="true"/>          <property name="datanucleus.ConnectionURL" value="appengine"/>      </properties>  </persistence-unit>

JPA Call:

public List<?> findAll(Class<?> entityClass)   {        EntityManager em = JPA_EMF.get().createEntityManager();        javax.persistence.Query q = em.createQuery("SELECT o FROM " + entityClass.getSimpleName() + " o",entityClass);        List<?> results = q.getResultList();        return results;  }

Console Output:

Mar 30, 2013 9:49:06 PM com.google.apphosting.utils.config.AppEngineWebXmlReader    readAppEngineWebXml    INFO: Successfully processed /home/user/Documents/eclipse-workspace/IberisAdmin/war/WEB-INF/appengine-web.xml    Mar 30, 2013 9:49:06 PM com.google.apphosting.utils.config.AbstractConfigXmlReader readConfigXml    INFO: Successfully processed /home/user/Documents/eclipse-workspace/IberisAdmin/war/WEB-INF/web.xml    Mar 30, 2013 9:49:06 PM com.google.appengine.tools.development.SystemPropertiesManager setSystemProperties    INFO: Overwriting system property key 'java.util.logging.config.file', value '/home/user/.eclipse/org.eclipse.platform_3.7.0_155965261/plugins/com.google.appengine.eclipse.sdkbundle_1.7.6/appengine-java-sdk-1.7.6/config/sdk/logging.properties' with value 'WEB-INF/logging.properties' from '/home/user/Documents/eclipse-workspace/IberisAdmin/war/WEB-INF/appengine-web.xml'    Mar 30, 2013 9:49:07 PM com.google.apphosting.utils.jetty.JettyLogger info  INFO: Logging to JettyLogger(null) via com.google.apphosting.utils.jetty.JettyLogger    Mar 30, 2013 9:49:07 PM com.google.apphosting.utils.jetty.JettyLogger info  INFO: jetty-6.1.x    Mar 30, 2013 9:49:10 PM com.sun.faces.config.ConfigureListener contextInitialized  INFO: Initializing Mojarra 2.1.12 ( 20120814-1522) for context ''    Mar 30, 2013 9:49:13 PM com.sun.faces.spi.InjectionProviderFactory createInstance  INFO: JSF1048: PostConstruct/PreDestroy annotations present.  ManagedBeans methods marked with these annotations will have said annotations processed.    Mar 30, 2013 9:49:21 PM org.primefaces.webapp.PostConstructApplicationEventListener processEvent  INFO: Running on PrimeFaces 3.5    Mar 30, 2013 9:49:21 PM org.primefaces.extensions.application.PostConstructApplicationEventListener processEvent  INFO: Running on PrimeFaces Extensions 0.6.3    Mar 30, 2013 9:49:22 PM com.google.apphosting.utils.jetty.JettyLogger info  INFO: Started SelectChannelConnector@127.0.0.1:8888    Mar 30, 2013 9:49:22 PM com.google.appengine.tools.development.AbstractServer startup  INFO: Server default is running at http://localhost:8888/    Mar 30, 2013 9:49:22 PM com.google.appengine.tools.development.AbstractServer startup  INFO: The admin console is running at http://localhost:8888/_ah/admin    Mar 30, 2013 9:49:22 PM com.google.appengine.tools.development.DevAppServerImpl start  INFO: Dev App Server is now running    Mar 30, 2013 9:49:35 PM com.google.appengine.api.datastore.dev.LocalDatastoreService init  INFO: Local Datastore initialized:   Type: High Replication  Storage: /home/user/Documents/eclipse-workspace/IberisAdmin/war/WEB-INF/appengine-generated/local_db.bin    Mar 30, 2013 9:49:35 PM com.google.appengine.api.datastore.dev.LocalDatastoreService load  INFO: The backing store, /home/user/Documents/eclipse-workspace/IberisAdmin/war/WEB-   INF/appengine-generated/local_db.bin, does not exist. It will be created.    Mar 30, 2013 9:49:37 PM com.google.apphosting.utils.jetty.JettyLogger warn

Are backups occurring for you? (not for me)

On my D0 instance, backups are scheduled, but they never occur.

There is no message as to why.

I read that there should be a cloudsqladmin user, which is used to do backups.

Yet, on my D0 instance, and also on a D1 instance I created just for testing this, the command "select * from mysql.user" generates only the following users:

Host User

localhost root

127.0.0.1 root

::1 root

localhost

So I have two questions:

Do backups work for you?

Do you see the cloudsqladmin user listed?

Any suggestion on how to get backups to run would be appreciated.

Luca

Re: Enabling Backups for Google Cloud SQL

This is fantastic.

However, my scheduled backups have so far failed to run -- I filed issue https://code.google.com/p/googlecloudsql/issues/detail?id=63

Is this due to the fact that I am using the introductory D0 plan?

Luca

On Friday, February 15, 2013 11:30:22 AM UTC-8, Joe Faith wrote:

Dear Google Cloud SQL User,

We believe that regular backups are vital to ensure the security of your data against accidental errors, and Cloud SQL allows you to schedule backups taken daily. So, as from now, we will be turning on backups by default for new database instances created on the service. The instance remains online while the backup is taken, and 7 days of backups are stored without charge.

From Feb 20 2013, we will also turn on backups for all existing database instances that do not currently have them enabled. Please see https://developers.google.com/cloud-sql/docs/sched_backups for more information about automated backups.

Note that the storage of backups is included in the cost of a Cloud SQL instance. However, the process of backing up your instance will result in you being charged for the time that the instance is active (except in the case of free instances). A backup will be taken only if there have been changes to your data since the last backup. See https://developers.google.com/cloud-sql/docs/billing for more information about charges.

If you would NOT like backups enabled for your instance then please fill out this form by Feb 19 2013:
https://docs.google.com/a/google.com/forms/d/1vrFy9iwFlhr1k92YgoXsY5CD7mlAnxo2cEmMC_aGMV8/viewform

Alternatively you can disable backups from the Google Developers Console at any time
https://code.google.com/apis/console.

Joe Faith
Google Cloud SQL Product Manager

Thursday, March 28, 2013

Re: Issues with prepared statements using driver jar

On Thu, Mar 28, 2013 at 10:39 AM, Diwaker Gupta <diwaker@maginatics.com> wrote:

Thanks, Ken.

To raise a meta point though: why does GC SQL require a custom driver
jar?

We did it because of limitations in GAE and other Google infrastructure at the time.

AWS RDS works out of the box with the MySQL connector/J jar as
well as any MySQL client. Would be best if GC SQL also worked out of
the box with standard MySQL clients. This significant reduces friction
and lowers the barrier to entry. Right now its a bit of a hassle even
to kick the tires on GC SQL because of the custom client, custom jar
requirements.

Agreed. :)

On Thu, Mar 28, 2013 at 10:31 AM, Ken Ashcraft <kash@google.com> wrote:
> On Wed, Mar 27, 2013 at 11:11 AM, Diwaker Gupta <diwaker@maginatics.com>
> wrote:
>>
>> I'm using the instructions from:
>> https://developers.google.com/cloud-sql/docs/external
>>
>> I've already run the cmd line tool so there shouldn't be an authentication
>> issue here. We have an application that runs fine against vanilla MySQL, AWS
>> RDS and other MySQL variants. I'm trying to see if we can run into against
>> Google Cloud SQL. As part of the initialization, we create a database and
>> tables. This process fails against GC SQL with the following error:
>>
>> java.sql.SQLException: This command is not supported in the prepared
>> statement protocol yet
>>
>
> Do you have a mysqldump file? You can upload that and import it.
> https://developers.google.com/cloud-sql/docs/import_export
>
>>
>> Are there known gaps in the SQL Driver for prepared statements? Are these
>> documented anywhere?
>>
> https://code.google.com/p/googlecloudsql/issues/list
>
>>
>> Finally, there are several usability issues with the SQL jar when using in
>> other applications:
>>
>> * It is not available in Maven Central. This will be an issue for almost
>> any production JVM app out there.
>> * It bundles in various dependencies like jackson, apache commons codec
>> etc. Without a proper pom.xml, this results in conflicts when bundling with
>> applications that already use these dependencies. Worse when the conflicts
>> are from multiple versions of the same dependency.
>> * Does not provide a META-INF/services/java.sql.Driver file in the jar.
>> This necessitates old-school explicit registration via
>> DriverManager.registerDriver instead of auto-loading supported by services.
>>
>
> Yes, we are aware that the jar file is difficult to use. We're working hard
> to fix that. Sorry for the difficulty in the meantime.
>
> Ken
>
>

> --
> You received this message because you are subscribed to a topic in the

> Google Groups "Google Cloud SQL discuss" group.

> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/google-cloud-sql-discuss/gQqXoveTqNU/unsubscribe?hl=en.
> To unsubscribe from this group and all its topics, send an email to

> google-cloud-sql-discuss+unsubscribe@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>

--
http://maginatics.com

--
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: Issues with prepared statements using driver jar

Thanks, Ken.

To raise a meta point though: why does GC SQL require a custom driver
jar? AWS RDS works out of the box with the MySQL connector/J jar as
well as any MySQL client. Would be best if GC SQL also worked out of
the box with standard MySQL clients. This significant reduces friction
and lowers the barrier to entry. Right now its a bit of a hassle even
to kick the tires on GC SQL because of the custom client, custom jar
requirements.

On Thu, Mar 28, 2013 at 10:31 AM, Ken Ashcraft <kash@google.com> wrote:
> On Wed, Mar 27, 2013 at 11:11 AM, Diwaker Gupta <diwaker@maginatics.com>
> wrote:
>>
>> I'm using the instructions from:
>> https://developers.google.com/cloud-sql/docs/external
>>
>> I've already run the cmd line tool so there shouldn't be an authentication
>> issue here. We have an application that runs fine against vanilla MySQL, AWS
>> RDS and other MySQL variants. I'm trying to see if we can run into against
>> Google Cloud SQL. As part of the initialization, we create a database and
>> tables. This process fails against GC SQL with the following error:
>>
>> java.sql.SQLException: This command is not supported in the prepared
>> statement protocol yet
>>
>
> Do you have a mysqldump file? You can upload that and import it.
> https://developers.google.com/cloud-sql/docs/import_export
>
>>
>> Are there known gaps in the SQL Driver for prepared statements? Are these
>> documented anywhere?
>>
> https://code.google.com/p/googlecloudsql/issues/list
>
>>
>> Finally, there are several usability issues with the SQL jar when using in
>> other applications:
>>
>> * It is not available in Maven Central. This will be an issue for almost
>> any production JVM app out there.
>> * It bundles in various dependencies like jackson, apache commons codec
>> etc. Without a proper pom.xml, this results in conflicts when bundling with
>> applications that already use these dependencies. Worse when the conflicts
>> are from multiple versions of the same dependency.
>> * Does not provide a META-INF/services/java.sql.Driver file in the jar.
>> This necessitates old-school explicit registration via
>> DriverManager.registerDriver instead of auto-loading supported by services.
>>
>
> Yes, we are aware that the jar file is difficult to use. We're working hard
> to fix that. Sorry for the difficulty in the meantime.
>
> Ken
>
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Google Cloud SQL discuss" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/google-cloud-sql-discuss/gQqXoveTqNU/unsubscribe?hl=en.
> To unsubscribe from this group and all its topics, send an email to
> google-cloud-sql-discuss+unsubscribe@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>

--
http://maginatics.com

--
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: Issues with prepared statements using driver jar

On Wed, Mar 27, 2013 at 11:11 AM, Diwaker Gupta <diwaker@maginatics.com> wrote:

I'm using the instructions from: https://developers.google.com/cloud-sql/docs/external

I've already run the cmd line tool so there shouldn't be an authentication issue here. We have an application that runs fine against vanilla MySQL, AWS RDS and other MySQL variants. I'm trying to see if we can run into against Google Cloud SQL. As part of the initialization, we create a database and tables. This process fails against GC SQL with the following error:

java.sql.SQLException: This command is not supported in the prepared statement protocol yet

Do you have a mysqldump file? You can upload that and import it.

https://developers.google.com/cloud-sql/docs/import_export

Are there known gaps in the SQL Driver for prepared statements? Are these documented anywhere?

https://code.google.com/p/googlecloudsql/issues/list

Finally, there are several usability issues with the SQL jar when using in other applications:

* It is not available in Maven Central. This will be an issue for almost any production JVM app out there.
* It bundles in various dependencies like jackson, apache commons codec etc. Without a proper pom.xml, this results in conflicts when bundling with applications that already use these dependencies. Worse when the conflicts are from multiple versions of the same dependency.

* Does not provide a META-INF/services/java.sql.Driver file in the jar. This necessitates old-school explicit registration via DriverManager.registerDriver instead of auto-loading supported by services.

Yes, we are aware that the jar file is difficult to use. We're working hard to fix that. Sorry for the difficulty in the meantime.

Ken

Wednesday, March 27, 2013

Re: Restarting suspended(!) gloud sql instance

Thanks, Tony! Instances are working now. Everything ok.

Your instances should be working now. Please ping us again if you're still unable to access them.

On Wed, Mar 27, 2013 at 7:59 AM, Fox Mulder <foxso...@gmail.com> wrote:

Yes. Instance still suspended, but billing status is active.

I try restart instance manually via menu, but recieve error "An unexpected error has occurred. We're looking into it."

--
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.

Issues with prepared statements using driver jar

I'm using the instructions from: https://developers.google.com/cloud-sql/docs/external

I've already run the cmd line tool so there shouldn't be an authentication issue here. We have an application that runs fine against vanilla MySQL, AWS RDS and other MySQL variants. I'm trying to see if we can run into against Google Cloud SQL. As part of the initialization, we create a database and tables. This process fails against GC SQL with the following error:

java.sql.SQLException: This command is not supported in the prepared statement protocol yet

Are there known gaps in the SQL Driver for prepared statements? Are these documented anywhere?

Finally, there are several usability issues with the SQL jar when using in other applications:

* It is not available in Maven Central. This will be an issue for almost any production JVM app out there.

* It bundles in various dependencies like jackson, apache commons codec etc. Without a proper pom.xml, this results in conflicts when bundling with applications that already use these dependencies. Worse when the conflicts are from multiple versions of the same dependency.

* Does not provide a META-INF/services/java.sql.Driver file in the jar. This necessitates old-school explicit registration via DriverManager.registerDriver instead of auto-loading supported by services.

Thanks,

Diwaker

Re: Restarting suspended(!) gloud sql instance

Your instances should be working now. Please ping us again if you're still unable to access them.

On Wed, Mar 27, 2013 at 7:59 AM, Fox Mulder <foxsoft2005@gmail.com> wrote:

Yes. Instance still suspended, but billing status is active.

I try restart instance manually via menu, but recieve error "An unexpected error has occurred. We're looking into it."

--
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: Restarting suspended(!) gloud sql instance

Can you tell us the instance name? Feel free to use the sql-team@google.com if you want to keep the name of the instance private.

-- Razvan ME

On Wed, Mar 27, 2013 at 7:59 AM, Fox Mulder <foxsoft2005@gmail.com> wrote:

Yes. Instance still suspended, but billing status is active.

I try restart instance manually via menu, but recieve error "An unexpected error has occurred. We're looking into it."

--
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: Restarting suspended(!) gloud sql instance

Yes. Instance still suspended, but billing status is active.

I try restart instance manually via menu, but recieve error "An unexpected error has occurred. We're looking into it."

Re: Restarting suspended(!) gloud sql instance

Hello,

If the instance is suspended due to billing issues, it should be automatically resumed once the billing status is active. Is your instance still suspended?

On Wed, Mar 27, 2013 at 1:36 AM, Fox Mulder <foxsoft2005@gmail.com> wrote:

Hi all!

I need to restart suspended instance. Billing is active now. No charges. Everything seems OK.

Is it 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.

Restarting suspended(!) gloud sql instance

Hi all!

I need to restart suspended instance. Billing is active now. No charges. Everything seems OK.

Is it possible?

Thanks.

Tuesday, March 26, 2013

Re: Google Cloud SQL: 10 GB max vs TB for alternatives

It's actually 100G of max storage.

See https://developers.google.com/cloud-sql/

Rob

On Tue, Mar 26, 2013 at 4:24 PM, Luca de Alfaro <luca.de.alfaro@gmail.com> wrote:

Google Clould SQL has a 10 GB maximum size.
Alternatives from Heroku to EC2 are in the order of TB, or 100x more.
Is there hope / plans for Google Cloud SQL allowing scaling to the TB sizes?

Luca

--
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: Google Cloud SQL: 10 GB max vs TB for alternatives

My mistake in reading the plans: the max size is 100 GB. This is a 10x, not a 100x, size difference.

Still there, but not as large.

Luca

On Tuesday, March 26, 2013 4:24:32 PM UTC-7, Luca de Alfaro wrote:

Google Clould SQL has a 10 GB maximum size.
Alternatives from Heroku to EC2 are in the order of TB, or 100x more.
Is there hope / plans for Google Cloud SQL allowing scaling to the TB sizes?

Luca

Google Cloud SQL: 10 GB max vs TB for alternatives

Google Clould SQL has a 10 GB maximum size.

Alternatives from Heroku to EC2 are in the order of TB, or 100x more.

Is there hope / plans for Google Cloud SQL allowing scaling to the TB sizes?

Luca

Re: Can one resize a DB once created?

Yes, you can change the tier to a larger tier after you create the instance. It will restart the database with the new settings after you apply the change.

Rob

On Tue, Mar 26, 2013 at 4:10 PM, Luca de Alfaro <luca.de.alfaro@gmail.com> wrote:

If I create a DB using one of the various plans (D0, D1, D2, ...), and my needs grow, can I then resize the DB to a bigger size (assumed I switch the billing)? What is the upgrade path otherwise? Any advice?

Luca

--
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: Can one resize a DB once created?

You can change the tier at any time. This will restart your instance, which will take a few seconds. Note that all the paid tiers can store up to 100GB.

On Mar 26, 2013 6:10 PM, "Luca de Alfaro" <luca.de.alfaro@gmail.com> wrote:

If I create a DB using one of the various plans (D0, D1, D2, ...), and my needs grow, can I then resize the DB to a bigger size (assumed I switch the billing)? What is the upgrade path otherwise? Any advice?

Luca

--
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.

Can one resize a DB once created?

If I create a DB using one of the various plans (D0, D1, D2, ...), and my needs grow, can I then resize the DB to a bigger size (assumed I switch the billing)? What is the upgrade path otherwise? Any advice?

Luca

Re: Loading mysql JDBC jar file -

I found some other posts about this issue;

http://stackoverflow.com/questions/8952696/java-google-app-engine-and-google-cloud-sql-running-on-local-dev-server

Isn't this issue still fixed?

Op donderdag 1 maart 2012 00:30:26 UTC+1 schreef Brian Duff het volgende:

Are you following the instructions in the documentation?

https://developers.google.com/cloud-sql/docs/developers_guide_java#using_the_java_development_server

Brian

On Tue, Feb 28, 2012 at 7:22 PM, shiv <shiv...@gmail.com> wrote:
I'm running my app locally, to test out connection to my new CloudSQL
Instance.

I'm loading the JDBC Driver in my code:
DriverManager.registerDriver(new AppEngineDriver());
Connection c = DriverManager
.getConnection("jdbc:google:rdbms://<projectName>:<InstanceName>/
<DBName>");

On executing locally, I get this error:

java.lang.ClassNotFoundException: com.mysql.jdbc.Driver
Caused by:
java.lang.IllegalStateException: java.lang.ClassNotFoundException:
com.mysql.jdbc.Driver

On forums, I read this:
"Google App Engine doesn't allow you to open Sockets. When you try to
load the JDBC driver, it makes a socket connection in a static block.
An exception in the static block leads to a ClassNotFoundException,
which is what you are seeing..."

Mysql-connector-java-5.1.18-bin.jar is in my Eclipse Build path.

What is the workaround to the Sockets issue in GAE?

In this appengine how-to section for cloudSQL, I don't find any
special reference to taking care of this situation:
https://developers.google.com/cloud-sql/docs/developers_guide_java#register_the_driver

Any pointers greatly appreciated!

Thanks,
-Shiv

Saturday, March 23, 2013

Re: How to connect to existing google cloud SQL database with external android app

Also it seems the new SDK 1.7.6 update has modified something. I now get a security exception try to connect to ....https://...appspot.com/_ah/api/ . I changed the 1.myapp to -1-myapp as per the documentations, but now I get a 404 error.

On Saturday, March 23, 2013 12:24:47 AM UTC-5, Jeremy Tzou wrote:

Thanks for the reply. Yes, I have done that. My main issue is that the entity classes read and write from the datastore. How do I get them to read and write from the google sql database?

On Thursday, March 21, 2013 6:54:43 PM UTC-5, Jeremy Tzou wrote:
So i've been trying for hours to figure out how to do this. Turns out after research that I need a GAE app to communicate with the database for the application because you can't connect to the sql db on android. So what I did was generate an android endpoints backend for an existing application. https://developers.google.com/eclipse/docs/endpoints-create-fromandroid

Now here is the problem. I am stuck. The app engine is supposed to be able to execute commands to send to the google sql db. But how do you do that? How do I set it so my GAE backend can connect to an existing google cloud sql server? I simply cannot find a tutorial that explains this.

I did find this https://developers.google.com/appengine/docs/java/cloud-sql/developers-guide, but that is not for android nor is it for an application with a GAE backend.

I could use some guidance.

Thanks

Friday, March 22, 2013

Re: How to connect to existing google cloud SQL database with external android app

Thanks for the reply. Yes, I have done that. My main issue is that the entity classes read and write from the datastore. How do I get them to read and write from the google sql database?

On Thursday, March 21, 2013 6:54:43 PM UTC-5, Jeremy Tzou wrote:

So i've been trying for hours to figure out how to do this. Turns out after research that I need a GAE app to communicate with the database for the application because you can't connect to the sql db on android. So what I did was generate an android endpoints backend for an existing application. https://developers.google.com/eclipse/docs/endpoints-create-fromandroid

Now here is the problem. I am stuck. The app engine is supposed to be able to execute commands to send to the google sql db. But how do you do that? How do I set it so my GAE backend can connect to an existing google cloud sql server? I simply cannot find a tutorial that explains this.

I did find this https://developers.google.com/appengine/docs/java/cloud-sql/developers-guide, but that is not for android nor is it for an application with a GAE backend.

I could use some guidance.

Thanks

Re: How to connect to existing google cloud SQL database with external android app

Jeremy,

Have you done these steps? You must permit GAE application to use this CloudSQL instance.

https://developers.google.com/cloud-sql/docs/access_control#appaccess

Em quinta-feira, 21 de março de 2013 20h54min43s UTC-3, Jeremy Tzou escreveu:

So i've been trying for hours to figure out how to do this. Turns out after research that I need a GAE app to communicate with the database for the application because you can't connect to the sql db on android. So what I did was generate an android endpoints backend for an existing application. https://developers.google.com/eclipse/docs/endpoints-create-fromandroid

Now here is the problem. I am stuck. The app engine is supposed to be able to execute commands to send to the google sql db. But how do you do that? How do I set it so my GAE backend can connect to an existing google cloud sql server? I simply cannot find a tutorial that explains this.

I did find this https://developers.google.com/appengine/docs/java/cloud-sql/developers-guide, but that is not for android nor is it for an application with a GAE backend.

I could use some guidance.

Thanks

Thursday, March 21, 2013

How to connect to existing google cloud SQL database with external android app

So i've been trying for hours to figure out how to do this. Turns out after research that I need a GAE app to communicate with the database for the application because you can't connect to the sql db on android. So what I did was generate an android endpoints backend for an existing application. https://developers.google.com/eclipse/docs/endpoints-create-fromandroid

Now here is the problem. I am stuck. The app engine is supposed to be able to execute commands to send to the google sql db. But how do you do that? How do I set it so my GAE backend can connect to an existing google cloud sql server? I simply cannot find a tutorial that explains this.

I did find this https://developers.google.com/appengine/docs/java/cloud-sql/developers-guide, but that is not for android nor is it for an application with a GAE backend.

I could use some guidance.

Thanks

Re: Issues making JDO work with MySQL

Hi Abhishek,

I think that I have got the same issue than Shweta:

I am moving my app from JDBC to JDO and made it work with the following configuration in the jdoconfig.xml file:

Configuration OK (Google CloudSql):

<persistence-manager-factory name="googleCloudSql">
<property name="javax.jdo.PersistenceManagerFactoryClass"
value="org.datanucleus.api.jdo.JDOPersistenceManagerFactory"/>
<property name="javax.jdo.option.ConnectionDriverName" value="com.google.appengine.api.rdbms.AppEngineDriver"/>
<property name="javax.jdo.option.ConnectionURL" value="jdbc:google:rdbms:myappdb:myapp"/>
<property name="javax.jdo.option.NontransactionalRead" value="true"/>
<property name="javax.jdo.option.NontransactionalWrite" value="true"/>
<property name="javax.jdo.option.RetainValues" value="true"/>
<property name="datanucleus.identifier.case" value="PreserveCase"/>
<property name="datanucleus.metadata.validate" value="false"/>
<property name="datanucleus.autoCreateSchema" value="true"/>
<property name="datanucleus.validateTables" value="false"/>
<property name="datanucleus.validateConstraints" value="false"/>
<property name="datanucleus.appengine.autoCreateDatastoreTxns" value="true"/>
</persistence-manager-factory>

But when I try to connect to my local MySql with the following configuration in the jdoconfig.xml file, it raise the following exception:

Configuration KO (local MySql):

<persistence-manager-factory name="localMySql">
<property name="javax.jdo.PersistenceManagerFactoryClass"
value="org.datanucleus.api.jdo.JDOPersistenceManagerFactory"/>
<property name="javax.jdo.option.ConnectionDriverName" value="com.mysql.jdbc.Driver"/>
<property name="javax.jdo.option.ConnectionURL" value="jdbc:mysql://localhost:3306/myapp"/>
<property name="javax.jdo.option.ConnectionUserName" value="root"/>
<property name="javax.jdo.option.ConnectionPassword" value="password"/>
<property name="javax.jdo.option.NontransactionalRead" value="true"/>
<property name="javax.jdo.option.NontransactionalWrite" value="true"/>
<property name="javax.jdo.option.RetainValues" value="true"/>
<property name="datanucleus.autoCreateSchema" value="true"/>
<property name="datanucleus.validateColumns" value="false"/>
<property name="datanucleus.appengine.autoCreateDatastoreTxns" value="true"/>
</persistence-manager-factory>

Libraries in ...\war\WEB-INF\lib:

(file name) (size) (date) (time)
appengine-api.jar 31.693.808 05/02/2013 12:18
appengine-api-1.0-sdk-1.7.5.jar 31.693.808 21/02/2013 18:36
appengine-api-labs.jar 4.927.863 21/02/2013 18:36
appengine-endpoints.jar 5.654.176 21/02/2013 18:36
appengine-jsr107cache-1.7.5.jar 6.962 21/02/2013 18:36
appengine-local-runtime-shared.jar 607.295 13/02/2013 14:42
appengine-tools-api.jar 17.164.175 13/02/2013 14:41
asm-4.0.jar 46.022 21/02/2013 18:36
datanucleus-api-jdo-3.1.3.jar 317.326 21/02/2013 18:36
datanucleus-api-jpa-3.1.3.jar 254.559 21/02/2013 18:36
datanucleus-appengine-2.1.2.jar 343.590 21/02/2013 18:36
datanucleus-core-3.1.3.jar 1.730.830 21/02/2013 18:36
datanucleus-rdbms-3.1.3.jar 1.541.907 23/02/2013 11:51
geronimo-jpa_2.0_spec-1.0.jar 114.863 21/02/2013 18:36
jdo-api-3.0.1.jar 201.124 21/02/2013 18:36
jsr107cache-1.1.jar 8.082 21/02/2013 18:36
jta-1.1.jar 15.071 21/02/2013 18:36
mysql-connector-java-5.1.22-bin.jar 832.960 06/09/2012 2:21
simple-xml-2.6.4.jar 389.439 25/11/2012 18:30

I am using Eclipse Juno Service Release 2 with GAE SDK v1.7.5

Exception:

mar 04, 2013 3:56:39 PM com.google.apphosting.utils.jetty.JettyLogger warn
WARNING: Error for /myapp
java.lang.ExceptionInInitializerError
at com.emunde.myapp.dao.mysql.MySqlLocalesDAO.getRegions(MySqlLocalesDAO.java:80)
at com.emunde.myapp.dao.mysql.MySqlLocalesDAO.get(MySqlLocalesDAO.java:35)
at com.emunde.myapp.MyApp.getLocales(MyApp.java:111)
at com.emunde.myapp.MyAppAdapter.getLocales(MyAppAdapter.java:49)
at com.emunde.myapp.MyAppSOAPHandler.handleGetLocalesRequest(MyAppSOAPHandler.java:107)
at com.emunde.myapp.MyAppSOAPHandler.handleSOAPRequest(MyAppSOAPHandler.java:61)
at com.emunde.myapp.MyAppServlet.doPost(MyAppServlet.java:46)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511)
at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1166)
at com.google.appengine.api.socket.dev.DevSocketFilter.doFilter(DevSocketFilter.java:74)
at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
at com.google.appengine.tools.development.ResponseRewriterFilter.doFilter(ResponseRewriterFilter.java:123)
at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
at com.google.appengine.tools.development.HeaderVerificationFilter.doFilter(HeaderVerificationFilter.java:34)
at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
at com.google.appengine.api.blobstore.dev.ServeBlobFilter.doFilter(ServeBlobFilter.java:61)
at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
at com.google.apphosting.utils.servlet.TransactionCleanupFilter.doFilter(TransactionCleanupFilter.java:43)
at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
at com.google.appengine.tools.development.StaticFileFilter.doFilter(StaticFileFilter.java:125)
at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
at com.google.appengine.tools.development.BackendServersFilter.doFilter(BackendServersFilter.java:97)
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 com.google.appengine.tools.development.DevAppEngineWebAppContext.handle(DevAppEngineWebAppContext.java:94)
at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
at com.google.appengine.tools.development.JettyContainerService$ApiProxyHandler.handle(JettyContainerService.java:409)
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.content(HttpConnection.java:938)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:755)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:218)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409)
at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)
Caused by: javax.jdo.JDOFatalInternalException: Error creating transactional connection factory
NestedThrowables:
java.lang.reflect.InvocationTargetException
at org.datanucleus.api.jdo.NucleusJDOHelper.getJDOExceptionForNucleusException(NucleusJDOHelper.java:557)
at org.datanucleus.api.jdo.JDOPersistenceManagerFactory.freezeConfiguration(JDOPersistenceManagerFactory.java:673)
at org.datanucleus.api.jdo.JDOPersistenceManagerFactory.createPersistenceManagerFactory(JDOPersistenceManagerFactory.java:326)
at org.datanucleus.api.jdo.JDOPersistenceManagerFactory.getPersistenceManagerFactory(JDOPersistenceManagerFactory.java:195)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.google.appengine.tools.development.agent.runtime.Runtime.invoke(Runtime.java:115)
at javax.jdo.JDOHelper$16.run(JDOHelper.java:1965)
at java.security.AccessController.doPrivileged(Native Method)
at javax.jdo.JDOHelper.invoke(JDOHelper.java:1960)
at javax.jdo.JDOHelper.invokeGetPersistenceManagerFactoryOnImplementation(JDOHelper.java:1166)
at javax.jdo.JDOHelper.getPersistenceManagerFactory(JDOHelper.java:808)
at javax.jdo.JDOHelper.getPersistenceManagerFactory(JDOHelper.java:1093)
at javax.jdo.JDOHelper.getPersistenceManagerFactory(JDOHelper.java:919)
at com.emunde.myapp.dao.PMF.<clinit>(PMF.java:8)
... 42 more
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
at java.lang.reflect.Constructor.newInstance(Unknown Source)
at com.google.appengine.tools.development.agent.runtime.Runtime.newInstance_(Runtime.java:127)
at com.google.appengine.tools.development.agent.runtime.Runtime.newInstance(Runtime.java:135)
at org.datanucleus.plugin.NonManagedPluginRegistry.createExecutableExtension(NonManagedPluginRegistry.java:681)
at org.datanucleus.plugin.PluginManager.createExecutableExtension(PluginManager.java:325)
at org.datanucleus.store.AbstractStoreManager.registerConnectionFactory(AbstractStoreManager.java:287)
at org.datanucleus.store.AbstractStoreManager.<init>(AbstractStoreManager.java:251)
at org.datanucleus.store.mapped.MappedStoreManager.<init>(MappedStoreManager.java:133)
at org.datanucleus.store.rdbms.RDBMSStoreManager.<init>(RDBMSStoreManager.java:239)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
at java.lang.reflect.Constructor.newInstance(Unknown Source)
at com.google.appengine.tools.development.agent.runtime.Runtime.newInstance_(Runtime.java:127)
at com.google.appengine.tools.development.agent.runtime.Runtime.newInstance(Runtime.java:135)
at org.datanucleus.plugin.NonManagedPluginRegistry.createExecutableExtension(NonManagedPluginRegistry.java:681)
at org.datanucleus.plugin.PluginManager.createExecutableExtension(PluginManager.java:301)
at org.datanucleus.NucleusContext.createStoreManagerForProperties(NucleusContext.java:476)
at org.datanucleus.NucleusContext.initialise(NucleusContext.java:288)
at org.datanucleus.api.jdo.JDOPersistenceManagerFactory.freezeConfiguration(JDOPersistenceManagerFactory.java:660)
... 57 more
Caused by: java.lang.ExceptionInInitializerError
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
at java.lang.reflect.Constructor.newInstance(Unknown Source)
at com.google.appengine.tools.development.agent.runtime.Runtime.newInstance_(Runtime.java:127)
at com.google.appengine.tools.development.agent.runtime.Runtime.newInstance(Runtime.java:148)
at org.datanucleus.store.rdbms.datasource.AbstractDataSourceFactory.loadDriver(AbstractDataSourceFactory.java:46)
at org.datanucleus.store.rdbms.datasource.DBCPBuiltinDataSourceFactory.makePooledDataSource(DBCPBuiltinDataSourceFactory.java:53)
at org.datanucleus.store.rdbms.ConnectionFactoryImpl.initialiseDataSources(ConnectionFactoryImpl.java:182)
at org.datanucleus.store.rdbms.ConnectionFactoryImpl.<init>(ConnectionFactoryImpl.java:95)
... 80 more
Caused by: java.security.AccessControlException: access denied ("java.lang.RuntimePermission" "modifyThreadGroup")
at java.security.AccessControlContext.checkPermission(Unknown Source)
at java.security.AccessController.checkPermission(Unknown Source)
at java.lang.SecurityManager.checkPermission(Unknown Source)
at com.google.appengine.tools.development.DevAppServerFactory$CustomSecurityManager.checkPermission(DevAppServerFactory.java:289)
at com.google.appengine.tools.development.DevAppServerFactory$CustomSecurityManager.checkAccess(DevAppServerFactory.java:314)
at java.lang.ThreadGroup.checkAccess(Unknown Source)
at java.lang.Thread.init(Unknown Source)
at java.lang.Thread.<init>(Unknown Source)
at com.mysql.jdbc.NonRegisteringDriver$1.<init>(NonRegisteringDriver.java:90)
at com.mysql.jdbc.NonRegisteringDriver.<clinit>(NonRegisteringDriver.java:89)
... 90 more

mar 04, 2013 3:56:39 PM com.google.apphosting.utils.jetty.JettyLogger warn
WARNING: Nested in java.lang.ExceptionInInitializerError:
javax.jdo.JDOFatalInternalException: Error creating transactional connection factory
at org.datanucleus.api.jdo.NucleusJDOHelper.getJDOExceptionForNucleusException(NucleusJDOHelper.java:557)
at org.datanucleus.api.jdo.JDOPersistenceManagerFactory.freezeConfiguration(JDOPersistenceManagerFactory.java:673)
at org.datanucleus.api.jdo.JDOPersistenceManagerFactory.createPersistenceManagerFactory(JDOPersistenceManagerFactory.java:326)
at org.datanucleus.api.jdo.JDOPersistenceManagerFactory.getPersistenceManagerFactory(JDOPersistenceManagerFactory.java:195)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.google.appengine.tools.development.agent.runtime.Runtime.invoke(Runtime.java:115)
at javax.jdo.JDOHelper$16.run(JDOHelper.java:1965)
at java.security.AccessController.doPrivileged(Native Method)
at javax.jdo.JDOHelper.invoke(JDOHelper.java:1960)
at javax.jdo.JDOHelper.invokeGetPersistenceManagerFactoryOnImplementation(JDOHelper.java:1166)
at javax.jdo.JDOHelper.getPersistenceManagerFactory(JDOHelper.java:808)
at javax.jdo.JDOHelper.getPersistenceManagerFactory(JDOHelper.java:1093)
at javax.jdo.JDOHelper.getPersistenceManagerFactory(JDOHelper.java:919)
at com.emunde.myapp.dao.PMF.<clinit>(PMF.java:8)
at com.emunde.myapp.dao.mysql.MySqlLocalesDAO.getRegions(MySqlLocalesDAO.java:80)
at com.emunde.myapp.dao.mysql.MySqlLocalesDAO.get(MySqlLocalesDAO.java:35)
at com.emunde.myapp.MyApp.getLocales(MyApp.java:111)
at com.emunde.myapp.MyAppAdapter.getLocales(MyAppAdapter.java:49)
at com.emunde.myapp.MyAppSOAPHandler.handleGetLocalesRequest(MyAppSOAPHandler.java:107)
at com.emunde.myapp.MyAppSOAPHandler.handleSOAPRequest(MyAppSOAPHandler.java:61)
at com.emunde.myapp.MyAppServlet.doPost(MyAppServlet.java:46)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511)
at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1166)
at com.google.appengine.api.socket.dev.DevSocketFilter.doFilter(DevSocketFilter.java:74)
at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
at com.google.appengine.tools.development.ResponseRewriterFilter.doFilter(ResponseRewriterFilter.java:123)
at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
at com.google.appengine.tools.development.HeaderVerificationFilter.doFilter(HeaderVerificationFilter.java:34)
at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
at com.google.appengine.api.blobstore.dev.ServeBlobFilter.doFilter(ServeBlobFilter.java:61)
at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
at com.google.apphosting.utils.servlet.TransactionCleanupFilter.doFilter(TransactionCleanupFilter.java:43)
at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
at com.google.appengine.tools.development.StaticFileFilter.doFilter(StaticFileFilter.java:125)
at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
at com.google.appengine.tools.development.BackendServersFilter.doFilter(BackendServersFilter.java:97)
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 com.google.appengine.tools.development.DevAppEngineWebAppContext.handle(DevAppEngineWebAppContext.java:94)
at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
at com.google.appengine.tools.development.JettyContainerService$ApiProxyHandler.handle(JettyContainerService.java:409)
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.content(HttpConnection.java:938)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:755)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:218)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409)
at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)
NestedThrowablesStackTrace:
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
at java.lang.reflect.Constructor.newInstance(Unknown Source)
at com.google.appengine.tools.development.agent.runtime.Runtime.newInstance_(Runtime.java:127)
at com.google.appengine.tools.development.agent.runtime.Runtime.newInstance(Runtime.java:135)
at org.datanucleus.plugin.NonManagedPluginRegistry.createExecutableExtension(NonManagedPluginRegistry.java:681)
at org.datanucleus.plugin.PluginManager.createExecutableExtension(PluginManager.java:325)
at org.datanucleus.store.AbstractStoreManager.registerConnectionFactory(AbstractStoreManager.java:287)
at org.datanucleus.store.AbstractStoreManager.<init>(AbstractStoreManager.java:251)
at org.datanucleus.store.mapped.MappedStoreManager.<init>(MappedStoreManager.java:133)
at org.datanucleus.store.rdbms.RDBMSStoreManager.<init>(RDBMSStoreManager.java:239)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
at java.lang.reflect.Constructor.newInstance(Unknown Source)
at com.google.appengine.tools.development.agent.runtime.Runtime.newInstance_(Runtime.java:127)
at com.google.appengine.tools.development.agent.runtime.Runtime.newInstance(Runtime.java:135)
at org.datanucleus.plugin.NonManagedPluginRegistry.createExecutableExtension(NonManagedPluginRegistry.java:681)
at org.datanucleus.plugin.PluginManager.createExecutableExtension(PluginManager.java:301)
at org.datanucleus.NucleusContext.createStoreManagerForProperties(NucleusContext.java:476)
at org.datanucleus.NucleusContext.initialise(NucleusContext.java:288)
at org.datanucleus.api.jdo.JDOPersistenceManagerFactory.freezeConfiguration(JDOPersistenceManagerFactory.java:660)
at org.datanucleus.api.jdo.JDOPersistenceManagerFactory.createPersistenceManagerFactory(JDOPersistenceManagerFactory.java:326)
at org.datanucleus.api.jdo.JDOPersistenceManagerFactory.getPersistenceManagerFactory(JDOPersistenceManagerFactory.java:195)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.google.appengine.tools.development.agent.runtime.Runtime.invoke(Runtime.java:115)
at javax.jdo.JDOHelper$16.run(JDOHelper.java:1965)
at java.security.AccessController.doPrivileged(Native Method)
at javax.jdo.JDOHelper.invoke(JDOHelper.java:1960)
at javax.jdo.JDOHelper.invokeGetPersistenceManagerFactoryOnImplementation(JDOHelper.java:1166)
at javax.jdo.JDOHelper.getPersistenceManagerFactory(JDOHelper.java:808)
at javax.jdo.JDOHelper.getPersistenceManagerFactory(JDOHelper.java:1093)
at javax.jdo.JDOHelper.getPersistenceManagerFactory(JDOHelper.java:919)
at com.emunde.myapp.dao.PMF.<clinit>(PMF.java:8)
at com.emunde.myapp.dao.mysql.MySqlLocalesDAO.getRegions(MySqlLocalesDAO.java:80)
at com.emunde.myapp.dao.mysql.MySqlLocalesDAO.get(MySqlLocalesDAO.java:35)
at com.emunde.myapp.MyApp.getLocales(MyApp.java:111)
at com.emunde.myapp.MyAppAdapter.getLocales(MyAppAdapter.java:49)
at com.emunde.myapp.MyAppSOAPHandler.handleGetLocalesRequest(MyAppSOAPHandler.java:107)
at com.emunde.myapp.MyAppSOAPHandler.handleSOAPRequest(MyAppSOAPHandler.java:61)
at com.emunde.myapp.MyAppServlet.doPost(MyAppServlet.java:46)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511)
at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1166)
at com.google.appengine.api.socket.dev.DevSocketFilter.doFilter(DevSocketFilter.java:74)
at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
at com.google.appengine.tools.development.ResponseRewriterFilter.doFilter(ResponseRewriterFilter.java:123)
at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
at com.google.appengine.tools.development.HeaderVerificationFilter.doFilter(HeaderVerificationFilter.java:34)
at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
at com.google.appengine.api.blobstore.dev.ServeBlobFilter.doFilter(ServeBlobFilter.java:61)
at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
at com.google.apphosting.utils.servlet.TransactionCleanupFilter.doFilter(TransactionCleanupFilter.java:43)
at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
at com.google.appengine.tools.development.StaticFileFilter.doFilter(StaticFileFilter.java:125)
at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
at com.google.appengine.tools.development.BackendServersFilter.doFilter(BackendServersFilter.java:97)
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 com.google.appengine.tools.development.DevAppEngineWebAppContext.handle(DevAppEngineWebAppContext.java:94)
at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
at com.google.appengine.tools.development.JettyContainerService$ApiProxyHandler.handle(JettyContainerService.java:409)
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.content(HttpConnection.java:938)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:755)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:218)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409)
at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)
Caused by: java.lang.ExceptionInInitializerError
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
at java.lang.reflect.Constructor.newInstance(Unknown Source)
at com.google.appengine.tools.development.agent.runtime.Runtime.newInstance_(Runtime.java:127)
at com.google.appengine.tools.development.agent.runtime.Runtime.newInstance(Runtime.java:148)
at org.datanucleus.store.rdbms.datasource.AbstractDataSourceFactory.loadDriver(AbstractDataSourceFactory.java:46)
at org.datanucleus.store.rdbms.datasource.DBCPBuiltinDataSourceFactory.makePooledDataSource(DBCPBuiltinDataSourceFactory.java:53)
at org.datanucleus.store.rdbms.ConnectionFactoryImpl.initialiseDataSources(ConnectionFactoryImpl.java:182)
at org.datanucleus.store.rdbms.ConnectionFactoryImpl.<init>(ConnectionFactoryImpl.java:95)
... 80 more
Caused by: java.security.AccessControlException: access denied ("java.lang.RuntimePermission" "modifyThreadGroup")
at java.security.AccessControlContext.checkPermission(Unknown Source)
at java.security.AccessController.checkPermission(Unknown Source)
at java.lang.SecurityManager.checkPermission(Unknown Source)
at com.google.appengine.tools.development.DevAppServerFactory$CustomSecurityManager.checkPermission(DevAppServerFactory.java:289)
at com.google.appengine.tools.development.DevAppServerFactory$CustomSecurityManager.checkAccess(DevAppServerFactory.java:314)
at java.lang.ThreadGroup.checkAccess(Unknown Source)
at java.lang.Thread.init(Unknown Source)
at java.lang.Thread.<init>(Unknown Source)
at com.mysql.jdbc.NonRegisteringDriver$1.<init>(NonRegisteringDriver.java:90)
at com.mysql.jdbc.NonRegisteringDriver.<clinit>(NonRegisteringDriver.java:89)
... 90 more

On Thursday, 19 January 2012 08:29:37 UTC, Abhishek Mathur wrote:

Hi,

The Socket class is a restricted class in appengine, thats why you are getting this error.
The classes that are allowed in appengine are listed in this white list:
http://code.google.com/appengine/docs/java/jrewhitelist.html

How are you making connection to the cloud sql database?

---Abhishek

On Tue, Jan 17, 2012 at 4:12 PM, Shw Jain <sjai...@gmail.com> wrote:

Hi,

I am trying to migrate a very simple JDO application on appengine
using google sql. I am having issues making Google SQL work with JDO.
When I tried with datanucleus-rdbms-1.1.5.jar & datanucleus-
rdbms-3.0.5.jar, but I get the error message:

Jan 17, 2012 2:35:20 PM org.datanucleus.store.rdbms.RDBMSManager
<init>
SEVERE: Failed initialising database.
java.lang.NoClassDefFoundError: java.net.Socket is a restricted class.
Please see the Google App Engine developer's guide for more details.
org.datanucleus.exceptions.NucleusDataStoreException:
java.lang.NoClassDefFoundError: java.net.Socket is a restricted class.
Please see the Google App Engine developer's guide for more details.
at org.datanucleus.store.rdbms.ConnectionFactoryImpl
$ManagedConnectionImpl.getConnection(ConnectionFactoryImpl.java:554)
at org.datanucleus.store.rdbms.RDBMSManager.<init>(RDBMSManager.java:
297)
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.google.appengine.tools.development.agent.runtime.Runtime.newInstance_(Runtime.java:
116)
at
com.google.appengine.tools.development.agent.runtime.Runtime.newInstance(Runtime.java:
124)
at
org.datanucleus.plugin.NonManagedPluginRegistry.createExecutableExtension(NonManagedPluginRegistry.java:
572)
at
org.datanucleus.plugin.PluginManager.createExecutableExtension(PluginManager.java:
300)
at
org.datanucleus.store.FederationManager.initialiseStoreManager(FederationManager.java:
168)
at
org.datanucleus.store.FederationManager.<init>(FederationManager.java:
70)
at
org.datanucleus.ObjectManagerFactoryImpl.initialiseStoreManager(ObjectManagerFactoryImpl.java:
153)
at
org.datanucleus.jdo.JDOPersistenceManagerFactory.freezeConfiguration(JDOPersistenceManagerFactory.java:
526)
at
org.datanucleus.store.appengine.jdo.DatastoreJDOPersistenceManagerFactory.getPersistenceManagerFactory(DatastoreJDOPersistenceManagerFactory.java:
127)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:
39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:
25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
com.google.appengine.tools.development.agent.runtime.Runtime.invoke(Runtime.java:
104)
at javax.jdo.JDOHelper$16.run(JDOHelper.java:1956)
at java.security.AccessController.doPrivileged(Native Method)
at javax.jdo.JDOHelper.invoke(JDOHelper.java:1951)
at
javax.jdo.JDOHelper.invokeGetPersistenceManagerFactoryOnImplementation(JDOHelper.java:
1159)
at javax.jdo.JDOHelper.getPersistenceManagerFactory(JDOHelper.java:
803)
at javax.jdo.JDOHelper.getPersistenceManagerFactory(JDOHelper.java:
1086)
at javax.jdo.JDOHelper.getPersistenceManagerFactory(JDOHelper.java:
914)
at dao1.PMF.getPersistenceManagerFactory(PMF.java:35)
at dao1.BaseDAO.saveOrUpdate(BaseDAO.java:38)

or Bundle "org.datanucleus.store.rdbms" requires "org.datanucleus"
version "3.0.5" but the resolved bundle has version "3.0.5" which is
outside the expected range while using rdbms3.0.5.jar.

Wonder if someone in google can write clear instruction on how to make
JDO work with Google SQL.

Thanks,
Shweta

Google Cloud SQL- Unofficial blog

Pages

Sunday, March 31, 2013

Re: Are backups occurring for you? (not for me)

Desain perubahan warna pada objek

GAE No connectivity to local dev MySQL instance with data nucleus

Are backups occurring for you? (not for me)

Re: Enabling Backups for Google Cloud SQL

Thursday, March 28, 2013

Re: Issues with prepared statements using driver jar

Re: Issues with prepared statements using driver jar

Re: Issues with prepared statements using driver jar

Wednesday, March 27, 2013

Re: Restarting suspended(!) gloud sql instance

Issues with prepared statements using driver jar

Re: Restarting suspended(!) gloud sql instance

Re: Restarting suspended(!) gloud sql instance

Re: Restarting suspended(!) gloud sql instance

Re: Restarting suspended(!) gloud sql instance

Restarting suspended(!) gloud sql instance

Tuesday, March 26, 2013

Re: Google Cloud SQL: 10 GB max vs TB for alternatives

Re: Google Cloud SQL: 10 GB max vs TB for alternatives

Google Cloud SQL: 10 GB max vs TB for alternatives

Re: Can one resize a DB once created?

Re: Can one resize a DB once created?

Can one resize a DB once created?

Re: Loading mysql JDBC jar file -

Saturday, March 23, 2013

Re: How to connect to existing google cloud SQL database with external android app

Friday, March 22, 2013

Re: How to connect to existing google cloud SQL database with external android app

Re: How to connect to existing google cloud SQL database with external android app

Thursday, March 21, 2013

How to connect to existing google cloud SQL database with external android app

Re: Issues making JDO work with MySQL

(file name)	(size)	(date)	(time)
appengine-api.jar	31.693.808	05/02/2013	12:18
appengine-api-1.0-sdk-1.7.5.jar	31.693.808	21/02/2013	18:36
appengine-api-labs.jar	4.927.863	21/02/2013	18:36
appengine-endpoints.jar	5.654.176	21/02/2013	18:36
appengine-jsr107cache-1.7.5.jar	6.962	21/02/2013	18:36
appengine-local-runtime-shared.jar	607.295	13/02/2013	14:42
appengine-tools-api.jar	17.164.175	13/02/2013	14:41
asm-4.0.jar	46.022	21/02/2013	18:36
datanucleus-api-jdo-3.1.3.jar	317.326	21/02/2013	18:36
datanucleus-api-jpa-3.1.3.jar	254.559	21/02/2013	18:36
datanucleus-appengine-2.1.2.jar	343.590	21/02/2013	18:36
datanucleus-core-3.1.3.jar	1.730.830	21/02/2013	18:36
datanucleus-rdbms-3.1.3.jar	1.541.907	23/02/2013	11:51
geronimo-jpa_2.0_spec-1.0.jar	114.863	21/02/2013	18:36
jdo-api-3.0.1.jar	201.124	21/02/2013	18:36
jsr107cache-1.1.jar	8.082	21/02/2013	18:36
jta-1.1.jar	15.071	21/02/2013	18:36
mysql-connector-java-5.1.22-bin.jar	832.960	06/09/2012	2:21
simple-xml-2.6.4.jar	389.439	25/11/2012	18:30