[google-appengine] Re: Channel Service: Allow-origin ( Cross-domain )

[Kristopher Giesing]

It should work cross-domain already.  Why do you need to configure those 
headers?

- Kris

On Monday, October 22, 2012 2:11:27 PM UTC-7, niedbalski wrote:
>
> Hello guys,
>
> Do you know any way or workaround to get the channel service working with 
> cross-domain requests? Is possible
> to configure the following headers??
>
> Access-Control-Allow-Headers,
> 'Access-Control-Allow-Origin', 
>
> Any hint or idea will be appreciated 
>

-- 
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/-/ZadMJmL8y4cJ.
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.

Re: [google-appengine] does the channel api work across domains?

[Kristopher Giesing]

The live version uses an embedded iFrame.  The dev server version can't 
work across domains without modifications, but I have gotten it to work by 
adding a method that overrides the base URL.

- Kris

On Monday, October 22, 2012 2:27:28 PM UTC-7, niedbalski wrote:
>
> Hello Chard ...
>
> The big question here is HOW ?
>
> On Friday, December 3, 2010 3:24:30 PM UTC-3, Peter Petrov wrote:
>>
>> You can. The Channel API is designed to workaround 
>> the JavaScript same-origin policy, and will work across domains.
>>
>> On Fri, Dec 3, 2010 at 8:16 PM, Chad Burt  wrote:
>>
>>> Say I have an application hosted outside of appengine. I'd like to build 
>>> a chat app hosted on appengine to take advantage of the channel API. Can I 
>>> use that system from the first app on a different domain? If so, will it 
>>> work on all browsers, or just those that support the crossdomain access 
>>> control header ?
>>> Thanks,
>>> -Chad
>>>
>>> -- 
>>> 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-a...@googlegroups.com.
>>> To unsubscribe from this group, send email to 
>>> google-appengi...@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 view this discussion on the web visit 
https://groups.google.com/d/msg/google-appengine/-/XhrDeAk5WQUJ.
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: Issues with Channel connection status

[Kristopher Giesing]

Yeah, I already starred that one.

So... what's the solution?  Is there one or do I need to roll my own 
channel replacement?

On Monday, October 22, 2012 12:46:43 PM UTC-7, Aleksei Rovenski wrote:
>
> My experience with presence notifications is also that they are 
> unreliable. 
> Channel API has some problems, you can read this topic for more:
>
> https://groups.google.com/forum/?fromgroups=#!searchin/google-appengine/channel$20unreliable/google-appengine/lqaCMEj8IyQ/7eWTcLqJxWsJ
>
> I have created an issue some time ago re presences problem, please star 
> it. 
> It is as simple as adding a timestamp to presence notification.
> http://code.google.com/p/googleappengine/issues/detail?id=8151
>
> PS Btw for about a month now there is a new problem that working channel 
> stops receiving messages w/o any errors for undefined period of time and 
> then may start receiving them again...
>
>

-- 
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/-/yeFYz_SIikYJ.
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: No warmup requests are being issued by the Java instance scheduler

[Kristopher Giesing]

I'm not asking you to prove it to yourself or me, but to Google :)

- Kris

On Monday, October 22, 2012 3:17:44 PM UTC-7, Carl Schroeder wrote:
>
> It is actually pretty easy to prove when a request is going to a cold 
> instance vs a warmed up one. Simply output a log line from a place that is 
> only called during initialization of an instance. Make sure that the warmup 
> handler calls this part of the code, and that the code is only called once 
> per instance. I put mine in the abstraction layer that sits between 
> appengine, and my application code. 
>
> My warmup handler shows this log message. So does any user facing request 
> that causes an instance of my app to be initialized.
>
> Also, I did a search for "This request caused a new process" in the log 
> files. Just today, 27 instance starts. My app can serve its user base off a 
> single instance with excellent response times. (If only I had a way to tell 
> the scheduler to piss off)
>
> For the past hour, I had 3 warmups handled and 4 user facing requests 
> routed to cold instances. I verified that the instances spun up by user 
> facing requests had different IDs than the ones spun up by warmup reqeusts. 
> I have an AWS instance that hits my site once every 60s to attempt to 
> insure that there is always a dynamic instance loaded. I have 1 resident 
> instance configured to "enable" warmups.
>
>
> On Monday, October 22, 2012 2:55:19 PM UTC-7, Kristopher Giesing wrote:
>>
>> Can you post the relevant logs?  Each request is stamped with the ID of 
>> the instance that served it.
>>
>> When I looked into my own logs I found that the request I thought was 
>> cold-served was actually going to a recently warmed instance, but that the 
>> warmup request didn't fully initialize everything so the first request 
>> after warmup was still too long.  But it sounds like you have more and 
>> better data here to prove something is actually broken.
>>
>> - Kris
>>
>> On Monday, October 22, 2012 11:07:11 AM UTC-7, Carl Schroeder wrote:
>>>
>>> I just tested with my Application Settings configured to have 1 Resident 
>>> instance.
>>>
>>> With 1 resident, and 1 idle instance. I hit a page reload. 7 requests 
>>> were served by the instances according to the Instances pane in the App 
>>> Engine Console. The requests were handled in the following manner:
>>> Zero went to the Resident instance. 
>>> 3 new instances were spun up. 2 with warmup requests, 1 with the first 
>>> user request given to a cold start.
>>> 4 then went to the existing idle dynamic instance
>>> 1 of the new instances handled 3 requests, the other 2 only handled 
>>> warmups.
>>>
>>> The VERY first request (the basic HTML of the page) went to a cold 
>>> instance. This happened despite the fact that there was an idle Resident 
>>> instance available AND an idle Dynamic instance available. The user 
>>> experience is staring at the browser for 20 seconds before anything 
>>> happens. That is unacceptable.
>>>
>>> Even with 4 dynamic instances, the scheduler is still spinning up new 
>>> ones with user facing requests. This is bizarre, pathological, diabolical, 
>>> nonsensical behavior. I am running out of adjectives here.
>>>
>>>

-- 
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/-/wR97gMq2QmwJ.
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] JPA and foreignkey to an entity "dico"

[ocrv]

Hello

I have two entity :

@Entity
public class City implements Serialiuzable
{
  @Id
  @GeneratedValue(strategy=GenerationType.IDENTITY)
  private Key gk_key;
  
  @Basic
  private String gs_city;
  @Basic
  private String gs_postalCode;
...
}
I create all city for belgium (2500 entity)

My seconde entity : 
@Entity
@Table(uniqueConstraints = { 
@UniqueConstraint(columnNames = { "gs_idGoogle", "gs_pseudo" }) })
public class User implements Serializable
{

  @Id
  @GeneratedValue(strategy=GenerationType.IDENTITY)
  private Key gk_key;

...
  @ManyToOne 
  @JoinTable(name = "USER_CITY")
  @JoinColumn(name = "gk_city")
  private City go_city;
...
}

When I create (em.persist) or modify (em.merge) an entity User, I have this 
Exception
A parent cannot be established or changed once an object has been persisted.

I use JPA

Thank you and sorry for my english

-- 
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/-/PKGZidSDnQYJ.
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.

