This week's book giveaway is in the Servlets forum.
We're giving away four copies of Murach's Java Servlets and JSP and have Joel Murach on-line!
See this thread for details.
The moose likes Tomcat and the fly likes Tomcat Crashing / Refusal to respond Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Murach's Java Servlets and JSP this week in the Servlets forum!
JavaRanch » Java Forums » Products » Tomcat
Bookmark "Tomcat Crashing / Refusal to respond" Watch "Tomcat Crashing / Refusal to respond" New topic
Author

Tomcat Crashing / Refusal to respond

Sunday Oyeniyi
Greenhorn

Joined: Jul 12, 2005
Posts: 14
I recently deployed a tomcat based helpdesk application that is being used / tested (pilot use) within a division of a very large organization. Total number of users within this division is about one hundred and thirty - (130). The problem I am having now is that sometimes tomcat just stop responding, if you try to open the site it just refuse to come up. I need someone to direct me to how I check what the problem is with Tomcat so that I can correct now before the whole organization starts using it. It will have approximate number of users in the range of 4000 - 5000.

Pls assist very quickly.


Performance is Everything!
William Brogden
Author and all-around good cowpoke
Rancher

Joined: Mar 22, 2000
Posts: 12759
    
    5
Can you get any statistics from the host machine when Tomcat stops responding? Particular interest would be the CPU useage and memory paging activity.

If Tomcat is not responding and the CPU usage is low I would suspect a Thread race condition.

Does your application have to conduct database operations?

Can you monitor Tomcat with the management application to see the memory and thread usage?

Java version, operating system, tomcat version???

Bill
Sunday Oyeniyi
Greenhorn

Joined: Jul 12, 2005
Posts: 14
I am running an MS Windows 2000 Server with Service Pack 4 with 1.5GB RAM on an IBM xSeries 235/8671 Xeo CPU 2.80GHz server. Tomcat version = 5.5.17, JVM = 1.5.0_06_b05, JVM Vendor = Sun Microsystem, OS Version = 5.0, OS Architecture = x86, Currently when tomcat isnot hanging CPU & MEM usage seems excellent CPU averages between 0 - 1% and very occasionally spikes up and down. The Total Paging File Size for all drivers = 2046MB though no paging file size is set for drive E where tomcat is installeld. YES - my system is doing a lot of RDBMS operations on MS SQL 2000. I have checked the Server Status / Complete Server status in tomcat management application but could not decipher / understand how to use it to monitor the threads state and memory utilisation

Please advise me further on how to identify the possible cause of tomcat crash. Sometimes it crash 3 - 4 times within 12 hours and at times no crash at all for the whole day. We're looking at a very high availabilty system
Sivaraman Lakshmanan
Ranch Hand

Joined: Aug 02, 2003
Posts: 231
Hi Sunday,
You say that the application crashes within 2 to 3 hours and sometime no crashes, then I think some part of the application is taking too much of resources. So first thing is try to profile the application for memory. second if there is a database operation see if the queries are giving problems if yes try to tune the frequently running queries. For query monitoring query analyzer in MS SQL 2000 will help you.

Increasing the memory for the jvm will also help.


Regards,
Sivaraman.L
Sunday Oyeniyi
Greenhorn

Joined: Jul 12, 2005
Posts: 14
Tomcat just stop responding a while ago and below is the server status using Tomcat monitoring tool. I was not able to get to the system to check the state of memory & CPU usage but without re-starting it just starts responding again.

Please advise:

JVM
Free memory: 1.09 MB Total memory: 63.56 MB Max memory: 63.56 MB
http-8080
Max threads: 150 Min spare threads: 25 Max spare threads: 75 Current thread count: 150 Current thread busy: 136
Max processing time: 1456560 ms Processing time: 41355.273 s Request count: 20643 Error count: 752 Bytes received: 10.61 MB Bytes sent: 410.87 MB




