[appengine-java] Massive delete (mapreduce based) > Datastore viewer & Datastore statistics unavailable

2010-12-09 Thread Cyrille Vincey
My problem:
1. I execute a massive delete over a large number of entities (30 million),
using a mapreduce-based job similar to Ikai's one (*)
2. Then both the datastore viewer and the datastore statistics in the
dashboard become unavailable: I get this famous "the server encountered an
error (blahblah)" page.

Yet, servlet-based queries against the datastore are ok, and the datastore
indexes viewer do not show any error.
Any clue ?

(*) 
http://ikaisays.com/2010/07/09/using-the-java-mapper-framework-for-app-engin
e/



-- 
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-j...@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: Checking admin priviledges using UserService in a cron/task-queue task execution

2010-12-09 Thread andrew

Ikai / Google ??

Any official word on the expected/desired behavior of the UserService
for a cron task or task queue task, w.r.t. checking of the user
"isAdmin()" ??

thanks

Andrew

-- 
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-j...@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: AppEngine 1.4.0 now supports jsp-config in web.xml

2010-12-09 Thread George Moschovitis
Interesting,


I love seeing "uncool" but still useful features added in the SDK.


-g.

-- 
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-j...@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] Problem switching to 1.4.0 - JSP compilation fails

2010-12-09 Thread l.denardo
Hello,
I'm having trouble switching to 1.4.0 SDK.

Development server starts regularly, but when I try to load my login
page (a jsp file) I get the following error:

[WARN] /_ah/login_required
org.apache.jasper.JasperException: Unable to compile class for JSP:

An error occurred at line: 1 in the generated java file
The type javax.servlet.jsp.PageContext cannot be resolved. It is
indirectly referenced from required .class files

An error occurred at line: 1 in the generated java file
The type javax.servlet.jsp.tagext.TagSupport cannot be resolved. It is
indirectly referenced from required .class files

[more similar entries follow]

An error occurred at line: 1,079 in the generated java file
javax.servlet.jsp.tagext.JspTag cannot be resolved to a type

Stacktrace:
at
org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandler.java:
92)
at
org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java:
330)
at
org.apache.jasper.compiler.JDTCompiler.generateClass(JDTCompiler.java:
439)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:349)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:327)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:314)
at
org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:
592)
at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:
317)
at
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:
313)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:260)
at com.google.appengine.tools.development.PrivilegedJspServlet.access
$101(PrivilegedJspServlet.java:23)
at com.google.appengine.tools.development.PrivilegedJspServlet
$2.run(PrivilegedJspServlet.java:59)
at java.security.AccessController.doPrivileged(Native Method)
at
com.google.appengine.tools.development.PrivilegedJspServlet.service(PrivilegedJspServlet.java:
57)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:
511)
at org.mortbay.jetty.servlet.ServletHandler
$CachedChain.doFilter(ServletHandler.java:1166)
at
com.google.appengine.api.blobstore.dev.ServeBlobFilter.doFilter(ServeBlobFilter.java:
58)
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
com.google.appengine.tools.development.StaticFileFilter.doFilter(StaticFileFilter.java:
122)
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.utils.jetty.DevAppEngineWebAppContext.handle(DevAppEngineWebAppContext.java:
70)
at
org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:
152)
at com.google.appengine.tools.development.JettyContainerService
$ApiProxyHandler.handle(JettyContainerService.java:349)
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 org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:547)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
at
org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:
409)
at org.mortbay.thread.QueuedThreadPool
$PoolThread.run(QueuedThreadPool.java:582)

Looks like the jsp-api.jar in the SDK is getting ignored, but it's
there and is also visible by Eclipse (auto-completion imports
correctly the "missing" classes if you try to use them from the
editor).
Is anyone facing the same? Do you know if there's any configuration I
have to check to see if everything's fine?

I'm running on Ubuntu, Eclipse Helios, GWT 2.1.0 and of course GAE
1.4.0 (from 1.3.8), Google Plugin for Eclipse v.1.4.0.

