E_VERSION")*
>
> Also, try logging *System.getenv() *to see what the system has to offer.
>
> On Tue, Oct 16, 2018 at 10:30 AM Ben Rometsch > wrote:
>
>> I'm running the Flex VM, not standard. That class is not available to me.
>>
>> On Monday, 15 October 2018 23
I'm running the Flex VM, not standard. That class is not available to me.
On Monday, 15 October 2018 23:30:10 UTC+1, Julie (cloud platform support)
wrote:
>
> Do you need a scripted method of getting the info? If so try this Java
> API class
>
I'm running a tweaked version of gcr.io/google_appengine/openjdk with a
Play Framework 1.5 application on Flex VM. Running
System.getenv("CURRENT_VERSION_ID")
Returns nothing. Is there a way to get the current version ID from the Java
runtime?
Thanks
--
You received this message because
Great - thanks!
On Wednesday, 18 April 2018 16:20:37 UTC+1, Jordan (Cloud Platform Support)
wrote:
>
> We are indeed working on providing Node.js language support for App Engine
> Standard. It is still in the early access stage and you can try it by
> filling out the Early Access request form
https://github.com/GoogleCloudPlatform/nodejs-docs-samples/blob/master/appengine/hello-world/standard/app.yaml
Can anyone comment on this? Is this happening?
--
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To unsubscribe from this group
OK thanks - have submitted https://issuetracker.google.com/issues/68793577
On Wednesday, 1 November 2017 18:28:01 UTC, Kenworth (Google Cloud
Platform) wrote:
>
> Hi Ben, a thread like this is off-topic for Google Groups. As it may
> potentially be a defect on the platform and most likely lead
As an update, I notice that both VMs were restarted at similar
times
https://s3-eu-west-1.amazonaws.com/dabnster-screenshots/App_Engine_Instances_-_HoxtonMix_Admin_EU_2017-11-01_14-03-37.png
On Wednesday, 1 November 2017 14:01:16 UTC, Ben Rometsch wrote:
>
> I have a Java (play fra
I have a Java (play framework) application running in the GAE flexible
environment that has been running perfectly for months. For the last week
the application has been showing error messages at around 13:00 UTC each
day. After around 10 minutes the app resumes normal operation without me
took longer than 30m0s seconds
On Wednesday, 31 May 2017 15:10:24 UTC+1, Ben Rometsch wrote:
>
> I'm seeing this again, where a build of my app that was working fine is
racker.google.com/issues/new> including debug logs, time
> stamps, and details of what solutions you've tried.
>
> On Thursday, April 27, 2017 at 12:15:51 PM UTC-4, Ben Rometsch wrote:
>>
>> 10 minutes later attempting to deploy the same code worked correctly.
>>
&
10 minutes later attempting to deploy the same code worked correctly.
--
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
After several successful deployments, I have started getting errors at the
end of the process:
Updating service [default]...failed.
ERROR: (gcloud.app.deploy) Error Response: [4] Timed out creating VMs.
Is there any way this can be mitigated?
--
You received this message because you are
thread once I've finished testing.
>>
>> On Sunday, March 5, 2017 at 4:03:23 AM UTC-5, Ben Rometsch wrote:
>>>
>>> Hmm I tried extending FROM gcr.io/google_appengine/openjdk but it's
>>> still not working. Any ideas? How does the cron.yaml get proces
Hmm I tried extending FROM gcr.io/google_appengine/openjdk but it's still
not working. Any ideas? How does the cron.yaml get processed included into
the Appengine backend?
On Saturday, 4 March 2017 14:19:23 UTC, Ben Rometsch wrote:
>
> Hi,
>
> I'm running a custom Docker runtime on
ou can upload with appcfg.py also).
>
> Nick
> On 05/03/2017 1:19 AM, "Ben Rometsch" <b...@solidstategroup.com
> > wrote:
>
>> Hi,
>>
>> I'm running a custom Docker runtime on flexible VMs. I have an cron.yaml
>> file in my root dir that looks
Hi,
I'm running a custom Docker runtime on flexible VMs. I have an cron.yaml
file in my root dir that looks like:
cron:
- description: daily summary job
url: /tasks/test
schedule: every 1 minutes
It's not being run. Is cron.yaml supported in custom Docker runtimes? The
documentation
6 at 8:48:37 PM UTC+3, Ben Rometsch wrote:
>>
>> Im seeing this on the STDOUT logs when I ssh into the machine - not sure
>> how relevant it is?
>>
>> 2016-09-02 16:43:46.730:WARN:oejx.XmlConfiguration:main: Config error at
>> > default="."/>
(URLClassLoader.java:361)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
On Friday, 2 September 2016 18:12:40 UTC+1, Ben Rometsch wrote:
>
> I have exactly the same problem. Need an urgent solution! I have 2
> flexible VMs running one app. Both servers just got restarte
I have exactly the same problem. Need an urgent solution! I have 2 flexible
VMs running one app. Both servers just got restarted as part of their
weekly upgrade and are now completely broken! Is anyone at Google looking
at this?
On Friday, 2 September 2016 14:55:16 UTC+1, Arnold Minde wrote:
code works out!
>
> Cheers,
>
> Nick
> Cloud Platform Community Support
>
> On Monday, August 22, 2016 at 7:36:41 AM UTC-4, Ben Rometsch wrote:
>>
>> Hi Nick,
>>
>> I'm not sure where to find the cpu_ms vs ms times? Can you point me to
>> where I would fin
CPU or a network
> call?
>
> Cheers,
>
> Nick
> Cloud Platform Community Support
>
> On Friday, August 19, 2016 at 6:07:01 AM UTC-4, Ben Rometsch wrote:
>>
>> Thanks for the reply Nick.
>>
>> I dont think I was clear in my previous post, but when I think t
this screen wrong?
On Wednesday, 17 August 2016 10:19:17 UTC+1, Ben Rometsch wrote:
>
> We are running a Java Cloud Endpoints API on Flexible VMs. Most of the
> endpoints complete in a timely manner, but from time to time we see things
> like the attached in the trace:
>
&
We are running a Java Cloud Endpoints API on Flexible VMs. Most of the
endpoints complete in a timely manner, but from time to time we see things
like the attached in the trace:
I have 2 flexible VM instances running. In the console, the graph (that
used to work back when they were "Managed VMs") shows zero instances?
--
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To unsubscribe from this group and stop
24 matches
Mail list logo
