[google-appengine] Re: unable to generate cloud endpoint client library - 500 Internal Server Error

2015-02-16 Thread Mario 
Hello Pravin,

It's better that you ask this question in Stackoverflow.com because there, 
more people will see the question increasing the chances of getting quickly 
a correct answer. Furthermore, it will be easier for other people to look 
for an answer when having similar issues.

Kind regards,

Mario C.
Cloud Platform Support.

On Monday, February 9, 2015 at 9:56:55 AM UTC+1, pravin wrote:
>
> I'm receiving this error message when trying to generate cloud endpoint 
> client library. 
>
> eclipse.buildId=v21.0.1-543035
> java.version=1.6.0_25
> java.vendor=Sun Microsystems Inc.
> BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
> Framework arguments:  -product com.android.ide.eclipse.adt.package.product 
> -product com.android.ide.eclipse.adt.package.product -product 
> com.android.ide.eclipse.adt.package.product
> Command-line arguments:  -os win32 -ws win32 -arch x86 -product 
> com.android.ide.eclipse.adt.package.product -product 
> com.android.ide.eclipse.adt.package.product -data C:\07-02-2015 workspace 
> -product com.android.ide.eclipse.adt.package.product
>
> Error
> Mon Feb 09 14:17:48 IST 2015
> Unexpected Exception
>
> java.lang.reflect.InvocationTargetException
> 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.gdt.eclipse.appengine.swarm.wizards.helpers.SwarmApiCreator.createClientLibFromApiConfig(SwarmApiCreator.java:104)
> at 
> com.google.gdt.eclipse.appengine.swarm.wizards.helpers.SwarmApiCreator.createSwarmApi(SwarmApiCreator.java:212)
> at 
> com.google.gdt.eclipse.appengine.swarm.wizards.helpers.SwarmServiceCreator.create(SwarmServiceCreator.java:475)
> at 
> com.google.gdt.eclipse.appengine.swarm.wizards.GenerateSwarmApiAction$1.run(GenerateSwarmApiAction.java:84)
> at 
> org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:464)
> at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:372)
> at 
> org.eclipse.jface.dialogs.ProgressMonitorDialog.run(ProgressMonitorDialog.java:507)
> at 
> com.google.gdt.eclipse.appengine.swarm.wizards.GenerateSwarmApiAction.run(GenerateSwarmApiAction.java:80)
> at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:251)
> at 
> org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584)
> at 
> org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501)
> at 
> org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4169)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3758)
> at 
> org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1029)
> at 
> org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at 
> org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:923)
> at 
> org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:86)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:588)
> at 
> org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at 
> org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:543)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
> at 
> org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
> at 
> org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at 
> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
> at 
> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
> at 
> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:353)
> at 
> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:180)
> 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 org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:629)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1438)
> Caused by: 
> com.google.appengine.repackaged.com.google.api.client.http.HttpResponseException:
>  
> 500 Internal Server Error
> at 
> com.google.appengine.repackaged.com.google.api.client.http.HttpReques

Re: [google-appengine] How to setup a GAE managed VM

2015-02-16 Thread Mario 
Hello Deepak,

I'd ask you to post this question in Stackoverflow.com. Thus, it will be 
seen by many developers that will be able to provide the most accurate 
answer to it. Furthermore, it will be easier to find it in the future, when 
another user has a similar question.

Thanks in advance.

Regards,

Mario C.
Google Cloud Platform.

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/837bcf44-2bee-4600-8b9d-ee0896d01e20%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: NoseGAE not fit for testing?

2015-02-16 Thread Mario 
Hi John,

There a full thread about this in GitHub 
. I believe that's the best place 
to follow this conversation. Please have a look at it.

Kind regards,

Mario C.
Google Cloud Platform.