Thenk you very much
regards
Lorenzo

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine for Java" group.
To post to this group, sen

[appengine-java] Massive Problems with CPU/Guice Servlet and Channel API

2010-12-09 Thread Flori
Hey all,

I try to use the new Channel API. On localhost i've no problems, but
the deployed version, unfortunately, does not work at all.

There are two different problems:

1) High CPU Avg after calling a Guice Managed servlet:

>The servlet which builds the token has a very high (not normal) CPU Avg:
>12-09 07:46AM 31.531 /token?_dc=1291909591556 200 2330ms 5080cpu_ms 
>2770api_cpu_ms 0kb Mozilla/5.0 (X11; U; Linux i686; en-US) AppleWebKit/534.10 
>(KHTML, like Gecko) >Chrome/8.0.552.215 Safari/534.10,gzip(gfe)
>217.119.50.53 - FloOnWeb [09/Dec/2010:07:46:33 -0800] "GET 
>/token?_dc=1291909591556 HTTP/1.1" 200 199 - "Mozilla/5.0 (X11; U; Linux i686; 
>en-US) AppleWebKit/534.10 (KHTML, >like Gecko) Chrome/8.0.552.215 
>Safari/534.10,gzip(gfe)" - ms=2331 cpu_ms=5080 api_cpu_ms=2770 
>cpm_usd=0.141237 loading_request=1 pending_ms=451
>I 12-09 07:46AM 33.860
>This request caused a new process to be started for your application, and thus 
>caused your application code to be loaded for the first time. This request may 
>thus take longer and use >more CPU than a typical request for your application.

Current Load Table Overview: /token  5   3323 (3323)!79%

Hmm okay the request caused a new process, but this message appears
after every refresh! So can anyone give me a hint what's going wrong?
It takes about 5-7 seconds until the page appears and the servlet
responses. You can find the (not much) Servlet source here:
http://code.google.com/p/phone-messenger/source/browse/trunk/src/de/rentoudu/chat/server/servlet/ChannelTokenServlet.java

So it's not really much code...

2) Channel API Error
After deploy, I get the following javascript error (console):

> Uncaught Error
> h  jsapi:1
> Ed  jsapi:80
> $  jsapi:75
> Gd.open  jsapi:81
> loadApplication  application.js:158

You can try it here: https://phone-messenger.appspot.com/  - just
login, wait, open console and you'll get the same error
The call happens in: 
http://code.google.com/p/phone-messenger/source/browse/trunk/war/javascripts/application.js
(about line 156)

I really hope someone can help me, so thanks in advance for any
helpful hints!

-- 
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-j...@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] Server error when deleting a version

2010-12-09 Thread dleshem
Hello,

I'm getting an error when trying to delete versions 2 and 3 of my
application (id = "implied2").
Attempting to delete these versions using AppEngine's control panel
displays "A server error has occurred".

Any suggestions?
Danny

-- 
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-j...@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] AppEngine-java-sdk-1.4.0 Eclipse plugin for Mac

2010-12-09 Thread Sumi
Is the AppEngine-java-sdk-1.4.0 Eclipse plugin for Mac available ?

if so from where can it be downloaded...I searched everywhere and non of the
available ones worked..

If it is not available yet, anyone knows what is the expected date of
availability?

Our launch date has come to a halt due the unable to deploy problem ...

so any help is highly appreciated.

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



Re: [appengine-java] migrating to 1.4 task queues

2010-12-09 Thread A. Stevko
The only other surprise was when I upgrade the eclipse project to using 1.4,
it _silently failed_ to copy the 1.4 jar files into my project.
This resulted in class not found exceptions during startup.
I've seen other posts that stated this happened when the files where
manually put into place but that is not my case. I've always relied on the
eclipse project tool for managing the gae & gwt versions.