StageTimeB SentB RecvClientVHostRequest
S1471903 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
S1474153 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
S721038 ms0 KB0 KB10.8.5.17310.100.21.25POST /helpdesk/validatelogon.jsp HTTP/1.1
S1473684 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
S1475731 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
S1473794 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
S667569 ms0 KB0 KB10.8.5.12910.100.21.25GET /helpdesk/selectresp.jsp HTTP/1.1
S1473450 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
S1475075 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
S1474997 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
S738021 ms0 KB0 KB10.8.5.17310.100.21.25POST /helpdesk/validatelogon.jsp HTTP/1.1
S1475699 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
S1475324 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
S1475512 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
S1475966 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
S1475919 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
S2563 ms0 KB0 KB10.100.2.19010.100.21.25GET /manager/status HTTP/1.1
S1475841 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
S1476590 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
S1470559 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
S1469184 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
S1479137 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
R???
R???
S1477668 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
S1478324 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
R???
S1479794 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
S1478653 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
S1478403 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
S555774 ms0 KB0 KB10.100.21.14110.100.21.25GET /helpdesk/selectresp.jsp HTTP/1.1
S1477638 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
R???
S1477513 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
S1477466 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
S684132 ms0 KB0 KB10.100.21.14110.100.21.25GET /helpdesk/reportnewissueextended.jsp HTTP/1.1
S1477388 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
S1477356 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
R???
S1477731 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
S1477699 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
S638742 ms0 KB0 KB10.8.6.2210.100.21.25POST /helpdesk/validatelogon.jsp HTTP/1.1
S1478575 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
S815458 ms0 KB0 KB10.0.146.25010.100.21.25POST /helpdesk/validatelogon.jsp HTTP/1.1
S1478965 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
S1479419 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
R???
S1479809 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
S1480262 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
S1480700 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
S623117 ms0 KB0 KB10.100.21.14110.100.21.25GET /helpdesk/selectresp.jsp HTTP/1.1
S1481168 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
S1480622 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
S1481106 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
S1481512 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
R???
S1481887 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
S574414 ms0 KB0 KB10.100.2.19010.100.21.25POST /helpdesk/validatelogon.jsp HTTP/1.1
S1482778 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
S564993 ms0 KB0 KB10.8.6.8210.100.21.25POST /helpdesk/validatelogon.jsp HTTP/1.1
S1482700 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
S1482669 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
S1482638 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
R???
S1483043 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
S1238735 ms0 KB0 KB10.0.146.25010.100.21.25POST /helpdesk/validatelogon.jsp HTTP/1.1
S1483856 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
S1484324 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
S567336 ms0 KB0 KB10.100.21.14110.100.21.25GET /helpdesk/selectresp.jsp HTTP/1.1
S118358 ms0 KB0 KB10.8.5.9110.100.21.25POST /helpdesk/validatelogon.jsp HTTP/1.1
S1486168 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
S1486153 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
S710882 ms0 KB0 KB10.8.5.17310.100.21.25POST /helpdesk/validatelogon.jsp HTTP/1.1
S1486075 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
R???
S1485044 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
S178279 ms0 KB0 KB10.100.2.19010.100.21.25POST /helpdesk/validatelogon.jsp HTTP/1.1
S1485449 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
S1485418 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
S102030 ms0 KB0 KB10.8.5.5110.100.21.25POST /helpdesk/validatelogon.jsp HTTP/1.1
S1177156 ms0 KB0 KB10.0.146.25010.100.21.25POST /helpdesk/validatelogon.jsp HTTP/1.1
S1485262 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
S742475 ms0 KB0 KB10.8.5.17310.100.21.25POST /helpdesk/validatelogon.jsp HTTP/1.1
S1485637 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
S566430 ms0 KB0 KB10.100.21.14110.100.21.25GET /helpdesk/selectresp.jsp HTTP/1.1
S1485590 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
S1485543 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
S1485512 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
S1485918 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
S1485903 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
R???
S1485434 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
S1484887 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
S1484871 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
S1485309 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
S1485293 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
S1485262 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
S1485653 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
S1485622 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
S1485591 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
S574899 ms0 KB0 KB10.100.2.19010.100.21.25POST /helpdesk/validatelogon.jsp HTTP/1.1
S1485966 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
R???
S1485856 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
S1485840 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
S123139 ms0 KB0 KB10.8.6.6010.100.21.25POST /helpdesk/validatelogon.jsp HTTP/1.1
S1485777 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
S1485231 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
S1485215 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
S1485684 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
S1485653 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
S1486059 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
S1486028 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
S1485981 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
S1485950 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
S1485528 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
R???
S1485606 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
S68421 ms0 KB0 KB10.100.2.19010.100.21.25POST /helpdesk/validatelogon.jsp HTTP/1.1
S1485950 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
S1485919 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
S1485919 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
S1485341 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
S1485294 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
R???
S1485216 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
S1485184 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
S1485138 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
S1485121 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
S1485074 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
S1485528 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
S1485965 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
S1485918 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
S1485903 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
S1486294 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
S1486247 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
S1486699 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
S629226 ms0 KB0 KB10.100.2.19010.100.21.25POST /helpdesk/validatelogon.jsp HTTP/1.1
S1487153 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
S1487543 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
R???
S1487481 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
S1487903 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
S1487871 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
R???
S1488246 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
S1488027 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
S1487965 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
S1488387 ms0 KB0 KB10.8.5.8210.100.21.25POST /helpdesk/reportnewissueextended.jsp HTTP/1.1
R???