On Wednesday, February 11, 2015 at 5:09:24 AM UTC+1, John Louis Del Rosario 
wrote:
>
> From the NoseGAE readme: 
>
> Due to changes in the sandboxing mechanisms in dev_appserver2, it isn't 
> possible for NoseGAE to simulate the deployed environment any longer. The 
> sandboxing feature had to be removed since there is no longer any way to 
> toggle it between noses own internal workings.
>
> This means that certain tests may pass locally but the code in question 
> will fail in production due to restricted modules and functions. As of now 
> there is no workaround but pull requests are welcome!
>
> That sounds like a pretty big deal? Doesn't the limitation defeat the 
> purpose of testing? What exactly are the restricted modules and functions 
> mentioned?
>
> I posted here instead of opening an issue on Github to start a discussion 
> on whether we should be concerned (we've been using NoseGAE from the 
> start), and what alternatives can we use if it is cause for concern.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/707b890e-7743-49a0-991d-bef0da431416%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: Google App Engine community support is moving to Stack Overflow

2015-02-16 Thread Official George 
I want for real
On Oct 4, 2013 6:06 AM, "rcp"  wrote:

> -1 from an 'enthusiast programmer'; SO considers me un-washed despite my
> relentless effort to be concise and precise.
>
>
> On Monday, February 6, 2012 6:14:54 PM UTC-8, Ikai Lan wrote:
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> *Hi App Engine Developers,In the last few years, the Q&A website Stack
>> Overflow  has become an invaluable tool for
>> developer communities. We’re pleased to announce that we are migrating to
>> Stack Overflow as the official channel for answering development questions
>> about Google App Engine.The google-appengine
>>  group will remain open
>> for general discussions and announcements that are better suited for the
>> groups format.We believe that Stack Overflow is better platform for sharing
>> knowledge and answering support questions given its larger community,
>> de-duping of similar questions and contributor reputation system. We also
>> expect that App Engine developers will be able to contribute and benefit
>> from the wider range of language-related information not specific to App
>> Engine. In addition, due to Stack Overflow’s use of OpenID for account
>> management, developers will not need to create a new account to participate
>> in the discussion - developers will be able to log in with any of the
>> identity providers supported by Stack Overflow, including Google
>> Accounts.We plan on deprecating the App Engine language-specific groups,
>> namely google-appengine-python
>>  and
>> google-appengine-java
>> . The
>> google-appengine-go
>> 
>> discussion group will continue to remain open for at least as long as the
>> Go runtime is in experimental status. The Python and Java groups will be
>> placed into read-only on March 5th, 2012. While answering technical
>> questions, we will begin nudging developers to ask their questions on Stack
>> Overflow using the google-app-engine tag
>> .Please let us
>> know if there are any questions or concerns about this announcement.Happy
>> coding!- Ikai Lan, on behalf of the App Engine team*
>>
>  --
> You received this message because you are subscribed to a topic in the
> Google Groups "Google App Engine" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/google-appengine/Z6XN_64cA7w/unsubscribe
> .
> To unsubscribe from this group and all its topics, send an email to
> google-appengine+unsubscr...@googlegroups.com.
> To post to this group, send email to google-appengine@googlegroups.com.
> Visit this group at http://groups.google.com/group/google-appengine.
> For more options, visit https://groups.google.com/groups/opt_out.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CADexNdTYYvendOEMj%2BPa8y%3DY3_v_-9dc18CpZ9SG5uVDmdn6Lw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: Google App Engine community support is moving to Stack Overflow

2015-02-16 Thread 'Alex Martelli' via Google App Engine 
On Mon, Feb 16, 2015 at 5:23 AM, Official George 
wrote:

> I want for real
>
Sorry, it's opaque to me what you mean by that.  Elucidate please?

Alex


