[appengine-java] Re: Unable to navigate my app in production server, while in development server works fine
Solved. It was a path problem in web.xml. I didn't put the first slash (/) in the paths to the jsp files. Thanks to everyone who tried to help. -- 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: Unable to navigate my app in production server, while in development server works fine
Here is the exception raised when I try to open a jsp page inside my app. I remember I saw a different Exception ona of these days but a can't remember it and now it's not in the logs list. java.lang.RuntimeException: java.io.NotSerializableException: resources.LanguageSelector at com.google.apphosting.runtime.jetty.SessionManager.serialize(SessionManager.java:393) at com.google.apphosting.runtime.jetty.SessionManager.createEntityForSession(SessionManager.java:370) at com.google.apphosting.runtime.jetty.SessionManager$AppEngineSession.save(SessionManager.java:164) at com.google.apphosting.runtime.jetty.SaveSessionFilter.doFilter(SaveSessionFilter.java:41) 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:238) 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:135) at com.google.apphosting.runtime.JavaRuntime.handleRequest(JavaRuntime.java:261) at com.google.apphosting.base.RuntimePb$EvaluationRuntime$6.handleBlockingRequest(RuntimePb.java:8495) at com.google.apphosting.base.RuntimePb$EvaluationRuntime$6.handleBlockingRequest(RuntimePb.java:8493) at com.google.net.rpc.impl.BlockingApplicationHandler.handleRequest(BlockingApplicationHandler.java:24) at com.google.net.rpc.impl.RpcUtil.runRpcInApplication(RpcUtil.java:435) at com.google.net.rpc.impl.Server$RpcTask.runInContext(Server.java:572) at com.google.tracing.TraceContext$TraceContextRunnable$1.run(TraceContext.java:448) at com.google.tracing.TraceContext.runInContext(TraceContext.java:688) at com.google.tracing.TraceContext$AbstractTraceContextCallback.runInInheritedContextNoUnref(TraceContext.java:326) at com.google.tracing.TraceContext$AbstractTraceContextCallback.runInInheritedContext(TraceContext.java:318) at com.google.tracing.TraceContext$TraceContextRunnable.run(TraceContext.java:446) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:636) Caused by: java.io.NotSerializableException: resources.LanguageSelector at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1173) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:343) at java.util.HashMap.writeObject(HashMap.java:1018) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:962) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1478) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1409) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1167) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:343) at com.google.apphosting.runtime.jetty.SessionManager.serialize(SessionManager.java:390) -- 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
[appengine-java] Re: Unable to navigate my app in production server, while in development server works fine
Here is it, it was an IllegalStateException. I don't know where the problem
is. Thanks again
1.
Failed startup of context
com.google.apphosting.utils.jetty.runtimeappenginewebappcont...@ea443f{/,/base/data/home/apps/kokonutcmpny/1.347395332617629339}
org.mortbay.util.MultiException[java.lang.IllegalStateException: No forced
path servlet for blog/blog.jsp, java.lang.IllegalStateException: No forced path
servlet for shop/cart.jsp, java.lang.IllegalStateException: No forced path
servlet for contact/contact.jsp, java.lang.IllegalStateException: No forced
path servlet for administration/dashboard.jsp, java.lang.IllegalStateException:
No forced path servlet for index.jsp, java.lang.IllegalStateException: No
forced path servlet for shop/product.jsp, java.lang.IllegalStateException: No
forced path servlet for administration/productEditor.jsp,
java.lang.IllegalStateException: No forced path servlet for
administration/shopAdmin.jsp, java.lang.IllegalStateException: No forced path
servlet for shop/shop.jsp]
at
org.mortbay.jetty.servlet.ServletHandler.initialize(ServletHandler.java:656)
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:191)
at
com.google.apphosting.runtime.jetty.AppVersionHandlerMap.getHandler(AppVersionHandlerMap.java:168)
at
com.google.apphosting.runtime.jetty.JettyServletEngineAdapter.serviceRequest(JettyServletEngineAdapter.java:123)
at
com.google.apphosting.runtime.JavaRuntime.handleRequest(JavaRuntime.java:261)
at
com.google.apphosting.base.RuntimePb$EvaluationRuntime$6.handleBlockingRequest(RuntimePb.java:8495)
at
com.google.apphosting.base.RuntimePb$EvaluationRuntime$6.handleBlockingRequest(RuntimePb.java:8493)
at
com.google.net.rpc.impl.BlockingApplicationHandler.handleRequest(BlockingApplicationHandler.java:24)
at com.google.net.rpc.impl.RpcUtil.runRpcInApplication(RpcUtil.java:435)
at com.google.net.rpc.impl.Server$RpcTask.runInContext(Server.java:572)
at
com.google.tracing.TraceContext$TraceContextRunnable$1.run(TraceContext.java:448)
at com.google.tracing.TraceContext.runInContext(TraceContext.java:688)
at
com.google.tracing.TraceContext$AbstractTraceContextCallback.runInInheritedContextNoUnref(TraceContext.java:326)
at
com.google.tracing.TraceContext$AbstractTraceContextCallback.runInInheritedContext(TraceContext.java:318)
at
com.google.tracing.TraceContext$TraceContextRunnable.run(TraceContext.java:446)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:636)
java.lang.IllegalStateException: No forced path servlet for blog/blog.jsp
at
org.mortbay.jetty.servlet.ServletHandler.initialize(ServletHandler.java:679)
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:191)
at
com.google.apphosting.runtime.jetty.AppVersionHandlerMap.getHandler(AppVersionHandlerMap.java:168)
at
com.google.apphosting.runtime.jetty.JettyServletEngineAdapter.serviceRequest(JettyServletEngineAdapter.java:123)
at
com.google.apphosting.runtime.JavaRuntime.handleRequest(JavaRuntime.java:261)
at
com.google.apphosting.base.RuntimePb$EvaluationRuntime$6.handleBlockingRequest(RuntimePb.java:8495)
at
com.google.apphosting.base.RuntimePb$EvaluationRuntime$6.handleBlockingRequest(RuntimePb.java:8493)
at
com.google.net.rpc.impl.BlockingApplicationHandler.handleRequest(BlockingApplicationHandler.java:24)
at com.google.net.rpc.impl.RpcUtil.runRpcInApplication(RpcUtil.java:435)
at com.google.net.rpc.impl.Server$RpcTask.runInContext(Server.java:572)
at
com.google.tracing.TraceContext$TraceContextRunnable$1.run(TraceContext.java:448)
at com.google.tracing.TraceContext.runInContext(TraceContext.java:688)
at
[appengine-java] Re: Unable to navigate my app in production server, while in development server works fine
Ok, this is a mistery, now, I have deployed again (without changing anything, i think, XD) and I can acccess some pages in my website, but others remain with problems. You can see this in the url for the app: www.kokonutcmpny.appspot.com -- 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: Unable to navigate my app in production server, while in development server works fine
I'm still trying to make my app work in GAE server but I don't find answers. I tried removing all the info from web.xml except the welcome file entry. According to what I have understood reading the forums, that way, I can access my jsp files typing directly it's URL, for example: myapp.appspot.com/shop/shop.jsp. Once again, it work fine in development server but chashes in production server. This time, when I access to the pages the message from the browser is this one: Error: Server Error The server encountered an error and could not complete your request. If the problem persists, please reporthttp://code.google.com/appengine/community.htmlyour problem and mention this error message and the query that caused it. Thanks in advance. -- 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: Unable to navigate my app in production server, while in development server works fine
I also came across an error while defining jsp-file servlet mappings into web.xml just like what have you done. Anyway I suggest you check the logs on your appengine application. You should be able to see a stack-trace of the failure. could u post it? for more info refer http://code.google.com/appengine/articles/logging.html -- 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: Unable to navigate my app in production server, while in development server works fine
Here is my index.jsp. I don't actually understand what you suspect, but hope
you do. XD
%@ page language=java contentType=text/html; charset=UTF-8
pageEncoding=UTF-8%
%@ taglib uri=http://java.sun.com/jstl/fmt_rt; prefix=fmt %
%@ taglib uri=http://java.sun.com/jstl/core_rt; prefix=c %
jsp:useBean id=CartController class=kokonut.shop.cart.CartController
scope=session /
jsp:useBean id=LanguageSelector class=resources.LanguageSelector
scope=session /
!DOCTYPE html PUBLIC -//W3C//DTD HTML 4.01 Transitional//EN
http://www.w3.org/TR/html4/loose.dtd;
html
head
meta http-equiv=Content-Type content=text/html; charset=UTF-8
style type=text/css media=all@import
pageStyle.css;/style
link href=//fonts.googleapis.com/css?family=Raleway:100
rel=stylesheet type=text/css
link href=//fonts.googleapis.com/css?family=Inconsolata:regular
rel=stylesheet type=text/css
link
href=//fonts.googleapis.com/css?family=Droid+Sans:regular,bold
rel=stylesheet type=text/css
titleKokonut Web/title
/head
body
div id=regionSwitcher
fmt:setLocale value=%=LanguageSelector.getLocaleName()%
scope=session /
div id=languages
ul
li id=euskaraa
href=/selectLocale?locale=eu_ESbeuskara/b/a/li
li id=castellanoa
href=/selectLocale?locale=es_ESbcastellano/b/a/li
li id=englisha
href=/selectLocale?locale=en_UKbenglish/b/a/li
/ul
/div
/div
fmt:bundle basename=ApplicationResources
div id=pageContainer
div id=menu
ul
li id=homea href=/bfmt:message key=home
//b/a/li
li id=storea href=/shopbfmt:message
key=shop //b/a/li
li id=bloga href=/blogbfmt:message
key=blog //b/a/li
li id=contacta href=/contactbfmt:message
key=contact //b/a/li
/ul
/div
div id=header
div id=cartPlacea href=/cart
img src=images/Cart.png alt=cart image
% if (CartController.getNumberOfProducts() ==
0) {
%
fmt:message key=emptyCart /
%} else {
%
fmt:message key=cart /:
%=CartController.getNumberOfProducts()% fmt:message key=products /
%}
%
br/
fmt:message key=totalPrice /:
%=CartController.getTotalPrice()% €
/a
/div
h1KokonutCompany/h1
/div
div id=sidebar
Lorem Ipsum is simply dummy text of the printing and
typesetting industry. Lorem Ipsum has been the industry's standard dummy
text ever since the 1500s, when an unknown printer took a galley of type and
scrambled it to make a type specimen book. It has survived not only five
centuries, but also the leap into electronic typesetting, remaining
essentially unchanged. It was popularised in the 1960s with the release of
Letraset sheets containing Lorem Ipsum passages, and more recently with
desktop publishing software like Aldus PageMaker including versions of Lorem
Ipsum.
/div
div id=content
div class=padding
Lorem Ipsum is simply dummy text of the printing
and typesetting industry. Lorem Ipsum has been the industry's standard dummy
text ever since the 1500s, when an unknown printer took a galley of type and
scrambled it to make a type specimen book. It has survived not only five
centuries, but also the leap into electronic typesetting, remaining
essentially unchanged. It was popularised in the 1960s with the release of
Letraset sheets containing Lorem Ipsum passages, and more recently with
desktop publishing software like Aldus PageMaker including versions of Lorem
Ipsum.
Lorem Ipsum is simply dummy text of the printing
and typesetting industry. Lorem Ipsum has been the industry's standard dummy
text ever since the 1500s, when an unknown printer took a galley of type and
scrambled it to make a type specimen book. It has survived not only five
centuries, but also the leap into electronic typesetting, remaining
essentially unchanged. It was popularised in the 1960s with the release of
Letraset sheets containing Lorem Ipsum passages, and more recently with
desktop publishing software like Aldus PageMaker including versions of Lorem
Ipsum.
/div
/div
div id=footer
div id=altNava href=/fmt:message key=home
//a | a href=/shopfmt:message key=shop //a | a
[appengine-java] Re: Unable to navigate my app in production server, while in development server works fine
Would you mind to post your index.jsp as well? I suspect it's because GAE server is case sensitive, and the thrown exception is not serializable On Jan 4, 10:05 pm, Markel Arizaga markel.ariz...@gmail.com wrote: Hi, I got stuck. I Googled and have been searching in the forums during the last days but I don't find an answer that fixes my problem, so I'm sorry if this has been already commented. I'm developing an app using Java version of GAE and it works fine in local server. I used eclipse plugin and also NetBeans IDE and worked with both but the problem begins when I try to upload the app to GAE. Once uploaded I can only access the welcome file (index.jsp) but any other page is not loaded. The browser gives messages like Error: Forbidden and Error: Not Found. I think something in my web.xml is wrong but I'm not able to figure out what it is. In my web.xml I declare my servlet classes as well the jsp files and I think I'm doing it correctly: servlet servlet-nameNAME/servlet-name servlet-classPACKAGE.CLASS/servlet-class /servlet servlet-mapping servlet-nameNAME/servlet-name url-pattern/PATH/url-pattern /servlet-mapping servlet servlet-nameNAME2/servlet-name jsp-fileFOLDER/NAME2.jsp/jsp-file /servlet servlet-mapping servlet-nameNAME2/servlet-name url-pattern/PATH2/url-pattern /servlet-mapping I have also a welcome file declared exactly like the documentation says and a security constraint as follows: security-constraint web-resource-collection url-pattern/adminZone/*/url-pattern /web-resource-collection auth-constraint role-nameadmin/role-name /auth-constraint /security-constraint I saw the logs in the dashboard and I realised that NotSerializableExceptions were thrown refering to one of my classes but the problems persists after I made it Serializable. I hope someone will have any idea, 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-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.
