[google-appengine] Re: Why is App Engine calling contextInitialized repeatedly?

2017-06-07 Thread 'George (Cloud Platform Support)' via Google App Engine
Hello Joshua, This is potentially a quite interesting issue. Which global variables or static fields do you intend to set? How were these sometimes already set? Some examples and relevant detail would come handy. In fact, the contextInitialized method receives notification that the web applic

Re: [google-appengine] Re: Why is App Engine calling contextInitialized repeatedly?

2017-06-07 Thread Joshua Fox
On Wed, Jun 7, 2017 at 6:01 PM, 'George (Cloud Platform Support)' via Google App Engine wrote: > Hello Joshua, > > This is potentially a quite interesting issue. Which global variables or > static fields do you intend to set? > Just some static variables which are set from Datastore to reflect so

Re: [google-appengine] Re: Why is App Engine calling contextInitialized repeatedly?

2017-06-07 Thread Joshua Fox
The concept "Idle Resident instance" might be relevant here. Are instances switched from active to idle to active -- not actually stopping the JVM on switch to idle, and invoking *contextInitialized *on switch to active? On Wed, Jun 7, 2017 at 6:17 PM, Joshua Fox wrote: > > > On Wed, Jun 7,

Re: [google-appengine] Re: Why is App Engine calling contextInitialized repeatedly?

2017-06-08 Thread 'George Suceveanu' via Google App Engine
There are no "idle" instances, and one of the reasons is precisely what we speak of: possible initialization issues. Instances are either wholly new and spun up to secure scalability, or totally destroyed, in other words either alive or dead, nothing in-between. On 8 June 2017 at 02:53, Joshua Fox