Re: [google-appengine] How to change the version of Jetty in my Google App Engine

['Ludovic Champenois' via Google App Engine]

For java 17 bundled services (configured via appengine-web.xml not 
app.yaml) the jetty version is provided (managed plaform) and cannot be 
changed.


For non bundled services (app.yaml configuration) whatever web server of 
the market can be used including latest jetty versions.


Ludo

On 7/27/22 8:16 PM, 'Mike Wallace' via Google App Engine wrote:


Within IntelliJ I have a Google App Engine Standard Local Server 
running. I'm in the process of updating to Java 17 and also all of my 
3rd party libraries and have moved to GAE 2.0.5 and Jetty 11.0.11 in 
all of my project's pom files. However, when I start up the server I see:


INFO:oejs.Server:main: jetty-9.4.46.v20220331

and I'm getting failures that seem to confirm the above, that an older 
version of Jetty is being used. Where can I update the Jetty version 
that the app engine uses?


Here's the stack trace. The latest versions should be using 
jakarta.ws.rs.Path instead of javax.


java.lang.TypeNotPresentException: Type javax.ws.rs.Path not present 
at 
java.base/sun.reflect.annotation.TypeNotPresentExceptionProxy.generateException(TypeNotPresentExceptionProxy.java:47) 
at 
java.base/sun.reflect.annotation.AnnotationInvocationHandler.invoke(AnnotationInvocationHandler.java:89) 
at jdk.proxy2/jdk.proxy2.$Proxy2.value(Unknown Source) at 
org.eclipse.jetty.annotations.AnnotationConfiguration.createServletContainerInitializerAnnotationHandlers(AnnotationConfiguration.java:579) 
at 
org.eclipse.jetty.annotations.AnnotationConfiguration.configure(AnnotationConfiguration.java:343) 
at 
org.eclipse.jetty.webapp.WebAppContext.configure(WebAppContext.java:498) 
at 
org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1409) 
at 
org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:916) 
at 
org.eclipse.jetty.servlet.ServletContextHandler.doStart(ServletContextHandler.java:288) 
at 
org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:524) 
at 
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73) 
at 
org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:169) 
at 
org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:110) 
at 
org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:97) 
at 
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73) 
at 
org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:169) 
at org.eclipse.jetty.server.Server.start(Server.java:423) at 
org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:110) 
at 
org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:97) 
at org.eclipse.jetty.server.Server.doStart(Server.java:387) at 
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73) 
at 
com.google.appengine.tools.development.jetty9.JettyContainerService.startContainer(JettyContainerService.java:366)


--
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/3ec6a90b-9617-480e-9771-3a39f941c576n%40googlegroups.com 
.


--
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/2b375ede-8cd0-42e1-c528-17b1cf961388%40google.com.

Re: [google-appengine] Re: hot reload: mvn google cloud sdk

[Ludovic Champenois]

Hi,

You can install InteliJ on wsl2 according to 
https://nirisarri.github.io/2020-11-03-how-to-install-and-run-intellij-idea-for-linux-in-wsl2/


similar steps should work for NetBeans or Eclipse I guess.

Ludp

On 4/21/22 2:55 AM, 'Rajesh G' via Google App Engine wrote:
If you dont' use IDE  like eclipse or netbeans (it is not available on 
windows 11 wsl2 env)

Use mvn compile.
It is working for me now on windows 11.  I will try on wsl2 later.

On Sat, Apr 16, 2022 at 10:20 PM Ludovic Champenois 
 wrote:


Hi,
Almost there,  I think you are missing this critical line in your
pom.xml:
    

target/${project.artifactId}-${project.version}/WEB-INF/classes
        
...

This way, the compile on save is put the changed class in the
correct web app location.
At least, I tested it in NetBeans and it works great as NetBeans
can do compile automatically when you save a java file, even in
the Maven project.
Ludo


On Saturday, April 16, 2022 at 4:50:43 AM UTC-7
rajesh...@veersoftsolutions.com wrote:

Hello,
I have created a simple java appengine using maven archetypes.
I am not using eclipse (because I don't have eclipse in
windows wsl2.)

I run the server using
mvn appengine:run

Then I do simple changes to a servlet. Then another window, I run
mvn:compile.  It compiles into the target/snapshot folder

However, I am not seeing the changes on the server.  The
latest servlet changes is not reflected

I tried the following settings also in the pom.xml file.  The
server is not restarted


   true



--
Support Team
www.servicefolder.com <https://www.servicefolder.com>
/Field Service Software on Google Cloud Platform and Mobile/
/

/

-- 
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 view this discussion on the web visit

https://groups.google.com/d/msgid/google-appengine/02a10f06-ff90-4e1b-80ae-457c49a56bf9n%40googlegroups.com

<https://groups.google.com/d/msgid/google-appengine/02a10f06-ff90-4e1b-80ae-457c49a56bf9n%40googlegroups.com?utm_medium=email_source=footer>.



--
Support Team
www.servicefolder.com <https://www.servicefolder.com>
/Field Service Software on Google Cloud Platform and Mobile/
/

/
--
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/5XT9ASv7iM4/unsubscribe.
To unsubscribe from this group and all its topics, send an email to 
google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CA%2BS7ijY2QAOGaP%2B38XD4To%3DUiqyDWNx44_S6PvVcLdU%2BU3yWtg%40mail.gmail.com 
<https://groups.google.com/d/msgid/google-appengine/CA%2BS7ijY2QAOGaP%2B38XD4To%3DUiqyDWNx44_S6PvVcLdU%2BU3yWtg%40mail.gmail.com?utm_medium=email_source=footer>.


--
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/eedb662d-ced9-e9c0-0060-58ac339e79d2%40gmail.com.

Re: [google-appengine] Re: hot reload: mvn google cloud sdk

[Ludovic Champenois]

Hi,
Try to follow the doc at:
https://cloud.google.com/appengine/docs/standard/java/maven-reference#appenginerun
Especially the config for the Pom.xml file to put the classes in the
correct folder.

Thanks


On Tue, Apr 19, 2022 at 8:43 PM 'Rajesh G' via Google App Engine <
google-appengine@googlegroups.com> wrote:

> Hi, any ideas on how to make the hot reload work
>
> Thanks
>
> On Sat, Apr 16, 2022 at 5:20 PM Rajesh G <
> rajesh.gu...@veersoftsolutions.com> wrote:
>
>> Hello,
>> I have created a simple java appengine using maven archetypes.
>> I am not using eclipse (because I don't have eclipse in windows wsl2.)
>>
>> I run the server using
>> mvn appengine:run
>>
>> Then I do simple changes to a servlet. Then another window, I run
>> mvn:compile.  It compiles into the target/snapshot folder
>>
>> However, I am not seeing the changes on the server.  The latest servlet
>> changes is not reflected
>>
>> I tried the following settings also in the pom.xml file.  The server is
>> not restarted
>>
>> 
>>   true
>> 
>>
>>
>> --
>> Support Team
>> www.servicefolder.com
>> *Field Service Software on Google Cloud Platform and Mobile*
>>
>>
>>
>
> --
> Support Team
> www.servicefolder.com
> *Field Service Software on Google Cloud Platform and Mobile*
>
>
> --
> 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/5XT9ASv7iM4/unsubscribe
> .
> To unsubscribe from this group and all its topics, send an email to
> google-appengine+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-appengine/CA%2BS7ijaEYSV83h6rvK-NDF8bpTw%3Dx31cSrtzmZExufXu%3DP%3DqzQ%40mail.gmail.com
> 
> .
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CAGV2Ug_TH0s%2Bgct_XtPz7HhY_crJ084vLKaAV%2B5M8XAh9Tb8ng%40mail.gmail.com.

[google-appengine] Re: hot reload: mvn google cloud sdk

[Ludovic Champenois]

Hi,
Almost there,  I think you are missing this critical line in your pom.xml:


target/${project.artifactId}-${project.version}/WEB-INF/classes

...

This way, the compile on save is put the changed class in the correct web 
app location.
At least, I tested it in NetBeans and it works great as NetBeans can do 
compile automatically when you save a java file, even in the Maven project.
Ludo


On Saturday, April 16, 2022 at 4:50:43 AM UTC-7 
rajesh...@veersoftsolutions.com wrote:

> Hello,
> I have created a simple java appengine using maven archetypes.
> I am not using eclipse (because I don't have eclipse in windows wsl2.)
>
> I run the server using
> mvn appengine:run
>
> Then I do simple changes to a servlet. Then another window, I run 
> mvn:compile.  It compiles into the target/snapshot folder
>
> However, I am not seeing the changes on the server.  The latest servlet 
> changes is not reflected 
>
> I tried the following settings also in the pom.xml file.  The server is 
> not restarted
>
> 
>   true
> 
>
>
> --
> Support Team
> www.servicefolder.com 
> 
> *Field Service Software on Google Cloud Platform and Mobile*
>
>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/02a10f06-ff90-4e1b-80ae-457c49a56bf9n%40googlegroups.com.

Re: [google-appengine] Re: Servlet Spec 12.2 violation: glob '*' can only exist at end of prefix based matches: bad spec "/*.xhtml"

[Ludovic Champenois]

Hi again,
Let me know if you can update the app in a way it does not define the
incorrect mapping...  I hope it is not too complicated,
Thanks!

On Sun, Apr 3, 2022 at 12:10 PM Ludovic Champenois <
ludovic.champen...@gmail.com> wrote:

> Hi,
> So the app worked for the past 2 years without new deployment? Recently,
> the Jetty web server got upgraded to 9.4.45... It might be more strict
> regarding servlet 3.1 compliance in this area? Can you share more snippet
> of code?
> Ludo
>
> On Saturday, April 2, 2022 at 8:00:26 PM UTC-7 henry@gmail.com wrote:
>
>> After  2 years of troubles work JSF application raised this exception:
>>
>> Uncaught exception from servlet java.lang.IllegalArgumentException:
>> Servlet Spec 12.2 violation: glob '*' can only exist at end of prefix based
>> matches: bad spec "/*.xhtml"at
>> org.eclipse.jetty.http.pathmap.ServletPathSpec.assertValidServletPathSpec(ServletPathSpec.java:157)
>>at
>> org.eclipse.jetty.http.pathmap.ServletPathSpec.(ServletPathSpec.java:56)
>>at
>> org.eclipse.jetty.servlet.ServletHandler.updateMappings(ServletHandler.java:1424)
>>at
>> org.eclipse.jetty.servlet.ServletHandler.doStart(ServletHandler.java:164)
>>  at
>> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
>>at
>> org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:169)
>>at
>> org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:110)
>>at
>> org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:97)
>>at
>> org.eclipse.jetty.security.SecurityHandler.doStart(SecurityHandler.java:411)
>>at
>> org.eclipse.jetty.security.ConstraintSecurityHandler.doStart(ConstraintSecurityHandler.java:417)
>>at
>> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
>>at
>> org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:169)
>>at
>> org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:110)
>>at
>> org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:97)
>>at
>> org.eclipse.jetty.server.handler.ScopedHandler.doStart(ScopedHandler.java:120)
>>at
>> org.eclipse.jetty.server.session.SessionHandler.doStart(SessionHandler.java:505)
>>at
>> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
>>at
>> org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:169)
>>at
>> org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:110)
>>at
>> org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:97)
>>at
>> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
>>at
>> org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:169)
>>at
>> org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:110)
>>at
>> org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:97)
>>at
>> org.eclipse.jetty.server.handler.ScopedHandler.doStart(ScopedHandler.java:120)
>>at
>> org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler.java:969)
>>at
>> org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:375)
>>at
>> org.eclipse.jetty.webapp.WebAppContext.startWebapp(WebAppContext.java:1449)
>>at
>> com.google.apphosting.runtime.jetty94.AppEngineWebAppContext.startWebapp(AppEngineWebAppContext.java:263)
>>at
>> org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1414)
>>at
>> org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:910)
>>at
>> org.eclipse.jetty.servlet.ServletContextHandler.doStart(ServletContextHandler.java:288)
>>at
>> org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:524)
>>  at
>> com.google.apphosting.runtime.jetty94.AppEngineWebAppContext.doStart(AppEngineWebAppContext.java:207)
>>at
>> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
>>at
>> com.google.apphosting.runtime.jetty94.AppVersionHandlerFactory.doCreateHandler(AppVersionHandlerFactory.java:178)
>>at
>> com.google.apphosting.runtime.jetty94.AppVersionHandlerFactory.createHandler(AppVersionHandlerFactory.java:112)
>> 

[google-appengine] Re: Servlet Spec 12.2 violation: glob '*' can only exist at end of prefix based matches: bad spec "/*.xhtml"

[Ludovic Champenois]

More info regarding spec 
at 
https://stackoverflow.com/questions/58033540/how-to-create-a-multiple-wildcard-url-pattern-in-web-xml

On Sunday, April 3, 2022 at 12:10:02 PM UTC-7 Ludovic Champenois wrote:

> Hi,
> So the app worked for the past 2 years without new deployment? Recently, 
> the Jetty web server got upgraded to 9.4.45... It might be more strict 
> regarding servlet 3.1 compliance in this area? Can you share more snippet 
> of code?
> Ludo
>
> On Saturday, April 2, 2022 at 8:00:26 PM UTC-7 henry@gmail.com wrote:
>
>> After  2 years of troubles work JSF application raised this exception:
>>
>> Uncaught exception from servlet java.lang.IllegalArgumentException: 
>> Servlet Spec 12.2 violation: glob '*' can only exist at end of prefix based 
>> matches: bad spec "/*.xhtml"at 
>> org.eclipse.jetty.http.pathmap.ServletPathSpec.assertValidServletPathSpec(ServletPathSpec.java:157)
>>  
>>at 
>> org.eclipse.jetty.http.pathmap.ServletPathSpec.(ServletPathSpec.java:56)
>>  
>>at 
>> org.eclipse.jetty.servlet.ServletHandler.updateMappings(ServletHandler.java:1424)
>>  
>>at 
>> org.eclipse.jetty.servlet.ServletHandler.doStart(ServletHandler.java:164)   
>>  at 
>> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
>>  
>>at 
>> org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:169)
>>  
>>at 
>> org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:110)
>>  
>>at 
>> org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:97)
>>  
>>at 
>> org.eclipse.jetty.security.SecurityHandler.doStart(SecurityHandler.java:411) 
>>at 
>> org.eclipse.jetty.security.ConstraintSecurityHandler.doStart(ConstraintSecurityHandler.java:417)
>>  
>>at 
>> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
>>  
>>at 
>> org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:169)
>>  
>>at 
>> org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:110)
>>  
>>at 
>> org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:97)
>>  
>>at 
>> org.eclipse.jetty.server.handler.ScopedHandler.doStart(ScopedHandler.java:120)
>>  
>>at 
>> org.eclipse.jetty.server.session.SessionHandler.doStart(SessionHandler.java:505)
>>  
>>at 
>> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
>>  
>>at 
>> org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:169)
>>  
>>at 
>> org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:110)
>>  
>>at 
>> org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:97)
>>  
>>at 
>> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
>>  
>>at 
>> org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:169)
>>  
>>at 
>> org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:110)
>>  
>>at 
>> org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:97)
>>  
>>at 
>> org.eclipse.jetty.server.handler.ScopedHandler.doStart(ScopedHandler.java:120)
>>  
>>at 
>> org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler.java:969)
>>  
>>at 
>> org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:375)
>>  
>>at 
>> org.eclipse.jetty.webapp.WebAppContext.startWebapp(WebAppContext.java:1449) 
>>at 
>> com.google.apphosting.runtime.jetty94.AppEngineWebAppContext.startWebapp(AppEngineWebAppContext.java:263)
>>  
>>at 
>> org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1414) 
>>at 
>> org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:910)
>>  
>>at 
>> org.eclipse.jetty.servlet.ServletContextHandler.doStart(ServletContextHandler.java:288)
>>  
>>at 
>> org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:524)   
>>  at 
>> com.google.apphosting.runtime.jetty94.AppEngineWebAppContext.doStart(AppEngineWebAppContext.java:207)
>>  
>>at 
>> org.eclipse.jetty.util.component.AbstractLifeCycl

[google-appengine] Re: Servlet Spec 12.2 violation: glob '*' can only exist at end of prefix based matches: bad spec "/*.xhtml"

[Ludovic Champenois]

Hi,
So the app worked for the past 2 years without new deployment? Recently, 
the Jetty web server got upgraded to 9.4.45... It might be more strict 
regarding servlet 3.1 compliance in this area? Can you share more snippet 
of code?
Ludo

On Saturday, April 2, 2022 at 8:00:26 PM UTC-7 henry@gmail.com wrote:

> After  2 years of troubles work JSF application raised this exception:
>
> Uncaught exception from servlet java.lang.IllegalArgumentException: 
> Servlet Spec 12.2 violation: glob '*' can only exist at end of prefix based 
> matches: bad spec "/*.xhtml"at 
> org.eclipse.jetty.http.pathmap.ServletPathSpec.assertValidServletPathSpec(ServletPathSpec.java:157)
>  
>at 
> org.eclipse.jetty.http.pathmap.ServletPathSpec.(ServletPathSpec.java:56)
>  
>at 
> org.eclipse.jetty.servlet.ServletHandler.updateMappings(ServletHandler.java:1424)
>  
>at 
> org.eclipse.jetty.servlet.ServletHandler.doStart(ServletHandler.java:164)   
>  at 
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
>  
>at 
> org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:169)
>  
>at 
> org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:110)
>  
>at 
> org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:97)
>  
>at 
> org.eclipse.jetty.security.SecurityHandler.doStart(SecurityHandler.java:411) 
>at 
> org.eclipse.jetty.security.ConstraintSecurityHandler.doStart(ConstraintSecurityHandler.java:417)
>  
>at 
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
>  
>at 
> org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:169)
>  
>at 
> org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:110)
>  
>at 
> org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:97)
>  
>at 
> org.eclipse.jetty.server.handler.ScopedHandler.doStart(ScopedHandler.java:120)
>  
>at 
> org.eclipse.jetty.server.session.SessionHandler.doStart(SessionHandler.java:505)
>  
>at 
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
>  
>at 
> org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:169)
>  
>at 
> org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:110)
>  
>at 
> org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:97)
>  
>at 
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
>  
>at 
> org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:169)
>  
>at 
> org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:110)
>  
>at 
> org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:97)
>  
>at 
> org.eclipse.jetty.server.handler.ScopedHandler.doStart(ScopedHandler.java:120)
>  
>at 
> org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler.java:969)
>  
>at 
> org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:375)
>  
>at 
> org.eclipse.jetty.webapp.WebAppContext.startWebapp(WebAppContext.java:1449) 
>at 
> com.google.apphosting.runtime.jetty94.AppEngineWebAppContext.startWebapp(AppEngineWebAppContext.java:263)
>  
>at 
> org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1414) 
>at 
> org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:910)
>  
>at 
> org.eclipse.jetty.servlet.ServletContextHandler.doStart(ServletContextHandler.java:288)
>  
>at 
> org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:524)   
>  at 
> com.google.apphosting.runtime.jetty94.AppEngineWebAppContext.doStart(AppEngineWebAppContext.java:207)
>  
>at 
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
>  
>at 
> com.google.apphosting.runtime.jetty94.AppVersionHandlerFactory.doCreateHandler(AppVersionHandlerFactory.java:178)
>  
>at 
> com.google.apphosting.runtime.jetty94.AppVersionHandlerFactory.createHandler(AppVersionHandlerFactory.java:112)
>  
>at 
> com.google.apphosting.runtime.jetty94.AppVersionHandlerMap.getHandler(AppVersionHandlerMap.java:82)
>  
>at 
> com.google.apphosting.runtime.jetty94.JettyServletEngineAdapter.serviceRequest(JettyServletEngineAdapter.java:167)
>  
>at 
> com.google.apphosting.runtime.RequestRunner.dispatchServletRequest(RequestRunner.java:264)
>  
>at 
> com.google.apphosting.runtime.RequestRunner.dispatchRequest(RequestRunner.java:229)
>  
>at 
> com.google.apphosting.runtime.RequestRunner.run(RequestRunner.java:194)   
>  at 
> com.google.apphosting.runtime.ThreadGroupPool$PoolEntry.run(ThreadGroupPool.java:273)
>  
>at java.lang.Thread.run(Thread.java:748) 
>