Manually deleting the various 1.3.8 jars and resetting the project's app
engine version to 1.4.0 put the whole thing back on track.

One other thing that is bothering me now although it may or may not be
related to the 1.4 upgrade migration,
Many UI 500 responses are context startup initialization failures like:

12-09 10:22AM 56.796

Failed startup of context
com.google.apphosting.utils.jetty.runtimeappenginewebappcont...@1cc5461{/,/base/data/home/apps/ninuku-archivist/1-0-6d.346785216597395753}
com.google.apphosting.api.DeadlineExceededException: This request
(96acdaff3e9f45cd) started at 2010/12/09 18:22:28.108 UTC and was
still executing at 2010/12/09 18:22:56.787 UTC.
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)



 and -
12-09 09:58AM 28.574

Failed startup of context
com.google.apphosting.utils.jetty.runtimeappenginewebappcont...@15780d9{/,/base/data/home/apps/ninuku-archivist/1-0-6d.346785216597395753}
com.google.inject.CreationException: Guice creation errors:

1) Error injecting method,
com.google.inject.internal.ComputationException:
com.google.inject.internal.ComputationException:
java.lang.SecurityException: Unable to get members for class
com.ninuku.memories.server.handler.journal.DeletePhotoChapterHandler
  at 
net.customware.gwt.dispatch.server.guice.ActionHandlerLinker.linkHandlers(ActionHandlerLinker.java:30)

1 error
at 
com.google.inject.internal.Errors.throwCreationExceptionIfErrorsExist(Errors.java:354)
at 
com.google.inject.InjectorBuilder.injectDynamically(InjectorBuilder.java:173)
at com.google.inject.InjectorBuilder.build(InjectorBuilder.java:113)
at com.google.inject.Guice.createInjector(Guice.java:92)





On Wed, Dec 8, 2010 at 12:39 PM, Stevko  wrote:

> I'm dealing with the change in task queue apis away from .labs.
>
> One change I've encoutered that is not mentioned in the release notes:
> http://code.google.com/p/googleappengine/wiki/SdkForJavaReleaseNotes
>
> import static
> com.google.appengine.api.labs.taskqueue.TaskOptions.Builder.url;
> is now undefined.
>
> I suspect this is the proper replacement method
> import static
> com.google.appengine.api.taskqueue.TaskOptions.Builder.withUrl;
>
> Any other surprises with migrating to 1.4 task queues?
>
> --
> 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-j...@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.
>
>

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



Re: [appengine-java] DEPLOYMENT FAILING AGAIN

2010-12-09 Thread Ikai Lan (Google)
Is this with the 1.4.0 SDK? Are you mapping URLs to JSP files? There's
another thread about this issue - we're looking into it.

--
Ikai Lan
Developer Programs Engineer, Google App Engine
Blogger: http://googleappengine.blogspot.com
Reddit: http://www.reddit.com/r/appengine
Twitter: http://twitter.com/app_engine



On Wed, Dec 8, 2010 at 12:56 PM, Sumi  wrote:

> Unable to update app: Failed to compile jsp files.
>
>
> See the deployment console for more details
>
> Unable to update app: Failed to compile jsp files.
>
> ===
>
>
> I DIDN'T MAKE ANY CHANGES TO JSP PAGES
>
> --
> 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-j...@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.
>

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



Re: [appengine-java] multiple emails being sent

2010-12-09 Thread Ikai Lan (Google)
Are you making these calls in a task queue? There are known issues where a
timeout exception will be thrown by the Mail API even though the mail was
successfully sent - this'll cause the task to retry and resend the email.

--
Ikai Lan
Developer Programs Engineer, Google App Engine
Blogger: http://googleappengine.blogspot.com
Reddit: http://www.reddit.com/r/appengine
Twitter: http://twitter.com/app_engine



On Wed, Dec 8, 2010 at 2:33 PM, byraray  wrote:

> When sending 1 email request using  pic...@appid.appspotmail.com
> app engine send 5 extra emails replies to the same address.
>
> public class PickupMailHandlerServlet extends HttpServlet {
>
>public static final long serialVersionUID = 1L;
>
>public void doPost(HttpServletRequest req, HttpServletResponse resp)
>throws IOException {
>
>final Logger log =
> Logger.getLogger(PickupMailHandlerServlet.class.getName());
>
>Properties sendprops = new Properties();
>Session session = Session.getDefaultInstance(sendprops,
> null);
>
>try {
>
>Message msg = new MimeMessage(session,req.getInputStream());
>
>String summary = msg.getSubject();
>String description = getText(msg);
>
>msg.setFrom(new InternetAddress("pic...@...i.com",
> "me"));
>  msg.addRecipient(Message.RecipientType.TO, new
> InternetAddress("m...@yahoo.com", ""));
>msg.setSubject(summary);
>msg.setText(description);
>Transport.send(msg);
>}
>
>catch (UnsupportedEncodingException e) {
>log.severe("UnsupportedEncodingException");
>log.severe(e.getMessage());
>return;
>}
>
>catch (MessagingException e) {
>log.severe("MessagingException");
>log.severe(e.getMessage());
>return;
>}
>
>catch (Exception e) {
>log.severe("Exception");
>log.severe(e.getMessage());
>}
>}
>
> --
> 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-j...@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.
>
>

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



Re: [appengine-java] Problem switching to 1.4.0 - JSP compilation fails

2010-12-09 Thread Ikai Lan (Google)
We're reproduced this. It seems to happen when you map a URL to a JSP, and
only on the development server.

--
Ikai Lan
Developer Programs Engineer, Google App Engine
Blogger: http://googleappengine.blogspot.com
Reddit: http://www.reddit.com/r/appengine
Twitter: http://twitter.com/app_engine



On Thu, Dec 9, 2010 at 8:36 AM, l.denardo  wrote:

> Hello,
> I'm having trouble switching to 1.4.0 SDK.
>
> Development server starts regularly, but when I try to load my login
> page (a jsp file) I get the following error:
>
> [WARN] /_ah/login_required
> org.apache.jasper.JasperException: Unable to compile class for JSP:
>
> An error occurred at line: 1 in the generated java file
> The type javax.servlet.jsp.PageContext cannot be resolved. It is
> indirectly referenced from required .class files
>
> An error occurred at line: 1 in the generated java file
> The type javax.servlet.jsp.tagext.TagSupport cannot be resolved. It is
> indirectly referenced from required .class files
>
> [more similar entries follow]
>
> An error occurred at line: 1,079 in the generated java file
> javax.servlet.jsp.tagext.JspTag cannot be resolved to a type
>
> Stacktrace:
>at
>
> org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandler.java:
> 92)
>at
> org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java:
> 330)
>at
> org.apache.jasper.compiler.JDTCompiler.generateClass(JDTCompiler.java:
> 439)
>at org.apache.jasper.compiler.Compiler.compile(Compiler.java:349)
>at org.apache.jasper.compiler.Compiler.compile(Compiler.java:327)
>at org.apache.jasper.compiler.Compiler.compile(Compiler.java:314)
>at
> org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:
> 592)
>at
> org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:
> 317)
>at
> org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:
> 313)
>at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:260)
>at
> com.google.appengine.tools.development.PrivilegedJspServlet.access
> $101(PrivilegedJspServlet.java:23)
>at com.google.appengine.tools.development.PrivilegedJspServlet
> $2.run(PrivilegedJspServlet.java:59)
>at java.security.AccessController.doPrivileged(Native Method)
>at
>
> com.google.appengine.tools.development.PrivilegedJspServlet.service(PrivilegedJspServlet.java:
> 57)
>at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
>at
> org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:
> 511)
>at org.mortbay.jetty.servlet.ServletHandler
> $CachedChain.doFilter(ServletHandler.java:1166)
>at
>
> com.google.appengine.api.blobstore.dev.ServeBlobFilter.doFilter(ServeBlobFilter.java:
> 58)
>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
>
> com.google.appengine.tools.development.StaticFileFilter.doFilter(StaticFileFilter.java:
> 122)
>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.utils.jetty.DevAppEngineWebAppContext.handle(DevAppEngineWebAppContext.java:
> 70)
>at
> org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:
> 152)
>at com.google.appengine.tools.development.JettyContainerService
> $ApiProxyHandler.handle(JettyContainerService.java:349)
>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 org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:547)
>at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)
>at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
>at
> org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:
> 409)
>at org.mortbay.thread.QueuedThreadPool
> $PoolThread.run(QueuedThreadPool.java:582)
>
> Looks like the jsp-api.jar in the SDK is getting ignored, but it's
> there