> On Oct 4, 2013 6:06 AM, "rcp"  wrote:
>
>> -1 from an 'enthusiast programmer'; SO considers me un-washed despite my
>> relentless effort to be concise and precise.
>>
>>
>> On Monday, February 6, 2012 6:14:54 PM UTC-8, Ikai Lan wrote:
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> *Hi App Engine Developers,In the last few years, the Q&A website Stack
>>> Overflow  has become an invaluable tool for
>>> developer communities. We’re pleased to announce that we are migrating to
>>> Stack Overflow as the official channel for answering development questions
>>> about Google App Engine.The google-appengine
>>>  group will remain open
>>> for general discussions and announcements that are better suited for the
>>> groups format.We believe that Stack Overflow is better platform for sharing
>>> knowledge and answering support questions given its larger community,
>>> de-duping of similar questions and contributor reputation system. We also
>>> expect that App Engine developers will be able to contribute and benefit
>>> from the wider range of language-related information not specific to App
>>> Engine. In addition, due to Stack Overflow’s use of OpenID for account
>>> management, developers will not need to create a new account to participate
>>> in the discussion - developers will be able to log in with any of the
>>> identity providers supported by Stack Overflow, including Google
>>> Accounts.We plan on deprecating the App Engine language-specific groups,
>>> namely google-appengine-python
>>>  and
>>> google-appengine-java
>>> . The
>>> google-appengine-go
>>> 
>>> discussion group will continue to remain open for at least as long as the
>>> Go runtime is in experimental status. The Python and Java groups will be
>>> placed into read-only on March 5th, 2012. While answering technical
>>> questions, we will begin nudging developers to ask their questions on Stack
>>> Overflow using the google-app-engine tag
>>> .Please let us
>>> know if there are any questions or concerns about this announcement.Happy
>>> coding!- Ikai Lan, on behalf of the App Engine team*
>>>
>>  --
>> You received this message because you are subscribed to a topic in the
>> Google Groups "Google App Engine" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/google-appengine/Z6XN_64cA7w/unsubscribe
>> .
>> To unsubscribe from this group and all its topics, send an email to
>> google-appengine+unsubscr...@googlegroups.com.
>> To post to this group, send email to google-appengine@googlegroups.com.
>> Visit this group at http://groups.google.com/group/google-appengine.
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>  --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-appengine+unsubscr...@googlegroups.com.
> To post to this group, send email to google-appengine@googlegroups.com.
> Visit this group at http://groups.google.com/group/google-appengine.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-appengine/CADexNdTYYvendOEMj%2BPa8y%3DY3_v_-9dc18CpZ9SG5uVDmdn6Lw%40mail.gmail.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CAE46Be8BV93wBs%2BWa2s5v%3Dn-YdVgrwPOtTJjAe9Db-GOE03zxw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Machine system clock is incorrect ??

2015-02-16 Thread Alex Martelli 
On Monday, February 9, 2015 at 11:13:23 PM UTC-8, Marcial Roman wrote:
>
> As announced before community support is moving to Stack Overflow. [1] 
>

Yes, that was the decision three years ago -- but we're going to do things 
slightly differently going forward.

StackOverflow (SO) is about **software development** questions, with some 
further constraints -- see http://stackoverflow.com/help/on-topic .  The SO 
community understandably does *not* appreciate questions that are not about 
SW development -- in particular, questions about system and network 
administration have their own site within the same "stackexchange" family 
-- ServerFault (SF).

Many technical questions about App Engine are indeed about SW development 
and perfectly appropriate for SO -- great!

*But* a few technical questions are instead about system and network 
administration -- and, for those, SF is the right place.

And of course some questions are not welcome on either site -- for example, 
quoting from the FAQ above, "Questions asking us to *recommend or find a 
book, tool, software library, tutorial" *are not welcome there.  For *those* 
kind 
of questions, this Google Group is therefore the best place to ask!
 

> I will recommend you to post this specific question on Stack Overflow. 
> Simply post your question tagging it with "google-app-engine", and a member 
> of our support team or a member of our global developer community will 
> respond shortly after.
>

I would consider this specific question to be most likely a system 
administration one -- thus more appropriate for Server Fault (with the same 
tag).  We do sponsor and monitor tags "google-app-engine", 
"google-compute-engine", and "google-cloud-platform" on both SO and SF. 
 Yes, I do need to change https://cloud.google.com/support/ , which does 
not mention ServerFault; I'm working on that:-).

To me, it's part of acknowledging that we don't only have a *developer* 
community -- there's also a community of *system administrators*, some of 
whom may also be developers, but not necessarily all of them -- likely a 
smaller community, but highly professional and fully deserving of our 
support and recognition.  (The issue looms larger for other Google Cloud 
Platform products, like Google Compute Engine, where the ratio of developer 
vs sysadm questions is also larger than for App Engine; but it makes sense 
for GAE, too!-).