-- 

Re: [google-appengine] Re: Questions Re: App Engine bundled services for Java 11

['Ludovic Champenois' via Google App Engine]

Hi,

We have added Java 11 bundled services samples instruction under 
https://github.com/GoogleCloudPlatform/java-docs-samples/tree/main/appengine-java11-bundled-services, 
with 1 full sample available (Datastore).


Try the instructions on taskqueues-deferred, pull and push samples for 
Java8, it should be the same user code.


If the Javadoc is still there, it should work.

Let us know how it goes!

Cheers,

Ludo


On 2/22/22 8:09 PM, 'Matt Larkin' via Google App Engine wrote:

Hi Martin,
>- Does this allow enqueueing tasks within a datastore transaction? I 
can see from the Javadoc that the Queue.add(Transaction txn, 
TaskOptions taskOptions) method is still there but not sure how the 
bundled services work internally. i.e. are they proxying to the new 
services or connecting to the legacy ones.
Yes, the bundled services in 2nd-gen have the same behavior as in 
1st-gen, including transactional tasks.  These services actually use 
the /exact same backends/services /that they always have, the work we 
are doing now just enables the use of these backends by certain 
2nd-gen runtimes (Java/Python/Go).


>Is there any guidance on when this might be GA?
We are targeting GA, for Java/Python/Go runtimes, at the end of Q1 
2022 (~end of March 2022)


Best,
Matt
On Tuesday, February 22, 2022 at 2:55:53 AM UTC-8 
mar...@mondo.ventures wrote:


Not sure if this is the best place to ask but can't find any
dedicated preview google group for the 2nd-gen bundled services.
It seems like this could save us a lot of effort to get up to Java
11 but I've got a couple of questions:

- Does this allow enqueueing tasks within a datastore transaction?
I can see from the Javadoc that the Queue.add(Transaction txn,
TaskOptions taskOptions) method is still there but not sure how
the bundled services work internally. i.e. are they proxying to
the new services or connecting to the legacy ones.

- Is there any guidance on when this might be GA?

Thanks
Martin

--
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/7af621c5-70ef-4fb6-b299-5c8cb6a4e9cbn%40googlegroups.com 
.


--
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/4f772909-912a-d67f-b34a-c9ed38c825a5%40google.com.

[google-appengine] Re: 500 - Request was aborted after waiting too long to attempt to service your reques

['Ludovic Champenois' via Google App Engine]

Can you tell us with runtime are you using (Java, py, go?) and which 
versions?
Are you app.yaml based or appengine-web.xml based?

Ludo

On Tuesday, September 28, 2021 at 5:50:06 PM UTC+2 Will Reiher wrote:

> Totally, not a huge amount of them but definitely more RPC errors and 
> timeouts in the last week or so. I'd expect the odd one but it would seem 
> that some infrastructure changes are causing issues.
>
> On Tuesday, September 21, 2021 at 7:57:13 AM UTC-7 Leonard Cremer wrote:
>
>> We are suddenly getting a lot of these type of errors on services that 
>> have not changed recently. 
>>
>> Is anyone else experiencing similar errors. 
>>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/59d60cce-f6f0-46b3-82a9-483131952d3en%40googlegroups.com.

[google-appengine] Re: URRGENT - Newer version of my Spring MVC application not instantiating

['Ludovic Champenois' via Google App Engine]

Can you describe the directory structure of your app (where is 
appengine-web.xml and your JSPs, maybe with a ls -l web/)
and what is the content of appengine-web.xml)

See 
also https://cloud.google.com/appengine/docs/standard/java11/services/access
Ludo

On Monday, September 27, 2021 at 7:25:33 AM UTC+2 rat@gmail.com wrote:

> [image: App1.png]I 
>
> I am deploying newer version of my Spring MVC Java application to Google 
> app engine. But it is not building application on google server and 
> throwing Error 404. 
>
> While debugging I found that WEB-INF folder of newer (11) version has not 
> includes jsp files and classes folder which was there in previous(8) 
> version. 
>
> I have tried all thing whole day unable figure out why JSPs are not there. 
> Application is running fine locally. 
> Please help urgently and check the attached screenshots.
> [image: commands.png]
>
>
> Thanks in advance
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/0f2dfbfe-6447-4389-bee5-a2004a2d6209n%40googlegroups.com.

[google-appengine] Re: Variable substitution in App Engine 11 app.yaml

['Ludovic Champenois' via Google App Engine]

src/main/appengine/app.yaml is indeed the configuration for pure Java11 
apps, bundling your web server...
You can now also use the beta Java11 runtime with GAE bundled apis, the 
same way as Java8 with appengine-web.xml as seen in

https://cloud.google.com/appengine/docs/standard/java11/services/access

If you still want to use app.yaml, you'll need to configure the Maven 
resources filtering 
plugin 
https://maven.apache.org/plugins/maven-resources-plugin/examples/filter.html 
with the correct settings so it can handle app.yaml files.

Ludo

On Monday, October 11, 2021 at 3:45:39 PM UTC+2 t...@terratrue.com wrote:

>
> We've got several App Engine projects that I am migrating from App Engine 
> 8 to App Engine 11 on Spring Boot. A number of them use a 
> vpc-access-connector in their appengine-web.xml file, which we inject using 
> resource filtering in the maven-war-plugin. The new way to configure the 
> app engine is to use a `src/main/appengine/app.yaml` file and a jar instead 
> of a war, as the artifact however I have been unable to determine how to do 
> variable substitution into the app.yaml file.
>
> I need to inject different values based on the maven profile being run. We 
> currently define vpc access connector values in maven properties sections 
> within profiles aligned with our spring profiles for each of our deployment 
> environments, like test, ea and prod.
>
> What is the solution here?
>
> Is there some way to use different app.yaml files based on which profile 
> is being invoked? (This is not the best solution, as it would mean most of 
> the file content would be static copies, though the common stuff could be 
> moved to an included yaml.)
>
> Or is there some syntax I can't locate online that will allow me to set an 
> environment variable or maven property and refer to it from within the 
> `src/main/appengine/app.yaml` file?
>
> Thanks for any assistance!
> Tom Harris
>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/328e4098-f835-45d2-97c4-a21ef70e435bn%40googlegroups.com.

[google-appengine] Re: Exceeded hard memory limit of 256 MB on F4 instance at Free Trial

['Ludovic Champenois' via Google App Engine]

Can you share your source code directory structure, and where is located 
app.yaml, and how you build then deploy?

On Thursday, October 14, 2021 at 4:32:30 PM UTC+2 andreas...@gmail.com 
wrote:

> Looks like this is an deployment issue.
>
> The direct deployment of the quarkus application with ' gcloud app deploy' 
> seems not to deploy the app.yaml correctly.
>
> Using the maven plugin helps with the issue: mvn clean package 
> appengine:deploy. 
>
> Andreas Bartelt schrieb am Montag, 11. Oktober 2021 um 15:45:38 UTC+2:
>
>> Hi all!
>>
>> I've get messages like this one:
>> "Exceeded hard memory limit of 256 MB with 274 MB after servicing 2 
>> requests total. Consider setting a larger instance class in app.yaml."
>> And my application throws HTTP 500 errors in response.
>>
>> My app.yaml:
>> runtime: java11
>> instance_class: F4
>>
>> Also tried F4_G1 to no avail.
>>
>> I'am on GAE standard in the Free Trial.
>>
>> How to debug this?
>>
>> Regards, Andreas
>>
>>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/42e7d508-c4c8-4525-be99-46224398ddf6n%40googlegroups.com.

Re: [google-appengine] App Engine 11 with Cloud SQL mysql "No suitable driver"

['Ludovic Champenois' via Google App Engine]

Related 
documentation: 
https://dev.mysql.com/doc/connector-j/8.0/en/connector-j-usagenotes-connect-drivermanager.html

On Monday, October 18, 2021 at 4:42:24 PM UTC+2 Ludovic Champenois wrote:

