[appengine-java] StackOverflowError when using remote API

2011-11-02 Thread Hakim 
Hi all

I'm trying to query the datastore of my application from another GAE/J app 
but I got this error using development server and also in production

Error for /servlet_url
java.lang.StackOverflowError
at java.lang.ThreadLocal$ThreadLocalMap.getEntry(ThreadLocal.java:381)
at java.lang.ThreadLocal$ThreadLocalMap.access$000(ThreadLocal.java:261)
at java.lang.ThreadLocal.get(ThreadLocal.java:146)
at 
com.google.appengine.tools.remoteapi.ThreadLocalDelegate.getDelegate(ThreadLocalDelegate.java:32)
at 
com.google.appengine.tools.remoteapi.ThreadLocalDelegate.makeSyncCall(ThreadLocalDelegate.java:41)
at 
com.google.appengine.tools.remoteapi.HostedRemoteApiDelegate.makeSyncCall(HostedRemoteApiDelegate.java:45)
at 
com.google.appengine.tools.remoteapi.ThreadLocalDelegate.makeSyncCall(ThreadLocalDelegate.java:41)
at 
com.google.appengine.tools.remoteapi.HostedRemoteApiDelegate.makeSyncCall(HostedRemoteApiDelegate.java:45)
at 
com.google.appengine.tools.remoteapi.ThreadLocalDelegate.makeSyncCall(ThreadLocalDelegate.java:41)
at 
com.google.appengine.tools.remoteapi.HostedRemoteApiDelegate.makeSyncCall(HostedRemoteApiDelegate.java:45)
at 
com.google.appengine.tools.remoteapi.ThreadLocalDelegate.makeSyncCall(ThreadLocalDelegate.java:41)
at 
com.google.appengine.tools.remoteapi.HostedRemoteApiDelegate.makeSyncCall(HostedRemoteApiDelegate.java:45)
at 
com.google.appengine.tools.remoteapi.ThreadLocalDelegate.makeSyncCall(ThreadLocalDelegate.java:41)
at 
com.google.appengine.tools.remoteapi.HostedRemoteApiDelegate.makeSyncCall(HostedRemoteApiDelegate.java:45)
at 
com.google.appengine.tools.remoteapi.ThreadLocalDelegate.makeSyncCall(ThreadLocalDelegate.java:41)
at 
com.google.appengine.tools.remoteapi.HostedRemoteApiDelegate.makeSyncCall(HostedRemoteApiDelegate.java:45)



After many tries, when checking the appstats of the first application, I see 
several successful queries to /remote_api but with no RPC call

*2011-11-02 23:22:59.298 "GET remote_api" 200 real=0ms cpu=0ms api=0ms 
overhead=0ms (0 RPCs)*


-- 
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/-/1Vdi3jWNiuwJ.
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.

[appengine-java] Re: Vosao instances are down. Please HELP!

2011-11-02 Thread Viðar Svansson 
We are experiencing the same problem. Production issue has been filed [1].
We need this fixed ASAP. This is the second time in a short period
that Vosao suddenly stops working on GAE.

[1] http://code.google.com/p/googleappengine/issues/detail?id=6231

Viğar

On Wed, Nov 2, 2011 at 8:16 PM, Armen Danielyan  wrote:
> Svitlana,
> Thank you for your quick response. It's good to know there is a way to fix
> the problem.
> Did you create a new version on the existing app or you created a new app
> from scratch?
> I'll follow these steps if no better solution is found within the next 24
> hours.
> I am sure everybody has/will have this problem.
> Thanks,
> Armen
>
> On Wed, Nov 2, 2011 at 4:09 PM, Svitlana Matsutska 
> wrote:
>>
>> I had exactly the same problem.
>> The only way (fast) to solve it was to create new google app, move all
>> data to new app, make from scratch installation of vosao-0.9.9 on new app.
>> If you can find the better way, please share.
>> Regards
>> Svitlana
>> 2011/11/2 Armen 
>>>
>>> All of my Vosao instances are down. It seems Google again changed
>>> something...
>>> Any ideas on how to fix this?
>>>
>>> Uncaught exception from servlet
>>> java.lang.NoClassDefFoundError: Could not initialize class
>>> org.vosao.filter.ContextFilter
>>> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
>>> at
>>> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
>>> at
>>> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
>>> at java.lang.reflect.Constructor.newInstance(Constructor.java:532)
>>> at java.lang.Class.newInstance0(Class.java:372)
>>> at java.lang.Class.newInstance(Class.java:325)
>>> at org.mortbay.jetty.servlet.Holder.newInstance(Holder.java:153)
>>> at org.mortbay.jetty.servlet.FilterHolder.doStart(FilterHolder.java:92)
>>> at
>>> org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
>>> at
>>> org.mortbay.jetty.servlet.ServletHandler.initialize(ServletHandler.java:662)
>>> at org.mortbay.jetty.servlet.Context.startContext(Context.java:140)
>>> at
>>> org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1250)
>>> at
>>> org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:517)
>>> at
>>> org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:467)
>>> at
>>> org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
>>> at
>>> com.google.apphosting.runtime.jetty.AppVersionHandlerMap.createHandler(AppVersionHandlerMap.java:202)
>>> at
>>> com.google.apphosting.runtime.jetty.AppVersionHandlerMap.getHandler(AppVersionHandlerMap.java:171)
>>> at
>>> com.google.apphosting.runtime.jetty.JettyServletEngineAdapter.serviceRequest(JettyServletEngineAdapter.java:123)
>>> at
>>> com.google.apphosting.runtime.JavaRuntime$RequestRunnable.run(JavaRuntime.java:418)
>>> at
>>> com.google.tracing.TraceContext$TraceContextRunnable.runInContext(TraceContext.java:449)
>>> at
>>> com.google.tracing.TraceContext$TraceContextRunnable$1.run(TraceContext.java:455)
>>> at com.google.tracing.TraceContext.runInContext(TraceContext.java:695)
>>> at
>>> com.google.tracing.TraceContext$AbstractTraceContextCallback.runInInheritedContextNoUnref(TraceContext.java:333)
>>> at
>>> com.google.tracing.TraceContext$AbstractTraceContextCallback.runInInheritedContext(TraceContext.java:325)
>>> at
>>> com.google.tracing.TraceContext$TraceContextRunnable.run(TraceContext.java:453)
>>> at
>>> com.google.apphosting.runtime.ThreadGroupPool$PoolEntry.run(ThreadGroupPool.java:251)
>>> at java.lang.Thread.run(Thread.java:679)
>>>
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine for Java" group.
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.