Re: [appengine-java] Server error when deleting a version

2010-12-09 Thread Ikai Lan (Google)
I've cleared out these versions for you.

--
Ikai Lan
Developer Programs Engineer, Google App Engine
Blogger: http://googleappengine.blogspot.com
Reddit: http://www.reddit.com/r/appengine
Twitter: http://twitter.com/app_engine



On Thu, Dec 9, 2010 at 9:21 AM, dleshem  wrote:

> Hello,
>
> I'm getting an error when trying to delete versions 2 and 3 of my
> application (id = "implied2").
> Attempting to delete these versions using AppEngine's control panel
> displays "A server error has occurred".
>
> Any suggestions?
> Danny
>
> --
> 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-j...@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.
>
>

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



Re: [appengine-java] migrating to 1.4 task queues

2010-12-09 Thread Ikai Lan (Google)
Thanks for the update, Andy. I'm not sure what the 500s you're seeing are
yet, but I'll keep an eye out for reports.

--
Ikai Lan
Developer Programs Engineer, Google App Engine
Blogger: http://googleappengine.blogspot.com
Reddit: http://www.reddit.com/r/appengine
Twitter: http://twitter.com/app_engine



On Thu, Dec 9, 2010 at 12:36 PM, A. Stevko  wrote:

> The only other surprise was when I upgrade the eclipse project to using
> 1.4, it _silently failed_ to copy the 1.4 jar files into my project.
> This resulted in class not found exceptions during startup.
> I've seen other posts that stated this happened when the files where
> manually put into place but that is not my case. I've always relied on the
> eclipse project tool for managing the gae & gwt versions.
>
> Manually deleting the various 1.3.8 jars and resetting the project's app
> engine version to 1.4.0 put the whole thing back on track.
>
> One other thing that is bothering me now although it may or may not be
> related to the 1.4 upgrade migration,
> Many UI 500 responses are context startup initialization failures like:
>
> 12-09 10:22AM 56.796
>
>
> Failed startup of context 
> com.google.apphosting.utils.jetty.runtimeappenginewebappcont...@1cc5461{/,/base/data/home/apps/ninuku-archivist/1-0-6d.346785216597395753}
> com.google.apphosting.api.DeadlineExceededException: This request 
> (96acdaff3e9f45cd) started at 2010/12/09 18:22:28.108 UTC and was still 
> executing at 2010/12/09 18:22:56.787 UTC.
>   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)
>
>
>
>  and -
> 12-09 09:58AM 28.574
>
>
> Failed startup of context 
> com.google.apphosting.utils.jetty.runtimeappenginewebappcont...@15780d9{/,/base/data/home/apps/ninuku-archivist/1-0-6d.346785216597395753}
> com.google.inject.CreationException: Guice creation errors:
>
> 1) Error injecting method, com.google.inject.internal.ComputationException: 
> com.google.inject.internal.ComputationException: java.lang.SecurityException: 
> Unable to get members for class 
> com.ninuku.memories.server.handler.journal.DeletePhotoChapterHandler
>   at 
> net.customware.gwt.dispatch.server.guice.ActionHandlerLinker.linkHandlers(ActionHandlerLinker.java:30)
>
> 1 error
>   at 
> com.google.inject.internal.Errors.throwCreationExceptionIfErrorsExist(Errors.java:354)
>   at 
> com.google.inject.InjectorBuilder.injectDynamically(InjectorBuilder.java:173)
>   at com.google.inject.InjectorBuilder.build(InjectorBuilder.java:113)
>   at com.google.inject.Guice.createInjector(Guice.java:92)
>
>
>
>
>
> On Wed, Dec 8, 2010 at 12:39 PM, Stevko  wrote:
>
>> I'm dealing with the change in task queue apis away from .labs.
>>
>> One change I've encoutered that is not mentioned in the release notes:
>> http://code.google.com/p/googleappengine/wiki/SdkForJavaReleaseNotes
>>
>> import static
>> com.google.appengine.api.labs.taskqueue.TaskOptions.Builder.url;
>> is now undefined.
>>
>> I suspect this is the proper replacement method
>> import static
>> com.google.appengine.api.taskqueue.TaskOptions.Builder.withUrl;
>>
>> Any other surprises with migrating to 1.4 task queues?
>>
>> --
>> 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-j...@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.
>>
>>
>  --
> 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-j...@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.
>

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