Re: [google-appengine] Re: Thread Support on GAE

[Andrew Jessup]

For reference, we announced background threads for Python and Java in the 
1.6.4 release, which allows for a process that can outlive the request that 
triggered it.

https://developers.google.com/appengine/docs/python/backends/overview#background_threads
https://developers.google.com/appengine/docs/java/backends/overview#background_threads

-- 
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/-/4hsc8im1XiYJ.
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] Channel Service: Allow-origin ( Cross-domain )

[niedbalski]

Hello guys,

Do you know any way or workaround to get the channel service working with 
cross-domain requests? Is possible
to configure the following headers??

Access-Control-Allow-Headers,
'Access-Control-Allow-Origin', 

Any hint or idea will be appreciated 

-- 
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/-/VFjBL7OeMkgJ.
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.

Re: [google-appengine] does the channel api work across domains?

[niedbalski]

Hello Chard ...

The big question here is HOW ?

On Friday, December 3, 2010 3:24:30 PM UTC-3, Peter Petrov wrote:
>
> You can. The Channel API is designed to workaround 
> the JavaScript same-origin policy, and will work across domains.
>
> On Fri, Dec 3, 2010 at 8:16 PM, Chad Burt 
> > wrote:
>
>> Say I have an application hosted outside of appengine. I'd like to build 
>> a chat app hosted on appengine to take advantage of the channel API. Can I 
>> use that system from the first app on a different domain? If so, will it 
>> work on all browsers, or just those that support the crossdomain access 
>> control header ?
>> Thanks,
>> -Chad
>>
>> -- 
>> 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-a...@googlegroups.com
>> .
>> To unsubscribe from this group, send email to 
>> google-appengi...@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 view this discussion on the web visit 
https://groups.google.com/d/msg/google-appengine/-/p6oGqk0rgAMJ.
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] Got an SecurityException - Unable to get members for class

[Jambi]

Hey guys,

I am desperate. I´m working with appengine an Objectify and everything was 
great. I have a small app with only one Servlet on the server side. I am 
pretty sure that i haven´t made any changes that could cause this error and 
everything works fine on my local machine but I updated my app and now it´s 
not working anymore. 

How ever: When I´m trying to register my domain classes in my servlet I get 
the following exception (everything worked a few days ago on app engine):

Uncaught exception from servlet
javax.servlet.UnavailableException: java.lang.SecurityException: Unable to get 
members for class de...shared.ResortBase
at 
org.mortbay.jetty.servlet.ServletHolder.makeUnavailable(ServletHolder.java:415)
at 
org.mortbay.jetty.servlet.ServletHolder.initServlet(ServletHolder.java:458)
at 
org.mortbay.jetty.servlet.ServletHolder.getServlet(ServletHolder.java:339)
at 
org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:487)
at 
org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1166)
at 
com.google.apphosting.utils.servlet.ParseBlobUploadFilter.doFilter(ParseBlobUploadFilter.java:102)
at 
org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
at 
com.google.apphosting.runtime.jetty.SaveSessionFilter.doFilter(SaveSessionFilter.java:35)
at 
org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
at 
com.google.apphosting.utils.servlet.TransactionCleanupFilter.doFilter(TransactionCleanupFilter.java:43)
at 
org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
at 
org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:388)
at 
org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
at 
org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
at 
org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:418)
at 
com.google.apphosting.runtime.jetty.AppVersionHandlerMap.handle(AppVersionHandlerMap.java:266)
at 
org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
at org.mortbay.jetty.Server.handle(Server.java:326)
at 
org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542)
at 
org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:923)
at 
com.google.apphosting.runtime.jetty.RpcRequestParser.parseAvailable(RpcRequestParser.java:76)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
at 
com.google.apphosting.runtime.jetty.JettyServletEngineAdapter.serviceRequest(JettyServletEngineAdapter.java:146)
at 
com.google.apphosting.runtime.JavaRuntime$RequestRunnable.run(JavaRuntime.java:447)
at 
com.google.tracing.TraceContext$TraceContextRunnable.runInContext(TraceContext.java:454)
at 
com.google.tracing.TraceContext$TraceContextRunnable$1.run(TraceContext.java:461)
at com.google.tracing.TraceContext.runInContext(TraceContext.java:703)
at 
com.google.tracing.TraceContext$AbstractTraceContextCallback.runInInheritedContextNoUnref(TraceContext.java:338)
at 
com.google.tracing.TraceContext$AbstractTraceContextCallback.runInInheritedContext(TraceContext.java:330)
at 
com.google.tracing.TraceContext$TraceContextRunnable.run(TraceContext.java:458)
at 
com.google.apphosting.runtime.ThreadGroupPool$PoolEntry.run(ThreadGroupPool.java:251)
at java.lang.Thread.run(Thread.java:679)


any ideas?

-- 
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/-/LlX-Rr2eINYJ.
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: No warmup requests are being issued by the Java instance scheduler

[Carl Schroeder]

It is actually pretty easy to prove when a request is going to a cold 
instance vs a warmed up one. Simply output a log line from a place that is 
only called during initialization of an instance. Make sure that the warmup 
handler calls this part of the code, and that the code is only called once 
per instance. I put mine in the abstraction layer that sits between 
appengine, and my application code. 

My warmup handler shows this log message. So does any user facing request 
that causes an instance of my app to be initialized.

Also, I did a search for "This request caused a new process" in the log 
files. Just today, 27 instance starts. My app can serve its user base off a 
single instance with excellent response times. (If only I had a way to tell 
the scheduler to piss off)

For the past hour, I had 3 warmups handled and 4 user facing requests 
routed to cold instances. I verified that the instances spun up by user 
facing requests had different IDs than the ones spun up by warmup reqeusts. 
I have an AWS instance that hits my site once every 60s to attempt to 
insure that there is always a dynamic instance loaded. I have 1 resident 
instance configured to "enable" warmups.


On Monday, October 22, 2012 2:55:19 PM UTC-7, Kristopher Giesing wrote:
>
> Can you post the relevant logs?  Each request is stamped with the ID of 
> the instance that served it.
>
> When I looked into my own logs I found that the request I thought was 
> cold-served was actually going to a recently warmed instance, but that the 
> warmup request didn't fully initialize everything so the first request 
> after warmup was still too long.  But it sounds like you have more and 
> better data here to prove something is actually broken.
>
> - Kris
>
> On Monday, October 22, 2012 11:07:11 AM UTC-7, Carl Schroeder wrote:
>>
>> I just tested with my Application Settings configured to have 1 Resident 
>> instance.
>>
>> With 1 resident, and 1 idle instance. I hit a page reload. 7 requests 
>> were served by the instances according to the Instances pane in the App 
>> Engine Console. The requests were handled in the following manner:
>> Zero went to the Resident instance. 
>> 3 new instances were spun up. 2 with warmup requests, 1 with the first 
>> user request given to a cold start.
>> 4 then went to the existing idle dynamic instance
>> 1 of the new instances handled 3 requests, the other 2 only handled 
>> warmups.
>>
>> The VERY first request (the basic HTML of the page) went to a cold 
>> instance. This happened despite the fact that there was an idle Resident 
>> instance available AND an idle Dynamic instance available. The user 
>> experience is staring at the browser for 20 seconds before anything 
>> happens. That is unacceptable.
>>
>> Even with 4 dynamic instances, the scheduler is still spinning up new 
>> ones with user facing requests. This is bizarre, pathological, diabolical, 
>> nonsensical behavior. I am running out of adjectives here.
>>
>>