[appengine-java] java.io.IOException: Error posting to URL: https://appengine.google.com/api/appversion/create?app_id=abc

2011-11-02 Thread arjun zacharia 
Hi All,

I am having this error when i am uploading to my application id = 

Details.


I own this domain say xyz.com  ; i have linked this domain
to Google apps.  I wanted to add this domain to my appspot account say
abc.appspot.com ; so registered in google app engine with email address
ad...@xyz.com and added the application - abc and addedthe subdomain "www"
of xyz to abc.appspot.com.

Now when i put the application id - abc appropriate integer version in my
app-engine.xml  and try to upload i get the error message as follows



java.io.IOException: Error posting to URL:
https://appengine.google.com/api/appversion/create?app_id=abc&version=2&;
404 Not Found
This application does not exist (app_id=u'abc').

Is this because the application is registered to a non gmail account. But i
don't seem to have a workaround as my domain is registered to Google apps.


Can anyone help me fix this issue? I've been struggling on this for a long
time

Thanks in advance

Arjun

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine for Java" group.
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.

[appengine-java] Ad hoc reporting methods

2011-11-02 Thread Kyle Baley 
Looking for stories on how others do ad hoc reporting against their 
AppEngine databases with Java. I understand from this 
postthat
 the Deferred API and Files API can be used. Is that what's commonly 
done by others?

Other options we're considering:
- Regular backups to CSV, then sucking the data into a SQL database
- When data is written to AppEngine, also make an API call to some other 
service that stores it into a SQL database
- Write an API against the datastore to expose data required by reports

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

[appengine-java] Re: 1.6.0 Prerelease SDKs are out

2011-11-02 Thread Marcel Overdijk 
This is the same I'm wondering...

On Nov 2, 12:21 am, Roberto Saccon  wrote:
> to migrate an existing app to HDR with the new tool, can I keep now the
> app-id ?
>
> --
> Roberto

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine for Java" group.
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.

[appengine-java] Re: Change from String to Integer , now can't rid of Zombie instances... what is the right procedure to do so?

2011-11-02 Thread Daniel 
Thx 4 the detailed example, Will read it at later on today

Daniel.

On Nov 1, 6:40 pm, Ronoaldo José de Lana Pereira
 wrote:
> Daniel,
>
> To "convert" old session data I started to persist just the user Id in
> session. Sadly, unlike memcache, you can't control how the session is
> deserialized. In my case, any request with has the old user data in session
> was throwing 500 erros and I couldn't control this behavior (it was a
> filter from the gae...). What I did was something like this:
>
> public MyUser getCurrentUser(HttpServletRequest req) {
>    Object userOrId = req.getSession().getAttribute("user");
>    if (userOrId instanceof Long) {
>       return loadUserFromDsOrMemcache((Long) userOrId);
>    } else {
>       // Remove user from session and start storing ID for next change to
> User class dont raise exceptoins ...
>       User user = (User) userOrId;
>       req.getSession().setAttribute("user", user.getId());
>       return user;
>    }
>
> }
>
> This way I could get rid of storing this in session and of the app being
> unacessible when I changed my model (wich was happening heavly by the
> way...). Note that at the time I deployed this code, the User object hasn't
> changed.
>
> After running this for a while (you can expire sessions or delete them in
> bulk from the datastore so you can force them to expire, I deployed the new
> version.
>
> To store json data, you may use some json library that can map/convert
> to/from Java -> Json, like Google Gson:
>
> String userJson = new Gson().toJson(user);
> req.getSession().setAttribute("user", userJson);
> (...)
>
> String userJson = (String) req.getSession().getAttribute("user");
> if (userJson != null) {
>    User user = new Gson().fromJson(User.class, userJson);
>
> }
>
> This way you can add/remove fields to you model, and old session data will
> be restored as expected. Note that is a good practice to set defaults for
> the new fields, so your session data won't create unusable objects. In your
> original post, the change from string to integer may be solved by
> overriding the Gson de-serializer to handle the id field as number and not
> as string. I guess that you can change the way Java will de-serialize your
> classes too, but I'm not sure if this will solve your particular issue
> mentioned.
>
> Not sure if this is the best way to handle, but this is how I solved on our
> live app.
>
> More on Gson:http://code.google.com/p/google-gson/.
>
> Hope this helps (sorry for some typos or misspelled words)
>
> Best Regards,
>
> -Ronoaldo

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine for Java" group.
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.

[appengine-java] Re: 1.6.0 Prerelease SDKs are out

2011-11-02 Thread andrew 
Does the HRD migration tool migrate all namespaces from the old appid
to the new one (and off-course the data in each one)?

Thanks

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine for Java" group.
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.