> So it seems a generic Java well known error
>
> https://stackoverflow.com/questions/22384710/java-sql-sqlexception-no-suitable-driver-found-for-jdbcmysql-localhost3306
> Maybe the GAE Java8 runtime is a bit smarter and does this for you.
> Anyway, it seems what your are doing is now the right thing,
> Cheers,
> Ludo
>
> On Wednesday, October 13, 2021 at 7:40:38 PM UTC+2 t...@terratrue.com 
> wrote:
>
>>
>> No, we are using pure app.yaml, no more appengine-web.xml in our modules.
>>
>> On Mon, Oct 11, 2021 at 5:24 PM 'Ludovic Champenois' via Google App 
>> Engine  wrote:
>>
>>> Hi,
>>> Thanks for the update and the solution,
>>> We are looking and trying to understand the delta between the 2 
>>> runtimes...
>>> Just to be sure, you are using the new Beta Java11 runtime with bundled 
>>> APIs (so using appengine-web.xml), right?
>>> Ludo
>>>
>>> On Monday, October 11, 2021 at 1:04:24 PM UTC-7 t...@terratrue.com 
>>> wrote:
>>>
>>>> I posted this a week ago, and I solved this issue - I just had to add a 
>>>> `Class.forName("com.mysql.cj.jdbc.Driver")` call, which was not needed in 
>>>> App Engine 8 with Java 8 when running in the cloud, but apparently it is 
>>>> now required. Without this, the database connection pool just 
>>>> cannot initialize, and all you get is a stack trace which ultimately ends 
>>>> with "No suitable driver".
>>>>
>>>> Thanks,
>>>> Tom Harris
>>>>
>>>>
>>>> On Mon, Oct 11, 2021 at 6:45 AM Tom Harris  wrote:
>>>>
>>>>> Hi all, running into a very thorny issue that I have spent 
>>>>> considerable time on now, without a working solution.
>>>>>
>>>>> We have a set of Java 8 AppEngine-based microservices that I am 
>>>>> upgrading to Java 11 and Spring Boot. The services are using MySQL via 
>>>>> Cloud SQL with Google's socket factory. Locally, we use the MySQL driver 
>>>>> directly and the services run as expected.
>>>>>
>>>>> However when I try to deploy out to a cloud environment, when the code 
>>>>> tries to instantiate the Hikari connection pool using Cloud SQL, I 
>>>>> receive 
>>>>> the dreaded "No suitable driver" error from the JDBC DriverManager.
>>>>>
>>>>> Our project includes these two dependencies:
>>>>> 
>>>>>   com.google.cloud.sql
>>>>>   mysql-socket-factory-connector-j-8
>>>>>   1.3.3
>>>>> 
>>>>> 
>>>>>   mysql
>>>>>   mysql-connector-java
>>>>>   8.0.26
>>>>> 
>>>>>
>>>>> Here is the code that is failing:
>>>>> HikariConfig config = new HikariConfig();
>>>>> config.addDataSourceProperty("useSSL", "false");
>>>>> config.addDataSourceProperty("useUnicode", "true");
>>>>> config.addDataSourceProperty("characterEncoding", "UTF-8");
>>>>> config.setRegisterMbeans(true);
>>>>>
>>>>> config.setJdbcUrl("jdbc:mysql:///dbname");
>>>>> config.setUsername(dbUser);
>>>>> config.setPassword(dbPassword);
>>>>> config.addDataSourceProperty("socketFactory", 
>>>>> "com.google.cloud.sql.mysql.SocketFactory");
>>>>> config.addDataSourceProperty("cloudSqlInstance", 
>>>>> instanceConnectionName);
>>>>>
>>>>> return new HikariDataSource(config);
>>>>>
>>>>> And every time I try to fire up the service after deploying it to the 
>>>>> cloud, I am seeing the error:
>>>>>
>>>>> Caused by: java.lang.RuntimeException: Failed to get driver instance 
>>>>> for jdbcUrl=jdbc:mysql:///dbname  at 
>>>>> com.zaxxer.hikari.util.DriverDataSource.(DriverDataSource.java:114) 
>>>>> at 
>>>>> com.zaxxer.hikari.pool.PoolBase.initializeDataSource(PoolBase.java:331) 
>>>>> at com.zaxxer.hikari.pool.PoolBase.(PoolBase.java:114) at 
>>>>> com.zaxxer.hikari.pool.HikariPool.(HikariPool.java:10

Re: [google-appengine] App Engine 11 with Cloud SQL mysql "No suitable driver"

['Ludovic Champenois' via Google App Engine]

So it seems a generic Java well known error
https://stackoverflow.com/questions/22384710/java-sql-sqlexception-no-suitable-driver-found-for-jdbcmysql-localhost3306
Maybe the GAE Java8 runtime is a bit smarter and does this for you.
Anyway, it seems what your are doing is now the right thing,
Cheers,
Ludo

On Wednesday, October 13, 2021 at 7:40:38 PM UTC+2 t...@terratrue.com wrote:

>
> No, we are using pure app.yaml, no more appengine-web.xml in our modules.
>
> On Mon, Oct 11, 2021 at 5:24 PM 'Ludovic Champenois' via Google App Engine 
>  wrote:
>
>> Hi,
>> Thanks for the update and the solution,
>> We are looking and trying to understand the delta between the 2 
>> runtimes...
>> Just to be sure, you are using the new Beta Java11 runtime with bundled 
>> APIs (so using appengine-web.xml), right?
>> Ludo
>>
>> On Monday, October 11, 2021 at 1:04:24 PM UTC-7 t...@terratrue.com wrote:
>>
>>> I posted this a week ago, and I solved this issue - I just had to add a 
>>> `Class.forName("com.mysql.cj.jdbc.Driver")` call, which was not needed in 
>>> App Engine 8 with Java 8 when running in the cloud, but apparently it is 
>>> now required. Without this, the database connection pool just 
>>> cannot initialize, and all you get is a stack trace which ultimately ends 
>>> with "No suitable driver".
>>>
>>> Thanks,
>>> Tom Harris
>>>
>>>
>>> On Mon, Oct 11, 2021 at 6:45 AM Tom Harris  wrote:
>>>
>>>> Hi all, running into a very thorny issue that I have spent considerable 
>>>> time on now, without a working solution.
>>>>
>>>> We have a set of Java 8 AppEngine-based microservices that I am 
>>>> upgrading to Java 11 and Spring Boot. The services are using MySQL via 
>>>> Cloud SQL with Google's socket factory. Locally, we use the MySQL driver 
>>>> directly and the services run as expected.
>>>>
>>>> However when I try to deploy out to a cloud environment, when the code 
>>>> tries to instantiate the Hikari connection pool using Cloud SQL, I receive 
>>>> the dreaded "No suitable driver" error from the JDBC DriverManager.
>>>>
>>>> Our project includes these two dependencies:
>>>> 
>>>>   com.google.cloud.sql
>>>>   mysql-socket-factory-connector-j-8
>>>>   1.3.3
>>>> 
>>>> 
>>>>   mysql
>>>>   mysql-connector-java
>>>>   8.0.26
>>>> 
>>>>
>>>> Here is the code that is failing:
>>>> HikariConfig config = new HikariConfig();
>>>> config.addDataSourceProperty("useSSL", "false");
>>>> config.addDataSourceProperty("useUnicode", "true");
>>>> config.addDataSourceProperty("characterEncoding", "UTF-8");
>>>> config.setRegisterMbeans(true);
>>>>
>>>> config.setJdbcUrl("jdbc:mysql:///dbname");
>>>> config.setUsername(dbUser);
>>>> config.setPassword(dbPassword);
>>>> config.addDataSourceProperty("socketFactory", 
>>>> "com.google.cloud.sql.mysql.SocketFactory");
>>>> config.addDataSourceProperty("cloudSqlInstance", 
>>>> instanceConnectionName);
>>>>
>>>> return new HikariDataSource(config);
>>>>
>>>> And every time I try to fire up the service after deploying it to the 
>>>> cloud, I am seeing the error:
>>>>
>>>> Caused by: java.lang.RuntimeException: Failed to get driver instance 
>>>> for jdbcUrl=jdbc:mysql:///dbname  at 
>>>> com.zaxxer.hikari.util.DriverDataSource.(DriverDataSource.java:114) 
>>>> at com.zaxxer.hikari.pool.PoolBase.initializeDataSource(PoolBase.java:331) 
>>>> at com.zaxxer.hikari.pool.PoolBase.(PoolBase.java:114) at 
>>>> com.zaxxer.hikari.pool.HikariPool.(HikariPool.java:108) at 
>>>> com.zaxxer.hikari.HikariDataSource.(HikariDataSource.java:81) at 
>>>> com.terratrue.db.DataSources.initDataSourceForCloudEnvironmentForUser(DataSources.java:276)
>>>> Caused by: java.sql.SQLException: No suitable driver at 
>>>> java.sql/java.sql.DriverManager.getDriver(DriverManager.java:298) at 
>>>> com.zaxxer.hikari.util.DriverDataSource.(DriverDataSource.java:106) 
>>>> ... 53 common frames omitted"
>>>>
>>>> I have searched the internet for anything that would help resolve this 
>>>> issue, bu

Re: [google-appengine] App Engine 11 with Cloud SQL mysql "No suitable driver"

['Ludovic Champenois' via Google App Engine]

Hi,
Thanks for the update and the solution,
We are looking and trying to understand the delta between the 2 runtimes...
Just to be sure, you are using the new Beta Java11 runtime with bundled 
APIs (so using appengine-web.xml), right?
Ludo

On Monday, October 11, 2021 at 1:04:24 PM UTC-7 t...@terratrue.com wrote:

> I posted this a week ago, and I solved this issue - I just had to add a 
> `Class.forName("com.mysql.cj.jdbc.Driver")` call, which was not needed in 
> App Engine 8 with Java 8 when running in the cloud, but apparently it is 
> now required. Without this, the database connection pool just 
> cannot initialize, and all you get is a stack trace which ultimately ends 
> with "No suitable driver".
>
> Thanks,
> Tom Harris
>
>
> On Mon, Oct 11, 2021 at 6:45 AM Tom Harris  wrote:
>
>> Hi all, running into a very thorny issue that I have spent considerable 
>> time on now, without a working solution.
>>
>> We have a set of Java 8 AppEngine-based microservices that I am upgrading 
>> to Java 11 and Spring Boot. The services are using MySQL via Cloud SQL with 
>> Google's socket factory. Locally, we use the MySQL driver directly and the 
>> services run as expected.
>>
>> However when I try to deploy out to a cloud environment, when the code 
>> tries to instantiate the Hikari connection pool using Cloud SQL, I receive 
>> the dreaded "No suitable driver" error from the JDBC DriverManager.
>>
>> Our project includes these two dependencies:
>> 
>>   com.google.cloud.sql
>>   mysql-socket-factory-connector-j-8
>>   1.3.3
>> 
>> 
>>   mysql
>>   mysql-connector-java
>>   8.0.26
>> 
>>
>> Here is the code that is failing:
>> HikariConfig config = new HikariConfig();
>> config.addDataSourceProperty("useSSL", "false");
>> config.addDataSourceProperty("useUnicode", "true");
>> config.addDataSourceProperty("characterEncoding", "UTF-8");
>> config.setRegisterMbeans(true);
>>
>> config.setJdbcUrl("jdbc:mysql:///dbname");
>> config.setUsername(dbUser);
>> config.setPassword(dbPassword);
>> config.addDataSourceProperty("socketFactory", 
>> "com.google.cloud.sql.mysql.SocketFactory");
>> config.addDataSourceProperty("cloudSqlInstance", instanceConnectionName);
>>
>> return new HikariDataSource(config);
>>
>> And every time I try to fire up the service after deploying it to the 
>> cloud, I am seeing the error:
>>
>> Caused by: java.lang.RuntimeException: Failed to get driver instance for 
>> jdbcUrl=jdbc:mysql:///dbname  at 
>> com.zaxxer.hikari.util.DriverDataSource.(DriverDataSource.java:114) 
>> at com.zaxxer.hikari.pool.PoolBase.initializeDataSource(PoolBase.java:331) 
>> at com.zaxxer.hikari.pool.PoolBase.(PoolBase.java:114) at 
>> com.zaxxer.hikari.pool.HikariPool.(HikariPool.java:108) at 
>> com.zaxxer.hikari.HikariDataSource.(HikariDataSource.java:81) at 
>> com.terratrue.db.DataSources.initDataSourceForCloudEnvironmentForUser(DataSources.java:276)
>> Caused by: java.sql.SQLException: No suitable driver at 
>> java.sql/java.sql.DriverManager.getDriver(DriverManager.java:298) at 
>> com.zaxxer.hikari.util.DriverDataSource.(DriverDataSource.java:106) 
>> ... 53 common frames omitted"
>>
>> I have searched the internet for anything that would help resolve this 
>> issue, but I can't seem to find a relevant solution. The jar files for both 
>> libs are found in the app-staging folder, so I know they are getting 
>> deployed with the service.
>>
>> Does anyone have suggestions as to what to do next?
>>
>> Thanks,
>> Tom Harris
>>
>> -- 
>> 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-appengi...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/google-appengine/792e5183-dea5-458f-8c44-abf185d5f8ebn%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/cbbd3ab0-e63e-470f-8415-11a8b3c11697n%40googlegroups.com.

Re: [google-appengine] Re: Where can your run "legacy" Google App Engine (Java) applications?

[Ludovic Champenois]

Hi,
Ludo (from the Java App Engine team here).
Good news: as of today, we are providing to select customers a private 
preview access to a new Java11 GAE runtime with many of the App Engine APIs 
(com.google.appengine.api.*) support for easy GAE application upgrade from 
Java8.
This new Java11 runtime is an extension of the previous Java11 runtime 
 (which did not 
support the 'legacy' API), and it is based on Jetty 9.4 Web server and 
existing well know Java Web Apps, configured with appengine-web.xml (not 
app.yaml) under a WEB-INF/ web app directory, and same existing tooling 
(Maven, Gradle).
It would be great if existing Java8 GAE customers could try this private 
preview on a new version of their app (and obviously do not use it to 
server production traffic yet), and give us feedback!

Some of the major bundled GAE services the Private Preview now include:

   - - Memcache
   - - Datastore / Objectify with GAE Datastore
   - - URLfetch
   - - Blobstore
   - - Images
   - - Task Queues
   - - Users
   - - Mail


If you would like to register for the Private Preview, please fill out the 
Registration Form 

.  
Registering will get you access to the Private Preview documentation, which 
includes the full API docs for the runtime.

Thanks for trying it now and helping us fine tuning it so we can make it 
public soon!
Ludo

On Thursday, April 29, 2021 at 5:56:51 PM UTC-7 Wesley C (Google) wrote:

> At this time, you can run those applications with the "bundled services" 
> on our Java 8 App Engine runtime 
> . That's the 
> latest version w/the bundled services available. The other one is Java 11 
> but *without* bundled services 
> . Also see the 
> documentation 
> page highlighting the differences b/w both 1st and 2nd generation runtimes 
> .
>
> While we're committed to supporting legacy runtimes 
> , 
> we've also got guides to help developers move off bundled services so 
> they can upgrade to Java 11 
> . 
> We're planning additional resources to help users upgrade their apps, so 
> stay tuned for those. The first bunch for Python launched recently 
> ,
>  
> and we're planning equivalent resources for Java after all the Python ones 
> are done.
>
> Cheers,
> --Wesley
>
> On Thu, Apr 29, 2021 at 3:21 PM 'cyberquarks' via Google App Engine <
> google-a...@googlegroups.com> wrote:
>
>> Hi, our app is built on Google App Engine (Java) version 1.9.40 where all 
>> components are "integrated" into the runtime, the Datastore, the Task Queue 
>> etc. 
>>
>> On Friday, April 30, 2021 at 1:53:21 AM UTC+8 Elliott (Cloud Platform 
>> Support) wrote:
>>
>>>
>>> Hello,
>>>
>>> I understand that you would like to run a legacy Java App Engine 
>>> application on the infrastructure that exists currently in Google Cloud 
>>> Platform without modifying the existing project.
>>>
>>> I was able to find a document 
>>> , 
>>> which describes the legacy 8 version of Java still supported. What version 
>>> of Java are you using? Are you using Google App Standard or Google App Flex?
>>>
>>> I’m thinking that depending on your answer, you may choose to use 
>>> Containers in Google Cloud Run  to create 
>>> your environment but you indicated that you do not wish to modify your 
>>> project.
>>>
>>> So to provide more options, I would ask you to give detail about your 
>>> project.
>>>
>>>
>>>
>>> On Thursday, April 29, 2021 at 10:14:18 AM UTC-4 qqua...@protonmail.com 
>>> wrote:
>>>
 Where can you run GAE application built with "integrated" Datastore? 
 Meaning, those application that were build prior to Google platform making 
 the Datastore a separate service from the "core" GAE service. That is 
 without modifying the project.

 Can the current Google App Engine run "legacy" applications?

>>> -- 
>> 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-appengi...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/google-appengine/eeeaee50-0677-4f9d-9b54-a3206409e6fcn%40googlegroups.com
>>  
>> 

[google-appengine] Re: Exceeded soft memory limit - how to configure app.yaml for java 11

[Ludovic Champenois]

Hi,
I am not sure JAVA_TOOL_OPTIONS is supported (nor documented) for GAE 
Java11..
You have a few options:
1/ either move to
instance_class: F4
or
instance_class: F2

to get bigger instances.
Or manually control your entrypoint... I assume you deployed a jar, let's 
call it myjar.jar

the default entrypoint generated is:
java -jar myjar.jar

You can change it by adding this to your app.yaml:

entrypoint: java -XX:MaxRAM=200m -Xmx200m -jar myjar.jar

Some more doc 
at 
https://cloud.google.com/appengine/docs/standard/java11/runtime#application_startup

Hope this helps,
Ludo

On Wednesday, March 24, 2021 at 10:31:54 AM UTC-7 ra wrote:

> Hi,
>
> I am running in the issue "Exceeded soft memory limit of 256 MB with
> 283 MB after servicing 3 requests total.
> Consider setting a larger instance class in app.yaml.".
>
> My app.yaml looks like this:
>
> 
> runtime: java11
> instance_class: F1
>
> env_variables:
> JAVA_TOOL_OPTIONS: "-XX:MaxRAM=200m -Xmx200m"
> inbound_services:
> - warmup
>
> handlers:
> - url: /.*
> script: auto
> secure: always
> redirect_http_response_code: 301
>
> automatic_scaling:
> min_instances: 1
> max_instances: 2
>
> # Connecting to the cloud sql instance via app engine standard needs a
> vpc access connector:
> # 
> https://stackoverflow.com/questions/51328359/how-to-connect-to-cloud-sql-mysql-database-from-app-engine
> vpc_access_connector:
> name: "projects/locations/europe-west3/connectors/serverless-connector"
> ##
>
> My question now is: How can I tell the java runtime to NOT use more
> than the available RAM of the instance?
>
> Strangely: Anything I set in terms of -Xmx gets discarded and my app
> always has a max heap of 127.729664MB.
> So it seems my JAVA_TOOL_OPTIONS do not get picked up by the JVM.
>
> So where does the rest of the memory go?
> Or is this "something else" like the serverless connector in the
> container that consumes all the memory?
>
>
> Thanks!
>
>
> Raphael
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/55cf6419-9a2b-4fb5-a51d-086d084ade78n%40googlegroups.com.

[google-appengine] Re: Issues with App Engine migration from the legacy SDK (appcfg) to Cloud SDK

[Ludovic Champenois]

Hi, did you follow my advice from August 31rst?
If you could share your web.xml, appengine-web.xml and your gradle build 
files, I cam take a look, as it seems a missing dependency to have the 
correct jar to compile and deploy  with the missing class 
"com.google.api.server.spi.EndpointsServlet" declared in your web.xml I 
guess...

Happy to help with more info,
Ludo

On Sunday, September 6, 2020 at 2:30:41 PM UTC-7 aliza...@gmail.com wrote:

> Anyone cares to respond?  We're seriously considering switching to a 
> competitor of Google App Engine due to this poorly executed forced 
> migration and poor customer support.  That's thousands of dollars of lost 
> revenue per year for Google App Engine.  This is your last chace to get 
> your act together, apart from the very bad press for GCP!
>
> On Tuesday, September 1, 2020 at 9:41:18 PM UTC-4 Ramtin Alizadegan wrote:
>
>> yananc, this feature used to exist in Android Studio with the integration 
>> with App Engine SDK.  However, it's been REMOVED by the new migration 
>> to Cloud SDK!  I'd imagine a proper migration would have guaranteed a 
>> seamless transition first.  *This app-engine project used to be deployed 
>> just fine from Android Studio.*
>>
>> Our ‘appengine-web.xml’ doesn't really have much in it.  How do we add 
>> the Jetty configurations to it?  This is what our 'web.xml' looks like:
>>
>> 
>> > xmlns="http://java.sun.com/xml/ns/javaee;
>> xmlns:web="http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd;
>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>> version="2.5"
>> xsi:schemaLocation="http://java.sun.com/xml/ns/javaee 
>> http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd;>
>>
>> 
>> 
>> EndpointsServlet
>> com.google.api.server.spi.EndpointsServlet
>> 
>> 
>> services
>> ..list of services
>> 
>> 
>> 
>> restricted
>> false
>> 
>> 
>> 
>> 
>> EndpointsServlet
>> /_ah/api/*
>> 
>> 
>> 
>> 
>>
>> It looks like our gradle is not correctly processed.  Any help would be 
>> appreciated especially since Google Support seems unresponsive after this 
>> botched migration.
>> On Monday, August 31, 2020 at 2:33:54 PM UTC-4 yananc wrote:
>>
>>> Hello, 
>>>
>>> Thank you for your response. I would suggest you to follow the link 
>>>  to file a 
>>> Feature Request on the support for Android Studio so our Engineering team 
>>> can further investigate. However, there is no ETA or if the feature will be 
>>> implemented.
>>> For the deployment issue, based on the provided information, it would be 
>>> helpful to review the ‘appengine-web.xml’ to make sure all the 
>>> configuration is correct, especially the configuration about how Jetty is 
>>> started.
>>>
>>> On Saturday, August 29, 2020 at 12:32:46 PM UTC-4 aliza...@gmail.com 
>>> wrote:
>>>
 Hi Manpreet,

 Thank you for your response.  We already know that GCP does not support 
 Android Studio.  But why?  If GCP wants to compete with AWS, Azure, 
 Oracle, 
 etc. it needs to move in the direction of providing more cenvenience, not 
 move away from convenience...

 Any way, we contacted Google Cloud Platform Support at <
 cloud-proactive-comms+...@google.com> but we didn't receive any 
 responses.

 We're following this documentation:   
 https://cloud.google.com/appengine/docs/standard/java/sdk-gcloud-migration#migrate_config_script
   

 Our Java Android app-engine project uses gradle and datanucleus.  (It 
 doesn't use Maven build tool as there's no pom.xml file in our entire 
 project.)  We have already created the cron.yaml and index.yaml files and 
 they work correctly from within Android Studio.

 On Friday, August 28, 2020 at 10:58:10 PM UTC-4 Manpreet Sidhu (Google 
 Cloud Support) wrote:

>
> As listed on the “Migrating to the Cloud SDK-based Gradle plugin 
> ”
>  
> document, Android Studio is not supported. In order to run and deploy 
> your 
> applications, you need to directly invoke Gradle.
>
> Can you please shed light as to how you contacted the App Engine 
> Support in the past (Google Groups, Support Plan, other community 
> channels, 
> ect...)? Can you also please share any documentation that you are 
> following? The documents will allow us and the community to see how you 
> are 
> doing the migration and why it isn’t successfully deploying.
> On Friday, August 28, 2020 at 12:53:03 PM UTC-4 aliza...@gmail.com 
> wrote:
>
>> We are trying to migrate our Java Android app-engine project to the 
>> Cloud SDK based app-engine as Google requested and quite honestly, we 
>> find 
>> it very inconvenient and silly compared to deploying it from 
>> Android Studio...  Why is the Cloud SDK app-engine integration with 
>> Android 

Re: [google-appengine] Re: Issues with App Engine migration from the legacy SDK (appcfg) to Cloud SDK

['Ludovic Champenois' via Google App Engine]

It seems it complain about a missing 
com.google.api.server.spi.EndpointsServlet servlet defined in the 
web.xml... Maybe you did not add the dependency?


Can you see if 
https://cloud.google.com/endpoints/docs/frameworks/java/migrating is 
helping you, especially the Gradle section?


Cheers,

Ludo

On 8/31/20 11:33 AM, 'yananc' via Google App Engine wrote:


Hello,

Thank you for your response. I would suggest you to follow the link 
 to file a 
Feature Request on the support for Android Studio so our Engineering 
team can further investigate. However, there is no ETA or if the 
feature will be implemented.


For the deployment issue, based on the provided information, it would 
be helpful to review the ‘appengine-web.xml’ to make sure all the 
configuration is correct, especially the configuration about how Jetty 
is started.


On Saturday, August 29, 2020 at 12:32:46 PM UTC-4 aliza...@gmail.com 
wrote:


Hi Manpreet,

Thank you for your response.  We already know that GCP does not
support Android Studio.  But why?  If GCP wants to compete with
AWS, Azure, Oracle, etc. it needs to move in the direction of
providing more cenvenience, not move away from convenience...

Any way, we contacted Google Cloud Platform Support at
 but we didn't receive any
responses.

We're following this documentation:

https://cloud.google.com/appengine/docs/standard/java/sdk-gcloud-migration#migrate_config_script


Our Java Android app-engine project uses gradle and datanucleus. 
(It doesn't use Maven build tool as there's no pom.xml file in our
entire project.)  We have already created the cron.yaml and
index.yaml files and they work correctly from within Android Studio.

On Friday, August 28, 2020 at 10:58:10 PM UTC-4 Manpreet Sidhu
(Google Cloud Support) wrote:


As listed on the “Migrating to the Cloud SDK-based Gradle
plugin

”
document, Android Studio is not supported. In order to run and
deploy your applications, you need to directly invoke Gradle.

Can you please shed light as to how you contacted the App
Engine Support in the past (Google Groups, Support Plan, other
community channels, ect...)? Can you also please share any
documentation that you are following? The documents will allow
us and the community to see how you are doing the migration
and why it isn’t successfully deploying.
On Friday, August 28, 2020 at 12:53:03 PM UTC-4
aliza...@gmail.com wrote:

We are trying to migrate our Java Android app-engine
project to the Cloud SDK based app-engine as Google
requested and quite honestly, we find it very
inconvenient and silly compared to deploying it from
Android Studio...  Why is the Cloud SDK app-engine
integration with Android Studio not provided by default as
before?  Any way, when we try to deploy this app-engine
project by running the command:

>gcloud app deploy .\appengine-web.xml --version 3
--no-promote

The application fails to start with this error in the
cloud logs:

Uncaught exception from servlet
MultiException[javax.servlet.UnavailableException: Class
loading error for holder

EndpointsServlet@e968f07==com.google.api.server.spi.EndpointsServlet,jsp=null,order=-1,inst=false,
javax.servlet.UnavailableException: Class loading error
for holder

org.eclipse.jetty.servlet.ServletHandler.initialize(ServletHandler.java:863)
at

org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:349)
at

org.eclipse.jetty.webapp.WebAppContext.startWebapp(WebAppContext.java:1406)
at

com.google.apphosting.runtime.jetty9.AppEngineWebAppContext.startWebapp(AppEngineWebAppContext.java:175)
at

org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1368)
at

org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:778)
at

org.eclipse.jetty.servlet.ServletContextHandler.doStart(ServletContextHandler.java:262)
at

org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:522)
at

com.google.apphosting.runtime.jetty9.AppEngineWebAppContext.doStart(AppEngineWebAppContext.java:120)
at

org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at

com.google.apphosting.runtime.jetty9.AppVersionHandlerMap.createHandler(AppVersionHandlerMap.java:240)
 

Re: [google-appengine] Re: Bigger app sizes with Cloud SDK than with AppCfg

['Ludovic Champenois' via Google App Engine]

There is only 1 staging logic, inside appcfg tooling, which is used (as 
is) in the cloud SDK, so staging is technically the same.


In appcfg, it uses a temporary directory (deleted at the end unless you 
use a flag to retain the upload dir).


In cloud SDK and new plugins, the default location is visible to the 
customer (appengine-staging) and can be overwritten via a flag.


There is no reason at all I understand about why app size would differ 
based on the tooling. Maybe different default flags in compilers?


If you have a specific project that shows this behavior, I am all ears.

Ludo

On 1/30/20 11:41 PM, 'DIEGO GARCIA TEBA' via Google App Engine wrote:

Thanks Olu!

I'll do it.

Regards,
Diego

On Thursday, January 30, 2020 at 8:21:20 PM UTC+1, Olu wrote:

Hi, Diego

There are a number of reasons that could account for the change in
the Application size. In fact, there was a similar report in the
past where the size of the application version using the Maven
CloudSDK plugin actually was found to be lesser compared to the
version from AppCfg. To evaluate specifically your version, I
suggest you open an issue[1], with which a Support Engineer would
be able to review your project and evaluate the specific App
Engine versions to determine exactly what may be causing the
difference in sizes for your application.

[1]https://developers.google.com/issue-tracker/#public_users


--
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/b1024ee7-3f1b-475c-b89f-6c0696467acd%40googlegroups.com 
.


--
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/3eea20e3-c4a7-fe0f-7467-ea315acc6cdd%40google.com.

Re: [google-appengine] issue of migration from Java8 to Java 11 for app engine standard model

['Ludovic Champenois' via Google App Engine]

Hi,

AppEngine Java11 does not have support for the local appserver emulator, 
as any type of workload can be used (not a Jetty Servlet Server anymore).


So for Java11, the DevAppServerRunner run action is not available (or 
produces this type of error). Only the deployment action is possible.


In order to test locally your application, you would have to locally run 
the equivalent of your entrypoint (in app.yaml). A default one is a 
command like


java -jar myjar.jar if this is your application in the jar.

Cheers,

Ludo

On 11/19/19 7:04 PM, Han Ju Kim wrote:
Hi I'm trying to migrate existing app engine standard model (JDK8) to 
Java11 according to the guide at Google cloud
https://cloud.google.com/appengine/docs/standard/java11/java-differences 



There is no issue on compile, but we I try to run on local development 
server it generates this error. I'm using maven and tried "maven 
package appengine:run".

Please find my error as below

Any guide and information will be appreciated.



Nov 20, 2019 3:53:17 PM 
com.google.cloud.tools.appengine.operations.DevAppServerRunner run
INFO: submitting command: C:\Program 
Files\Java\openjdk-11.0.5-1\bin\java.exe -Xms2048m -Xmx8092m 
-Duse_jetty9_runtime=true -D--enable_all_permissions=true 
-Dappengine.sdk.root=C:\Users\hkim\AppData\Local\google\ct4j-cloud-sdk\LATEST\google-cloud-sdk\platform\google_appengine\google\appengine\tools\java 
-cp 
C:\Users\hkim\AppData\Local\google\ct4j-cloud-sdk\LATEST\google-cloud-sdk\platform\google_appengine\google\appengine\tools\java\lib\appengine-tools-api.jar 
com.google.appengine.tools.development.DevAppServerMain 
--application=mywms --allow_remote_shutdown --disable_update_check 
--no_java_agent D:\\Iridium\target\iridium-1.0.0
[INFO] GCLOUD: WARNING: An illegal reflective access operation has 
occurred
[INFO] GCLOUD: WARNING: Illegal reflective access by 
com.google.appengine.tools.development.StreamHandlerFactory 
(file:/C:/Users/hkim/AppData/Local/google/ct4j-cloud-sdk/LATEST/google-cloud-sdk/platform/google_appengine/google/appengine/tools/java/lib/impl/appengine-local-runtime.jar) 
to method java.net.URL.getURLStreamHandler(java.lang.String)
[INFO] GCLOUD: WARNING: Please consider reporting this to the 
maintainers of com.google.appengine.tools.development.StreamHandlerFactory
[INFO] GCLOUD: WARNING: Use --illegal-access=warn to enable warnings 
of further illegal reflective access operations
[INFO] GCLOUD: WARNING: All illegal access operations will be denied 
in a future release
[INFO] GCLOUD: 
com.google.apphosting.utils.config.AppEngineConfigException: Invalid 
configuration
[INFO] GCLOUD:  at 
com.google.appengine.tools.development.DevAppServerImpl.reportDeferredConfigurationException(DevAppServerImpl.java:432)
[INFO] GCLOUD:  at 
com.google.appengine.tools.development.DevAppServerImpl.doStart(DevAppServerImpl.java:233)
[INFO] GCLOUD:  at 
com.google.appengine.tools.development.DevAppServerImpl.access$000(DevAppServerImpl.java:44)
[INFO] GCLOUD:  at 
com.google.appengine.tools.development.DevAppServerImpl$1.run(DevAppServerImpl.java:220)
[INFO] GCLOUD:  at 
com.google.appengine.tools.development.DevAppServerImpl$1.run(DevAppServerImpl.java:218)
[INFO] GCLOUD:  at 
java.base/java.security.AccessController.doPrivileged(Native Method)
[INFO] GCLOUD:  at 
com.google.appengine.tools.development.DevAppServerImpl.start(DevAppServerImpl.java:218)
[INFO] GCLOUD:  at 
com.google.appengine.tools.development.DevAppServerMain$StartAction.apply(DevAppServerMain.java:404)
[INFO] GCLOUD:  at 
com.google.appengine.tools.util.Parser$ParseResult.applyArgs(Parser.java:45)
[INFO] GCLOUD:  at 
com.google.appengine.tools.development.DevAppServerMain.run(DevAppServerMain.java:257)
[INFO] GCLOUD:  at 
com.google.appengine.tools.development.DevAppServerMain.main(DevAppServerMain.java:248)
[INFO] GCLOUD: Caused by: 
com.google.apphosting.utils.config.AppEngineConfigException: Line 2, 
column 4: Unable to find property 'env' on class: 
com.google.apphosting.utils.config.AppYaml
[INFO] GCLOUD:  at 
com.google.apphosting.utils.config.AppYaml.parse(AppYaml.java:1491)
[INFO] GCLOUD:  at 
com.google.apphosting.utils.config.AppYamlProcessor.convert(AppYamlProcessor.java:42)
[INFO] GCLOUD:  at 
com.google.apphosting.utils.config.EarHelper.readWebModule(EarHelper.java:171)
[INFO] GCLOUD:  at 
com.google.appengine.tools.development.ApplicationConfigurationManager$WarModuleConfigurationHandle.readConfiguration(ApplicationConfigurationManager.java:416)
[INFO] GCLOUD:  at 
com.google.appengine.tools.development.ApplicationConfigurationManager.(ApplicationConfigurationManager.java:157)
[INFO] GCLOUD:  at 
com.google.appengine.tools.development.ApplicationConfigurationManager.newWarConfigurationManager(ApplicationConfigurationManager.java:99)
[INFO] GCLOUD:  at 

[google-appengine] Re: AppEngine Java SDK 1.9.73 is not available in Maven central

['Ludovic Champenois' via Google App Engine]

Hi,
It should be online now,
Cheers,


On Thursday, March 28, 2019 at 5:17:37 AM UTC-7, Yuri Sergiichuk wrote:
>
> Hi all.
>
> I've noticed that the 1.9.73 version of the AppEngine Java SDK was 
> released 
>  back 
> on March 26, but it is not yet available in the Maven Central repository. 
> And it is not the first time 
>  the 
> SDK for Java is not available in the Maven repository.
>

-- 
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 https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/a5ba9b9a-325a-4a01-9075-10b3e2a26c8c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: GAE java8 switch by simply putting runtime java8 fails:

['Ludovic Champenois' via Google App Engine]

Hi,
Sorry to see the error message...
It seems you are using Cloud Endpoints v1?
v1 is now deprecated for Java7 and not supported for Java8... Can you try 
to upgrade to Cloud Endpoints v2?

See 
https://cloud.google.com/endpoints/docs/frameworks/legacy/v1/java/migrating
https://cloud.google.com/appengine/docs/standard/java/release-notes for the 
release notes.

Ludo

On Sunday, September 17, 2017 at 8:01:13 AM UTC-7, Frank Nestel wrote:
>
> My tiny app usually displays no errors at all, below exceptions look all 
> bad and happen every 20 seconds with a unused version:
>
> Here is the log link
>
> https://console.cloud.google.com/logs/viewer?project=badgers-987=0=false=2017-09-17T14%3A54%3A17.984979000Z=gae_app%2Fmodule_id%2Fdefault%2Fversion_id%2F39-java8=projects%2Fbadgers-987%2Flogs%2Fappengine.googleapis.com%252Frequest_log=resource.type%3D%22gae_app%22%0Aresource.labels.zone%3D%22eu2%22%0Aresource.labels.project_id%3D%22badgers-987%22%0Aresource.labels.version_id%3D%2239-java8%22%0Aresource.labels.module_id%3D%22default%22%0Atimestamp%3D%222017-09-17T14%3A54%3A17.984979000Z%22%0AinsertId%3D%2259be8c9a00068348f172be0c%22
>
> Copies of exceptions:
> exception 1:
> 16:55:24.315 com.google.apphosting.runtime.jetty9.JettyLogger warn: 
> /_ah/spi/BackendService.getApiConfigs (JettyLogger.java:29 
> )
>  
> java.lang.NullPointerException at 
> com.google.api.server.spi.SystemServiceServlet.execute(
> SystemServiceServlet.java:100 
> )
>  
> at com.google.api.server.spi.SystemServiceServlet.doPost(
> SystemServiceServlet.java:71 
> )
>  
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:707) at 
> javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at 
> org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:848) at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1772)
>  
> at 
> com.google.apphosting.utils.servlet.ParseBlobUploadFilter.doFilter(ParseBlobUploadFilter.java:125)
>  
> at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1759)
>  
> at 
> com.google.apphosting.runtime.jetty9.SaveSessionFilter.doFilter(SaveSessionFilter.java:37)
>  
> at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1759)
>  
> at 
> com.google.apphosting.utils.servlet.JdbcMySqlConnectionCleanupFilter.doFilter(JdbcMySqlConnectionCleanupFilter.java:60)
>  
> at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1759)
>  
> at 
> com.google.apphosting.utils.servlet.TransactionCleanupFilter.doFilter(TransactionCleanupFilter.java:48)
>  
> at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1759)
>  
> at 
> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:582) 
> at 
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143) 
> at 
> org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:524) 
> at 
> org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226)
>  
> at 
> org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1180)
>  
> at 
> org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:512) 
> at 
> org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)
>  
> at 
> org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1112)
>  
> at 
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141) 
> at 
> com.google.apphosting.runtime.jetty9.AppVersionHandlerMap.handle(AppVersionHandlerMap.java:297)
>  
> at 
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134)
>  
> at org.eclipse.jetty.server.Server.handle(Server.java:534) at 
> org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:320) at 
> com.google.apphosting.runtime.jetty9.RpcConnection.handle(RpcConnection.java:219)
>  
> at 
> com.google.apphosting.runtime.jetty9.RpcConnector.serviceRequest(RpcConnector.java:81)
>  
> at 
> com.google.apphosting.runtime.jetty9.JettyServletEngineAdapter.serviceRequest(JettyServletEngineAdapter.java:108)
>  
> at 
> com.google.apphosting.runtime.JavaRuntime$RequestRunnable.dispatchServletRequest(JavaRuntime.java:650)
>  
> at 
> com.google.apphosting.runtime.JavaRuntime$RequestRunnable.dispatchRequest(JavaRuntime.java:612)
>  
> at 
> 

Re: [google-appengine] Stability of Java 8 on Standard Environment

['Ludovic Champenois' via Google App Engine]

Hi,

Thanks for the feedback.

A newer push (soon) will address the load time issue that is related to 
a wrong timeout value,


Cheers,

Ludo


On 7/11/17 6:00 PM, Thomas Wiradikusuma wrote:

I noticed that my app is 0.5mb smaller but takes longer to load and uses more 
memory. This is simply by comparing data from GCP console (open new tab of same 
console page, refresh, see what's different).



--
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 https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/0d4f8b37-63ab-457a-b2db-2e113abb236f%40google.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: Google App Engine standard now supports Java 8

['Ludovic Champenois' via Google App Engine]

On 6/29/17 5:43 AM, Attila-Mihaly Balazs wrote:

+1! Party! :-)

Now could we please get connections from GAE standard to the Postgres 
instances? :-)
Sure, can you try 
https://github.com/GoogleCloudPlatform/java-docs-samples/tree/master/appengine-java8/postgres 
and see if it works for you?


Ludo

--
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 https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/1f337b5f-195c-445d-b5d8-1b831f934117%40googlegroups.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 https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/88958243-08fb-4aa0-e72b-3ddeadf23416%40google.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Endpoints build issue GAE 1.9.44

['ludovic Champenois' via Google App Engine]

1.9.46 is now out,

Ludo


On 10/19/16 3:00 PM, Paul Mazzuca wrote:

Anyone else encounter the following issue when updating GAE?

Updated from 1.9.42 -> 1.9.44 today. Did not change anything except 
the version.  I received the following error:


[ERROR] Failed to execute goal 
com.google.appengine:appengine-maven-plugin:1.9.44:endpoints_get_discovery_doc 
(default) on project oasis-endpoints: Execution default of goal 
com.google.appengine:appengine-maven-plugin:1.9.44:endpoints_get_discovery_doc 
failed: An API incompatibility was encountered while executing 
com.google.appengine:appengine-maven-plugin:1.9.44:endpoints_get_discovery_doc: 
java.lang.NoSuchMethodError: 
com.google.common.reflect.TypeToken.isSupertypeOf(Ljava/lang/reflect/Type;)Z


--
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 https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/230f6d12-7fb7-46ec-91a9-6771cd2f1201%40googlegroups.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 https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/4d7a8658-8a34-b12c-108a-cd05a30783d5%40google.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Endpoints build issue GAE 1.9.44

['ludovic Champenois' via Google App Engine]

Hi,


So it seems there is a bad dependency to guava 18 instead of 19.

Will be fixed in the next release.

Ludo


On 10/19/16 3:00 PM, Paul Mazzuca wrote:

Anyone else encounter the following issue when updating GAE?

Updated from 1.9.42 -> 1.9.44 today. Did not change anything except 
the version.  I received the following error:


[ERROR] Failed to execute goal 
com.google.appengine:appengine-maven-plugin:1.9.44:endpoints_get_discovery_doc 
(default) on project oasis-endpoints: Execution default of goal 
com.google.appengine:appengine-maven-plugin:1.9.44:endpoints_get_discovery_doc 
failed: An API incompatibility was encountered while executing 
com.google.appengine:appengine-maven-plugin:1.9.44:endpoints_get_discovery_doc: 
java.lang.NoSuchMethodError: 
com.google.common.reflect.TypeToken.isSupertypeOf(Ljava/lang/reflect/Type;)Z


--
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 https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/230f6d12-7fb7-46ec-91a9-6771cd2f1201%40googlegroups.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 https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/37439b9f-c407-7d48-2781-43b01c119966%40google.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Endpoints build issue GAE 1.9.44

['ludovic Champenois' via Google App Engine]

Sorry about that. Investigating.

Meanwhile, move back to 42, just for Endpoints generation if you can.

Thanks.


On 10/19/16 3:00 PM, Paul Mazzuca wrote:

Anyone else encounter the following issue when updating GAE?

Updated from 1.9.42 -> 1.9.44 today. Did not change anything except 
the version.  I received the following error:


[ERROR] Failed to execute goal 
com.google.appengine:appengine-maven-plugin:1.9.44:endpoints_get_discovery_doc 
(default) on project oasis-endpoints: Execution default of goal 
com.google.appengine:appengine-maven-plugin:1.9.44:endpoints_get_discovery_doc 
failed: An API incompatibility was encountered while executing 
com.google.appengine:appengine-maven-plugin:1.9.44:endpoints_get_discovery_doc: 
java.lang.NoSuchMethodError: 
com.google.common.reflect.TypeToken.isSupertypeOf(Ljava/lang/reflect/Type;)Z


--
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 https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/230f6d12-7fb7-46ec-91a9-6771cd2f1201%40googlegroups.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 https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/acfd0c73-7879-b6af-fff4-c5e1bcbd201d%40google.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: Java 8 and the App Engine

['ludovic Champenois' via Google App Engine]

On 5/27/16 2:24 PM, Stefan Falk wrote:

It appears that Java 8 is still not supported ..

I am currently developing a GWT application and I compile both, the 
client and the server, against Java 8 .. I recently discovered that if 
I deploy my application to GAE that I get the "Unsupported major.minor 
version 52.0" exception on every request :-Z


Any idea how long it will take until Java 8 is going to be supported?
We are getting close, finalizing the necessary security sandbox changes. 
This is the hardest part, I hope you'll like what you can do on it.

Meanwhile, you can investigate the flexible environment.
Ludo


BR;

On Saturday, 23 May 2015 01:08:45 UTC+2, Ludovic Champenois wrote:

Hi,
While I can not predict when it will come up, I can tell you we
are working on enable Java 8 to the good old App Engine (not that
old!!!).
We want to make it as secure as our current Java 7 runtime, and
once we feel we are ready, we'll push it.

For now,it is only possible on Managed VMs, as a custom runtime.

Ludo (TML Google App Engine Runtimes)


On Friday, May 22, 2015 at 2:35:39 AM UTC-7, ra wrote:

Hi there,


I am wondering if anyone can comment on whether it is even
planned to
implement Java 8 support on good old App Engine.
There is a feature request open for more than 2 years now:
https://code.google.com/p/googleappengine/issues/detail?id=9537
<https://code.google.com/p/googleappengine/issues/detail?id=9537>

It feels weird that App Engine only supports a Java version
where the official Oracle JDK is end of life.


Thanks for any enlightenment!



Raphael

--
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 
<mailto:google-appengine+unsubscr...@googlegroups.com>.
To post to this group, send email to google-appengine@googlegroups.com 
<mailto:google-appengine@googlegroups.com>.

Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/f5cb8f0e-9527-4384-9730-6544d816053a%40googlegroups.com 
<https://groups.google.com/d/msgid/google-appengine/f5cb8f0e-9527-4384-9730-6544d816053a%40googlegroups.com?utm_medium=email_source=footer>.

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 https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/beea5eae-36b6-341c-7731-914e07536a92%40google.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: AppEngine Endpoints Issue?

['ludovic Champenois' via Google App Engine]

Fixed in 1.9.38.

Ludo


On 5/28/16 7:26 AM, Shruti Bilgundi wrote:

Facing the same issue.. Does it work with the version 1.9.36?

On Sunday, May 22, 2016 at 7:04:19 AM UTC+5:30, Ludovic Champenois wrote:

I think the issue got fixed in 1.9.38 that should be out shortly.
Meanwhile, you can revert to 1.9.36,
Ludo

On 5/21/16 9:00 AM, Olukorede Aguda wrote:

Also facing this issue. Any update? It doesn't help that we're
running into this while evaluating adoption of AppEngine :(

On Tuesday, 10 May 2016 17:53:09 UTC+1, Paul Mazzuca wrote:

When running the following EndPoints example with GAE 1.9.37
as so,

|git clone

https://github.com/GoogleCloudPlatform/appengine-endpoints-helloworld-java-maven

<http://github.com/GoogleCloudPlatform/appengine-endpoints-helloworld-java-maven>|

#change the version in the POM to 1.9.37

|
< code>
mvn appengine:devserver
|

I receive the following error:

[ERROR] Failed to execute goal

com.google.appengine:appengine-maven-plugin:1.9.37:endpoints_get_discovery_doc
(default) on project helloworld: Execution default of goal

com.google.appengine:appengine-maven-plugin:1.9.37:endpoints_get_discovery_doc
failed: A required class was missing while executing

com.google.appengine:appengine-maven-plugin:1.9.37:endpoints_get_discovery_doc:

com/google/appengine/repackaged/com/google/api/client/repackaged/org/apache/commons/codec/binary/StringUtils

Could an essential EndPoints class have been removed in the
latest GAE release, or am I missing something?
||
||
||

-- 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-appengi...@googlegroups.com . To post to this
group, send email to google-a...@googlegroups.com .
Visit this group at
https://groups.google.com/group/google-appengine
<https://groups.google.com/group/google-appengine>. To view this
discussion on the web visit

https://groups.google.com/d/msgid/google-appengine/f00f2fd4-ea8e-47ec-9c93-a6541174586b%40googlegroups.com

<https://groups.google.com/d/msgid/google-appengine/f00f2fd4-ea8e-47ec-9c93-a6541174586b%40googlegroups.com?utm_medium=email_source=footer>.
For more options, visit https://groups.google.com/d/optout
<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 
<mailto:google-appengine+unsubscr...@googlegroups.com>. To post to 
this group, send email to google-appengine@googlegroups.com 
<mailto:google-appengine@googlegroups.com>. Visit this group at 
https://groups.google.com/group/google-appengine. To view this 
discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/aaaf2d78-4a8a-482d-98cf-58f5ab5c6f45%40googlegroups.com 
<https://groups.google.com/d/msgid/google-appengine/aaaf2d78-4a8a-482d-98cf-58f5ab5c6f45%40googlegroups.com?utm_medium=email_source=footer>. 
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 https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/0a71766d-7e08-9741-f248-e22c16727db6%40google.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: AppEngine Endpoints Issue?

['ludovic Champenois' via Google App Engine]

I think the issue got fixed in 1.9.38 that should be out shortly.
Meanwhile, you can revert to 1.9.36,
Ludo

On 5/21/16 9:00 AM, Olukorede Aguda wrote:
Also facing this issue. Any update? It doesn't help that we're running 
into this while evaluating adoption of AppEngine :(


On Tuesday, 10 May 2016 17:53:09 UTC+1, Paul Mazzuca wrote:

When running the following EndPoints example with GAE 1.9.37 as so,

|git clone

https://github.com/GoogleCloudPlatform/appengine-endpoints-helloworld-java-maven

|

#change the version in the POM to 1.9.37

|
|
mvn appengine:devserver
|
|

I receive the following error:

[ERROR] Failed to execute goal

com.google.appengine:appengine-maven-plugin:1.9.37:endpoints_get_discovery_doc
(default) on project helloworld: Execution default of goal

com.google.appengine:appengine-maven-plugin:1.9.37:endpoints_get_discovery_doc
failed: A required class was missing while executing

com.google.appengine:appengine-maven-plugin:1.9.37:endpoints_get_discovery_doc:

com/google/appengine/repackaged/com/google/api/client/repackaged/org/apache/commons/codec/binary/StringUtils

Could an essential EndPoints class have been removed in the latest
GAE release, or am I missing something?
||
||
||

-- 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 
https://groups.google.com/group/google-appengine. To view this 
discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/f00f2fd4-ea8e-47ec-9c93-a6541174586b%40googlegroups.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 https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/57410C84.9050205%40google.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: AppEngine Endpoints Issue?

['ludovic Champenois' via Google App Engine]

Investigating,
Thanks for the detailled info,
Ludo

On 5/11/16 8:14 AM, Paul Mazzuca wrote:
I think this is a bug in GAE. I also think that it can affect deployed 
instances since GAE uses the latest version in production.  I would be 
interested in knowing if there is a workaround or if we have to wait 
for the next version?


On Tuesday, May 10, 2016 at 9:24:50 PM UTC-7, Shian Wu wrote:


I got same problem when using GAE java 1.9.37.
It is work with GAE java 1.9.34 before.

After compare source of
com.google.appengine.repackaged.com.google.api.client.util.StringUtils
, I found it is a little different.

In 1.9.34
|


packagecom.google.appengine.repackaged.com.google.api.client.util;publicclassStringUtils{publicstaticfinalStringLINE_SEPARATOR

=System.getProperty("line.separator");publicstaticbyte[]getBytesUtf8(Stringstring){returncom.google.appengine.repackaged.org.apache.commons.codec.binary.StringUtils.getBytesUtf8(string);}publicstaticStringnewStringUtf8(byte[]bytes){returncom.google.appengine.repackaged.org.apache.commons.codec.binary.StringUtils.newStringUtf8(bytes);}privateStringUtils(){}}

|
In 1.9.37
|


packagecom.google.appengine.repackaged.com.google.api.client.util;publicclassStringUtils{publicstaticfinalStringLINE_SEPARATOR

=System.getProperty("line.separator");publicstaticbyte[]getBytesUtf8(Stringstring){returncom.google.appengine.repackaged.com.google.api.client.repackaged.org.apache.commons.codec.binary.StringUtils.getBytesUtf8(string);}publicstaticStringnewStringUtf8(byte[]bytes){returncom.google.appengine.repackaged.com.google.api.client.repackaged.org.apache.commons.codec.binary.StringUtils.newStringUtf8(bytes);}privateStringUtils(){}}

|
And I can not find

com.google.appengine.repackaged.com.google.api.client.repackaged.org.apache.commons.codec.binary.StringUtils
in GAE java 1.9.37
I think this is why it can't work.
Is this a bug or something I miss when upgrade to GAE java 1.9.37
? On Wednesday, May 11, 2016 at 12:53:09 AM UTC+8, Paul Mazzuca wrote:

When running the following EndPoints example with GAE 1.9.37
as so,

|git clone

https://github.com/GoogleCloudPlatform/appengine-endpoints-helloworld-java-maven

|

#change the version in the POM to 1.9.37

|
|
mvn appengine:devserver
|
|

I receive the following error:

[ERROR] Failed to execute goal

com.google.appengine:appengine-maven-plugin:1.9.37:endpoints_get_discovery_doc
(default) on project helloworld: Execution default of goal

com.google.appengine:appengine-maven-plugin:1.9.37:endpoints_get_discovery_doc
failed: A required class was missing while executing

com.google.appengine:appengine-maven-plugin:1.9.37:endpoints_get_discovery_doc:

com/google/appengine/repackaged/com/google/api/client/repackaged/org/apache/commons/codec/binary/StringUtils

Could an essential EndPoints class have been removed in the
latest GAE release, or am I missing something?
||
||
||

-- 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 
https://groups.google.com/group/google-appengine. To view this 
discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/5182da26-f473-49d8-a0bc-74042c8bf591%40googlegroups.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 https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/57334EB1.8080900%40google.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] GAE Java FE env deployment issue

['ludovic Champenois' via Google App Engine]

On 4/3/16 11:16 AM, Deepak Singh wrote:

Thanks Ludovic. Got this idea and worked on it.

However when we run the gcloud preview app deploy /app.yaml, throws 
following error


INFO: Attempting refresh to obtain initial access_token
INFO: Refreshing access_token
WARNING: If this is your first deployment, please try again.
ERROR: (gcloud.preview.app.deploy) Server responded with code [400]:
  Bad Request Unexpected HTTP status 400.
  Failed Project Preparation (app_id='s~'). App Engine service
account has insufficient permissions for project. Developer or owner 
required.



All of the permissions are enabled in console but still the error 
persists. Could you pls help on the same ?

Do a gcloud config list
and see if the account listed here is an owner.
Ludo



On Sun, Apr 3, 2016 at 4:07 AM, 'ludovic Champenois' via Google App 
Engine <google-appengine@googlegroups.com 
<mailto:google-appengine@googlegroups.com>> wrote:


So I guess you've been using the appcfg.sh tool to deploy a web
app built the way you want...(maybe via Ant?)

Continue to do that, but change the flags used by appcfg and
replace the update subcommand with the stage sub command. The
stage subcommand takes an extra param at the end that is the
location of an empty staging directory that will be populated with
correct content.
Then you can use the Cloud SDK to deploy this staging directory
(pointing to it's app.yaml at the root).
gcloud preview app deploy stagingDir/app.yaml
Ludo


On 4/2/16 11:59 AM, Deepak Singh wrote:

Hi,

I have a running java web app on gae sandbox for last 3 years.
Now would like to migrate it to GAE flexible env. We found the
documents which recommends to use maven and build and deploy. We
dont use maven in our app and would like not to use. So, is there
any convenient way to deploy the app on FE without a maven
project architecture ? Pls sugeest.

-- 
Tech
-- 
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
<mailto:google-appengine+unsubscr...@googlegroups.com>.
To post to this group, send email to
google-appengine@googlegroups.com
<mailto:google-appengine@googlegroups.com>.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit

https://groups.google.com/d/msgid/google-appengine/CAF6cnzbYypRrMJZzGihN6CGHGJdR7qrjN6U%2ByyBoP23CXAQGXw%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
<mailto:google-appengine+unsubscr...@googlegroups.com>.
To post to this group, send email to
google-appengine@googlegroups.com
<mailto:google-appengine@googlegroups.com>.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit

https://groups.google.com/d/msgid/google-appengine/570049B4.4030807%40google.com

<https://groups.google.com/d/msgid/google-appengine/570049B4.4030807%40google.com?utm_medium=email_source=footer>.
For more options, visit https://groups.google.com/d/optout.




--
Deepak Singh
--
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 
<mailto:google-appengine+unsubscr...@googlegroups.com>.
To post to this group, send email to google-appengine@googlegroups.com 
<mailto:google-appengine@googlegroups.com>.

Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CAF6cnzbotyO1VYzQm9tQaJoshvcp0rg6ag5CU571U_XUHqZgFg%40mail.gmail.com 
<https://groups.google.com/d/msgid/google-appengine/CAF6cnzbotyO1VYzQm9tQaJoshvcp0rg6ag5CU571U_XUHqZgFg%40mail.gmail.com?utm_medium=email_source=footer>.

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 https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/570197EA.601%40google.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] GAE Java FE env deployment issue

['ludovic Champenois' via Google App Engine]

So I guess you've been using the appcfg.sh tool to deploy a web app 
built the way you want...(maybe via Ant?)


Continue to do that, but change the flags used by appcfg and replace the 
update subcommand with the stage sub command. The stage subcommand takes 
an extra param at the end that is the location of an empty staging 
directory that will be populated with correct content.
Then you can use the Cloud SDK to deploy this staging directory 
(pointing to it's app.yaml at the root).

gcloud preview app deploy stagingDir/app.yaml
Ludo

On 4/2/16 11:59 AM, Deepak Singh wrote:

Hi,

I have a running java web app on gae sandbox for last 3 years. Now 
would like to migrate it to GAE flexible env. We found the documents 
which recommends to use maven and build and deploy. We dont use maven 
in our app and would like not to use. So, is there any convenient way 
to deploy the app on FE without a maven project architecture ? Pls 
sugeest.


--
Tech
--
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 https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CAF6cnzbYypRrMJZzGihN6CGHGJdR7qrjN6U%2ByyBoP23CXAQGXw%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 https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/570049B4.4030807%40google.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: How can i set an order for .jar files in WEB-INF/lib

['Ludovic Champenois' via Google App Engine]

On 1/28/16 12:36 AM, Manuel Werder wrote:

yeah it was:
com.google.apphosting.api.ApiProxy$FeatureNotEnabledException: The 
Socket API will be enabled for this application once billing has been 
enabled in the admin console.
but as i said it was already enabled. so i deployed it to another 
project where billing already is enabled also.

And it works there. Seems to be a bug with my project or something?
Thanks for your help though,


This might help?
https://cloud.google.com/appengine/docs/java/runtime?hl=en#Java_Class_loader_JAR_ordering
Ludo

Manuel
Am Freitag, 22. Januar 2016 22:39:53 UTC+1 schrieb Nick (Cloud 
Platform Support):


Hey Manuel,

Is that an error output from your application, in the logs? Or a
pop-up in-browser? If the former, could you try to post any logs
or stack traces relevant?

On Friday, January 22, 2016 at 1:38:55 AM UTC-5, Manuel Werder wrote:

Hey Nick
In mymqttclient.jar is just a class with the specific function
i wanted to Change. In eclipse i can set the order in which
the Project will load my .jar's for Java Projects. That means
first it will load my .jar with the edited function and
therefore will ignore the original jar's function. I hope you
understand what i mean. But when i want to do it with a web
application i dont know how to do this.
But nevermind i think what you said is the cleaner way how to
do it. So I tried it and it seems to work. But now it says:
"The Socket API will be enabled for this application once
billing has been
enabled in the admin console."
so I added the project to my billing account, but it still
says I have to enable billing...


Am Donnerstag, 21. Januar 2016 23:45:47 UTC+1 schrieb Nick
(Cloud Platform Support):

... to clarify, I guess in addition to answering my above
post, I'm looking for a clarification on what you mean by
ordering the .jars at all.

--
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 https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/b067416b-aa14-4010-9b6d-48e151a96fa3%40googlegroups.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 https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/56AA885A.2000800%40google.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: application logging when using 'gcloud preview app run' in Java

['Ludovic Champenois' via Google App Engine]

On 8/19/15 8:51 PM, Matt Self wrote:
Hooray, I found a log location.  Tucked away in the safe_process.py 
debug output. By starting the with gcloud with a verbosity of debug 
(i.e. gcloud preview app run ./app.yaml --verbosity debug) it shows a 
setting of APP_ENGINE_LOG_CONFIG_PATTERN which indicated (for me) 
where logs were going.


e.g.
DEBUG 2015-08-20 03:39:22,137 safe_subprocess.py:60] Starting process 
['/usr/lib/jvm/java-7-oracle/bin/java', 
'-Dgcloud.java.application=/home/matt/src/java/blah/build', 
'-Djetty.home=/home/matt/google-cloud-sdk/platform/google_appengine/google/appengine/javamanagedvm/appengine-java-vmruntime', 
'-Djetty.base=/home/matt/google-cloud-sdk/platform/google_appengine/google/appengine/jettybasesdk', 
'-jar', ...*'APP_ENGINE_LOG_CONFIG_PATTERN': 
'/tmp/tmpMupjUTgae/log.%g',* 'TZ': 'UTC', 'SDKROOT': 
'/home/google-cloud-sdk/platform/google_appengine', 'GAE_LONG_APP_ID': 
'asd-87623', 'GAE_MODULE_INSTANCE': '0'}, cwd='/home/' ...


Inconvenient, as it changes every time, but it'll work for now. I'd 
love to hear of a way to override this or better yet get it into the 
main terminal window.

Just filed an internal bug to address this.
Ludo




On Wednesday, August 19, 2015 at 3:17:41 PM UTC-6, Matt Self wrote:

Ok, based on this thread
(https://code.google.com/p/google-cloud-sdk/issues/detail?id=163
https://code.google.com/p/google-cloud-sdk/issues/detail?id=163)
it seems that gcloud defaults to docker-less local development.
Unfortunately, when this is the case I can't seem to get
application logs to appear in the console (or anywhere else for
that matter).  I see that it falls back on using devappserver2.py
/ jetty, but I'm not sure where stdout is getting redirected. I do
see general request handling logging in the main console window,
but no application logging gets out. This is not the case if I use
mvn gcloud:run which logs just fine (to docker).


Again, if I use mvn gcloud:run, it defaults to using docker, and I
am able to find my logs by ssh-ing into the running container (in
/var/logs/appengine).  But when running via 'gcloud preview app
run' I get no app logs.


So, two questions:

First, where are the logs when running (dockerless) 'gcloud
preview app run'?  I have everything set up correctly (and can
confirm that app log messages are redirected from stdout to file
when running within docker container via mvn gcloud:run).


Second, is it possible to use the 'gcloud preview app run' with a
flag to indicate that it should run in docker mode?  A flag
could be a work around for me and would be handy in any case (as I
typically launch from the gcloud toolset so i can use a
dispatcher.yaml and other app.yaml modules).


Any insight into this is appreciated. Thanks for the help.


--
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 
mailto:google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com 
mailto: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/9c1f6d5a-958f-462d-b0a3-8bcfd9096aa7%40googlegroups.com 
https://groups.google.com/d/msgid/google-appengine/9c1f6d5a-958f-462d-b0a3-8bcfd9096aa7%40googlegroups.com?utm_medium=emailutm_source=footer.

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/55D5EDAC.5060609%40google.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Managed VM and logging with gcloud-maven-plugin

['Ludovic Champenois' via Google App Engine]

On 6/11/15 8:24 AM, 'Les Vogel' via Google App Engine wrote:
One last try, you had it in your email, 
 /home/vmagent/appengine-java-vmruntime/webapps/root/WEB-INF/logging.properties 



property name=java.util.logging.config.file 
value=/home/vmagent/appengine-java-vmruntime/webapps/root/WEB-INF/logging.properties/


If the full path doesn't work, I don't know what else to suggest to you.
Maybe file a bug... Maybe MVM is not setting the defaut current 
directory to the root of the app?


Ludo



On Thu, Jun 11, 2015 at 12:38 AM, Paolo Rascuna 
paolo.rasc...@imagini.net mailto:paolo.rasc...@imagini.net wrote:


I'm afraid, that didn't help.

On Wednesday, 10 June 2015 18:51:28 UTC+1, Les Vogel wrote:

Try changing it to /app/WEB-INF/logging.properties

Les

On Wed, Jun 10, 2015 at 2:26 AM, Paolo Rascuna
paolo@imagini.net wrote:

Thanks Les, but I already have such lines in my
logging.properties and these lines in my appengine-web.xml

!-- Configure java.util.logging --
system-properties
property name=java.util.logging.config.file
value=WEB-INF/logging.properties/
/system-properties

At this point I'm afraid the the logging.properties is not
being read (even though, logging into the docker container
(docker exec -ti `docker ps -q` bash ) I can see the file
in /home/vmagent/appengine-java-vmruntime/webapps/root/WEB-INF



On Thursday, 4 June 2015 17:48:58 UTC+1, Les Vogel wrote:

Not that I'm aware of, but the source code can be
found at

https://github.com/GoogleCloudPlatform/appengine-java-vm-runtime/
 It's just the messages I didn't want to see in my
debug logs.



On Thu, Jun 4, 2015 at 9:34 AM, Nick (Cloud Platform
Support) pay...@google.com wrote:

Hey Les,

Some of the lines in that logging.properties
example are quite interesting. Are they documented
anywhere in relation to Managed VMs?

Thanks,

Nick


On Thursday, June 4, 2015 at 12:05:11 PM UTC-4,
Les Vogel wrote:

The important thing was setting the classes
your interested in logs for in your:
*logging.properties* if you don't do that, you
won't see anything.

From one of mine:

# Set the default logging level for all
loggers to INFO
*.level = INFO*

# Loggers
*com.example.bigtable.managedvms.level=ALL*

org.apache.http.level=OFF
org.apache.http.wire.level=OFF

com.google.apphosting.repackaged.org.apache.http.wire.level=OFF


com.google.apphosting.vmruntime.VmAppLogsWriter.level=OFF
com.google.apphosting.vmruntime.VmApiProxyDelegate=OFF
com.google.apphosting.vmruntime.level=OFF


On Thu, Jun 4, 2015 at 2:49 AM, Paolo Rascuna
paolo@imagini.net wrote:

Thank you Les, but that's not working for
me... I tried that already, but that's the
docker logs output

$ docker logs -f `docker ps -q`
Info: Limiting Java heap size to: 1456M
Running locally and DBG_ENABLE is set,
enabling standard Java debugger agent
Listening for transport dt_socket at
address: 5005
2015-06-04 09:05:08.860:INFO::main:
Logging initialized @571ms
2015-06-04 09:05:09.001:INFO::main:
Redirecting stderr/stdout to

/var/log/app_engine/STDERR.2015_06_04.log//var/log/app_engine/STDOUT.2015_06_04.log


On Wednesday, 3 June 2015 18:09:45 UTC+1,
Les Vogel wrote:

There are changes coming to improve
things in the next few weeks.  In the
mean time, here's what I do:

Make sure .level=INFO or what you need
in your logging.properties .  For the
class(es) I'm working with I set the
class logging explicitly to:

[google-appengine] Re: Java 8 and the App Engine

[Ludovic Champenois]

Hi,
While I can not predict when it will come up, I can tell you we are working 
on enable Java 8 to the good old App Engine (not that old!!!).
We want to make it as secure as our current Java 7 runtime, and once we 
feel we are ready, we'll push it.

For now,it is only possible on Managed VMs, as a custom runtime.

Ludo (TML Google App Engine Runtimes)


On Friday, May 22, 2015 at 2:35:39 AM UTC-7, ra wrote:

 Hi there, 


 I am wondering if anyone can comment on whether it is even planned to 
 implement Java 8 support on good old App Engine. 
 There is a feature request open for more than 2 years now: 
 https://code.google.com/p/googleappengine/issues/detail?id=9537 

 It feels weird that App Engine only supports a Java version 
 where the official Oracle JDK is end of life. 


 Thanks for any enlightenment! 



 Raphael 


-- 
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/71da42c4-0d95-457e-a3bf-c3d014a8f31b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: App Engine + Maven + Hot swap of war

[Ludovic Champenois]

Hi,

If your pom.xml is configured in the build section like:

  build

!-- for hot reload of the web application--

outputDirectory
${project.build.directory}/${project.build.finalName}/WEB-INF/classes/
outputDirectory

plugins

  plugin

.



Then Eclipse, NetBeans and IntelliJ which are all supporting incremental 
compile on a java file Save, or update the static file resources in the 
exploded war directory, will trigger automatically a App Server restart, 
enable hot swap of your application just by saving files in the IDE:

Save and reload the app in the browser... Very effective.

Also documented at:

https://cloud.google.com/appengine/docs/java/tools/maven#app_engine_maven_plugin_goals

(Same feature is available for Managed VMs, and the cloud SDK Maven plugin:

https://cloud.google.com/appengine/docs/java/managed-vms/maven

)

Ludo

On Tuesday, April 28, 2015 at 7:29:59 AM UTC-7, Carl Emmoth wrote:

 Hello,

 so is it possible to run maven devserver (mvn appengine:devserver) and 
 have live hot swap for any changes in war dir?

 Like, if I change index.html with new text and refresh in browser, can it 
 update?

 It seems like fullScanSeconds only updates Java classes.

 Thanks,
 Carl


-- 
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/a59b8a0d-0fe8-45c4-ad20-e806f47a2214%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: SDK1.8.4 did break cloud enpoint generation

[Ludovic Champenois]

Which version of the GPE plugin itself are you using? Verify it is the 
latest: GPE 3.4.0


On Saturday, September 7, 2013 2:20:55 AM UTC-7, Johan Compagner wrote:

 I updated through eclipse to the 1.8.4 release, but then i tried to do the 
 endpoint generation it failed with this exception:

 java.lang.NoSuchMethodException: 
 com.google.api.server.spi.tools.CloudClientLibGenerator.generateClientLib(java.lang.String,
  
 com.google.api.server.spi.tools.ClientLibGenerator$Language, 
 java.lang.String, java.io.File)
 at java.lang.Class.getMethod(Class.java:1655)
 at 
 com.google.gdt.eclipse.appengine.swarm.wizards.helpers.SwarmApiCreator.createClientLibFromApiConfig(SwarmApiCreator.java:101)
 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:1057)
 at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4170)
 at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3759)
 at 
 org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113)
 at 
 org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
 at 
 org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997)
 at 
 org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138)
 at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610)
 at 
 org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
 at 
 org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567)
 at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
 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:354)
 at 
 org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181)
 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:606)
 at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636)
 at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
 at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
 at org.eclipse.equinox.launcher.Main.main(Main.java:1426)


 i quickly reverted to 1.8.3 and that works fine.

 Also in 1.8.4 i suddenly also got another json exception that a @named 
 string param was conflicting (which works fine in 1.8.3)
 that names param (so thats in the url) does somehow collide with a name 
 that is nested deep down in the body object (which is a java (json) object)
 So the name param would be something like:

 code

 and deep down in the body contents i would also have something like

 object.object2.code

 now it seems that those 2 are the same and conflict with each other?


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

[google-appengine] GAE Java 1.8.1 and broken automatic jetty reload

[Ludovic Champenois]

Hey, it seems a bug...
Yes, any file change triggers a reload...
For now, it is possible to configure the db loc elsewhere?
Will need to filter better...

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

[google-appengine] Local development database

[Ludovic Champenois]

Please file a bug. It might be complicated to fix as these internal classes 
change at every release (hence being repackaged for private only consumption...)

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

Re: [google-appengine] GAE Java 1.8.1 and broken automatic jetty reload

[Ludovic Champenois]

Can you try to point the system property  appengine.generated.dir to an
existing dir outside of the web-inf area?



On Thu, Jun 13, 2013 at 5:06 AM, Raphael André Bauer 
raphael.andre.ba...@gmail.com wrote:

 On Thu, Jun 13, 2013 at 1:41 PM, Ludovic Champenois l...@google.com
 wrote:
  Hey, it seems a bug...
  Yes, any file change triggers a reload...
  For now, it is possible to configure the db loc elsewhere?
  Will need to filter better...

 I have actually no idea how to configure the db loc.

 In Ninja I can also use Jetty which also has an automatic reload that
 works differently and does not pick up changes in the
 appengine_generated dir. But it is not ideal. Ideal is using GAE's
 original devserver - with a working hot reload mode...

 By the way - why is hot reload mode not mentioned on the changelog?
 (https://code.google.com/p/googleappengine/wiki/SdkForJavaReleaseNotes)


 Thanks for the quick answer :)

 Raphael

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

[google-appengine] Re: Google App Engine SDK 1.8.0 is now available!

[Ludovic Champenois]

How can we reproduce this error? So far, we can't so we need more 
information about your set up.
Can you share your PATH, env variables?
Do you have another app engine SDK installed?
Which framework do you use from your web app?



On Tuesday, May 21, 2013 3:00:04 AM UTC-7, Jeff Lockhart wrote:

 I'm getting this error when attempting to deploy my app after updating to 
 1.8.

 java.io.IOException: Jar ...\appengine-api-1.0-sdk-1.8.0.jar is too large. 
 Consider using --enable_jar_splitting.

 I ran appcfg from the SDK bin directory. It is the latest 1.8 version and 
 still get the error. Windows 8 x64. Tried with both Java 7u21 x64 and Java 
 6u38 x64.

 On Friday, May 17, 2013 1:45:53 PM UTC-6, Vishwanath Arondekar wrote:

 I observed that this error comes If you are using old version of appcfg 
 with 1.8 version of jar. Run appcfg from 1.8 SDK bin and it should work.

 On Saturday, 11 May 2013 03:02:32 UTC+5:30, Matt Staten wrote:

 I'm getting errors regarding the size of the API jar: 
 appengine-api-1.0-sdk-1.8.0.jar is too large. Consider using 
 --enable_jar_splitting. I thought this was fixed with 1.7.7.1... did it 
 get bugged again?

 On Wednesday, May 8, 2013 4:36:21 PM UTC-7, Richmond Manzana wrote:

 Hi everyone,

 We're happy to announce that we have released the 1.8.0 SDK.


 For more details, please read our blog post and release notes.

 Release notes for Python:
 http://code.google.com/p/googleappengine/wiki/SdkReleaseNotes

 Release notes for Java:
 http://code.google.com/p/googleappengine/wiki/SdkForJavaReleaseNotes

 Release notes for Go:
 https://code.google.com/p/googleappengine/wiki/SdkForGoReleaseNotes

 Cheers!

 P.S. If you don't see the appengine-maven-plugin release, it takes a 
 while to replicate.  You can either wait a little bit, or if you add the 
 following in the pom you can see the master:

  repositories
repository
idsonatype-google-releases/id
nameSonatype Google Releases/name
url
 https://oss.sonatype.org/service/local/repositories/google-releases/content
 /url
/repository
/repositories

 Richmond Manzana
 Technical Program Manager
 Google App Engine



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

[google-appengine] Re: Google App Engine SDK 1.8.0 is now available!

[Ludovic Champenois]

Seems to be a different bug but same effect, as the original scenario 
(involving JSPs) was solved in 1.8.0...
Can you describe a bit more the web app you have and which frameworks you 
are using? (Maven? JDO? JPA? etc)
Once we have a reproducible case, we can address it asap.

Thanks!

On Friday, May 10, 2013 2:32:32 PM UTC-7, Matt Staten wrote:

 I'm getting errors regarding the size of the API jar: 
 appengine-api-1.0-sdk-1.8.0.jar is too large. Consider using 
 --enable_jar_splitting. I thought this was fixed with 1.7.7.1... did it 
 get bugged again?

 On Wednesday, May 8, 2013 4:36:21 PM UTC-7, Richmond Manzana wrote:

 Hi everyone,

 We're happy to announce that we have released the 1.8.0 SDK.


 For more details, please read our blog post and release notes.

 Release notes for Python:
 http://code.google.com/p/googleappengine/wiki/SdkReleaseNotes

 Release notes for Java:
 http://code.google.com/p/googleappengine/wiki/SdkForJavaReleaseNotes

 Release notes for Go:
 https://code.google.com/p/googleappengine/wiki/SdkForGoReleaseNotes

 Cheers!

 P.S. If you don't see the appengine-maven-plugin release, it takes a 
 while to replicate.  You can either wait a little bit, or if you add the 
 following in the pom you can see the master:

  repositories
repository
idsonatype-google-releases/id
nameSonatype Google Releases/name
url
 https://oss.sonatype.org/service/local/repositories/google-releases/content
 /url
/repository
/repositories

 Richmond Manzana
 Technical Program Manager
 Google App Engine



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

[google-appengine] Re: Google App Engine SDK 1.8.0 is now available!

[Ludovic Champenois]

Hi,

For the App Engine Maven plugin, if you need it absolutely now, before the 
Maven caching system gets updated, you can add this as weel:
  pluginRepositories
pluginRepository
idsonatype-google-releases/id
nameSonatype Google Releases/name

urlhttps://oss.sonatype.org/service/local/repositories/google-releases/content/url
/pluginRepository
  /pluginRepositories

In a few hours, it will not be needed.


On Wednesday, May 8, 2013 4:36:21 PM UTC-7, Richmond Manzana wrote:

 Hi everyone,

 We're happy to announce that we have released the 1.8.0 SDK.


 For more details, please read our blog post and release notes.

 Release notes for Python:
 http://code.google.com/p/googleappengine/wiki/SdkReleaseNotes

 Release notes for Java:
 http://code.google.com/p/googleappengine/wiki/SdkForJavaReleaseNotes

 Release notes for Go:
 https://code.google.com/p/googleappengine/wiki/SdkForGoReleaseNotes

 Cheers!

 P.S. If you don't see the appengine-maven-plugin release, it takes a while 
 to replicate.  You can either wait a little bit, or if you add the 
 following in the pom you can see the master:

  repositories
repository
idsonatype-google-releases/id
nameSonatype Google Releases/name
url
 https://oss.sonatype.org/service/local/repositories/google-releases/content
 /url
/repository
/repositories

 Richmond Manzana
 Technical Program Manager
 Google App Engine


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

Re: [google-appengine] Re: Google App Engine SDK 1.7.7 is now available!

[ludovic Champenois]

On 4/10/13 2:35 PM, Francois MASUREL wrote:

Yes, without success.


François Masurel


Hi,

The Java App Engine 1.7.7.1 SDK is now available with a fix for this 
windows specific issue. The Eclipse SDK plugin, as well as the App 
Engine Maven plugin have also been updated.


Happy coding...



On Wed, Apr 10, 2013 at 11:28 PM, Takashi Matsuo tmat...@google.com 
mailto:tmat...@google.com wrote:


Hi Francois,

Thanks for the report. Have you tried it with --enable_jar_splitting?


On Wed, Apr 10, 2013 at 1:59 PM, Francois Masurel
f.masu...@gmail.com mailto:f.masu...@gmail.com wrote:

Getting also the same appengine-api-1.0-sdk-1.7.7.jar is too
large error.

I'm on Windows 7 x64 with latest GAE and Java 7 SDK and
the appengine-api-1.0-sdk-1.7.7.jar is 30.6MB big.

Thanx for your help.

François


On Wednesday, April 10, 2013 9:15:04 PM UTC+2, Sekhar wrote:

I'm getting a appengine-api-1.0-sdk-1.7.7.jar is too
large error when deploying. Are we expected to split this
manually or is there a workaround?

On Tuesday, April 9, 2013 3:44:38 PM UTC-7, Richmond
Manzana wrote:

Hi everyone,

We're happy to announce that we have released the
1.7.7 SDK.

This release includes new features such as updates to
the Maven Plugin, and Outbound Sockets.  We're also
happy to announce that we have removed the weekly
$2.10 minimum spend for billing enabled apps :)

For more details, please read our blog post and
release notes.

Announcement:

http://googleappengine.blogspot.com/2013/04/app-engine-177-released.html

Releae notes for Python:
http://code.google.com/p/googleappengine/wiki/SdkReleaseNotes

Release notes for Java:

http://code.google.com/p/googleappengine/wiki/SdkForJavaReleaseNotes

Release notes for Go:

https://code.google.com/p/googleappengine/wiki/SdkForGoReleaseNotes

Cheers!

Richmond Manzana
Technical Program Manager
Google App Engine

-- 
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
mailto:google-appengine%2bunsubscr...@googlegroups.com.
To post to this group, send email to
google-appengine@googlegroups.com
mailto:google-appengine@googlegroups.com.
Visit this group at
http://groups.google.com/group/google-appengine?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.





-- 
Takashi Matsuo | Developers Programs Engineer | tmat...@google.com

mailto:tmat...@google.com
-- 
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/r5JNlfkqq94/unsubscribe?hl=en.
To unsubscribe from this group and all its topics, send an email
to google-appengine+unsubscr...@googlegroups.com
mailto:google-appengine%2bunsubscr...@googlegroups.com.
To post to this group, send email to
google-appengine@googlegroups.com
mailto:google-appengine@googlegroups.com.
Visit this group at
http://groups.google.com/group/google-appengine?hl=en.
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?hl=en.
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [google-appengine] Re: Google App Engine SDK 1.7.7 is now available!

[Ludovic Champenois]

Hi,
We are tracking this issue internally...Only on windows, and if your app is 
using some JSP right?
It's a combination of 2 things: the api jar becoming too big (we will 
compress it soon), and the jspc compiler keeping a lock on the files in the 
jspc classpath, making the api jar not deletable (we do not need to upload 
it to the runtime server)... Windows file locking system makes the locked 
file non deletable...
Until we push a new SDK, the only workaround would be for you to modify 
your local SDK this way:
1/ unjar the impacted jar.
2/ rejar it with the jar command default (i.e compression) and making sure 
you keep all the META-INF manifest (using the m flag) content in the new 
jar. It contains critical info for the processing.
This will workaround the issue, while waiting for a new push.




On Wednesday, April 10, 2013 2:35:01 PM UTC-7, Francois MASUREL wrote:

 Yes, without success.


 François Masurel


 On Wed, Apr 10, 2013 at 11:28 PM, Takashi Matsuo 
 tma...@google.comjavascript:
  wrote:

 Hi Francois,

 Thanks for the report. Have you tried it with --enable_jar_splitting?


 On Wed, Apr 10, 2013 at 1:59 PM, Francois Masurel 
 f.ma...@gmail.comjavascript:
  wrote:

 Getting also the same appengine-api-1.0-sdk-1.7.7.**jar is too large 
 error.

 I'm on Windows 7 x64 with latest GAE and Java 7 SDK and 
 the appengine-api-1.0-sdk-1.7.7.**jar is 30.6MB big.

 Thanx for your help.

 François


 On Wednesday, April 10, 2013 9:15:04 PM UTC+2, Sekhar wrote:

 I'm getting a appengine-api-1.0-sdk-1.7.7.**jar is too large error 
 when deploying. Are we expected to split this manually or is there a 
 workaround?

 On Tuesday, April 9, 2013 3:44:38 PM UTC-7, Richmond Manzana wrote:

 Hi everyone,

 We're happy to announce that we have released the 1.7.7 SDK.

 This release includes new features such as updates to the Maven 
 Plugin, and Outbound Sockets.  We're also happy to announce that we have 
 removed the weekly $2.10 minimum spend for billing enabled apps :)

 For more details, please read our blog post and release notes.

 Announcement:
 http://googleappengine.**blogspot.com/2013/04/app-**
 engine-177-released.htmlhttp://googleappengine.blogspot.com/2013/04/app-engine-177-released.html

 Releae notes for Python:
 http://code.google.com/p/**googleappengine/wiki/**SdkReleaseNoteshttp://code.google.com/p/googleappengine/wiki/SdkReleaseNotes

 Release notes for Java:
 http://code.google.com/p/**googleappengine/wiki/**
 SdkForJavaReleaseNoteshttp://code.google.com/p/googleappengine/wiki/SdkForJavaReleaseNotes

 Release notes for Go:
 https://code.google.com/p/**googleappengine/wiki/**
 SdkForGoReleaseNoteshttps://code.google.com/p/googleappengine/wiki/SdkForGoReleaseNotes

 Cheers!

 Richmond Manzana
 Technical Program Manager
 Google App Engine

  -- 
 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-appengi...@googlegroups.com javascript:.
 To post to this group, send email to 
 google-a...@googlegroups.comjavascript:
 .
 Visit this group at 
 http://groups.google.com/group/google-appengine?hl=en.
 For more options, visit https://groups.google.com/groups/opt_out.
  
  




 -- 
 Takashi Matsuo | Developers Programs Engineer | 
 tma...@google.comjavascript:
  
 -- 
 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/r5JNlfkqq94/unsubscribe?hl=en
 .
 To unsubscribe from this group and all its topics, send an email to 
 google-appengi...@googlegroups.com javascript:.
 To post to this group, send email to 
 google-a...@googlegroups.comjavascript:
 .
 Visit this group at http://groups.google.com/group/google-appengine?hl=en
 .
 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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[google-appengine] Re: Test and Upgrade your App Engine Java Application to a Java 7 runtime...now.

[Ludovic Champenois]

Hi,

It's coming! Are you ready?

Google App Engine Java SDK 1.7.7 (shipping very soon) will deploy all Java 
applications to the new Java 7 runtime. Did you do a sanity test with your 
current Java applications?  Many of you have done it already: Thank you! So 
far, no migration issues have been reported.

In general, Java 7 runtime is backwards compatible with Java 6, and will 
run all pre-existing Java applications that did not rely on 
implementation-specific functionality.  Please refer to the Oracle white 
paper on Java 7 and Java 
6http://www.oracle.com/technetwork/java/javase/compatibility-417013.html 
compatibility 
for additional details.

It is still time to try deploying a new version of your application with 
the --use_java7 flag with the appcfg tool and and see that your application 
is behaving as before. Remenber that this flag will be on by default going 
forward in GAE 1.7.7. In the near future all App Engine Java applications 
will run a the new Java 7 runtime.

Cheers.


On Thursday, March 14, 2013 6:56:32 PM UTC-7, Ludovic Champenois wrote:

 Hi,
 A quick status on the Java 7 migration: No news is good news right?
 Applications (very large and small)  having tried or even completely 
 upgraded to the Java 7 runtime have not discovered runtime issue: this is 
 great news!
 More applications every single day, and counting...

 If you have not started testing your application with the new Java 7 
 runtime, this is the right time now to do it either with the current 1.7.5 
 release, or the coming 1.7.6 release (we push a preview SDK earlier this 
 week).

 Cheers.

 On Wednesday, February 27, 2013 10:37:01 AM UTC-8, Ludovic Champenois 
 wrote:

 Hi,

 As part of Google App Engine 1.7.5 release on February 13, 2013, we 
 introduced Preview support of App Engine Java 7 runtime.  In early April, 
 Google will commence upgrading our internal applications from Java 6 to 
 Java 7.  In conjunction with this effort, we highly recommend that all of 
 our App Engine customers begin testing and eventually migrate their 
 applications to Java 7 runtime within the next couple of months. 

 Please find below some additional technical information to assist with 
 testing and migrating your application to Java 7 environment:

 *Java 6 and Java 7 Compatibility*
  
 In general, Java 7 runtime is backwards compatible with Java 6, and will 
 run all pre-existing Java applications that did not rely on 
 implementation-specific functionality.  Please refer to the Oracle white 
 paper on Java 7 and Java 
 6http://www.oracle.com/technetwork/java/javase/compatibility-417013.htmlcompatibility
  for additional details.

 *Procedure for Testing*
  
 For all your Java App Engine applications, here are the steps for testing 
 in the new Java 7 environment.

 1.  App Engine can support multiple live versions of a given application. 
  It is best to create a new version of your app and deploy it to a Java 7 
 runtime.

 2.  You can deploy to a new Java 7 runtime with one of the following 
 steps:

 a)  Recompile your Java Application with a full JDK 7 compiler. You can 
 test it with the GAE 1.7.5 SDK, and when ready, use the regular appcfg SDK 
 tool that will detect that the Java byte code is Java 7 compliant and will 
 use a Java7 runtime for this application version.

 b)  If you are still compiling your Java application with a JDK 6 
 compiler, you can deploy to the Java 7 runtime by adding the *--use_java7
 * flag to the appcfg SDK tool.

 Please review the Google Java 7 
 Considerationshttps://developers.google.com/appengine/docs/java/java7paper 
 for additional information on configuring Java 7. 

 3.  Assuming you have your default application version still running with 
 a Java 6 runtime and a new version running in Java 7, you can use the 
 Google App Engine Traffic Splitting feature to slowly ramp up traffic on 
 the new Java 7 runtime.  Consider starting with 5%, then increase gradually 
 to 10%, 20%, and so on as your app is behaving as expected.  See our Traffic 
 Splitting 
 documenthttps://developers.google.com/appengine/docs/adminconsole/trafficsplittingfor
  more information about this tool.

 Thanks for spending the time to make sure your application is Java 7 
 ready now. Only a very few incompatible behaviors may have to be fixed in 
 your applications. 

  



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

Re: [google-appengine] Maven and GAE endpoints

[ludovic Champenois]

On 3/16/13 10:09 PM, William Ferguson wrote:
I'm trying to convert an existing AppEngine app that uses org.restlet 
as transport to use cloud endpoints. I was planning on moving to 
endpoints to gain better access to authenticated users specifically 
from Android devices. But I'm finding that the endpoint tooling 
doesn't play very nicely with Maven and could use some pointers on 
making it less tedious.


In particular with org.restlet I defined my server interfaces in 
projectA, app engine implementation in projectB and Android client 
impl in projectC. All cleanly separate. But with the endpoint tooling:

1) It assumes that the engine app is in a folder called 'war'
2) It requires all classes declared in the method signatures to have 
their source in the app engine project (they can't be contained in a 
dependent jar).
3) Creates a client ?project? library embedded in the war/web-inf 
folder of the engine server app which contains source, dependencies, 
proguard config and needs to be cut out of the server app and added to 
the client app.
4) Maybe I missed this but I couldn't see a way to force params into 
the request body instead of being part of the URL..



Does someone have a good example project that uses Maven to build 
using endpoints?


What Maven plugins are people using. I have been using 
net.kindleit:maven-gae-plugin to date, but it looks close to abandoned 
now and doesn't support endpoints.
  appengine-maven-plugin looks newish and pretty clean (doesn't 
support the endpoint tooling)
  maven-endpoint-plugin generates the server api descriptor but not 
any of the client classes.




Hi,
We are working on fixing this bug:
https://code.google.com/p/googleappengine/issues/detail?id=8833sort=-idcolspec=ID%20Type%20Component%20Status%20Stars%20Summary%20Language%20Priority%20Owner%20Log
Once fixed, the new appengine-maven-plugin will be updated to also 
support endpoints, I hope soon.

We are also working on improving the documentation. Stay tune,

Ludo


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

[google-appengine] Re: Test and Upgrade your App Engine Java Application to a Java 7 runtime...now.

[Ludovic Champenois]

Hi,
A quick status on the Java 7 migration: No news is good news right?
Applications (very large and small)  having tried or even completely 
upgraded to the Java 7 runtime have not discovered runtime issue: this is 
great news!
More applications every single day, and counting...

If you have not started testing your application with the new Java 7 
runtime, this is the right time now to do it either with the current 1.7.5 
release, or the coming 1.7.6 release (we push a preview SDK earlier this 
week).

Cheers.

On Wednesday, February 27, 2013 10:37:01 AM UTC-8, Ludovic Champenois wrote:

 Hi,

 As part of Google App Engine 1.7.5 release on February 13, 2013, we 
 introduced Preview support of App Engine Java 7 runtime.  In early April, 
 Google will commence upgrading our internal applications from Java 6 to 
 Java 7.  In conjunction with this effort, we highly recommend that all of 
 our App Engine customers begin testing and eventually migrate their 
 applications to Java 7 runtime within the next couple of months. 

 Please find below some additional technical information to assist with 
 testing and migrating your application to Java 7 environment:

 *Java 6 and Java 7 Compatibility*
  
 In general, Java 7 runtime is backwards compatible with Java 6, and will 
 run all pre-existing Java applications that did not rely on 
 implementation-specific functionality.  Please refer to the Oracle white 
 paper on Java 7 and Java 
 6http://www.oracle.com/technetwork/java/javase/compatibility-417013.htmlcompatibility
  for additional details.

 *Procedure for Testing*
  
 For all your Java App Engine applications, here are the steps for testing 
 in the new Java 7 environment.

 1.  App Engine can support multiple live versions of a given application. 
  It is best to create a new version of your app and deploy it to a Java 7 
 runtime.

 2.  You can deploy to a new Java 7 runtime with one of the following steps:

 a)  Recompile your Java Application with a full JDK 7 compiler. You can 
 test it with the GAE 1.7.5 SDK, and when ready, use the regular appcfg SDK 
 tool that will detect that the Java byte code is Java 7 compliant and will 
 use a Java7 runtime for this application version.

 b)  If you are still compiling your Java application with a JDK 6 
 compiler, you can deploy to the Java 7 runtime by adding the 
 *--use_java7*flag to the appcfg SDK tool.

 Please review the Google Java 7 
 Considerationshttps://developers.google.com/appengine/docs/java/java7paper 
 for additional information on configuring Java 7. 

 3.  Assuming you have your default application version still running with 
 a Java 6 runtime and a new version running in Java 7, you can use the 
 Google App Engine Traffic Splitting feature to slowly ramp up traffic on 
 the new Java 7 runtime.  Consider starting with 5%, then increase gradually 
 to 10%, 20%, and so on as your app is behaving as expected.  See our Traffic 
 Splitting 
 documenthttps://developers.google.com/appengine/docs/adminconsole/trafficsplittingfor
  more information about this tool.

 Thanks for spending the time to make sure your application is Java 7 ready 
 now. Only a very few incompatible behaviors may have to be fixed in your 
 applications. 

  


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

Re: [google-appengine] Re: GAE/J: Deadline exceeded on CloudSQL connection initialization

[Ludovic Champenois]

Good finding, that matches our observations as well...
Maybe the option should be turned on by default?



On Fri, Mar 1, 2013 at 12:51 AM, Dariya Blagaya d...@cloudwk.com wrote:

 We solved this problem. Hibernate use reflection during initialization
 process, but reflection depends on reading files from file system.

 It seems that in GAE there is a problem with reading files (including
 .class files)  and sometimes this process can be quite long.

 The solution is very simple - to pack all compiled files to jar and deploy
 project like one file. In GAE SDK 1.7.4. there is an opportunity to deploy
 project by command file (by appcfg) as one jar using --enable_jar_classes
 flag.

 Now everything work absolutely correct without random performance
 collapses.

 Понеділок, 18 лютого 2013 р. 11:51:46 UTC+2 користувач Oleg Bashtenko
 написав:

 Hi!
 I'm using CloudSQL with Hibernate (v 4.1.7), and sometimes opening new
 connection to CloudSQL takes too much time. More specific, the problem is
 in initialization of Bytecode provider. Usually it takes about 5 seconds,
 but sometimes up to 40-50 seconds! This problem causes
 DeadlineExceededException for such requests. I was unable to find any
 information regarding this type of problem.

 Could someone please help me with this problem? Our app id is
 teamwork-ms.

 Here is a part of the log entry (notice the time for records in bold):
 I2013-02-13 22:15:17.586
 com.teamwork.tms.server.api.**WarmupServlet init: Initiate Google
 CloudSQL database connection on startup
 I2013-02-13 22:15:20.761
 org.hibernate.annotations.**common.Version clinit: HCANN01:
 Hibernate Commons Annotations {4.0.1.Final}
 I2013-02-13 22:15:20.865
 org.hibernate.Version logVersion: HHH000412: Hibernate Core {4.1.7.Final}
 I2013-02-13 22:15:20.871
 org.hibernate.cfg.Environment clinit: HHH000206: hibernate.properties
 not found
 I*2013-02-13 22:15:20.876*
 *org.hibernate.cfg.Environment buildBytecodeProvider: HHH21:
 Bytecode provider name : javassist*
 W*2013-02-13 22:16:11.152*
 *org.hibernate.mapping.RootClass checkCompositeIdentifier: HHH38:
 Composite-id class does not override equals(): com.teamwork.tms.server.sql_
 entities.auxiliary.pk.ApplicationCompanyScopePK*
 W2013-02-13 22:16:11.153
 org.hibernate.mapping.**RootClass checkCompositeIdentifier: HHH39:
 Composite-id class does not override hashCode():
 com.teamwork.tms.server.sql_**entities.auxiliary.pk.**
 ApplicationCompanyScopePK

 Thanks in advance!

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

[google-appengine] Test and Upgrade your App Engine Java Application to a Java 7 runtime...now.

[Ludovic Champenois]

Hi,

As part of Google App Engine 1.7.5 release on February 13, 2013, we 
introduced Preview support of App Engine Java 7 runtime.  In early April, 
Google will commence upgrading our internal applications from Java 6 to 
Java 7.  In conjunction with this effort, we highly recommend that all of 
our App Engine customers begin testing and eventually migrate their 
applications to Java 7 runtime within the next couple of months. 

Please find below some additional technical information to assist with 
testing and migrating your application to Java 7 environment:

*Java 6 and Java 7 Compatibility*
 
In general, Java 7 runtime is backwards compatible with Java 6, and will 
run all pre-existing Java applications that did not rely on 
implementation-specific functionality.  Please refer to the Oracle white 
paper on Java 7 and Java 
6http://www.oracle.com/technetwork/java/javase/compatibility-417013.htmlcompatibility
 for additional details.

*Procedure for Testing*
 
For all your Java App Engine applications, here are the steps for testing 
in the new Java 7 environment.

1.  App Engine can support multiple live versions of a given application. 
 It is best to create a new version of your app and deploy it to a Java 7 
runtime.

2.  You can deploy to a new Java 7 runtime with one of the following steps:

a)  Recompile your Java Application with a full JDK 7 compiler. You can 
test it with the GAE 1.7.5 SDK, and when ready, use the regular appcfg SDK 
tool that will detect that the Java byte code is Java 7 compliant and will 
use a Java7 runtime for this application version.

b)  If you are still compiling your Java application with a JDK 6 compiler, 
you can deploy to the Java 7 runtime by adding the *--use_java7* flag to 
the appcfg SDK tool.

Please review the Google Java 7 
Considerationshttps://developers.google.com/appengine/docs/java/java7paper 
for additional information on configuring Java 7. 

3.  Assuming you have your default application version still running with a 
Java 6 runtime and a new version running in Java 7, you can use the Google 
App Engine Traffic Splitting feature to slowly ramp up traffic on the new 
Java 7 runtime.  Consider starting with 5%, then increase gradually to 10%, 
20%, and so on as your app is behaving as expected.  See our Traffic 
Splitting 
documenthttps://developers.google.com/appengine/docs/adminconsole/trafficsplittingfor
 more information about this tool.

Thanks for spending the time to make sure your application is Java 7 ready 
now. Only a very few incompatible behaviors may have to be fixed in your 
applications. 

 

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

Re: [google-appengine] Re: Jersey REST with List as a query parameter

[ludovic Champenois]

On 1/4/13 7:51 AM, Ryan Chazen wrote:
Is there any way to run unit tests on appengine directly instead of 
running them only on the dev server?


At any rate, the error is not from the multiple query parameters, but 
rather (found from a Google search), that the addHeader method on 
AppEngine live does not accept nulls while the dev server does.


The javadocs don't specify if it can or can't accept nulls, so I'm not 
sure what the correct behavior is.

http://docs.oracle.com/javaee/5/api/javax/servlet/http/HttpServletResponse.html#addHeader%28java.lang.String,%20java.lang.String%29

However, the live and dev server really should both function the same 
way - either the dev server should disallow nulls or the live should 
allow them.

It makes testing difficult if live and dev server behave differently.


I agree. Please file a bug and will take care of it. My preference is to 
fix it at the SDK level.


Ludo


--
You received this message because you are subscribed to the Google 
Groups Google App Engine group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-appengine/-/1dGUFsY7JDsJ.

To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.


--
You received this message because you are subscribed to the Google Groups Google 
App Engine group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Re: JSP Compilation takes more than 1 hr

[Ludovic Champenois]

Awesome!
Thanks for sharing. Yes, in fact we've improved a lot the JSP compilation 
in 1.7.4.

Ludo


On Wednesday, January 2, 2013 11:44:39 AM UTC-8, Jitendra Gupta wrote:

 Hi,

 Thanks a lot.
 I have updated GAE SDK   to GAE SDK 1.7.4 version. Now JSP compilation 
 takes normal time, its really very fast.

 Thanks,
 Jeet


 On Sunday, December 30, 2012 5:11:58 AM UTC+5:30, Ludovic Champenois wrote:

 Hi,
 Sorry to hear about the regression.
 JSP compilation is done on your local development machine and has nothing 
 to do with production environment or the fact that the application is using 
 master/slave or HRD.

 A few questions:
 1/ are you using GAE SDK 1.7.4 version where we modified the way JSP 
 compilation is done (and improved a lot performance for the JSP compiler)?
 2/ if not, please use upgrade to the SDK 1.7.4.
 3/ if you are in fact using the SDK 1.7.4, we would love to understand 
 why suddenly your compilation time has increased...If you could share some 
 details about which JDK you are using, how many tag libs you have, the 
 number of JSPs, how many libs do you have in web-inf/lib? If you could 
 share more info about the application, we can certainly address the issue 
 you are facing,

 Thanks,


 On Saturday, December 29, 2012 12:14:35 PM UTC-8, Michael Hermus wrote:

 I have also recently noticed a huge spike in JSP compilation time. There 
 is definitely something going in the GAE java production environment (for 
 some customers at least).

 On Saturday, December 29, 2012 11:38:09 AM UTC-5, Jitendra Gupta wrote:

 Hi,

 I used google app engine for my one application, its on High 
 Replication storage scheme. When same application was on master/slave it 
 took normal time to compile jsp pages
 but now it takes more than 1 hr.

 Reading application configuration data...
 29 Dec, 2012 8:23:41 PM 
 com.google.apphosting.utils.config.AppEngineWebXmlReader 
 readAppEngineWebXml
 INFO: Successfully processed 
 /usr/local/apache-tomcat-6.0.28/webapps/sample-paper/WEB-INF/appengine-web.xml
 29 Dec, 2012 8:23:41 PM 
 com.google.apphosting.utils.config.AbstractConfigXmlReader readConfigXml
 INFO: Successfully processed 
 /usr/local/apache-tomcat-6.0.28/webapps/sample-paper/WEB-INF/web.xml
 Beginning server interaction for tech-course...
 0% Creating staging directory
 5% Scanning for jsp files.
 8% Compiling jsp files.
 29 Dec, 2012 9:42:55 PM 
 com.google.apphosting.utils.config.AbstractConfigXmlReader readConfigXml
 INFO: Successfully processed 
 /tmp/appcfg5287499496253305068.tmp/WEB-INF/web.xml

 Can any one help me, why it takes so long time to compile jsp.



-- 
You received this message because you are subscribed to the Google Groups 
Google App Engine group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-appengine/-/IYXyrwJTlMIJ.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Re: JSP Compilation takes more than 1 hr

[Ludovic Champenois]

Hi,
Sorry to hear about the regression.
JSP compilation is done on your local development machine and has nothing 
to do with production environment or the fact that the application is using 
master/slave or HRD.

A few questions:
1/ are you using GAE SDK 1.7.4 version where we modified the way JSP 
compilation is done (and improved a lot performance for the JSP compiler)?
2/ if not, please use upgrade to the SDK 1.7.4.
3/ if you are in fact using the SDK 1.7.4, we would love to understand why 
suddenly your compilation time has increased...If you could share some 
details about which JDK you are using, how many tag libs you have, the 
number of JSPs, how many libs do you have in web-inf/lib? If you could 
share more info about the application, we can certainly address the issue 
you are facing,

Thanks,


On Saturday, December 29, 2012 12:14:35 PM UTC-8, Michael Hermus wrote:

 I have also recently noticed a huge spike in JSP compilation time. There 
 is definitely something going in the GAE java production environment (for 
 some customers at least).

 On Saturday, December 29, 2012 11:38:09 AM UTC-5, Jitendra Gupta wrote:

 Hi,

 I used google app engine for my one application, its on High Replication 
 storage scheme. When same application was on master/slave it took normal 
 time to compile jsp pages
 but now it takes more than 1 hr.

 Reading application configuration data...
 29 Dec, 2012 8:23:41 PM 
 com.google.apphosting.utils.config.AppEngineWebXmlReader readAppEngineWebXml
 INFO: Successfully processed 
 /usr/local/apache-tomcat-6.0.28/webapps/sample-paper/WEB-INF/appengine-web.xml
 29 Dec, 2012 8:23:41 PM 
 com.google.apphosting.utils.config.AbstractConfigXmlReader readConfigXml
 INFO: Successfully processed 
 /usr/local/apache-tomcat-6.0.28/webapps/sample-paper/WEB-INF/web.xml
 Beginning server interaction for tech-course...
 0% Creating staging directory
 5% Scanning for jsp files.
 8% Compiling jsp files.
 29 Dec, 2012 9:42:55 PM 
 com.google.apphosting.utils.config.AbstractConfigXmlReader readConfigXml
 INFO: Successfully processed 
 /tmp/appcfg5287499496253305068.tmp/WEB-INF/web.xml

 Can any one help me, why it takes so long time to compile jsp.



-- 
You received this message because you are subscribed to the Google Groups 
Google App Engine group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-appengine/-/dax8Egg8M30J.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Re: Setting Java7 flag

[Ludovic Champenois]

Java7 is currently for Trusted Tester and you can apply at: 
https://docs.google.com/a/google.com/forms/viewform?id=13UvQiEjr7ob-QXMSFch5LByQN8vHa70Rl98g8ipCf9c

Soon, we'll open to everyone.
Via Eclipse, you'll be able to add the --use_java7 flag to the appcfg tool 
in the next GPE release.
For now, assuming you are a trusted tester, you'll have to build your app 
and use the command line tool bin/appcfg  to update the application with 
the --use_java7 flag.

If you do not want to use Java7, you need to setup the Eclipse java 
compiler used by your project to target a Java 6 environment by adding 
these 2 flags to the javac compiler arguments:

-target 6 -source 6

This will create classes with the correct bytecode to run in a JVM 6 
environment.
Ludo

On Wednesday, December 26, 2012 11:48:35 PM UTC-8, Ramses wrote:

 Hello Al,

 Am getting following errorr when deploying to App Engine from Eclipse Juno

 The application contains Java 7 classes, but the --use_java7 flag has not 
 been set.

 Any idea how to to set the Java7 flag?

 Thanks


-- 
You received this message because you are subscribed to the Google Groups 
Google App Engine group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-appengine/-/e1Mq6Np1UVAJ.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Re: 1.7.4 Pre-release SDKs Available

[Ludovic Champenois]

Great!
The key change here for 1.7.4 is the way the appcfg.{sh|cmd} tool finds a 
javac compiler to compile the generated classes from JSP files.
Eclipse a bit complex to configure:
- there is a JVM used by Eclipse
- there is potentially a JRE/JDK configured to be used by your app engine 
project
- there is potentially a JRE/JDK used by an Eclipse spawed process to run 
the appcfg tool.
In this case, I think the last one was a JRE instead of a JDK.
We are updating the error message to be more clear.
The good news is that the JSP compilation phase has been dramatically 
improved: it is must faster now if you have many JSPs to precompile.
Thanks.

On Monday, December 10, 2012 9:30:34 AM UTC-8, Savaş L. wrote:

 i tried to reproduce the error i get, on a fresh eclipse and jdk 
 install with an empty project. 
 there was no error, and worked well. 

 1.7.4 seems more strict to match/find a jdk version that is same for 
 both eclipse, eclipse project, and appcfg tool. 

 the steps i took to make my original project work: 
 - i clean the WEB-INF/classes folder for my project 
 - i made a clean install of jdk 
 - i wrote a constant -vm path in eclipse.ini  to make eclipse force to 
 use specified jdk version 
 - i added new jdk to path  system variable table of win 7 
 - i changed munjutaglib.java to something another like munjutags.java 

 and problems gone, i could able to deploy with 1.7.4 
 thanks to Ludo, to show me a way for the solution. 


-- 
You received this message because you are subscribed to the Google Groups 
Google App Engine group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-appengine/-/Pm3fvRdBtfQJ.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Re: 1.7.4 Pre-release SDKs Available

[Ludovic Champenois]

Hi,
We are pushing Maven artifacts the same day as the release, so hopefully 
very very soon (tm).
You'll also notice a new Maven App Engine plugin that allows you to get a 
SDK and start the local dev server as well as updating your apps 
all directly from Maven...
 

On Monday, December 10, 2012 11:41:53 AM UTC-8, Andrew Kandzuba wrote:

 Hi Richmond,

 Good news for all GAE devs!
 I have a quick question - any maven repos for GAE 1.7.4 are yet available 
 for those who use it? 
 I was try to migrate to new API but got

 Downloading: 
 http://maven.objectify-appengine.googlecode.com/git/com/google/appengine/appengine-api-1.0-sdk/1.7.4/appengine-api-1.0-sdk-1.7.4.pom
 [WARNING] The POM for com.google.appengine:appengine-api-1.0-sdk:jar:1.7.4 
 is missing, no dependency information available
 Downloading: 
 http://repo1.maven.org/maven2/com/google/appengine/appengine-tools-sdk/1.7.4/appengine-tools-sdk-1.7.4.pom
 Downloading: 
 http://maven.objectify-appengine.googlecode.com/git/com/google/appengine/appengine-tools-sdk/1.7.4/appengine-tools-sdk-1.7.4.pom
 [WARNING] The POM for com.google.appengine:appengine-tools-sdk:jar:1.7.4 
 is missing, no dependency information available
 Downloading: 
 http://repo1.maven.org/maven2/com/google/appengine/appengine-api-labs/1.7.4/appengine-api-labs-1.7.4.pom
 Downloading: 
 http://maven.objectify-appengine.googlecode.com/git/com/google/appengine/appengine-api-labs/1.7.4/appengine-api-labs-1.7.4.pom
 [WARNING] The POM for com.google.appengine:appengine-api-labs:jar:1.7.4 is 
 missing, no dependency information available
 Downloading: 
 http://repo1.maven.org/maven2/com/google/appengine/appengine-api-stubs/1.7.4/appengine-api-stubs-1.7.4.pom
 Downloading: 
 http://maven.objectify-appengine.googlecode.com/git/com/google/appengine/appengine-api-stubs/1.7.4/appengine-api-stubs-1.7.4.pom
 [WARNING] The POM for com.google.appengine:appengine-api-stubs:jar:1.7.4 
 is missing, no dependency information available
 Downloading: 
 http://repo1.maven.org/maven2/com/google/appengine/appengine-testing/1.7.4/appengine-testing-1.7.4.pom
 Downloading: 
 http://maven.objectify-appengine.googlecode.com/git/com/google/appengine/appengine-testing/1.7.4/appengine-testing-1.7.4.pom
 [WARNING] The POM for com.google.appengine:appengine-testing:jar:1.7.4 is 
 missing, no dependency information available

 Thanks in advance!

 Andrew.

 On Saturday, December 8, 2012 11:20:27 AM UTC+2, Richmond Manzana wrote:

 Hello Everyone!

 We've posted the pre-release SDKs for Python and Java here:
 http://code.google.com/p/googleappengine/downloads/list

 My apologies for not announcing this to the group sooner, some of you may 
 have noticed that they were available about a day ago.

 Pre-release notes below.

 Cheers,

 Rich


 App Engine Python SDK - Pre-Release Notes

 Version 1.7.4
 ===
 - Mail API Quotas have been updated. For more information please see:
 https://developers.google.com/appengine/docs/quotas.html
 - Background threads are now a GA feature.
 - Traffic Splitting is now a GA feature.
 - Task Queue Statistics is now a GA feature.
 - Logs API now has the ability to fetch requests based on a list of
   request_ids. Currently, this only works in production and is not supported
   in dev_appserver.
 - Python Interpreter has been upgraded to 2.7.3.
 - WebOb 1.2.3 is now available for Python 2.7.
 - DISTINCT for Datastore queries is now available as an experimental feature.
 - Matplotlib v1.1.1 is now available as an experimental feature.
 - The decommissioned Conversion API has been removed.
 - Channel API now supports channels being used across multiple application
   versions and backends. You can also limit channel usage to a specific
   application version by adding it to the client id when creating a channel.
 http://code.google.com/p/googleappengine/issues/detail?id=5123
 - Mail API now sends notifications for emails that bounce.
 http://code.google.com/p/googleappengine/issues/detail?id=7451






 App Engine Java SDK - Pre-Release Notes

 Version 1.7.4
 =
 - Mail API Quotas have been updated. For more information please see:
 https://developers.google.com/appengine/docs/quotas.html
 - Traffic Splitting is now a GA feature.
 - Task Queue Statistics is now a GA feature.
 - Logs API now has the ability to fetch requests based on a list of
   request_ids. Currently, this only works in production and is not supported
   in dev_appserver.
 - DISTINCT feature for Datastore queries is now available as an experimental
   feature.
 - The decommissioned Conversion API has been removed.
 - Channel API now supports channels being used across multiple application
   versions and backends. You can also limit channel usage to a specific
   application version by adding it to the client id when creating a channel.
 http://code.google.com/p/googleappengine/issues/detail?id=5123
 - Mail API now sends notifications for emails that bounce.
 

Re: [google-appengine] Re: 1.7.4 Pre-release SDKs Available

[Ludovic Champenois]

The group id is *com.google.appengine* and we push it with any new release 
of the SDK, like the other artifacts.
Dependency is 
dependency
  groupIdcom.google.appengine/groupId
   artifactIdappengine-maven-plugin/artifactId
   version1.7.3/version
/dependency

(1.7.4 soon),
Doc is for now at https://code.google.com/p/appengine-maven-plugin/
More sample projects soon.
Ludo

On Monday, December 10, 2012 2:50:51 PM UTC-8, James Broberg wrote:

 New maven plugin? How does it differ from:
 https://github.com/maven-gae-plugin/maven-gae-plugin

 On 11 December 2012 08:06, Ludovic Champenois lu...@google.comjavascript:
  wrote:

 Hi,
 We are pushing Maven artifacts the same day as the release, so hopefully 
 very very soon (tm).
 You'll also notice a new Maven App Engine plugin that allows you to get a 
 SDK and start the local dev server as well as updating your apps 
 all directly from Maven...
  

 On Monday, December 10, 2012 11:41:53 AM UTC-8, Andrew Kandzuba wrote:

 Hi Richmond,

 Good news for all GAE devs!
 I have a quick question - any maven repos for GAE 1.7.4 are yet 
 available for those who use it? 
 I was try to migrate to new API but got

 Downloading: http://maven.objectify-**appengine.googlecode.com/git/**
 com/google/appengine/**appengine-api-1.0-sdk/1.7.4/**
 appengine-api-1.0-sdk-1.7.4.**pomhttp://maven.objectify-appengine.googlecode.com/git/com/google/appengine/appengine-api-1.0-sdk/1.7.4/appengine-api-1.0-sdk-1.7.4.pom
 [WARNING] The POM for com.google.appengine:**
 appengine-api-1.0-sdk:jar:1.7.**4 is missing, no dependency information 
 available
 Downloading: http://repo1.maven.org/maven2/**com/google/appengine/**
 appengine-tools-sdk/1.7.4/**appengine-tools-sdk-1.7.4.pomhttp://repo1.maven.org/maven2/com/google/appengine/appengine-tools-sdk/1.7.4/appengine-tools-sdk-1.7.4.pom
 Downloading: http://maven.objectify-**appengine.googlecode.com/git/**
 com/google/appengine/**appengine-tools-sdk/1.7.4/**
 appengine-tools-sdk-1.7.4.pomhttp://maven.objectify-appengine.googlecode.com/git/com/google/appengine/appengine-tools-sdk/1.7.4/appengine-tools-sdk-1.7.4.pom
 [WARNING] The POM for com.google.appengine:**appengine-tools-sdk:jar:1.7.4 
 is missing, no dependency information available
 Downloading: http://repo1.maven.org/maven2/**com/google/appengine/**
 appengine-api-labs/1.7.4/**appengine-api-labs-1.7.4.pomhttp://repo1.maven.org/maven2/com/google/appengine/appengine-api-labs/1.7.4/appengine-api-labs-1.7.4.pom
 Downloading: http://maven.objectify-**appengine.googlecode.com/git/**
 com/google/appengine/**appengine-api-labs/1.7.4/**
 appengine-api-labs-1.7.4.pomhttp://maven.objectify-appengine.googlecode.com/git/com/google/appengine/appengine-api-labs/1.7.4/appengine-api-labs-1.7.4.pom
 [WARNING] The POM for com.google.appengine:**appengine-api-labs:jar:1.7.4 
 is missing, no dependency information available
 Downloading: http://repo1.maven.org/maven2/**com/google/appengine/**
 appengine-api-stubs/1.7.4/**appengine-api-stubs-1.7.4.pomhttp://repo1.maven.org/maven2/com/google/appengine/appengine-api-stubs/1.7.4/appengine-api-stubs-1.7.4.pom
 Downloading: http://maven.objectify-**appengine.googlecode.com/git/**
 com/google/appengine/**appengine-api-stubs/1.7.4/**
 appengine-api-stubs-1.7.4.pomhttp://maven.objectify-appengine.googlecode.com/git/com/google/appengine/appengine-api-stubs/1.7.4/appengine-api-stubs-1.7.4.pom
 [WARNING] The POM for com.google.appengine:**appengine-api-stubs:jar:1.7.4 
 is missing, no dependency information available
 Downloading: http://repo1.maven.org/maven2/**com/google/appengine/**
 appengine-testing/1.7.4/**appengine-testing-1.7.4.pomhttp://repo1.maven.org/maven2/com/google/appengine/appengine-testing/1.7.4/appengine-testing-1.7.4.pom
 Downloading: http://maven.objectify-**appengine.googlecode.com/git/**
 com/google/appengine/**appengine-testing/1.7.4/**
 appengine-testing-1.7.4.pomhttp://maven.objectify-appengine.googlecode.com/git/com/google/appengine/appengine-testing/1.7.4/appengine-testing-1.7.4.pom
 [WARNING] The POM for com.google.appengine:**appengine-testing:jar:1.7.4 
 is missing, no dependency information available

 Thanks in advance!

 Andrew.

 On Saturday, December 8, 2012 11:20:27 AM UTC+2, Richmond Manzana wrote:

 Hello Everyone!

 We've posted the pre-release SDKs for Python and Java here:
 http://code.google.com/p/**googleappengine/downloads/listhttp://code.google.com/p/googleappengine/downloads/list

 My apologies for not announcing this to the group sooner, some of you 
 may have noticed that they were available about a day ago.

 Pre-release notes below.

 Cheers,

 Rich


 App Engine Python SDK - Pre-Release Notes

 Version 1.7.4
 ==**=
 - Mail API Quotas have been updated. For more information please see:
 https://developers.google.com/**appengine/docs/quotas.html 
 https://developers.google.com/appengine/docs/quotas.html
 - Background threads are now a GA feature.
 - Traffic Splitting is now a GA feature

[google-appengine] Re: 1.7.4 Pre-release SDKs Available

[Ludovic Champenois]

Hi, 
Sorry for the trouble. 
Could you share a few data from your project? 
For example: 
1/ the entire directory name where the app is (space in dir or not) 
2/ the exact location in the web app of the tag lib and the jsp using it. 
If relevant, some entries in the web.xml. 
3/ Some code fragment if possible of the usage 
4/ If you could share the tag lib and a small jsp using it, where you can 
reproduce the issue it would great! 
Let me know if you want to share the information privately. 

Many thanks for your support, I hope it will be easy to fix with your help, 
Ludo 

On Saturday, December 8, 2012 3:04:31 AM UTC-8, Savaş L. wrote:

 with 1.7.4 pre, i am getting a strange error, it works locally but 
 when i try to deploy it produces this.. 
 it doesnt see my custom made taglib, i couldnt find a solution yet.. 

 Preparing to deploy: 
 Created staging directory at: 'C:\Users\savi\AppData\Local\Temp 
 \appcfg1147116988784742342.tmp' 
 Scanning for jsp files. 
 Compiling jsp files. 
 com.google.appengine.tools.admin.JspCompilationException: Failed to 
 compile jsp files. 
 Exception in thread main org.apache.jasper.JasperException: The 
 class net.munju.viewhelpers.MunjuTagLib specified in TLD for the 
 function mu:postDateHelper cannot be found: 
 net.munju.viewhelpers.MunjuTagLib 
 at 
 org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:
  

 51) 
 at 
 org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java: 
 409) 
 at 
 org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java: 
 181) 
 at org.apache.jasper.compiler.Validator$ValidateVisitor 
 $1MapperELVisitor.visit(Validator.java:1644) 
 at 
 org.apache.jasper.compiler.ELNode$Function.accept(ELNode.java:129) 
 at org.apache.jasper.compiler.ELNode$Nodes.visit(ELNode.java:200) 
 at 
 org.apache.jasper.compiler.ELNode$Visitor.visit(ELNode.java:242) 
 at org.apache.jasper.compiler.ELNode$Root.accept(ELNode.java:56) 
 at org.apache.jasper.compiler.ELNode$Nodes.visit(ELNode.java:200) 
 at org.apache.jasper.compiler.Validator 
 $ValidateVisitor.getFunctionMapper(Validator.java:1672) 
 at org.apache.jasper.compiler.Validator 
 $ValidateVisitor.prepareExpression(Validator.java:1540) 
 at org.apache.jasper.compiler.Validator 
 $ValidateVisitor.visit(Validator.java:720) 
 at 
 org.apache.jasper.compiler.Node$ELExpression.accept(Node.java:958) 
 at org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2361) 
 at 
 org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2411) 


 On Dec 8, 11:20 am, Richmond Manzana richm...@google.com wrote: 
  Hello Everyone! 
  
  We've posted the pre-release SDKs for Python and Java here:
 http://code.google.com/p/googleappengine/downloads/list 
  
  My apologies for not announcing this to the group sooner, some of you 
 may 
  have noticed that they were available about a day ago. 
  
  Pre-release notes below. 
  
  Cheers, 
  
  Rich 
  
  App Engine Python SDK - Pre-Release Notes 
  
  Version 1.7.4 
  === 
  - Mail API Quotas have been updated. For more information please see: 
 https://developers.google.com/appengine/docs/quotas.html 
  - Background threads are now a GA feature. 
  - Traffic Splitting is now a GA feature. 
  - Task Queue Statistics is now a GA feature. 
  - Logs API now has the ability to fetch requests based on a list of 
request_ids. Currently, this only works in production and is not 
 supported 
in dev_appserver. 
  - Python Interpreter has been upgraded to 2.7.3. 
  - WebOb 1.2.3 is now available for Python 2.7. 
  - DISTINCT for Datastore queries is now available as an experimental 
 feature. 
  - Matplotlib v1.1.1 is now available as an experimental feature. 
  - The decommissioned Conversion API has been removed. 
  - Channel API now supports channels being used across multiple 
 application 
versions and backends. You can also limit channel usage to a specific 
application version by adding it to the client id when creating a 
 channel. 
 http://code.google.com/p/googleappengine/issues/detail?id=5123 
  - Mail API now sends notifications for emails that bounce. 
 http://code.google.com/p/googleappengine/issues/detail?id=7451 
  
  App Engine Java SDK - Pre-Release Notes 
  
  Version 1.7.4 
  = 
  - Mail API Quotas have been updated. For more information please see: 
 https://developers.google.com/appengine/docs/quotas.html 
  - Traffic Splitting is now a GA feature. 
  - Task Queue Statistics is now a GA feature. 
  - Logs API now has the ability to fetch requests based on a list of 
request_ids. Currently, this only works in production and is not 
 supported 
in dev_appserver. 
  - DISTINCT feature for Datastore queries is now available as an 
 experimental 
feature. 
  - The decommissioned 

[google-appengine] Re: Permission check bug in GAE

[Ludovic Champenois]

I see it works only when TestCallee is public.
Will check if this security rule can be relaxed.

Ludo

On Saturday, December 8, 2012 9:43:27 AM UTC-8, Zbynek Vyskovsky wrote:

 Hi,
 I found an issue with hibernate failure when initializing EntityManager, 
 due to security checks. This was already described at 
 http://code.google.com/p/hibernate-gae/issues/detail?id=5

 The problem is that GAE uses some wrapper to call the method which 
 disallows the access because of different package.

 I tried to create minimalistic code which works correctly in local JVM but 
 fails in GAE, please find below. This approach is completely correct in 
 Java, but it fails in GAE. Unfortunately it disallows to deploy hibernate 
 code right now. Can someone check what could be done with it or how to 
 work-around it?

 Best Regards,
Zbynek


 package com.example.gafail.servlet;

 class TestCallee
 {
 public static StringcalleeMethod()
 {
 return ok;
 }
 }

 package com.example.gafail.servlet;

 import javax.servlet.http.HttpServlet;
 import javax.servlet.http.HttpServletRequest;
 import javax.servlet.http.HttpServletResponse;


 public class GaFailServlet extends HttpServlet
 {
 private static final long serialVersionUID = 1L;

 @Override
 public voiddoGet(HttpServletRequest request, 
 HttpServletResponse response)
 {
 try {
 response.getWriter().write(Hello: 
 +TestCallee.class.getMethod(calleeMethod).invoke(null));
 }
 catch (Exception ex) {
 throw new RuntimeException(ex);
 }
 }
 }



-- 
You received this message because you are subscribed to the Google Groups 
Google App Engine group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-appengine/-/AvX23BUQjekJ.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[appengine-java] Re: Unable to start embedded HTTP server

[Ludovic Champenois]

Please, upgrade to 1.6.3.1 that solves this issue with newer JDKs.

Ludo

On Wednesday, March 14, 2012 12:42:03 AM UTC-7, Fan Yang wrote:

 Hi,

 I installed the latest SDK 1.6.3 and now I am getting following error when 
 I run an example web app following the tutorial on the GAE official website:

 Initializing App Engine server
 Unable to start embedded HTTP server
 com.google.gwt.core.ext.UnableToCompleteException: (see previous log 
 entries)
 at 
 com.google.appengine.tools.development.gwt.AppEngineLauncher.start(AppEngineLauncher.java:102)
 at com.google.gwt.dev.DevMode.doStartUpServer(DevMode.java:509)
 at com.google.gwt.dev.DevModeBase.startUp(DevModeBase.java:1068)
 at com.google.gwt.dev.DevModeBase.run(DevModeBase.java:811)
 at com.google.gwt.dev.DevMode.main(DevMode.java:311)
[ERROR] Unable to start App Engine server
 java.lang.RuntimeException: Unable to restore the previous TimeZone
 at 
 com.google.appengine.tools.development.DevAppServerImpl.restoreLocalTimeZone(DevAppServerImpl.java:228)
 at 
 com.google.appengine.tools.development.DevAppServerImpl.start(DevAppServerImpl.java:164)
 at 
 com.google.appengine.tools.development.gwt.AppEngineLauncher.start(AppEngineLauncher.java:97)
 at com.google.gwt.dev.DevMode.doStartUpServer(DevMode.java:509)
 at com.google.gwt.dev.DevModeBase.startUp(DevModeBase.java:1068)
 at com.google.gwt.dev.DevModeBase.run(DevModeBase.java:811)
 at com.google.gwt.dev.DevMode.main(DevMode.java:311)
 Caused by: java.lang.NoSuchFieldException: defaultZoneTL
 at java.lang.Class.getDeclaredField(Unknown Source)
 at 
 com.google.appengine.tools.development.DevAppServerImpl.restoreLocalTimeZone(DevAppServerImpl.java:222)
 ... 6 more
 [ERROR] shell failed in doStartupServer method

 I tried creating new project but still gettting same error. 


-- 
You received this message because you are subscribed to the Google Groups 
Google App Engine for Java group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-appengine-java/-/Z-JtcukMesQJ.
To post to this group, send email to google-appengine-java@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine-java+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine-java?hl=en.