P: Parse and prepare request S: Service F: Finishing R: Ready K: Keepalive
jk-8009
Max threads: 200 Min spare threads: 4 Max spare threads: 50 Current thread count: 4 Current thread busy: 1
Max processing time: 0 ms Processing time: 0.0 s Request count: 0 Error count: 0 Bytes received: 0.00 MB Bytes sent: 0.00 MB
StageTimeB SentB RecvClientVHostRequest
P: Parse and prepare request S: Service F: Finishing R: Ready K: Keepalive
________________________________________
William Brogden
Author and all-around good cowpoke
Rancher

Joined: Mar 22, 2000
Posts: 12759
    
    5
YOW! that looks alot like a problem I had one time.

Look at those huge numbers on the request thread running times! zb 1485966ms - 1486 seconds!!!

Something in reportnewissueextended.jsp is hung up waiting for something, maybe a DB connection or a DB query to complete. In my case it was an attempt to connect to a service that was not there anymore. When maxThreads are hung waiting, Tomcat won't respond at all.

You will have to figure out ways to detect these problems and abort request that can't be answered.

Your memory allocation is the default value, WAY too low for your anticipated load in full deployment. Those hung Threads are eating your memory up. There is a lot of tuning you can do - see the Connector element in your server.xml

Bill
Sunday Oyeniyi
Greenhorn

Joined: Jul 12, 2005
Posts: 14
Thanks Bill for the response at least for this particular case I have an idea - I am trying to reduce some RDBMS actvites on the page above.

The problem occured again today and this time around tomcat service went down completely. The error below is what is logged in tomcat's stdout.

java.sql.SQLException: General error
at sun.jdbc.odbc.JdbcOdbc.throwGenericSQLException(Unknown Source)
at sun.jdbc.odbc.JdbcOdbc.SQLFreeEnv(Unknown Source)
at sun.jdbc.odbc.JdbcOdbcDriver.closeConnection(Unknown Source)
at sun.jdbc.odbc.JdbcOdbcConnection.close(Unknown Source)
at com.ubagroup.itcare.General.branchList(General.java:214)
at org.apache.jsp.reportnewissueextended_jsp._jspService(reportnewissueextended_jsp.java:188)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:332)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
at java.lang.Thread.run(Unknown Source)

Please advise further.

1. Kindly direct me on how to increase the memory allocation for tomcat or jvm - I have a whole 1.56GB RAM wasting away.

2. Kindly direct me on the tuning I can do on the connector element in server.xml

Thanks for anticipated response.
William Brogden
Author and all-around good cowpoke
Rancher

Joined: Mar 22, 2000
Posts: 12759
    
    5
1. Kindly direct me on how to increase the memory allocation for tomcat or jvm - I have a whole 1.56GB RAM wasting away.

2. Kindly direct me on the tuning I can do on the connector element in server.xml


1. If you run Tomcat from a command prompt (not as a service) you can control the command line parameters that Java uses to run Tomcat with the JAVA_OPTS environment variable set in catalina.bat. Here is what I use to start with 64mb and use 100mb as a maximum:

See your Java installation tooldocs for use of command line variables affecting memory and lots of other stuff.

2. There are a lot of helpful comments embedded in server.xml and the attribute names are self-explanatory but I have not found any convenient explanation of the effect they have on performance. I run with the default settings which appear to be for a low load server. Perhaps a forum reader who configures for high load can help here.

You might try starting with this tomcat documentation. Pick the HTTP connector link to get a useful discussion of settings.

I found the Wrox book "Professional Apache Tomcat 5" to be very helpful.

Bill
[ November 22, 2006: Message edited by: William Brogden ]
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Tomcat Crashing / Refusal to respond
 
Similar Threads
Javamail - Invalid Address Problem
Need Help with FORM Based Authentication
jQuery event handlers
Tomcat unexpectedly shutdown
Apache Tomcat/4.0.6 - HTTP Status 500 - Internal Server Error