Tomcat jsp exception
Hello, I developed my application with Tomcat 4.0.3/Java 1.3. Now I moved to Tomcat 4.1.24/Java 1.4.1. On my first JSP I get an exception that doesn't tell me what's wrong going on. It is referring to one of my classes that is not even used in that particular JSP. Can anyone suggest where to start to fix this problem. I tried to compile it in many ways. The problem is that the exception that comes from JSP isn't informative enough. My project is compiled into a *.jar. This *.jar is put into the ./tomcat/webapps/cdk/WEB-INF/lib directory. exception org.apache.jasper.JasperException: lt/ktu/distance/sql/helpers/CountryManagerHelper ... root cause javax.servlet.ServletException: lt/ktu/distance/sql/helpers/CountryManagerHelper ... Thanks, -- Kaunas Regional Distance Education Center Programmer Phone: +370 674 05232 WWW: http://distance.ktu.lt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat jsp exception
> Further done in the trace, there should be a "root-cause". Including this > will help greatly in getting help for your particular problem. In my previous message I didn't want to paste all the long exception that I get. This time I'll post the ROOT CAUSE. Unfortunately, it doesn't tell me what's wrong. The error comes from tomcat4 inside. I hope someone can help me with that: root cause javax.servlet.ServletException: lt/ktu/distance/sql/helpers/CountryManagerHelper at org.apache.jasper.runtime.PageContextImpl.handlePageException(PageContextImpl.java:536) at org.apache.jsp.index_jsp._jspService(index_jsp.java:205) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:137) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:210) 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 org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:256) 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.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:171) 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.coyote.http11.Http11Processor.process(Http11Processor.java:594) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:392) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:565) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:619) at java.lang.Thread.run(Thread.java:536) > > "Mindaugas Genutis" <[EMAIL PROTECTED]> wrote in message > news:[EMAIL PROTECTED] > > > > Hello, > > > > I developed my application with Tomcat 4.0.3/Java 1.3. Now I moved to > > Tomcat 4.1.24/Java 1.4.1. > > > > On my first JSP I get an exception that doesn't tell me what's wrong going > > on. It is referring to one of my classes that is not even used in that > > particular JSP. > > > > Can anyone suggest where to start to fix this problem. I tried to compile > > it in many ways. The problem is that the exception that comes from JSP > > isn't informative enough. > > > > My project is compiled into a *.jar. This *.jar is put into the > > ./tomcat/webapps/cdk/WEB-INF/lib directory. > > > > exception > > > > org.apache.jasper.JasperException: > > lt/ktu/distance/sql/helpers/CountryManagerHelper > > ... > > > > root cause > >
IOException: failed to communicate with MySQL
Hello, My JSP application very often after night, in the morning stops communicating with MySQL database. I get an exception each morning (the exception body goes below). The application starts to work again after I restart it from the Tomcat Manager. Maybe someone else also had this same problem? My server configuration: Linux Redhat, Tomcat 4.1.24, Java 1.4.1. My assumptions where the problem might be: the MySQL connections are "eaten" by another application or they are "eaten" by my application somewhere inside and never closed. Or maybe during the night when no one is working with my application it somehow "frozes"? Can anyone give me a clue how to start debugging these early morning crashes? Another clue: Connections to the database are made through an SQLManager which is a class written by another programmer. The class is a singleton. Could it be that I have to reset it more often? The exception body goes here: java.sql.SQLException: Communication link failure: java.io.IOException at com.mysql.jdbc.MysqlIO.clearAllReceive(Unknown Source) at com.mysql.jdbc.MysqlIO.sqlQueryDirect(Unknown Source) at com.mysql.jdbc.MysqlIO.sqlQuery(Unknown Source) at com.mysql.jdbc.Connection.execSQL(Unknown Source) at com.mysql.jdbc.Connection.execSQL(Unknown Source) at com.mysql.jdbc.Statement.executeQuery(Unknown Source) at com.mysql.jdbc.jdbc2.Statement.executeQuery(Unknown Source) at lt.ktu.distance.sql.mysql.MySQLGUILanguageManagerHelper.loadGUILanguages(MySQLGUILanguageManagerHelper.java:48) at lt.ktu.distance.sql.GUILanguageManager.loadGUILanguages(GUILanguageManager.java:55) at org.apache.jsp.index_jsp._jspService(index_jsp.java:155) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:137) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:210) 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 org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:256) 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.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:171) 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.coyote.http11.Http11Processor.process(Http11Processor.java:594) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:392) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:565) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:619) at java.lang.Th
RE: IOException: failed to communicate with MySQL
> a couple of days ago a post went by talking about MySQL default timeout > being set to 8 hrs for connections... betting this might be your problem... Thanks for pointing this out. I've read the thread "Tomcat problems every morning". However, no solution was suggested in that thread. One can assume the solution implicitly: increase default MySQL timeout from 8 hours to say 48 hours. However, if my application stays idle for 48 hours during holidays, it will disconnect after that. Does anyone else have a suggestion on how to improve on this? > Hello, > > My JSP application very often after night, in the morning stops > communicating with MySQL database. I get an exception each morning (the > exception body goes below). The application starts to work again after I > restart it from the Tomcat Manager. > > Maybe someone else also had this same problem? My server configuration: > Linux Redhat, Tomcat 4.1.24, Java 1.4.1. > > My assumptions where the problem might be: the MySQL connections are > "eaten" by another application or they are "eaten" by my application > somewhere inside and never closed. Or maybe during the night when no one > is working with my application it somehow "frozes"? Can anyone give me a > clue how to start debugging these early morning crashes? > > Another clue: Connections to the database are made through an SQLManager > which is a class written by another programmer. The class is a singleton. > Could it be that I have to reset it more often? -- Kaunas Regional Distance Education Center Programmer Phone: +370 674 05232 WWW: http://distance.ktu.lt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
java.net.SocketException: Connection reset
Hello, I am getting the java.net.SocketException and my JSP application crashes. I have pasted the exception below. It comes from the catalina sockets engine. Does anyone have an idea where should I go further for fixing this socket problem? My server configuration: Redhat Linux, Tomcat 4.1.24, Java 1.4.1 2003-06-09 12:24:38 StandardWrapperValve[default]: Servlet.service() for servlet default threw exception java.net.SocketException: Connection reset at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:96) at java.net.SocketOutputStream.write(SocketOutputStream.java:136) at org.apache.coyote.http11.InternalOutputBuffer$OutputStreamOutputBuffer.doWrite(InternalOutputBuffer.java:668) at org.apache.coyote.http11.filters.IdentityOutputFilter.doWrite(IdentityOutputFilter.java:160) at org.apache.coyote.http11.InternalOutputBuffer.doWrite(InternalOutputBuffer.java:523) at org.apache.coyote.Response.doWrite(Response.java:524) at org.apache.coyote.tomcat4.OutputBuffer.realWriteBytes(OutputBuffer.java:384) at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:439) at org.apache.tomcat.util.buf.ByteChunk.append(ByteChunk.java:359) at org.apache.coyote.tomcat4.OutputBuffer.writeBytes(OutputBuffer.java:411) at org.apache.coyote.tomcat4.OutputBuffer.write(OutputBuffer.java:398) at org.apache.coyote.tomcat4.CoyoteOutputStream.write(CoyoteOutputStream.java:110) at org.apache.catalina.servlets.DefaultServlet.copyRange(DefaultServlet.java:1996) at org.apache.catalina.servlets.DefaultServlet.copy(DefaultServlet.java:1745) at org.apache.catalina.servlets.DefaultServlet.serveResource(DefaultServlet.java:1073) at org.apache.catalina.servlets.DefaultServlet.doGet(DefaultServlet.java:506) at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) 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:256) 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.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:171) 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.coyote.http11.Http11Processor.process(Http11Processor.java:594) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:392) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:565) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:619) at java.lang.Thread.run(Thread.java:536) Thanks, -- Kaunas Regional Distance Education Center Programmer Phone: +370 674 05232 WWW: http://distance.ktu.lt - To uns
Tomcat application performance & load
Hello, I have a JSP application that is lagging once in a while on the server. How could I profile or look at the performance of my application? For instance, how much network and machine load my JSP files induce. Thanks, -- Kaunas Regional Distance Education Center Programmer Phone: +370 674 05232 WWW: http://distance.ktu.lt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Tomcat hangs
Hello, Our Tomcat hangs once in a few days. When the load is larger, sometimes it hangs even a few times a day. Our system configuration is: Tomcat 4.1.24 JVM 1.4.2 Linux Redhat 2 GB RAM We have deployed a big JSP application on our Tomcat. Mostly it does database (MySQL) / XML processing. When Tomcat hangs, we can't stop it with the stop script. We need to 'kill' or even 'kill - 9' it. Can someone please suggest where should I start the research. Look for bugs in the JSPs, configure memory usage etc? Thanks, -- Kaunas Regional Distance Education Center Programmer Phone: +370 674 05232 WWW: http://distance.ktu.lt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Tomcat maximum heap size on Linux
I wanted to increase Tomcat's maximum heap size. I did it by putting the following string in the catalina.sh file (I'm running RedHat Linux): CATALINA_OPTS="-Djava.awt.headless=true -Xmx1024m" So, Tomcat can use 1Gb of my RAM. However, I'm observing Tomcat's usage with "top" under Linux and it stops growing at 150Mb. Looks like this option doesn't work. Where else could I increase it? I'm using JDK 1.4.2, Tomcat 4.1.24 -- Kaunas Regional Distance Education Center Programmer Phone: +370 674 05232 WWW: http://distance.ktu.lt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Tomcat maximum heap size on Linux
I expect to use it a few hundred Megabytes. It was quickly increasing in my eyes and stopped on 150Mb. Looks like its the system roof. Could it be so? > Howdy, > If it doesn't need more than 150MB, it won't use more than 150MB... Are > you blindly playing around with heap numbers, or did you actually > determine 1GB was required to handle your max expected load? > > Yoav Shapira > Millennium ChemInformatics > > > >-----Original Message- > >From: Mindaugas Genutis [mailto:[EMAIL PROTECTED] > >Sent: Wednesday, January 07, 2004 2:37 PM > >To: Tomcat Users List > >Subject: Tomcat maximum heap size on Linux > > > > > >I wanted to increase Tomcat's maximum heap size. I did it by putting > the > >following string in the catalina.sh file (I'm running RedHat Linux): > > > >CATALINA_OPTS="-Djava.awt.headless=true -Xmx1024m" > > > >So, Tomcat can use 1Gb of my RAM. > > > >However, I'm observing Tomcat's usage with "top" under Linux and it > stops > >growing at 150Mb. > > > >Looks like this option doesn't work. Where else could I increase it? > > > >I'm using JDK 1.4.2, Tomcat 4.1.24 > > > >-- > >Kaunas Regional Distance Education Center > >Programmer > >Phone: +370 674 05232 > >WWW: http://distance.ktu.lt > > > > > > > >- > >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] > > -- Kaunas Regional Distance Education Center Programmer Phone: +370 674 05232 WWW: http://distance.ktu.lt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