Re: [appengine-java] AppEngine-java-sdk-1.4.0 for mac corrupted

2010-12-09 Thread Tatyana
Actually it is ok on Mac 10.6.5
Should you check 'Downloads' directory? Screenshot indicates few downloads
of the same file.

On Thu, Dec 9, 2010 at 7:23 PM, Sumi  wrote:

>
> I downloaded it from here
> http://code.google.com/appengine/downloads.html
>
> and getting the error  "it cannot be unarchived"
>
>
> can someone help with the location for the correct sdk 1.4.0 for java
>
> --
> 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-j...@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.
>

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



Re: [appengine-java] AppEngine-java-sdk-1.4.0 for mac corrupted

2010-12-09 Thread Sumi
Thanks! I reinstalled al my eclipse plugins and now i am able to deploy.



On Thu, Dec 9, 2010 at 4:43 PM, Tatyana  wrote:

> Actually it is ok on Mac 10.6.5
> Should you check 'Downloads' directory? Screenshot indicates few downloads
> of the same file.
>
> On Thu, Dec 9, 2010 at 7:23 PM, Sumi  wrote:
>
>>
>> I downloaded it from here
>> http://code.google.com/appengine/downloads.html
>>
>> and getting the error  "it cannot be unarchived"
>>
>>
>> can someone help with the location for the correct sdk 1.4.0 for java
>>
>> --
>> 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-j...@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.
>>
>
>  --
> 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-j...@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.
>

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



Re: [appengine-java] DEPLOYMENT FAILING AGAIN

2010-12-09 Thread Sumi
I reinstalled all the eclipse plugins and now able to deploy.




On Thu, Dec 9, 2010 at 2:49 PM, Ikai Lan (Google)

> wrote:

> Is this with the 1.4.0 SDK? Are you mapping URLs to JSP files? There's
> another thread about this issue - we're looking into it.
>
> --
> Ikai Lan
> Developer Programs Engineer, Google App Engine
> Blogger: http://googleappengine.blogspot.com
> Reddit: http://www.reddit.com/r/appengine
> Twitter: http://twitter.com/app_engine
>
>
>
> On Wed, Dec 8, 2010 at 12:56 PM, Sumi  wrote:
>
>> Unable to update app: Failed to compile jsp files.
>>
>>
>> See the deployment console for more details
>>
>> Unable to update app: Failed to compile jsp files.
>>
>> ===
>>
>>
>> I DIDN'T MAKE ANY CHANGES TO JSP PAGES
>>
>> --
>> 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-j...@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.
>>
>
>  --
> 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-j...@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.
>

-- 
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-j...@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: Problem switching to 1.4.0 - JSP compilation fails

