large class file generated..
Title: Blank Hi, Could anyone shed some light on this problem? I'm using Tomcat 4.1.18.JASPER is creatinglots of lines for out.write statements and giving the following error. When compared to weblogic, the generated code after compiling the page is almost 12 times large. The same code works fine in weblogic. Any suggestions please? Thanks, Amar. Here is the exception trace and also screenshot attached.HTTP Status 500 - type Exception reportmessage description The server encountered an internal error () that prevented it from fulfilling this request.exception javax.servlet.ServletException: org/apache/jsp/help_pricing_jsp (Code of a method longer than 65535 bytes)at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:249)at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247)at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193)at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:260)at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)at org.apache.catalina.valves.CertificatesValve.invoke(CertificatesValve.java:246)at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2415)at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:170)at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172)at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223)at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:261)at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:360)at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:632)at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:590)at org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:707)at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:530)at java.lang.Thread.run(Thread.java:536)root cause java.lang.ClassFormatError: org/apache/jsp/help_pricing_jsp (Code of a method longer than 65535 bytes)at java.lang.ClassLoader.defineClass0(Native Method)at java.lang.ClassLoader.defineClass(ClassLoader.java:509)at java.lang.ClassLoader.defineClass(ClassLoader.java:438)at org.apache.jasper.servlet.JasperLoader.loadClass(JasperLoader.java:215)at org.apache.jasper.servlet.JasperLoader.loadClass(JasperLoader.java:131)at org.apache.jasper.JspCompilationContext.load(JspCompilationContext.java:504)at org.apache.jasper.servlet.JspServletWrapper.getServlet(JspServletWrapper.java:145)at org.apache.jasper.compiler.Compiler.isOutDated(Compiler.java:411)at org.apache.jasper.compiler.Compiler.isOutDated(Compiler.java:361)at org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:472)at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:184)at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295)at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241)at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247)at
Re: large class file generated..
Since a JSP is converted to java code, the jsp runs in a method called _jspService (or a very similar name as dicated by the spec). The java language itself has a constraint that no method may be larger than the upper limit you are running into. [I think jasper generates an out.print() for each \n combo instead of combining them. I can't remember...] Anyhoo ... See $TOMCAT_HOME/conf/web.xml to turn on mapped files which (I think) moves that static content to another file. Otherwise, if possible split the file and use jsp:include to include content if possible. It you are using @page include extensively - that would be a problem too since that helps you file to become bloated very quickly. -Tim Amarnath Reddy wrote: BlankHi, Could anyone shed some light on this problem? I'm using Tomcat 4.1.18. JASPER is creating lots of lines for out.write statements and giving the following error. When compared to weblogic, the generated code after compiling the page is almost 12 times large. The same code works fine in weblogic. Any suggestions please? Thanks, - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: large class file generated..
Tim, Thanks for the suggestions. Infact, you are right about the out.print statements. JASPER is creating new statements for each End Of Line and hence the problem. But weblogic is combining all of them to a sizeable single out.write statement. However I got through the problem by using run-time Jsp Includes and you have suggested this too. thanks. Apache Developers should dig in deep to correct the problem in JASPER itself! Amar. -Original Message- From: Tim Funk [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 05, 2003 5:40 PM To: Tomcat Users List Subject: Re: large class file generated.. Since a JSP is converted to java code, the jsp runs in a method called _jspService (or a very similar name as dicated by the spec). The java language itself has a constraint that no method may be larger than the upper limit you are running into. [I think jasper generates an out.print() for each \n combo instead of combining them. I can't remember...] Anyhoo ... See $TOMCAT_HOME/conf/web.xml to turn on mapped files which (I think) moves that static content to another file. Otherwise, if possible split the file and use jsp:include to include content if possible. It you are using @page include extensively - that would be a problem too since that helps you file to become bloated very quickly. -Tim Amarnath Reddy wrote: BlankHi, Could anyone shed some light on this problem? I'm using Tomcat 4.1.18. JASPER is creating lots of lines for out.write statements and giving the following error. When compared to weblogic, the generated code after compiling the page is almost 12 times large. The same code works fine in weblogic. Any suggestions please? Thanks, - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: large class file generated..
Howdy, It's been corrected already, as you'd have seen if you had a version newer than 4.1.18. Yoav Shapira Millennium ChemInformatics -Original Message- From: Amarnath Reddy [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 05, 2003 7:24 AM To: Tomcat Users List Subject: RE: large class file generated.. Tim, Thanks for the suggestions. Infact, you are right about the out.print statements. JASPER is creating new statements for each End Of Line and hence the problem. But weblogic is combining all of them to a sizeable single out.write statement. However I got through the problem by using run-time Jsp Includes and you have suggested this too. thanks. Apache Developers should dig in deep to correct the problem in JASPER itself! Amar. -Original Message- From: Tim Funk [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 05, 2003 5:40 PM To: Tomcat Users List Subject: Re: large class file generated.. Since a JSP is converted to java code, the jsp runs in a method called _jspService (or a very similar name as dicated by the spec). The java language itself has a constraint that no method may be larger than the upper limit you are running into. [I think jasper generates an out.print() for each \n combo instead of combining them. I can't remember...] Anyhoo ... See $TOMCAT_HOME/conf/web.xml to turn on mapped files which (I think) moves that static content to another file. Otherwise, if possible split the file and use jsp:include to include content if possible. It you are using @page include extensively - that would be a problem too since that helps you file to become bloated very quickly. -Tim Amarnath Reddy wrote: BlankHi, Could anyone shed some light on this problem? I'm using Tomcat 4.1.18. JASPER is creating lots of lines for out.write statements and giving the following error. When compared to weblogic, the generated code after compiling the page is almost 12 times large. The same code works fine in weblogic. Any suggestions please? Thanks, - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