-- 
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/-/hrtncFfN3LMJ.
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: No warmup requests are being issued by the Java instance scheduler

[Kristopher Giesing]

Can you post the relevant logs?  Each request is stamped with the ID of the 
instance that served it.

When I looked into my own logs I found that the request I thought was 
cold-served was actually going to a recently warmed instance, but that the 
warmup request didn't fully initialize everything so the first request 
after warmup was still too long.  But it sounds like you have more and 
better data here to prove something is actually broken.

- Kris

On Monday, October 22, 2012 11:07:11 AM UTC-7, Carl Schroeder wrote:
>
> I just tested with my Application Settings configured to have 1 Resident 
> instance.
>
> With 1 resident, and 1 idle instance. I hit a page reload. 7 requests were 
> served by the instances according to the Instances pane in the App Engine 
> Console. The requests were handled in the following manner:
> Zero went to the Resident instance. 
> 3 new instances were spun up. 2 with warmup requests, 1 with the first 
> user request given to a cold start.
> 4 then went to the existing idle dynamic instance
> 1 of the new instances handled 3 requests, the other 2 only handled 
> warmups.
>
> The VERY first request (the basic HTML of the page) went to a cold 
> instance. This happened despite the fact that there was an idle Resident 
> instance available AND an idle Dynamic instance available. The user 
> experience is staring at the browser for 20 seconds before anything 
> happens. That is unacceptable.
>
> Even with 4 dynamic instances, the scheduler is still spinning up new ones 
> with user facing requests. This is bizarre, pathological, diabolical, 
> nonsensical behavior. I am running out of adjectives here.
>
>

-- 
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/-/fVxm5TjouXsJ.
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.

Re: [google-appengine] No warmup requests are being issued by the Java instance scheduler

[Kristopher Giesing]

On Monday, October 22, 2012 5:51:38 AM UTC-7, Takashi Matsuo (Google) wrote:
>
>
> Hi Carl,
>
> On Mon, Oct 22, 2012 at 8:26 AM, Carl Schroeder 
> 
> > wrote:
>
>> Has this feature been disabled? Have the requirements for it changed?
>> The "Configured Services" section of my Application Settings says that 
>> "Warmup Requests" are enabled.
>> I can find no trace of any warmup requests in my logs.
>>
>
> Currently, the warmup requests are issued only when you have some min idle 
> instances settings instead of 'automatic'.
>

This isn't mentioned in the documentation anywhere that I can see.  Did I 
miss it?  It seems like an incredibly important point to leave out.
 

>
>> Also, the scheduler is still acting crazy. It is starting up new java 
>> instances (with user facing requests) when there are dynamic instances 
>> alive and well and idle. 20 second response times to REST calls that 
>> normally return in 50ms is simply unacceptable performance. Asking my users 
>> to wait 40 seconds while a page that contains multiple REST calls loads is 
>> simply not an option.
>>
>
> To avoid this, currently the options are
> * to have sufficient number of min idle instances
> or
> * to make your loading requests faster
>

The third option, of course, is to use something other than GAE.  Given 
that solution #1 pushes GAE costs over paying for an always-on host from 
another vendor, and #2 doesn't get you to a reasonable SLA, #3 honestly 
looks like the best choice from where I'm sitting.

I'm trying very hard not to get angry about this.  I actually have a good 
friend who is a developer on App Engine and I want very much to make this 
work, but it just seems like the scheduler is fundamentally broken, and 
Google is refusing to recognize it.  Am I missing something?  For those of 
you who have apps deployed on GAE, why isn't this behavior killing you?

- Kris
 

-- 
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/-/_a7nB5IG5u0J.
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.

Re: [google-appengine] Re: Where to report production issue?

[Dan Holevoet]

Hi everyone,

It looks like the template was inadvertently removed and is now restored.

Thanks,
Dan


On Mon, Oct 22, 2012 at 5:40 AM, Brian  wrote:

> Any response from Google on this? I was just about to enable billing on my
> app, but it seems foolish to pay for a service lacks a channel to report
> production issues! (Most other business models would consider this
> a fundamental primary service requirement, no?)
>
> --
> 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/-/2CVuWnROuqAJ.
>
> 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.
>



-- 
Dan Holevoet
Google Developer Relations

-- 
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: Issues with Channel connection status

[Aleksei Rovenski]

My experience with presence notifications is also that they are unreliable. 
Channel API has some problems, you can read this topic for more:
https://groups.google.com/forum/?fromgroups=#!searchin/google-appengine/channel$20unreliable/google-appengine/lqaCMEj8IyQ/7eWTcLqJxWsJ

I have created an issue some time ago re presences problem, please star it. 
It is as simple as adding a timestamp to presence notification.
http://code.google.com/p/googleappengine/issues/detail?id=8151

PS Btw for about a month now there is a new problem that working channel 
stops receiving messages w/o any errors for undefined period of time and 
then may start receiving them again...

-- 
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/-/40uFn1JzALQJ.
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.

Re: [google-appengine] Re: Datastore OFFSET is WORTHLESS

[Matija]

Holly shit... I am still like in 2010 XD 

Tnx.

On Monday, October 22, 2012 8:43:37 PM UTC+2, Alfred Fuller wrote:
>
> Yes:
>
> http://code.google.com/p/googleappengine/source/browse/trunk/java/src/main/com/google/appengine/api/datastore/Query.java#505
>
> http://code.google.com/p/googleappengine/source/browse/trunk/java/src/main/com/google/appengine/api/datastore/Cursor.java#87
>
>
> On Mon, Oct 22, 2012 at 11:37 AM, Matija 
> > wrote:
>
>> Also in Java API?
>>
>> On Monday, October 22, 2012 8:33:00 PM UTC+2, Alfred Fuller wrote:
>>
>>> Backwards paging is currently supported, you can see this ndb example of 
>>> how to do it: https://developers.google.**com/appengine/docs/python/ndb/
>>> **queries#cursors
>>>
>>>
>>> On Wed, Oct 10, 2012 at 12:29 AM, Matija  wrote:
>>>
 Hey,
 is there any news about backwards cursor? Two years ago they were 
 'presented' in next gen queries google io presentation. We did get some 
 features but not backwards cursors.

 Matija


 On Tuesday, October 9, 2012 4:14:29 AM UTC+2, Takashi Matsuo (Google) 
 wrote:

>
> Hi James,
>
> First of all, you are right. You should always use cursors whenever 
> possible.
>
> We used to offer only 'offset' for going back and forth within query 
> results before 1.3.1 release.
> http://googleappengine.**blogspo**t.jp/2010/02/app-**engine-sdk-**
> 131-including-**major.html
>
> Thus there is a lot of code with the 'offset' still running in the 
> production for a historical reason. It is hard for us to just kill this 
> feature.
> However, as you guys noticed, please use cursors whenever you can.
>
> If you want us to improve our documentation, maybe you can file a bug 
> on our issue tracker with more concret suggestions rather than ranting 
> with 
> the caps.
>
> Thanks,
>
> -- Takashi
>
>
> On Tue, Oct 9, 2012 at 8:09 AM, James Gilliam wrote:
>
>> You hurl insults while asserting offset has some usefulness without 
>> any support. So, give me an example of how it is anything but 
>> mathematically pathological.
>>  
>> On Monday, October 8, 2012 11:07:45 AM UTC-7, James Gilliam wrote:
>>>
>>> I discovered that GAE charges you for skipping entities in Datastore 
>>> with OFFSET.  So, if you want to retrieve 1 record at offset 10, you 
>>> pay 
>>> for reading 11.
>>>
>>> This makes OFFSET expensive and WORTHLESS ...
>>>
>>> Offset should never be mentioned in the documentation without a 
>>> footnote that says you can't afford to use it.
>>>
>>> Kinda pissed about this.
>>>
>>  -- 
>> 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/
>> **ms**g/google-appengine/-/**Kd0I90rUV**LcJ
>> .
>>  
>> To post to this group, send email to google-a...@googlegroups.**com.
>> To unsubscribe from this group, send email to google-appengi...@**
>> googlegroups**.com.
>>
>> For more options, visit this group at http://groups.google.com/**
>> group**/google-appengine?hl=en
>> .
>>
>
>
>
> -- 
> Takashi Matsuo | Developers Advocate | tma...@google.com
>
>   -- 
 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/-/**Ww6zx2oKOxMJ
 .

 To post to this group, send email to google-a...@googlegroups.**com.
 To unsubscribe from this group, send email to google-appengi...@**
 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 view this discussion on the web visit 
>> https://groups.google.com/d/msg/google-appengine/-/JMm4_mlQZTQJ.
>>
>> To post to this group, send email to 
>> google-a...@googlegroups.com
>> .
>> To unsubscribe from this group, send email to 
>> google-appengi...@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 view this discussion on the web visit 
h

Re: [google-appengine] Re: Datastore OFFSET is WORTHLESS

[Alfred Fuller]

Yes:
http://code.google.com/p/googleappengine/source/browse/trunk/java/src/main/com/google/appengine/api/datastore/Query.java#505
http://code.google.com/p/googleappengine/source/browse/trunk/java/src/main/com/google/appengine/api/datastore/Cursor.java#87


On Mon, Oct 22, 2012 at 11:37 AM, Matija  wrote:

> Also in Java API?
>
> On Monday, October 22, 2012 8:33:00 PM UTC+2, Alfred Fuller wrote:
>
>> Backwards paging is currently supported, you can see this ndb example of
>> how to do it: https://developers.google.**com/appengine/docs/python/ndb/*
>> *queries#cursors
>>
>>
>> On Wed, Oct 10, 2012 at 12:29 AM, Matija  wrote:
>>
>>> Hey,
>>> is there any news about backwards cursor? Two years ago they were
>>> 'presented' in next gen queries google io presentation. We did get some
>>> features but not backwards cursors.
>>>
>>> Matija
>>>
>>>
>>> On Tuesday, October 9, 2012 4:14:29 AM UTC+2, Takashi Matsuo (Google)
>>> wrote:
>>>

 Hi James,

 First of all, you are right. You should always use cursors whenever
 possible.

 We used to offer only 'offset' for going back and forth within query
 results before 1.3.1 release.
 http://googleappengine.**blogspo**t.jp/2010/02/app-**engine-sdk-**
 131-including-**major.html

 Thus there is a lot of code with the 'offset' still running in the
 production for a historical reason. It is hard for us to just kill this
 feature.
 However, as you guys noticed, please use cursors whenever you can.

 If you want us to improve our documentation, maybe you can file a bug
 on our issue tracker with more concret suggestions rather than ranting with
 the caps.

 Thanks,

 -- Takashi


 On Tue, Oct 9, 2012 at 8:09 AM, James Gilliam wrote:

> You hurl insults while asserting offset has some usefulness without
> any support. So, give me an example of how it is anything but
> mathematically pathological.
>
> On Monday, October 8, 2012 11:07:45 AM UTC-7, James Gilliam wrote:
>>
>> I discovered that GAE charges you for skipping entities in Datastore
>> with OFFSET.  So, if you want to retrieve 1 record at offset 10, you pay
>> for reading 11.
>>
>> This makes OFFSET expensive and WORTHLESS ...
>>
>> Offset should never be mentioned in the documentation without a
>> footnote that says you can't afford to use it.
>>
>> Kinda pissed about this.
>>
>  --
> 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/*
> *ms**g/google-appengine/-/**Kd0I90rUV**LcJ
> .
>
> To post to this group, send email to google-a...@googlegroups.**com.
> To unsubscribe from this group, send email to google-appengi...@**
> googlegroups**.com.
>
> For more options, visit this group at http://groups.google.com/**group
> **/google-appengine?hl=en
> .
>



 --
 Takashi Matsuo | Developers Advocate | tma...@google.com

   --
