I am experiencing the same behavior. Everything seems to work well both
ways, and yet, it would be nice to know what causes the difference.
Thomas
On Tuesday, January 28, 2020 at 11:14:05 AM UTC-7, DIEGO GARCIA TEBA wrote:
>
> Hi,
>
> I'm experiencing that deploying with Cloud SDK Maven Plugin
App Engine Standard…". You can read more at:
>
> https://cloud.google.com/eclipse/docs/deploying
>
> Hope that helps.
>
> Brian.
>
>
> On 18-Jun-2018, at 7:07 AM, Thomas Becker > wrote:
>
> George,
>
> I'm sure you're right about Maven being the better
George,
I'm sure you're right about Maven being the better way to do things. Here's
the reason why I haven't gone there. I've been working with the Google App
Engine Eclipse plugin since 2010 or so. I recently switched to the new
plugin, Google Cloud Tools for Eclipse. After installing that
cs/standard/java/tools/migrating-from-appcfg-to-gcloud
says
Currently, the gcloud command-line tool does not deploy Java applications
to production App Engine
I would much appreciate it if you could acknowledge that these two
statements are in contradiction to each other.
Sincerely,
Thomas Bec
tandard with "gcloud app deploy"
now works like a charm.
I would like to respectfully request to not change the default values of
options. Changing default vaules of options
is likely to cause a lot of people a lot of pain.
On Friday, June 15, 2018 at 9:40:31 AM UTC-6, Thomas Becke
Thanks for the information. As a suggestion, you may want to correct the
page
https://cloud.google.com/sdk/gcloud/reference/app/deploy
On that page, in the example section, it says, To deploy an App Engine
Standard Java service, run:
$ gcloud app deploy
* is that
it guarantees requests to go to different instances.
I don't remember much about how JDO works, but are you sure you are
opening/closing sessions correctly?
Jeff
On Tue, Aug 4, 2015 at 7:56 PM, Thomas Becker walkswiththeb...@gmail.com
wrote:
Thanks again for eveybody's input. It looks like I
loads from an open session will return the same object. JPA works
the same way.
Objectify's session is very similar to this (minus the dirty change
detection).
If you aren't closing your PM sessions... this would explain the problem.
Jeff
On Wed, Aug 5, 2015 at 11:59 AM, Thomas Becker
to confirm and not closing resulted in eventual while
closing resulted in strong consistency. Give it a try and let me know if
that helps.
On Saturday, August 1, 2015 at 6:24:55 PM UTC-4, Thomas Becker wrote:
I am using the app engine datastore with Java JDO. According to the
documentation
Thomas Becker walkswiththeb...@gmail.com
wrote:
Thanks, Jeff! And one more thing, it's pretty clear from the doc, but
let me make sure anyway. The same is true for ancestor queries, they
guarantee strong consistency even when not performed inside a transaction,
right?
Thomas
On Mon, Aug 3, 2015
faster
since it does not require a quorum response. However, this is a pretty
obscure feature.
Jeff
On Mon, Aug 3, 2015 at 7:30 PM, Thomas Becker walkswiththeb...@gmail.com
wrote:
Thanks for your detailed and thoughtful answer, Jeff. I was aware of the
fact that within a transaction, all
(Cloud Platform Support)
rbruy...@google.com wrote:
If you can create a sample app that shows this post on it on the PIT
https://code.google.com/p/googleappengine/issues/entry so I can
investigate this further.
On Saturday, August 1, 2015 at 6:24:55 PM UTC-4, Thomas Becker wrote:
I am using
a consistent result set.) See the article Transaction Isolation in
App Engine
https://cloud.google.com/appengine/articles/transaction_isolation for
more information on how entities and indexes are updated.
'
On Saturday, August 1, 2015 at 6:24:55 PM UTC-4, Thomas Becker wrote:
I am using
I am using the app engine datastore with Java JDO. According to the
documentation, ancestor queries are always strongly consistent. Recently,
however, I've been seeing a lot of stale data from ancestor queries. It
seems to happen randomly. A query may return the most recent data, and a
moment
27, 2013 8:53:33 PM UTC-7, Thomas Becker wrote:
I just deployed my Java app from Eclipse (Eclipse Kepler, GAE SDK 1.8.5).
The deployment succeeds, but the new version times out on every request.
When I deploy from a different machine that's still running Eclipse Juno
and GAE SDK 1.7.5, all
).
I've solved many problems like yours simply adding a v on the version
names.
2013/9/28 Thomas Becker walkswit...@gmail.com javascript:
Update: the problem occurs only when deploying from a Mac (Mac OS
10.7.5). All is well when I deploy from a Windows machine (except for the
minor glitch
Thanks, I'll try that!
On Sat, Sep 28, 2013 at 1:37 PM, Stefano Ciccarelli
sciccare...@gmail.comwrote:
Your has a single module named default, I would give a try adding a letter
to the version name.
Il giorno sabato 28 settembre 2013, Thomas Becker ha scritto:
You're talking about
Thanks, I'll try that!
On Saturday, September 28, 2013 1:37:59 PM UTC-7, Stefano Ciccarelli wrote:
Your has a single module named default, I would give a try adding a letter
to the version name.
Il giorno sabato 28 settembre 2013, Thomas Becker ha scritto:
You're talking about modules
Nah, using a letter in the version number didn't make a difference. Same
problem.
On Saturday, September 28, 2013 2:06:03 PM UTC-7, Thomas Becker wrote:
Thanks, I'll try that!
On Saturday, September 28, 2013 1:37:59 PM UTC-7, Stefano Ciccarelli wrote:
Your has a single module named default
I just deployed my Java app from Eclipse (Eclipse Kepler, GAE SDK 1.8.5).
The deployment succeeds, but the new version times out on every request.
When I deploy from a different machine that's still running Eclipse Juno
and GAE SDK 1.7.5, all is well. Two things are conspicuous:
1) The new
I actually did find two issues. When migrating to Java 7, one needs to
upgrade from JDO 2.3 (datanucleus plugin v1) to JDO 3.0 (datanucleus
plugin v2). This is stated in the documentation at the very end of the page
https://developers.google.com/appengine/docs/java/java7 .
But JDO 3.0
21 matches
Mail list logo
