I confirmed that the line number reported in a JSP stack dump from production will NOT match that reported in the test environment. The generated java memberHome_jsp.java located in the test environment is NOT the same source as used for production. Hence, the line number is of NO use unless we are given the source used by production deploy process.
HOW DO WE ACCESS the generated Java for JSPs created during the deploy process so that we can trouble-shoot stack dumps containing source code line numbers? On Apr 2, 11:01 pm, James H <[email protected]> wrote: > This trace below is from production environment. How do I find the > memberHome_jsp.java so I can verify the problem at line 165? I found > the .java file used for running locally, but this line# in question > was inappropriate in regard to causing a null issue...so I must be > looking at the wrong .java in the case of production dumps. Thanks, J > > Programming Details - java.lang.NullPointerException > at org.apache.jsp.app2.memberHome_jsp._jspService(memberHome_jsp.java: > 165) > at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:94) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:806) > at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java: > 511) > at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java: > 390) > at > org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java: > 216) -- 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 [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