2010-12-09 Thread Starman
I was using a servlet mapping to make my url nicer. Instead of
appid.appspot.com/MyApp.jsp, I had appid.appspot.com/servletname. And
I was using the jsp-file tag to map the servlet to the jsp file.

I have commented out the servlet definition and just let the jsp auto
mapping do its thing. And everything works fine, albeit with uglier
urls.

Btw, I'm using a jsp for my GWT host file instead of an html file so
that I can secure the app host file. Html being statically deployed
makes it impossible to secure at the servlet layer.

R.

On Dec 9, 6:03 pm, "Ikai Lan (Google)" 
wrote:
> We're reproduced this. It seems to happen when you map a URL to a JSP, and
> only on the development server.
>
> --
> Ikai Lan
> Developer Programs Engineer, Google App Engine
> Blogger:http://googleappengine.blogspot.com
> Reddit:http://www.reddit.com/r/appengine
> Twitter:http://twitter.com/app_engine
>
>
>
> On Thu, Dec 9, 2010 at 8:36 AM, l.denardo  wrote:
> > Hello,
> > I'm having trouble switching to 1.4.0 SDK.
>
> > Development server starts regularly, but when I try to load my login
> > page (a jsp file) I get the following error:
>
> > [WARN] /_ah/login_required
> > org.apache.jasper.JasperException: Unable to compile class for JSP:
>
> > An error occurred at line: 1 in the generated java file
> > The type javax.servlet.jsp.PageContext cannot be resolved. It is
> > indirectly referenced from required .class files
>
> > An error occurred at line: 1 in the generated java file
> > The type javax.servlet.jsp.tagext.TagSupport cannot be resolved. It is
> > indirectly referenced from required .class files
>
> > [more similar entries follow]
>
> > An error occurred at line: 1,079 in the generated java file
> > javax.servlet.jsp.tagext.JspTag cannot be resolved to a type
>
> > Stacktrace:
> >        at
>
> > org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandler.java:
> > 92)
> >        at
> > org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java:
> > 330)
> >        at
> > org.apache.jasper.compiler.JDTCompiler.generateClass(JDTCompiler.java:
> > 439)
> >        at org.apache.jasper.compiler.Compiler.compile(Compiler.java:349)
> >        at org.apache.jasper.compiler.Compiler.compile(Compiler.java:327)
> >        at org.apache.jasper.compiler.Compiler.compile(Compiler.java:314)
> >        at
> > org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:
> > 592)
> >        at
> > org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:
> > 317)
> >        at
> > org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:
> > 313)
> >        at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:260)
> >        at
> > com.google.appengine.tools.development.PrivilegedJspServlet.access
> > $101(PrivilegedJspServlet.java:23)
> >        at com.google.appengine.tools.development.PrivilegedJspServlet
> > $2.run(PrivilegedJspServlet.java:59)
> >        at java.security.AccessController.doPrivileged(Native Method)
> >        at
>
> > com.google.appengine.tools.development.PrivilegedJspServlet.service(PrivilegedJspServlet.java:
> > 57)
> >        at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
> >        at
> > org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:
> > 511)
> >        at org.mortbay.jetty.servlet.ServletHandler
> > $CachedChain.doFilter(ServletHandler.java:1166)
> >        at
>
> > com.google.appengine.api.blobstore.dev.ServeBlobFilter.doFilter(ServeBlobFilter.java:
> > 58)
> >        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
>
> > com.google.appengine.tools.development.StaticFileFilter.doFilter(StaticFileFilter.java:
> > 122)
> >        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.utils.jetty.DevAppEngineWebAppContext.handle(DevAppEngineWebAppContext.java:
> > 70)
> >        at
> > org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:
> > 152)
> >        at com.google.appengine.tools.development.JettyContainerService
> > $ApiProxyHandler.handle(JettyContainerService.java:349)
> >        at
> > org.mortbay.jetty.handler.Handler