>>> 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/-/**Ww6zx2oKOxMJ
>>> .
>>>
>>> To post to this group, send email to google-a...@googlegroups.**com.
>>> To unsubscribe from this group, send email to google-appengi...@**
>>> 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 view this discussion on the web visit
> https://groups.google.com/d/msg/google-appengine/-/JMm4_mlQZTQJ.
>
> 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.

Re: [google-appengine] Re: Datastore OFFSET is WORTHLESS

[Matija]

Also in Java API?

On Monday, October 22, 2012 8:33:00 PM UTC+2, Alfred Fuller wrote:
>
> Backwards paging is currently supported, you can see this ndb example of 
> how to do it: 
> https://developers.google.com/appengine/docs/python/ndb/queries#cursors
>
>
> On Wed, Oct 10, 2012 at 12:29 AM, Matija 
> > wrote:
>
>> Hey,
>> is there any news about backwards cursor? Two years ago they were 
>> 'presented' in next gen queries google io presentation. We did get some 
>> features but not backwards cursors.
>>
>> Matija
>>
>>
>> On Tuesday, October 9, 2012 4:14:29 AM UTC+2, Takashi Matsuo (Google) 
>> wrote:
>>
>>>
>>> Hi James,
>>>
>>> First of all, you are right. You should always use cursors whenever 
>>> possible.
>>>
>>> We used to offer only 'offset' for going back and forth within query 
>>> results before 1.3.1 release.
>>> http://googleappengine.**blogspot.jp/2010/02/app-**
>>> engine-sdk-131-including-**major.html
>>>
>>> Thus there is a lot of code with the 'offset' still running in the 
>>> production for a historical reason. It is hard for us to just kill this 
>>> feature.
>>> However, as you guys noticed, please use cursors whenever you can.
>>>
>>> If you want us to improve our documentation, maybe you can file a bug on 
>>> our issue tracker with more concret suggestions rather than ranting with 
>>> the caps.
>>>
>>> Thanks,
>>>
>>> -- Takashi
>>>
>>>
>>> On Tue, Oct 9, 2012 at 8:09 AM, James Gilliam wrote:
>>>
 You hurl insults while asserting offset has some usefulness without any 
 support. So, give me an example of how it is anything but 
 mathematically pathological.
  
 On Monday, October 8, 2012 11:07:45 AM UTC-7, James Gilliam wrote:
>
> I discovered that GAE charges you for skipping entities in Datastore 
> with OFFSET.  So, if you want to retrieve 1 record at offset 10, you pay 
> for reading 11.
>
> This makes OFFSET expensive and WORTHLESS ...
>
> Offset should never be mentioned in the documentation without a 
> footnote that says you can't afford to use it.
>
> Kinda pissed about this.
>
  -- 
 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/-/**Kd0I90rUVLcJ
 .
  
 To post to this group, send email to google-a...@googlegroups.**com.
 To unsubscribe from this group, send email to google-appengi...@**
 googlegroups.com.

 For more options, visit this group at http://groups.google.com/**
 group/google-appengine?hl=en
 .

>>>
>>>
>>>
>>> -- 
>>> Takashi Matsuo | Developers Advocate | tma...@google.com
>>>
>>>   -- 
>> 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/-/Ww6zx2oKOxMJ.
>>
>> To post to this group, send email to 
>> google-a...@googlegroups.com
>> .
>> To unsubscribe from this group, send email to 
>> google-appengi...@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 view this discussion on the web visit 
https://groups.google.com/d/msg/google-appengine/-/JMm4_mlQZTQJ.
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.

Re: [google-appengine] Re: Datastore OFFSET is WORTHLESS

[Alfred Fuller]

Backwards paging is currently supported, you can see this ndb example of
how to do it:
https://developers.google.com/appengine/docs/python/ndb/queries#cursors


On Wed, Oct 10, 2012 at 12:29 AM, Matija  wrote:

> Hey,
> is there any news about backwards cursor? Two years ago they were
> 'presented' in next gen queries google io presentation. We did get some
> features but not backwards cursors.
>
> Matija
>
>
> On Tuesday, October 9, 2012 4:14:29 AM UTC+2, Takashi Matsuo (Google)
> wrote:
>
>>
>> Hi James,
>>
>> First of all, you are right. You should always use cursors whenever
>> possible.
>>
>> We used to offer only 'offset' for going back and forth within query
>> results before 1.3.1 release.
>> http://googleappengine.**blogspot.jp/2010/02/app-**
>> engine-sdk-131-including-**major.html
>>
>> Thus there is a lot of code with the 'offset' still running in the
>> production for a historical reason. It is hard for us to just kill this
>> feature.
>> However, as you guys noticed, please use cursors whenever you can.
>>
>> If you want us to improve our documentation, maybe you can file a bug on
>> our issue tracker with more concret suggestions rather than ranting with
>> the caps.
>>
>> Thanks,
>>
>> -- Takashi
>>
>>
>> On Tue, Oct 9, 2012 at 8:09 AM, James Gilliam  wrote:
>>
>>> You hurl insults while asserting offset has some usefulness without any
>>> support. So, give me an example of how it is anything but
>>> mathematically pathological.
>>>
>>> On Monday, October 8, 2012 11:07:45 AM UTC-7, James Gilliam wrote:

 I discovered that GAE charges you for skipping entities in Datastore
 with OFFSET.  So, if you want to retrieve 1 record at offset 10, you pay
 for reading 11.

 This makes OFFSET expensive and WORTHLESS ...

 Offset should never be mentioned in the documentation without a
 footnote that says you can't afford to use it.

 Kinda pissed about this.

>>>  --
>>> 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/-/**Kd0I90rUVLcJ
>>> .
>>>
>>> To post to this group, send email to google-a...@googlegroups.**com.
>>> To unsubscribe from this group, send email to google-appengi...@**
>>> googlegroups.com.
>>>
>>> For more options, visit this group at http://groups.google.com/**
>>> group/google-appengine?hl=en
>>> .
>>>
>>
>>
>>
>> --
>> Takashi Matsuo | Developers Advocate | tma...@google.com
>>
>>   --
> 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/-/Ww6zx2oKOxMJ.
>
> 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: No warmup requests are being issued by the Java instance scheduler

[Carl Schroeder]

I just tested with my Application Settings configured to have 1 Resident 
instance.

With 1 resident, and 1 idle instance. I hit a page reload. 7 requests were 
served by the instances according to the Instances pane in the App Engine 
Console. The requests were handled in the following manner:
Zero went to the Resident instance. 
3 new instances were spun up. 2 with warmup requests, 1 with the first user 
request given to a cold start.
4 then went to the existing idle dynamic instance
1 of the new instances handled 3 requests, the other 2 only handled warmups.

The VERY first request (the basic HTML of the page) went to a cold 
instance. This happened despite the fact that there was an idle Resident 
instance available AND an idle Dynamic instance available. The user 
experience is staring at the browser for 20 seconds before anything 
happens. That is unacceptable.

Even with 4 dynamic instances, the scheduler is still spinning up new ones 
with user facing requests. This is bizarre, pathological, diabolical, 
nonsensical behavior. I am running out of adjectives here.

-- 
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/-/Cq3a4AW57IQJ.
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.

Re: [google-appengine] Re: Datastore Read Operations Quota Whacked-Out?

[Thiago Catoto]

Hi,

I remember some one talking about remote api over-consuming cause of his
"retry", so if you are getting some timeout and stuffs like that, the
remote api will try again and will consume your quota both times (the
success and the timeout).

Maybe this is your case... not sure if my information is correct too... are
you using Java? If so, your should try using python bulk upload (
https://developers.google.com/appengine/docs/python/tools/uploadingdata) if
it fit in your needs.

Hope it helps,

cheers.

On Sat, Oct 20, 2012 at 10:33 AM, Brian  wrote:

> Okay, so with a fresh unused (0%) quota today I tried running my remote
> api job again, but first I cut the size of the task down to 1/3 of what it
> was previously. On the first run, it consumed 1% of my daily read ops
> quota. Encouraged, I ran another batch and within moments it consumed all
> 100% of my quota again! What's up with that?! I can not trim my job down to
> any smaller chunks than this -- what can I do now to workaround this
> problem?
>
> --
> 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/-/vbz4pmqDfQUJ.
>
> 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.

Re: [google-appengine] No warmup requests are being issued by the Java instance scheduler

[Carl Schroeder]

The use of "resident" instances with a low site traffic profile resulted in 
a different version of the pathological behavior. With periods of low 
usage, the scheduler decommissioned dynamic instances. When traffic picked 
up again, it did not use the "resident" instances. Instead, it spun up 3 or 
4 dynamics causing the page load to stall out. At least, that was the case 
1 month ago when I ditched the entire concept of "min idle instances" 
(since they appeared to always be idle and never serve traffic). I use wget 
to issue a single request once every 60 seconds in an attempt to have at 
least 1 dynamic instance always available.

I will test again to see if "idle instances" actually add any value to a 
site with my traffic profile. Before, they doubled or tripled the cost and 
did not improve the user experience at all.

What is the reasoning behind not sending warmup requests?

I have already starred the relevant scheduler enhancement issues.

On Monday, October 22, 2012 5:51:38 AM UTC-7, Takashi Matsuo (Google) wrote:
>
>
> Hi Carl,
>
> On Mon, Oct 22, 2012 at 8:26 AM, Carl Schroeder 
> 
> > wrote:
>
>> Has this feature been disabled? Have the requirements for it changed?
>> The "Configured Services" section of my Application Settings says that 
>> "Warmup Requests" are enabled.
>> I can find no trace of any warmup requests in my logs.
>>
>
> Currently, the warmup requests are issued only when you have some min idle 
> instances settings instead of 'automatic'.
>  
>
>>
>> Also, the scheduler is still acting crazy. It is starting up new java 
>> instances (with user facing requests) when there are dynamic instances 
>> alive and well and idle. 20 second response times to REST calls that 
>> normally return in 50ms is simply unacceptable performance. Asking my users 
>> to wait 40 seconds while a page that contains multiple REST calls loads is 
>> simply not an option.
>>
>
> To avoid this, currently the options are
> * to have sufficient number of min idle instances
> or
> * to make your loading requests faster
>
> -- Takashi
>  
>
>>
>> I am back to deciding whether to port the java to python and stay on GAE, 
>> or trying out dynamoDB on AWS.
>>  
>> -- 
>> 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/-/U2PyWapvPqkJ.
>> To post to this group, send email to 
>> google-a...@googlegroups.com
>> .
>> To unsubscribe from this group, send email to 
>> google-appengi...@googlegroups.com .
>> For more options, visit this group at 
>> http://groups.google.com/group/google-appengine?hl=en.
>>
>
>
>
> -- 
> Takashi Matsuo | Developers Advocate | tma...@google.com 
>
>  

-- 
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/-/mOJNvj-ytFcJ.
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.

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

[alex]

I assume you're talking about Windows users only.
On Mac OS and Linux, I'm always using dev server with sqlite (mostly
py/py27) for many months now and it's blazing fast (for a dev server),
can't complain.

-- alex

On Mon, Oct 22, 2012 at 6:28 PM, Kenneth  wrote:
> If you're going to be moving to sqlite, please fix the following bug (or is
> it fixed in 1.7.3?):
>
> http://code.google.com/p/googleappengine/issues/detail?id=7717
>
> While there is a workaround you're going to kill people who are just
> starting out.
>
> Also, while sqlite is much faster starting up, each request feels quite a
> bit slower.  If I get some time I'll try to benchmark it and create an
> issue.
>
> Thanks.
>
>
> On Friday, October 19, 2012 7:04:41 PM UTC+1, Richmond Manzana wrote:
>>
>> Hi,
>>
>> We've posted the pre-release SDKs for Python and Java here:
>> http://code.google.com/p/googleappengine/downloads/list
>>
>> Pre-Release notes below.
>>
>> Cheers,
>>
>> Rich
>>
>> App Engine Python SDK - Release Notes
>>
>> Version 1.7.3
>> ===
>> - Django 1.4 is now supported in Python 2.7
>> - The file-based implementation of the Datastore stub will be deprecated
>> soon.
>>   A warning message informing users that SQLLite stub will be the default
>>   stub soon is now displayed.
>> - Datastore Index stats now report type instead of representation-type.
>> - Rich sort expressions beyond single field names are now supported in the
>>   Search API for dev_appserver.
>> - search.MIN_NUMBER_VALUE and search.MAX_NUMBER_VALUE are now public in
>> the
>>   Search API.
>> - Globally Consistent Indexes are now deprecated in the Search API.
>> - Index.list_documents() has been deprecated and replaced with
>>   Index.get_range() in the Search API.
>> - search.list_indexes() has been deprecated and replaced with
>>   search.get_indexes() in the Search API.
>> - Added method Index.get(doc_id) to get a document by its ID in the Search
>> API
>> - Index.add() has been deprecated and renamed to Index.put() in the Search
>> API.
>> - Index.remove() has been deprecated and renamed to Index.delete() in the
>>   Search API.
>> - The AddDocumentError and RemoveDocumentError classes, which were already
>>   deprecated, have been removed from the Search API.
>> - OperationCode.object_id and OperationCode.document_id, which were
>> already
>>   deprecated, have been removed from the Search API.
>> - Users can now change authentication options after app creation
>> http://code.google.com/p/googleappengine/issues/detail?id=483
>> - Fixed an issue with Datastore backup/restore finalization steps only
>> looking
>>   at the default queue in Admin Console.
>> - Fixed an NDB issue with Structured Properties not converting dict
>> properly.
>> http://code.google.com/p/appengine-ndb-experiment/issues/detail?id=207
>> - Fixed an NDB issue where multiple async transactions corrupt old
>>   Datastore connections.
>> http://code.google.com/p/appengine-ndb-experiment/issues/detail?id=209
>> - Fixed an NDB issue with fetch() with offset > 1000 returning an empty
>> list.
>> http://code.google.com/p/appengine-ndb-experiment/issues/detail?id=210
>> - Fixed an issue with 2 factor authentication not giving useful error
>> messages.
>> http://code.google.com/p/googleappengine/issues/detail?id=8020
>> - Fixed an issue in the Search API snippeting breaking if the field
>> contains
>>   a single word in dev_appserver.
>> http://code.google.com/p/googleappengine/issues/detail?id=8171
>> - Fixed an issue with PyCrypto AES cipher not running on dev_appserver.
>> http://code.google.com/p/googleappengine/issues/detail?id=8188
>>
>>
>>
>>
>>
>> App Engine Java SDK - Release Notes
>>
>> Version 1.7.3
>> =
>>
>> - We encourage you to try and test your application using Java 7 and App
>>   Engine SDK. Note that Java 7 is *not* a supported runtime.
>> - Java 7 Features that we encourage you to try in dev appserver:
>> Strings in switch
>> Binary integral literals and underscores in number literals
>> Multi-catch and more precise rethrow
>> Improved type inference for generic instance creation (diamond)
>> try-with-resources statement
>> Simplified varargs method invocation
>> - Java 7 features that are NOT supported:
>> All new Java 7 classes (the Google App Engine whitelist has not been
>> updated yet)
>> Method Handles
>> Invoke Dynamic bytecode
>> - InetAddress name resolution now displays UnknownHostException instead of
>> a
>>   runtime exception error when the host is unknown.
>> - Datastore Index stats now report type instead of representation-type.
>> - Class Loading Priority can now be granted to specific JAR files by
>> adding
>>   class-loader-config element in appengine-web.xml file. This is an
>>   experimental feature.
>> - Queries with transactions are now fully checked for consistency in
>> Remote
>>   API.
>> - Global Consistent Indexes are now deprecated in the Se

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

[Kenneth]

If you're going to be moving to sqlite, please fix the following bug (or is 
it fixed in 1.7.3?):

http://code.google.com/p/googleappengine/issues/detail?id=7717

While there is a workaround you're going to kill people who are just 
starting out.

Also, while sqlite is much faster starting up, each request feels quite a 
bit slower.  If I get some time I'll try to benchmark it and create an 
issue.

Thanks.


On Friday, October 19, 2012 7:04:41 PM UTC+1, Richmond Manzana wrote:
>
> Hi,
>
> We've posted the pre-release SDKs for Python and Java here:
> http://code.google.com/p/googleappengine/downloads/list
>
> Pre-Release notes below.
>
> Cheers,
>
> Rich
>
> App Engine Python SDK - Release Notes
>
> Version 1.7.3
> ===
> - Django 1.4 is now supported in Python 2.7
> - The file-based implementation of the Datastore stub will be deprecated 
> soon.
>   A warning message informing users that SQLLite stub will be the default
>   stub soon is now displayed.
> - Datastore Index stats now report type instead of representation-type.
> - Rich sort expressions beyond single field names are now supported in the
>   Search API for dev_appserver.
> - search.MIN_NUMBER_VALUE and search.MAX_NUMBER_VALUE are now public in the
>   Search API.
> - Globally Consistent Indexes are now deprecated in the Search API.
> - Index.list_documents() has been deprecated and replaced with
>   Index.get_range() in the Search API.
> - search.list_indexes() has been deprecated and replaced with
>   search.get_indexes() in the Search API.
> - Added method Index.get(doc_id) to get a document by its ID in the Search 
> API
> - Index.add() has been deprecated and renamed to Index.put() in the Search 
> API.
> - Index.remove() has been deprecated and renamed to Index.delete() in the
>   Search API.
> - The AddDocumentError and RemoveDocumentError classes, which were already
>   deprecated, have been removed from the Search API.
> - OperationCode.object_id and OperationCode.document_id, which were already
>   deprecated, have been removed from the Search API.
> - Users can now change authentication options after app creation
> http://code.google.com/p/googleappengine/issues/detail?id=483
> - Fixed an issue with Datastore backup/restore finalization steps only 
> looking
>   at the default queue in Admin Console.
> - Fixed an NDB issue with Structured Properties not converting dict 
> properly.
> http://code.google.com/p/appengine-ndb-experiment/issues/detail?id=207
> - Fixed an NDB issue where multiple async transactions corrupt old
>   Datastore connections.
> http://code.google.com/p/appengine-ndb-experiment/issues/detail?id=209
> - Fixed an NDB issue with fetch() with offset > 1000 returning an empty 
> list.
> http://code.google.com/p/appengine-ndb-experiment/issues/detail?id=210
> - Fixed an issue with 2 factor authentication not giving useful error 
> messages.
> http://code.google.com/p/googleappengine/issues/detail?id=8020
> - Fixed an issue in the Search API snippeting breaking if the field 
> contains
>   a single word in dev_appserver.
> http://code.google.com/p/googleappengine/issues/detail?id=8171
> - Fixed an issue with PyCrypto AES cipher not running on dev_appserver.
> http://code.google.com/p/googleappengine/issues/detail?id=8188
>
>
>
>
>
> App Engine Java SDK - Release Notes
>
> Version 1.7.3
> =
>
> - We encourage you to try and test your application using Java 7 and App
>   Engine SDK. Note that Java 7 is *not* a supported runtime.
> - Java 7 Features that we encourage you to try in dev appserver:
> Strings in switch
> Binary integral literals and underscores in number literals
> Multi-catch and more precise rethrow
> Improved type inference for generic instance creation (diamond)
> try-with-resources statement
> Simplified varargs method invocation
> - Java 7 features that are NOT supported:
> All new Java 7 classes (the Google App Engine whitelist has not been
> updated yet)
> Method Handles
> Invoke Dynamic bytecode
> - InetAddress name resolution now displays UnknownHostException instead of 
> a
>   runtime exception error when the host is unknown.
> - Datastore Index stats now report type instead of representation-type.
> - Class Loading Priority can now be granted to specific JAR files by adding
>   class-loader-config element in appengine-web.xml file. This is an
>   experimental feature.
> - Queries with transactions are now fully checked for consistency in Remote
>   API.
> - Global Consistent Indexes are now deprecated in the Search API.
> - ListResponse listDocuments(ListRequest) has been deprecated and
>   replaced with GetResponse getRange(GetRequest) in the Search 
> API.
> - ListIndexesReponse listIndexes(ListIndexesRequest) has been deprecated 
> and
>   replaced with GetResponse getIndexes(GetIndexesRequest) in the 
> Search
>   API.
> - getField(String) has been deprecated and aliased to getFields(Str

[google-appengine] Re: Datastore Failure

[srk]

Hi Luisa, 

Even for me the same error incurred. Do let me know when you could find the 
cause and solution for this issue.

Thanks
Srk

-- 
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/-/7dw48foSEZIJ.
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: Datastore Failure

[srk]

Hi, 

Even for me the same error incurred. Do let me know when you could find the 
cause and fix for this issue.

Thanks,
Srk


-- 
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/-/0gX4gk4it8wJ.
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: Datastore Failure

[srk]

Hi, 

Even for me the same error incurred. Do let me know if you find the cause 
and solution for this issue. 

Thanks
Srk

On Wednesday, September 1, 2010 2:10:29 AM UTC+5:30, Luisa wrote:
>
> I'm seeing errors trying to load any page in my site.  Non of my 
> database code has changed recently.  The error message looks like 
> this: 
>
> javax.jdo.JDODataStoreException: Datastore Failure at 
> org.datanucleus.jdo.NucleusJDOHelper.getJDOExceptionForNucleusException(NucleusJDOHelper.java:
>  
>
> 304) at 
> org.datanucleus.jdo.JDOPersistenceManager.getObjectById(JDOPersistenceManager.java:
>  
>
> 1676) at 
> org.datanucleus.jdo.JDOPersistenceManager.getObjectsById(JDOPersistenceManager.java:
>  
>
> 1700) at 
> org.datanucleus.jdo.JDOPersistenceManager.getObjectsById(JDOPersistenceManager.java:
>  
>
> 1745) at 
>
> or 
>
> javax.jdo.JDODataStoreException: Datastore Failure at 
> org.datanucleus.jdo.NucleusJDOHelper.getJDOExceptionForNucleusException(NucleusJDOHelper.java:
>  
>
> 304) at 
> org.datanucleus.jdo.JDOPersistenceManager.jdoMakePersistent(JDOPersistenceManager.java:
>  
>
> 674) at 
> org.datanucleus.jdo.JDOPersistenceManager.makePersistent(JDOPersistenceManager.java:
>  
>
> 694) 
>
> If you refresh the page after the error then the page loads 
> properly. 
>
> Please help.

-- 
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/-/mWYnD7sBL1sJ.
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.

Re: [google-appengine] No warmup requests are being issued by the Java instance scheduler

[Guenlay]

可以用 google_hk

2012/10/22 Jeff Schnitzer 

> Obligatory comment:  Yet another user who finds scheduler behavior to
> be "broken out of the box".
>
> Carl:  The relevant issue to star:
> http://code.google.com/p/googleappengine/issues/detail?id=7865
>
> Jeff
>
> On Mon, Oct 22, 2012 at 8:51 AM, Takashi Matsuo 
> wrote:
> >
> > Hi Carl,
> >
> > On Mon, Oct 22, 2012 at 8:26 AM, Carl Schroeder <
> schroeder.car...@gmail.com>
> > wrote:
> >>
> >> Has this feature been disabled? Have the requirements for it changed?
> >> The "Configured Services" section of my Application Settings says that
> >> "Warmup Requests" are enabled.
> >> I can find no trace of any warmup requests in my logs.
> >
> >
> > Currently, the warmup requests are issued only when you have some min
> idle
> > instances settings instead of 'automatic'.
> >
> >>
> >>
> >> Also, the scheduler is still acting crazy. It is starting up new java
> >> instances (with user facing requests) when there are dynamic instances
> alive
> >> and well and idle. 20 second response times to REST calls that normally
> >> return in 50ms is simply unacceptable performance. Asking my users to
> wait
> >> 40 seconds while a page that contains multiple REST calls loads is
> simply
> >> not an option.
> >
> >
> > To avoid this, currently the options are
> > * to have sufficient number of min idle instances
> > or
> > * to make your loading requests faster
> >
> > -- Takashi
> >
> >>
> >>
> >> I am back to deciding whether to port the java to python and stay on
> GAE,
> >> or trying out dynamoDB on AWS.
> >>
> >> --
> >> 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/-/U2PyWapvPqkJ.
> >> 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.
> >
> >
> >
> >
> > --
> > Takashi Matsuo | Developers Advocate | tmat...@google.com
> >
> > --
> > 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.
>
> --
> 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.
>
>

-- 
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.

Re: [google-appengine] No warmup requests are being issued by the Java instance scheduler

[Jeff Schnitzer]

Obligatory comment:  Yet another user who finds scheduler behavior to
be "broken out of the box".

Carl:  The relevant issue to star:
http://code.google.com/p/googleappengine/issues/detail?id=7865

Jeff

On Mon, Oct 22, 2012 at 8:51 AM, Takashi Matsuo  wrote:
>
> Hi Carl,
>
> On Mon, Oct 22, 2012 at 8:26 AM, Carl Schroeder 
> wrote:
>>
>> Has this feature been disabled? Have the requirements for it changed?
>> The "Configured Services" section of my Application Settings says that
>> "Warmup Requests" are enabled.
>> I can find no trace of any warmup requests in my logs.
>
>
> Currently, the warmup requests are issued only when you have some min idle
> instances settings instead of 'automatic'.
>
>>
>>
>> Also, the scheduler is still acting crazy. It is starting up new java
>> instances (with user facing requests) when there are dynamic instances alive
>> and well and idle. 20 second response times to REST calls that normally
>> return in 50ms is simply unacceptable performance. Asking my users to wait
>> 40 seconds while a page that contains multiple REST calls loads is simply
>> not an option.
>
>
> To avoid this, currently the options are
> * to have sufficient number of min idle instances
> or
> * to make your loading requests faster
>
> -- Takashi
>
>>
>>
>> I am back to deciding whether to port the java to python and stay on GAE,
>> or trying out dynamoDB on AWS.
>>
>> --
>> 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/-/U2PyWapvPqkJ.
>> 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.
>
>
>
>
> --
> Takashi Matsuo | Developers Advocate | tmat...@google.com
>
> --
> 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.

-- 
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.

Re: [google-appengine] No warmup requests are being issued by the Java instance scheduler

[Takashi Matsuo]

Hi Carl,

On Mon, Oct 22, 2012 at 8:26 AM, Carl Schroeder
wrote:

> Has this feature been disabled? Have the requirements for it changed?
> The "Configured Services" section of my Application Settings says that
> "Warmup Requests" are enabled.
> I can find no trace of any warmup requests in my logs.
>

Currently, the warmup requests are issued only when you have some min idle
instances settings instead of 'automatic'.


>
> Also, the scheduler is still acting crazy. It is starting up new java
> instances (with user facing requests) when there are dynamic instances
> alive and well and idle. 20 second response times to REST calls that
> normally return in 50ms is simply unacceptable performance. Asking my users
> to wait 40 seconds while a page that contains multiple REST calls loads is
> simply not an option.
>

To avoid this, currently the options are
* to have sufficient number of min idle instances
or
* to make your loading requests faster

-- Takashi


>
> I am back to deciding whether to port the java to python and stay on GAE,
> or trying out dynamoDB on AWS.
>
> --
> 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/-/U2PyWapvPqkJ.
> 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.
>



-- 
Takashi Matsuo | Developers Advocate | tmat...@google.com

-- 
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: Where to report production issue?

[Brian]

Any response from Google on this? I was just about to enable billing on my 
app, but it seems foolish to pay for a service lacks a channel to report 
production issues! (Most other business models would consider this 
a fundamental primary service requirement, no?)

-- 
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/-/2CVuWnROuqAJ.
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: Huge number of datastore reads?

[Brian]

Dave, did you get any resolution to this issue? I seem to be having a similar 
issue--
 5 minutes of read ops on a few objects via remote api consumes my free 
daily quota of 50K. 

-- 
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/-/BRM-dNM3p6oJ.
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] Installed Latest version of Eclipse and all add-on but can't view app in Chrome browser

[dt_da]

Hello,

I went through the getting started section in the Google App Engine for 
Java. I installed the following software:

   - Eclipse EE IDE (Version: Juno Release Build id: 20120614-1722), 
   - plugin GWT SDK 2.4.0 
   - plugin eclipse 4.2
   - plugin GAE Java SDK 1.7.2.1
   - plugin GWT designer 2.6.0 
   - Oracle Java SE 7u9 
   - Chome extension GWT Developer Plugin 1.0.1133

I tried creating a hello world google web application that uses both GWT 
and GAE SDKs, but when I try and run it in debug mode it creates a URL 
which when I click on it gives the following error message:


 If I try creating a hello world google web application with only GAE SDK 
it does not seem to work at all. 

I followed the instructions here: 
https://developers.google.com/appengine/docs/java/gettingstarted/
but there weren't very clear on the versions of eclipse to download and use 
or the version of Java to download and use. Does anybody else have the same 
issues or can you tell me what I am doing wrong??

-- 
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/-/kid3T40AfaUJ.
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: Persona and Shiro for identity and authorization

[Tim Niblett]

Jeff,

Thanks again for all the info.

I tried eyedee.me.  I can log in and out on the site but with Persona I get 
an infinite loop -- just keeps asking you to login.  I could see how the UI 
works though, which is encouraging.  I created a Github issue for it. 

Your 50/50 split is interesting.  Perhaps shows that people are _not_ happy 
with the lack of privacy on Facebook.


Tim

On Tuesday, October 16, 2012 9:52:19 PM UTC+1, Tim Niblett wrote:
>
> There is a demo at http://personashiro.appspot.com showing how to set up 
> Mozilla's Persona  for identity and Apache 
> Shiro  for authorization. There is a small demo 
> here  which 
> shows how to set things up.  The aim is to be as simple to program as the 
> built-in user service but to provide more authorization features.
>
> Persona isn't quite ready for prime time yet, but it looks interesting. 
>  It seems (in principle) to be more secure than using OAuth for 
> identification, for what that's worth.
>

-- 
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/-/Nml7bgX4--AJ.
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.