Happy coding!
>

...*and* happy system-administering, too!-)


Thanks,

Alex


>
> [1] https://groups.google.com/forum/#!topic/google-appengine/Z6XN_64cA7w
>
> On Wednesday, February 4, 2015 at 11:00:47 AM UTC+1, saintthor wrote:
>>
>> why cause this? the password is right.
>>
>> i run this in a remote machine which is in another timezone.
>> ===
>>
>>
>> $ python appcfg.py download_app -A djdqbbs -V d2 ./djdq
>> 09:48 AM Host: appengine.google.com
>> 09:48 AM Fetching file list...
>> Email: saintthor
>> Password for saintthor: 
>> Invalid username or password.
>> Email: saintthor
>> Password for saintt...@gmail.com: 
>> Invalid username or password.
>> Email: saintthor
>> Password for saintthor: 
>> Invalid username or password.
>>
>> Error: Machine system clock is incorrect.
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/f0e9ebcf-75ca-40cb-b2d8-04ecf33ac55f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] messageSource bean: ResourceBundle$Control is a restricted class

2015-02-16 Thread Ivan Martinov 
I am running into the same issue because I am attempting to change the 
encoding the messageSource bean is using to UTF-8.

In my case I am internationalizing my app and have properties in 2 
different languages, obviously the non-English language requiring UTF-8 
encoding.  

I was looking forward to using gae for this project, but this is definitely 
a huge roadblock.


-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/95e1da81-3158-43fa-a8a8-fb1d6279ee27%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Persistent storage for Managed VMs, please?

2015-02-16 Thread Avanish Raju 
Hi AppEngine/Managed VM gurus,

Can we please have a way to mount a persistent disk on to our managed VMs?

Now, I'm aware that Managed VMs are intended to be for "stateless use". But
here's my use case, the problem, and the solutions I've tried:

*Use Case*: I need secure web access from my Google AppEngine Java standard
module to an Apache Solr/SolrCloud instance/cluster.

*Problem*:
Apache Solr uses a custom DB which stores its index *on files*. Now, if
Datastore, Blobstore or GCS, or some other Google Cloud Platform technology
could somehow emulate the file system, that would work great. But none
does. These files are the only "state" for Solr, just like "Datastore"
would be "the state" for other AppEngine runtimes.

*Options tried:*
1) *Barebones Google Compute Engine instance*: I setup Solr there, and
opened up the firewall to access the instance from AppEngine. This has two
problems:
a) There's no way to setup firewall rules between GAE and GCE. So I have to
secure my traffic myself.
b) Apparently, HTTPS client requests from GAE to GCE are blocked. (Tried
using Sockets API from GAE; requests to other services work though)

2) *Managed VMs: *With a Dockerfile that can start up, fetch the Solr
release, start up. All good. But... the disk is ephemeral, of course. So
how do I back up data? Problem:
No Google Cloud Storage read/write scope. No way to provide extra
metadata/scopes. Otherwise I could have "saved the data" to GCS, and pulled
it up and set it through a Dockerfile when bringing up the instance.

3) *Managed VMs with an attached disk*: I was able to successfully write up
a script so that when my Docker container started up, it would get my
AppEngine java module(which has Compute API scope by default) to setup and
"attach" a disk to the Managed VM, if it wasn't already there! But...
problem here:
Docker doesn't permit "mount" to be run - this needs "privileged-mode
docker" to be running (otherwise we get a "mount: Permission Denied"), and
i couldn't find a way to pass on "privileged mode" to the Docker on Managed
VM.

So, any solutions? Can I not setup GAE <-> Apache Solr securely on Google
Cloud Platform? Must I move over my GAE Java stack off to pure GCE or other
IAAS offerings, or are there any solutions possible here?

Thanks for reading!
(And hope you have a solution!)
Avanish

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CAAsw5hHC5hHA15TxSqM6GFF%3DpEuBMGEDJ843g8_fr9QO610bqg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.