commons-fileupload memory problem
I am trying to use the commons-fileupload classes and cannot figure out how to keep my uploads from getting stored in memory. I am using the following methods: DefaultFileItemFactory fileItemFactory = new DefaultFileItemFactory( 10, new File(/tmp) ); DiskFileUpload upload = new DiskFileUpload( fileItemFactory ); When I run tomcat using JDK 1.5's jconsole program and upload a file, my memory usage jumps to about 10x the size of the attachment. Has anyone else used the library successfully? TIA. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: commons-fileupload memory problem
-Original Message- From: Elihu Smails I am trying to use the commons-fileupload classes and cannot figure out how to keep my uploads from getting stored in memory. I am using the following methods: DefaultFileItemFactory fileItemFactory = new DefaultFileItemFactory( 10, new File(/tmp) ); DiskFileUpload upload = new DiskFileUpload( fileItemFactory ); When I run tomcat using JDK 1.5's jconsole program and upload a file, my memory usage jumps to about 10x the size of the attachment. Has anyone else used the library successfully? Yes, very little problem once I got the hang of it. regards DaveP - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RES: commons-fileupload memory problem
We had the same problem and after debugging a few commons-fileupload classes (and Struts RequestProcessor) we could find that 250-500K of RAM was being used per request property (in multipart form, an object is created for each form field!). Since our form had the FormFile field plus 35 ordinary others...our request was consuming 20MB! We don't know the reason yet...so we had to isolate the FormFile field in a separated web-page...maybe we could use two form in the same page with the same result. Paulo Alvim Powerlogic - Brazil -Mensagem original- De: Elihu Smails [mailto:[EMAIL PROTECTED] Enviada em: quinta-feira, 24 de março de 2005 10:40 Para: Tomcat Users List Assunto: commons-fileupload memory problem I am trying to use the commons-fileupload classes and cannot figure out how to keep my uploads from getting stored in memory. I am using the following methods: DefaultFileItemFactory fileItemFactory = new DefaultFileItemFactory( 10, new File(/tmp) ); DiskFileUpload upload = new DiskFileUpload( fileItemFactory ); When I run tomcat using JDK 1.5's jconsole program and upload a file, my memory usage jumps to about 10x the size of the attachment. Has anyone else used the library successfully? TIA. - 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]
Memory Problem
I am using apache FOP to create some PDFs. I am facing OutOfMemory problem specially for Chinese PDFs. I understand that I can increase JVM memory. I tried to change the catalina.bat and inserted following line JAVA_OPTS = -Xmx512M First of all i am not sure whether above is correct or not (problem remains still same). Any idea ? exactly how i can increase the memory? and in what way i can check that i am really getting that much memory ? regards manisha - Do you Yahoo!? Yahoo! Mail - 250MB free storage. Do more. Manage less.
memory problem?
We often have to restart Tomcat because of an ODBC issue (yes, we're switching databases as soon as we can). However, I've noticed this error occuring in the Windows 2000 Event Log in association with Apache Tomcat: The CreateThread function failed for the following reason: Not enough storage is available to process this command. . It can show up a few times per day, or only every once in a while. From what I can tell by Googling around, this error message might actually have to do with us running out of system memory! However, I'm not certain, so I'm wondering if this means that Tomcat/JVM is running out of memory, or Windows is (in which case Tomcat would too, of course). In either case, does does this mean we need to move to clustering or whatever? The machine has about 3GB of RAM and the JVM gets half of that allocated to it. Thanks for any advice, Stephen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: strange memory problem
Hi, That's a good theory. Another question is are you compiling JSPs frequently at runtime? Yoav Shapira Millennium Research Informatics -Original Message- From: Joseph Shraibman [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 12, 2004 12:17 AM To: Tomcat Users List Subject: Re: strange memory problem java.lang.OutOfMemoryError is also thrown when java can't start up a thread because it reached the system limit. Could that be your problem? - 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]
strange memory problem
I try to run several instances of a large web application in one Tomcat. My JAVA_OPTS shell variable is set to -Xmx700m -Xms700m and the web application also reports that 700 MByte RAM are available, and maybe 180 MByte in use. After a few hours I got the java.lang.OutOfMemoryError in catalina.out. At this point the java processes are no larger than maybe 400 - 450 MByte. There is plenty of RAM left (the server has 1 GByte). The free memory as reported by the web application or Tomcat is nowhere tight, although it is difficult to pick a point of time right before the crash. I tried this with Tomcat 4.1.30 and 5.0.19. Java is j2sdk1.4.2_04. System is Linux 2.4.26 patched with grsecurity. Any help is really appreciated. Mit schönen Grüßen von Yahoo! Mail - http://mail.yahoo.de - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: strange memory problem
java.lang.OutOfMemoryError is also thrown when java can't start up a thread because it reached the system limit. Could that be your problem? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Memory problem with tomcat 4130
How knows how do i make to resolve this problem, is necesary to recompile the default kernel of linux redhat 9.0 and what flag must i to select. thanks? Software wrote: Hi, i've installed tomcat 4130 in my linux redhat 9.0 with the default kernel and j2sdk1.4.0 in a server with 1 GB RAM and 2.4Ghz Processor The problem is when i start the tomcat it start to consume the memory progressively and i don't have running any application in this moment, then i have to restart the tomcat again to get memory free. What can be wrong. Fabian - 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: Memory problem with tomcat 4130
Fabian, I am not sure if I have the answer to your memory problem but let me give you some information to get more help from others. 1. Where are you looking to see this memory use? 2. Does Tomcat stop responding? 3. Have you loaded any of your applications? No 4. Are you using a database? 5. What JDK version are you running? 1.4.0 6. Have you made any changes to the original configuration?(Server.xml, etc) 7. How are you starting Tomcat? 8. What options did you set?(Such as memory -Xmx128m) 9. Have you read the FAQ on memory? http://jakarta.apache.org/tomcat/faq/memory.html If you will answer as many of these as possible it will help in evaluating your problem. Doug www.parsonstechnical.com - Original Message - From: Software [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Sent: Friday, April 23, 2004 8:13 AM Subject: Re: Memory problem with tomcat 4130 How knows how do i make to resolve this problem, is necesary to recompile the default kernel of linux redhat 9.0 and what flag must i to select. thanks? Software wrote: Hi, i've installed tomcat 4130 in my linux redhat 9.0 with the default kernel and j2sdk1.4.0 in a server with 1 GB RAM and 2.4Ghz Processor The problem is when i start the tomcat it start to consume the memory progressively and i don't have running any application in this moment, then i have to restart the tomcat again to get memory free. What can be wrong. Fabian - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Memory problem with tomcat 4130
Hi 1. I'm using the top command to get information about the memory Mem: 1030392k av, 707688k used, 322704k free, 0k shrd, 118096k buff 354852k actv, 136300k in_d,1676k in_c Swap: 2048248k av,2832k used, 2045416k free 434288k cached If you see the server has 1 GB the memory RAM with minimal instalation of redhat, its installation start using about 70 MB of the memory, then when i've installed tomcat without any application the memory it was consume. 2. Yes i can to start annd stop de tomcat without any problem. 3. Yes i prove using a application to connect to the database, the procesor cosume about 99.9% then it leave the use of the procesos and all is normal but the memory process start to uses the memory progressive. 4. Yes our System Engineers using connections to Oracle database by network in our LAN. 5. I'm using j2sdk1.4.0 6. Yes i've modified this parameters in catalina.sh JAVA_HOME=/usr/java/j2sdk1.4.0 ; export JAVA_HOME CATALINA_HOME=/usr/local/tomcat4130 ; export CATALINA_HOME GCOPSIZE=5 JAVA_PARAMS=-DGCOPSIZE=%GCOPSIZE and i've modified the server.xml to redirect the locations of our application to this partition !-- Define the default virtual host -- Host name=localhost debug=0 appBase=/rootweb/appsweb/ unpackWARs=true autoDeploy=true 7. I've started the tomcat firts with this parameters JAVA_HOME=/usr/java/j2sdk1.4.0 ; export JAVA_HOME CATALINA_HOME=/usr/local/tomcat4130 ; export CATALINA_HOME JAVA_OPTS=-server -Xms128m -Xmx256m -Xrs CATALINA_OPTS=-server -Xms128m -Xmx256m -Xrs the -Xms128, -Xmx, -Server, -Xrs options and always happens the same. . Thanks for you help Parsons Technical Services wrote: Fabian, I am not sure if I have the answer to your memory problem but let me give you some information to get more help from others. 1. Where are you looking to see this memory use? 2. Does Tomcat stop responding? 3. Have you loaded any of your applications? No 4. Are you using a database? 5. What JDK version are you running? 1.4.0 6. Have you made any changes to the original configuration?(Server.xml, etc) 7. How are you starting Tomcat? 8. What options did you set?(Such as memory -Xmx128m) 9. Have you read the FAQ on memory? http://jakarta.apache.org/tomcat/faq/memory.html If you will answer as many of these as possible it will help in evaluating your problem. Doug www.parsonstechnical.com - Original Message - From: Software [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Sent: Friday, April 23, 2004 8:13 AM Subject: Re: Memory problem with tomcat 4130 How knows how do i make to resolve this problem, is necesary to recompile the default kernel of linux redhat 9.0 and what flag must i to select. thanks? Software wrote: Hi, i've installed tomcat 4130 in my linux redhat 9.0 with the default kernel and j2sdk1.4.0 in a server with 1 GB RAM and 2.4Ghz Processor The problem is when i start the tomcat it start to consume the memory progressively and i don't have running any application in this moment, then i have to restart the tomcat again to get memory free. What can be wrong. Fabian - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Memory problem with tomcat 4130
Hi, i've installed tomcat 4130 in my linux redhat 9.0 with the default kernel and j2sdk1.4.0 in a server with 1 GB RAM and 2.4Ghz Processor The problem is when i start the tomcat it start to consume the memory progressively and i don't have running any application in this moment, then i have to restart the tomcat again to get memory free. What can be wrong. Fabian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Odd Memory Problem
I have been battling a memory problem for a few months now with no luck. I have used profilers and everything else you could imagine. The problem is we have never been able to duplicate it on the testing servers it only happens on production which does not see much load at all (100 users a day). I noticed something very odd yesterday though. I am using the -XX:+UseConcMarkSweepGC and -Xms512m. I was monitoring the garbage collection activity very closely and I was receiving good performance for 3 days. I was seeing one garbage collection about every 5 minutes in the Catalina.out. Then out of nowhere the garbage collection starting going crazy, about one garbage collection a second, I checked the cpu usage and it was stuck around 60% used. There were only 2-4 people logged in at a time. The crazy garbage collection went on for a couple of hours before it eventually crapped out with Out of Memory errors. It almost seems like a section of the app caused this sudden outburst but there is no way our QA department hasn't went over the same section. I was hoping some one seen or heard of this before. Below is my environment. Thanks, Apache2.0.47 using mod_jk2 2 * tomcat4.1.24 J2sdk1.4.2_04
RE: Odd Memory Problem
Hi, As you say, it's unfortunate you can't reproduce this on a test server. What if you setup a test server and let JMeter pound at it for a few days? Is there something in your application, e.g. a user action, that would trigger an infinite loop or infinite recursion? That would cause that behavior you've described. And it would only take one user doing it one time, i.e. a very light load, to produce this problem. You'd have to carefully scrutinize your code... Yoav Shapira Millennium Research Informatics -Original Message- From: Rob Wichterman [mailto:[EMAIL PROTECTED] Sent: Friday, April 02, 2004 11:17 AM To: [EMAIL PROTECTED] Subject: Odd Memory Problem I have been battling a memory problem for a few months now with no luck. I have used profilers and everything else you could imagine. The problem is we have never been able to duplicate it on the testing servers it only happens on production which does not see much load at all (100 users a day). I noticed something very odd yesterday though. I am using the -XX:+UseConcMarkSweepGC and -Xms512m. I was monitoring the garbage collection activity very closely and I was receiving good performance for 3 days. I was seeing one garbage collection about every 5 minutes in the Catalina.out. Then out of nowhere the garbage collection starting going crazy, about one garbage collection a second, I checked the cpu usage and it was stuck around 60% used. There were only 2-4 people logged in at a time. The crazy garbage collection went on for a couple of hours before it eventually crapped out with Out of Memory errors. It almost seems like a section of the app caused this sudden outburst but there is no way our QA department hasn't went over the same section. I was hoping some one seen or heard of this before. Below is my environment. Thanks, Apache2.0.47 using mod_jk2 2 * tomcat4.1.24 J2sdk1.4.2_04 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]
Re: apache + 2 tomcat cluster memory problem
Thanks Filip. I only found the thread of mails starting March 17 with the title Horrible memory leak in tomcat 5.0.19 If this is indeed the mails you advised me to look at, here is what I found out: Our setup differs in a way that we are using mod_jk 1.2.5 instead of 2.0.2. So mod_jk 1.2.5 + Tomcat 5.0.19 has a memory leak problem as well. This suggests that maybe the problem is with Tomcat 5.0.19 (?) Appearantly someone else (Robert Kruger) had exactly the same problem and it was solved when they downgraded to Tomcat 5.0.18. We cannot do that either because of a bug fix regarding session states in 5.0.18. I don't mind using mod_jk 2.0.2 as long as it solves our problem; however there already seems to be a memory leak with the mod_jk 2.0.2 + tomcat 5.0.19 combination as well. In Robert's email, he predicts that maybe the problem is related to JMX registration issue described in http://www.mail-archive.com/[EMAIL PROTECTED]/ msg53035.html. I'll reply to his email to see if it was indeed the problem. What's the next step? Thanks, Asim On Mar 28, 2004, at 12:39 AM, Filip Hanik ((lists)) wrote: there was an earlier email about a mem leak in the connector for mod_jk, please go through the last weeks emails and let us know what you find out. Filip -Original Message- From: Asim Alp [mailto:[EMAIL PROTECTED] Sent: Saturday, March 27, 2004 7:55 PM To: Tomcat Users List Subject: apache + 2 tomcat cluster memory problem Hello everyone, I have 2 Tomcats (both 5.0.19) running on two separate machines. One machine also has Apache 2.0.49 installed on it for load balancing. Apache communicates with tomcat1 thru port 11005 and tomcat2 thru 12005. tomcat1 and Apache are on the same machine. Apache is set to forward /* to the load balancer (and then to Tomcats). We have over a hundred virtual hosts on our tomcats, so we don't want to worry about configuring Apache virtual hosts to serve the images and all the other files (that's why we forward /*, not just /*.jsp and /servlet/*). Both tomcats also have their http connector ports listening to port 8080 on their individual machines. We're using mod_jk_1.2.5_2.0.47.dll for Apache to Tomcat communication... Both our tomcats are running with the -Xms128m -Xmx256m options. With this configuration everything works perfect for about an hour, then our tomcats run out of memory... When we turn off clustering, and run a single Tomcat on port 80 (of course by shutting down Apache Httpd), we don't have any memory problems at all (for now, we're planning to use clustering to avoid down time, one server is actually enough to handle all the traffic). Does anyone have any idea why we'd run out of memory when our tomcats are talking to Apache through mod_jk? Thanks, Asim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --- Incoming mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.614 / Virus Database: 393 - Release Date: 3/5/2004 --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.614 / Virus Database: 393 - Release Date: 3/5/2004 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
apache + 2 tomcat cluster memory problem
Hello everyone, I have 2 Tomcats (both 5.0.19) running on two separate machines. One machine also has Apache 2.0.49 installed on it for load balancing. Apache communicates with tomcat1 thru port 11005 and tomcat2 thru 12005. tomcat1 and Apache are on the same machine. Apache is set to forward /* to the load balancer (and then to Tomcats). We have over a hundred virtual hosts on our tomcats, so we don't want to worry about configuring Apache virtual hosts to serve the images and all the other files (that's why we forward /*, not just /*.jsp and /servlet/*). Both tomcats also have their http connector ports listening to port 8080 on their individual machines. We're using mod_jk_1.2.5_2.0.47.dll for Apache to Tomcat communication... Both our tomcats are running with the -Xms128m -Xmx256m options. With this configuration everything works perfect for about an hour, then our tomcats run out of memory... When we turn off clustering, and run a single Tomcat on port 80 (of course by shutting down Apache Httpd), we don't have any memory problems at all (for now, we're planning to use clustering to avoid down time, one server is actually enough to handle all the traffic). Does anyone have any idea why we'd run out of memory when our tomcats are talking to Apache through mod_jk? Thanks, Asim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: apache + 2 tomcat cluster memory problem
there was an earlier email about a mem leak in the connector for mod_jk, please go through the last weeks emails and let us know what you find out. Filip -Original Message- From: Asim Alp [mailto:[EMAIL PROTECTED] Sent: Saturday, March 27, 2004 7:55 PM To: Tomcat Users List Subject: apache + 2 tomcat cluster memory problem Hello everyone, I have 2 Tomcats (both 5.0.19) running on two separate machines. One machine also has Apache 2.0.49 installed on it for load balancing. Apache communicates with tomcat1 thru port 11005 and tomcat2 thru 12005. tomcat1 and Apache are on the same machine. Apache is set to forward /* to the load balancer (and then to Tomcats). We have over a hundred virtual hosts on our tomcats, so we don't want to worry about configuring Apache virtual hosts to serve the images and all the other files (that's why we forward /*, not just /*.jsp and /servlet/*). Both tomcats also have their http connector ports listening to port 8080 on their individual machines. We're using mod_jk_1.2.5_2.0.47.dll for Apache to Tomcat communication... Both our tomcats are running with the -Xms128m -Xmx256m options. With this configuration everything works perfect for about an hour, then our tomcats run out of memory... When we turn off clustering, and run a single Tomcat on port 80 (of course by shutting down Apache Httpd), we don't have any memory problems at all (for now, we're planning to use clustering to avoid down time, one server is actually enough to handle all the traffic). Does anyone have any idea why we'd run out of memory when our tomcats are talking to Apache through mod_jk? Thanks, Asim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --- Incoming mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.614 / Virus Database: 393 - Release Date: 3/5/2004 --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.614 / Virus Database: 393 - Release Date: 3/5/2004 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: reclaiming memory problem PS
Jerald (or is it Gerald -- your email address and 'name' don't match), Now sessionStatus is getting caught fine, but when I try and redirect to a JSP after that, nothing happens. I originally tried mapping.findForward (Struts), response.sendRedirect and forwarding using RequestDispatcher. I have tried getSession(true) and false. What implications (if any) does session timeout have in terms of forwarding after the session is invalidated? Session state should have nothing to do with your ability to forward, etc. Can you post thesnippet of code where you try to redirect the user? -chris signature.asc Description: OpenPGP digital signature
Re: reclaiming memory problem PS
Hi, Its Gerald (long dull story), but you can call me anything you like. I can now say with some surety, that the forward is not the problem. In a Struts action, the null session is being picked up and the mapping.findForward(a_file.jsp); (a Struts forward method) is forwarding on to the specified resource. Great youd think. But no. It seems to forward to the specified resource (execution is being logged, System.out.println(some text); is written to the console etc), but in the client, nothing happens, regardless of which method is used to forward. Just the broken original app remains. I have forwarded to a simple JSP, which again logs that its being executed. But again nothing is loaded in to the browser. Do you have any ideas, as I am fast running out of them. I will consult the Struts list, but am yet unsure it is a Struts issue/question. Many thanks Gerald. Jerald (or is it Gerald -- your email address and 'name' don't match), Now sessionStatus is getting caught fine, but when I try and redirect to a JSP after that, nothing happens. I originally tried mapping.findForward (Struts), response.sendRedirect and forwarding using RequestDispatcher. I have tried getSession(true) and false. What implications (if any) does session timeout have in terms of forwarding after the session is invalidated? Session state should have nothing to do with your ability to forward, etc. Can you post thesnippet of code where you try to redirect the user? -chris ATTACHMENT part 2 application/pgp-signature name=signature.asc - Yahoo! Messenger - Communicate instantly...Ping your friends today! Download Messenger Now
Re: reclaiming memory problem PS
Jerald, session.setMaxInactiveTimeout(-1); Yeah, this is a bad idea. The session will never go away by itself. This *requires* the user to press a logout button, and for you to explicitly call session.invalidate(). Users frequently do not log themselves out, and their sessions will never die. You will eventually run out of memory. If you need a long timeout, just make it really long (like a couple of hours). There's usually no good reason to make it -1. PS is the session time out linked wirth inactivity? My session attribute only persists as long as I am using the app. That's exactly how the 'inactive' timeout works. -chris signature.asc Description: OpenPGP digital signature
Re: reclaiming memory problem PS
Hello, and thank you for that,
Yes, I am timing the session out and trying to handle the result. I have:
HttpSession objSession = request.getSession(true);
String sessionStatus = (String) objSession.getAttribute(sessionStatus);
if (sessionStatus == null) {
forward off to JSP
}
Now sessionStatus is getting caught fine, but when I try and redirect to a JSP after
that, nothing happens. I originally tried mapping.findForward (Struts),
response.sendRedirect and forwarding using RequestDispatcher. I have tried
getSession(true) and false. What implications (if any) does session timeout have in
terms of forwarding after the session is invalidated?
Many thanks
G.
Jerald,
session.setMaxInactiveTimeout(-1);
Yeah, this is a bad idea. The session will never go away by itself. This
*requires* the user to press a logout button, and for you to explicitly
call session.invalidate(). Users frequently do not log themselves out,
and their sessions will never die. You will eventually run out of memory.
If you need a long timeout, just make it really long (like a couple of
hours). There's usually no good reason to make it -1.
PS is the session time out linked wirth inactivity? My session
attribute only persists as long as I am using the app.
That's exactly how the 'inactive' timeout works.
-chris
ATTACHMENT part 2 application/pgp-signature name=signature.asc
-
Yahoo! Messenger - Communicate instantly...Ping your friends today! Download
Messenger Now
Re: reclaiming memory problem
Hello and thank you for that (all),
Originally,
request.getSession().setMaxInactiveInterval(-1);
was set. After some deliberation (not a lot), I opted for setting the session to time
out, defined in web.xml:
session-config
session-timeout1/session-timeout
/session-config
After defining the above, setting a value in the session, restarting TC, and running
my app, why does it continue to persist well after the session-timeout has elapsed?
When the session is timed out, is the current session invalidated and a new one
created? Hence all fields set in the original should be null? (the true attribute
(below) persists well past one minute)
Thanks again
G.
Code:
(servlet)
request.getSession().setAttribute(sessionStatus, true);
(JSP)
String sessionStatus = (String) request.getSession().getAttribute(sessionStatus);
out.println(alert('sessionStatus: + sessionStatus + '););
1. Reduce the session timeout.
2. Store less stuff in the session so that it's not such a memory drain.
3. Beg your customers to logout before leaving your app. ;)
-
Yahoo! Messenger - Communicate instantly...Ping your friends today! Download
Messenger Now
Re: reclaiming memory problem PS
PS is the session time out linked wirth inactivity? My session attribute only persists as long as I am using the app. G. - Yahoo! Messenger - Communicate instantly...Ping your friends today! Download Messenger Now
Re: reclaiming memory problem
Follow Sun's rules of garbage collection and all will be OK. Your session objects might have a reference to something that isn't letting the GC do its job. (I think) Profilers are good at find this kind of stuff. -Tim Jerald Powel wrote: Hello, How might I reclaim memory, e.g after a session expires when a client browser is closed down? Predicament: as I open up new client windows, the memory (viewed in Windows task manager) creeps up with each new window opened. The app that is loaded creates a session and stores various objects on it. But, when I close down a client window, the memory consumption remains at it's peak (and climbs with each successive new client opened) In other words, memory consumption increments but never decrements, necessitating a server bounce at unacceptable frequency. Why are the resources not being reclaimed, and how might I gently encourage resource reclamation? I fear System.gc() is not the answer here. Many thanks all for all input G. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: reclaiming memory problem
G, But, when I close down a client window, the memory consumption remains at it's peak (and climbs with each successive new client opened) In other words, memory consumption increments but never decrements, necessitating a server bounce at unacceptable frequency. What is your definition of 'never'? Java cannot immediately reclaim the memory used by that user's sesson if the user closes the browser. Tomcat doesn't know that the client has closed their browser. It must wait until the session times out (30 minutes, I think) before the session can be cleaned up automatically. Solutions? 1. Reduce the session timeout. 2. Store less stuff in the session so that it's not such a memory drain. 3. Beg your customers to logout before leaving your app. ;) Why are the resources not being reclaimed, and how might I gently encourage resource reclamation? I fear System.gc() is not the answer here. System.gc only tells the GC 'now might be a convenient time to run the GC'. Other than that, it's not much good. -chris signature.asc Description: OpenPGP digital signature
RE: reclaiming memory problem
Hola, But, when I close down a client window, the memory consumption remains at it's peak (and climbs with each successive new client opened) In other words, memory consumption increments but never decrements, necessitating a server bounce at unacceptable frequency. What is your definition of 'never'? Java cannot immediately reclaim the memory used by that user's sesson if the user closes the browser. Tomcat doesn't know that the client has closed their browser. It must wait until the session times out (30 minutes, I think) before the session can be cleaned up automatically. Solutions? 30 minutes is the default session timeout, yes. But your first question to the original poster, i.e. the definition of 'never', is a very good question. Remember that the JVM heap size grows monotonically. For example, if you need 50MB at some point and the JVM can allocate that, it will. Then sessions timeout and you only need 30MB, so the JVM will garbage collect. You will end up with 30MB allocated and 20MB free: the total will never go above the previous max (50MB) for the lifetime of the JVM. Yoav Shapira 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]
reclaiming memory problem
Hello, How might I reclaim memory, e.g after a session expires when a client browser is closed down? Predicament: as I open up new client windows, the memory (viewed in Windows task manager) creeps up with each new window opened. The app that is loaded creates a session and stores various objects on it. But, when I close down a client window, the memory consumption remains at it's peak (and climbs with each successive new client opened) In other words, memory consumption increments but never decrements, necessitating a server bounce at unacceptable frequency. Why are the resources not being reclaimed, and how might I gently encourage resource reclamation? I fear System.gc() is not the answer here. Many thanks all for all input G. - Yahoo! Messenger - Communicate instantly...Ping your friends today! Download Messenger Now
RE: out of memory problem. Help!
Try this in your jk2.properties file and see if it fixes it for 4.1.29. According to Bill Barker(thread: maxProcessors vs maxThreads), this is the same as the 5.x connector setting for jk2. container.maxThreads=value container.maxSpareThreads=value container.minSpareThreads=value Unfortunately I do not have time to mess with this right now, but I am interested to know if it fixes the leak. Charlie -Original Message- From: news [mailto:[EMAIL PROTECTED] On Behalf Of David Strupl Sent: Monday, January 19, 2004 2:08 PM To: [EMAIL PROTECTED] Subject: Re: out of memory problem. Help! This did not work for me in 4.1.29 since the only way to do this is to set minProcessors==maxProcessors but that did not have any effect in 4.1.29. I am not sure whether I could use xxxThreads there but downgrading to 4.1.27 did help. For those using 5.0.16 this can help - Filip thanks for finding out. Best, David Filip Hanik wrote: set maxSpareThreads=minSpareThreads=maxThreads will cause the system to never shrink the pool Filip -Original Message- From: news [mailto:[EMAIL PROTECTED] Behalf Of David Strupl Sent: Monday, January 19, 2004 9:58 AM To: [EMAIL PROTECTED] Subject: Re: out of memory problem. Help! Remy Maucherat wrote: This is not true: there's indeed a memory leak with 5.0.16, but it would occur only with specific traffic patterns. It will not bring a server down in just a few requests. Indeed. The thread pool has to grow and shrink for this to happen. Unfortunatelly quite common e.g. day and night traffic. D. - 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: out of memory problem. Help!
We fixed our session timeout to 15 minutes for 100 users and Tomcat hasn't crashed for 36 hours. Does anyone know how we can adjust for the possibilities of 1000's of users??? Christian Witucki Network Analyst 375 Essjay Road Williamsville, NY 14221 716-631-3001 x3812 CONFIDENTIALITY NOTICE. This e-mail and attachments, if any, may contain confidential information which is privileged and protected from disclosure by Federal and State confidentiality laws, rules or regulations. This e-mail and attachments, if any, are intended for the designated addressee only . If you are not the designated addressee, you are hereby notified that any disclosure, copying, or distribution of this e-mail and its attachments, if any, may be unlawful and may subject you to legal consequences. If you have received this e-mail and attachments in error, please contact Independent Health immediately at (716) 631-3001 and delete the e-mail and its attachments from your computer. Thank you for your attention. [EMAIL PROTECTED] 01/19/04 01:20AM Check session-timeout in web.xml. -1 is never timeout session-timeout-1/session-timeout -Original Message- From: Christophe Andreoli [mailto:[EMAIL PROTECTED] Sent: Friday, January 16, 2004 9:19 PM To: Tomcat Users List Subject: Re: out of memory problem. Help! Shapira, Yoav wrote: Howdy, root cause java.lang.OutOfMemoryError It happens When the corresponding request returns more than 2-3 rows from the database, not every time Perhaps you should allocate your JVM more memory, by using the Java -Xmx parameter. I did it and I gave 512 Mb. It works better but why are the 2000 objects are not garbaged after each request ? Alternatively, consider a system design that retrieves a smaller, fixed number of rows instead of 2-3 and lets the user scroll, say 100 rows at a time. Yoav Shapira - 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: out of memory problem. Help!
If you use tomcat 5.0.x upgrade to 5.0.18. If you use 4.1.x downgrade to 4.1.27. There is a significant memory leak in tomcat in 5.0.16, 4.1.28(29). Hope this helps, David Christian Witucki wrote: We fixed our session timeout to 15 minutes for 100 users and Tomcat hasn't crashed for 36 hours. Does anyone know how we can adjust for the possibilities of 1000's of users??? Christian Witucki Network Analyst 375 Essjay Road Williamsville, NY 14221 716-631-3001 x3812 CONFIDENTIALITY NOTICE. This e-mail and attachments, if any, may contain confidential information which is privileged and protected from disclosure by Federal and State confidentiality laws, rules or regulations. This e-mail and attachments, if any, are intended for the designated addressee only . If you are not the designated addressee, you are hereby notified that any disclosure, copying, or distribution of this e-mail and its attachments, if any, may be unlawful and may subject you to legal consequences. If you have received this e-mail and attachments in error, please contact Independent Health immediately at (716) 631-3001 and delete the e-mail and its attachments from your computer. Thank you for your attention. [EMAIL PROTECTED] 01/19/04 01:20AM Check session-timeout in web.xml. -1 is never timeout session-timeout-1/session-timeout -Original Message- From: Christophe Andreoli [mailto:[EMAIL PROTECTED] Sent: Friday, January 16, 2004 9:19 PM To: Tomcat Users List Subject: Re: out of memory problem. Help! Shapira, Yoav wrote: Howdy, root cause java.lang.OutOfMemoryError It happens When the corresponding request returns more than 2-3 rows from the database, not every time Perhaps you should allocate your JVM more memory, by using the Java -Xmx parameter. I did it and I gave 512 Mb. It works better but why are the 2000 objects are not garbaged after each request ? Alternatively, consider a system design that retrieves a smaller, fixed number of rows instead of 2-3 and lets the user scroll, say 100 rows at a time. Yoav Shapira - 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: out of memory problem. Help!
This is very interesting to hear. I can believe it too...we lose between 400K and 5MB per request and Tomcat 5.0.16 bombs out at 155. We have invested in JProfiler now to see why but your comment is curious. Are you on the development team? When will 5.0.18 become stable...does not seem to be a binary download yet Cheers ADC -Original Message- From: David Strupl [mailto:[EMAIL PROTECTED] Sent: 19 January 2004 17:00 To: [EMAIL PROTECTED] Subject: Re: out of memory problem. Help! If you use tomcat 5.0.x upgrade to 5.0.18. If you use 4.1.x downgrade to 4.1.27. There is a significant memory leak in tomcat in 5.0.16, 4.1.28(29). Hope this helps, David Christian Witucki wrote: We fixed our session timeout to 15 minutes for 100 users and Tomcat hasn't crashed for 36 hours. Does anyone know how we can adjust for the possibilities of 1000's of users??? Christian Witucki Network Analyst 375 Essjay Road Williamsville, NY 14221 716-631-3001 x3812 CONFIDENTIALITY NOTICE. This e-mail and attachments, if any, may contain confidential information which is privileged and protected from disclosure by Federal and State confidentiality laws, rules or regulations. This e-mail and attachments, if any, are intended for the designated addressee only . If you are not the designated addressee, you are hereby notified that any disclosure, copying, or distribution of this e-mail and its attachments, if any, may be unlawful and may subject you to legal consequences. If you have received this e-mail and attachments in error, please contact Independent Health immediately at (716) 631-3001 and delete the e-mail and its attachments from your computer. Thank you for your attention. [EMAIL PROTECTED] 01/19/04 01:20AM Check session-timeout in web.xml. -1 is never timeout session-timeout-1/session-timeout -Original Message- From: Christophe Andreoli [mailto:[EMAIL PROTECTED] Sent: Friday, January 16, 2004 9:19 PM To: Tomcat Users List Subject: Re: out of memory problem. Help! Shapira, Yoav wrote: Howdy, root cause java.lang.OutOfMemoryError It happens When the corresponding request returns more than 2-3 rows from the database, not every time Perhaps you should allocate your JVM more memory, by using the Java -Xmx parameter. I did it and I gave 512 Mb. It works better but why are the 2000 objects are not garbaged after each request ? Alternatively, consider a system design that retrieves a smaller, fixed number of rows instead of 2-3 and lets the user scroll, say 100 rows at a time. Yoav Shapira - 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] FONT SIZE=1 FACE=VERDANA,ARIAL COLOR=BLUE --- QAS Ltd. Developers of QuickAddress Software a href=http://www.qas.com;www.qas.com/a Registered in England: No 2582055 Registered in Australia: No 082 851 474 --- /FONT - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: out of memory problem. Help!
I am not on the developer team. But spent quite a lot of hours (days) latelly with figuring out why my copy of tomcat (4.1.29) leaks memory. The information bellow is based on the info from the dev mailing list + a thread on this mailing list with subject Tomcat Tuning Memory leak from last couple of days (weeks). I am still testing 4.1.27 and all seems fine so far. Re 5.0.18: thats a revision where the fix was commited - please check the dev mailing list with subject Found it - WAS: Memory leak and RE: [5.0.18] Build available. Hope this helps, David Allistair Crossley wrote: This is very interesting to hear. I can believe it too...we lose between 400K and 5MB per request and Tomcat 5.0.16 bombs out at 155. We have invested in JProfiler now to see why but your comment is curious. Are you on the development team? When will 5.0.18 become stable...does not seem to be a binary download yet Cheers ADC -Original Message- From: David Strupl [mailto:[EMAIL PROTECTED] Sent: 19 January 2004 17:00 To: [EMAIL PROTECTED] Subject: Re: out of memory problem. Help! If you use tomcat 5.0.x upgrade to 5.0.18. If you use 4.1.x downgrade to 4.1.27. There is a significant memory leak in tomcat in 5.0.16, 4.1.28(29). Hope this helps, David Christian Witucki wrote: We fixed our session timeout to 15 minutes for 100 users and Tomcat hasn't crashed for 36 hours. Does anyone know how we can adjust for the possibilities of 1000's of users??? Christian Witucki Network Analyst 375 Essjay Road Williamsville, NY 14221 716-631-3001 x3812 CONFIDENTIALITY NOTICE. This e-mail and attachments, if any, may contain confidential information which is privileged and protected from disclosure by Federal and State confidentiality laws, rules or regulations. This e-mail and attachments, if any, are intended for the designated addressee only . If you are not the designated addressee, you are hereby notified that any disclosure, copying, or distribution of this e-mail and its attachments, if any, may be unlawful and may subject you to legal consequences. If you have received this e-mail and attachments in error, please contact Independent Health immediately at (716) 631-3001 and delete the e-mail and its attachments from your computer. Thank you for your attention. [EMAIL PROTECTED] 01/19/04 01:20AM Check session-timeout in web.xml. -1 is never timeout session-timeout-1/session-timeout -Original Message- From: Christophe Andreoli [mailto:[EMAIL PROTECTED] Sent: Friday, January 16, 2004 9:19 PM To: Tomcat Users List Subject: Re: out of memory problem. Help! Shapira, Yoav wrote: Howdy, root cause java.lang.OutOfMemoryError It happens When the corresponding request returns more than 2-3 rows from the database, not every time Perhaps you should allocate your JVM more memory, by using the Java -Xmx parameter. I did it and I gave 512 Mb. It works better but why are the 2000 objects are not garbaged after each request ? Alternatively, consider a system design that retrieves a smaller, fixed number of rows instead of 2-3 and lets the user scroll, say 100 rows at a time. Yoav Shapira - 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] FONT SIZE=1 FACE=VERDANA,ARIAL COLOR=BLUE --- QAS Ltd. Developers of QuickAddress Software a href=http://www.qas.com;www.qas.com/a Registered in England: No 2582055 Registered in Australia: No 082 851 474 --- /FONT - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: out of memory problem. Help!
Allistair Crossley wrote: This is very interesting to hear. I can believe it too...we lose between 400K and 5MB per request and Tomcat 5.0.16 bombs out at 155. We have invested in JProfiler now to see why but your comment is curious. Are you on the development team? When will 5.0.18 become stable...does not seem to be a binary download yet I suggest you continue investigating with your profiler: you have a different problem. -Original Message- From: David Strupl [mailto:[EMAIL PROTECTED] Sent: 19 January 2004 17:00 To: [EMAIL PROTECTED] Subject: Re: out of memory problem. Help! If you use tomcat 5.0.x upgrade to 5.0.18. If you use 4.1.x downgrade to 4.1.27. There is a significant memory leak in tomcat in 5.0.16, 4.1.28(29). This is not true: there's indeed a memory leak with 5.0.16, but it would occur only with specific traffic patterns. It will not bring a server down in just a few requests. -- x Rémy Maucherat Senior Developer Consultant JBoss Group (Europe) SàRL x - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: out of memory problem. Help!
Remy Maucherat wrote: This is not true: there's indeed a memory leak with 5.0.16, but it would occur only with specific traffic patterns. It will not bring a server down in just a few requests. Indeed. The thread pool has to grow and shrink for this to happen. Unfortunatelly quite common e.g. day and night traffic. D. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: out of memory problem. Help!
set maxSpareThreads=minSpareThreads=maxThreads will cause the system to never shrink the pool Filip -Original Message- From: news [mailto:[EMAIL PROTECTED] Behalf Of David Strupl Sent: Monday, January 19, 2004 9:58 AM To: [EMAIL PROTECTED] Subject: Re: out of memory problem. Help! Remy Maucherat wrote: This is not true: there's indeed a memory leak with 5.0.16, but it would occur only with specific traffic patterns. It will not bring a server down in just a few requests. Indeed. The thread pool has to grow and shrink for this to happen. Unfortunatelly quite common e.g. day and night traffic. D. - 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: out of memory problem. Help!
This did not work for me in 4.1.29 since the only way to do this is to set minProcessors==maxProcessors but that did not have any effect in 4.1.29. I am not sure whether I could use xxxThreads there but downgrading to 4.1.27 did help. For those using 5.0.16 this can help - Filip thanks for finding out. Best, David Filip Hanik wrote: set maxSpareThreads=minSpareThreads=maxThreads will cause the system to never shrink the pool Filip -Original Message- From: news [mailto:[EMAIL PROTECTED] Behalf Of David Strupl Sent: Monday, January 19, 2004 9:58 AM To: [EMAIL PROTECTED] Subject: Re: out of memory problem. Help! Remy Maucherat wrote: This is not true: there's indeed a memory leak with 5.0.16, but it would occur only with specific traffic patterns. It will not bring a server down in just a few requests. Indeed. The thread pool has to grow and shrink for this to happen. Unfortunatelly quite common e.g. day and night traffic. D. - 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: out of memory problem. Help!
Check session-timeout in web.xml. -1 is never timeout session-timeout-1/session-timeout -Original Message- From: Christophe Andreoli [mailto:[EMAIL PROTECTED] Sent: Friday, January 16, 2004 9:19 PM To: Tomcat Users List Subject: Re: out of memory problem. Help! Shapira, Yoav wrote: Howdy, root cause java.lang.OutOfMemoryError It happens When the corresponding request returns more than 2-3 rows from the database, not every time Perhaps you should allocate your JVM more memory, by using the Java -Xmx parameter. I did it and I gave 512 Mb. It works better but why are the 2000 objects are not garbaged after each request ? Alternatively, consider a system design that retrieves a smaller, fixed number of rows instead of 2-3 and lets the user scroll, say 100 rows at a time. Yoav Shapira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
out of memory problem. Help!
Hello !
I have a Struts/jsp Application
Ich get an out of memory problem:javax.servlet.ServletException: Servlet
execution threw an exception
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:243)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:190)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:531)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
at
org.apache.catalina.valves.CertificatesValve.invoke(CertificatesValve.java:246)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at
org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2347)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
at
org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:170)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:170)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
at
org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:468)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at
org.apache.ajp.tomcat4.Ajp13Processor.process(Ajp13Processor.java:458)
at
org.apache.ajp.tomcat4.Ajp13Processor.run(Ajp13Processor.java:551)
at java.lang.Thread.run(Thread.java:536)
root cause
java.lang.OutOfMemoryError
It happens When the corresponding request returns more than 2-3
rows from the database, not every time
but surely if more request run parallely
From the 2-3 rows I am making the same number of the following
objects from this class
class{
public int humanId=-1;
public String humanDescription=;
public String swissProtId=;
public String swissProtName=;
public String function=;
public String subcellularLocation =;
public String alternativeProtein =;
public String pathway =;
public double mitoProt =-1;
public int mitoLocal=-1;
private double accuracy;
public String swissProtLink=;
private int hasEncephalHomolog=-1;
private int hasRickettsiaHomolog=-1;
private int hasYeastMitoHomolog=-1;
private int hasParalogMito=-1;
private int heartProteome=-1;
private int psort=-1;
private String mesClone=;
private String mesUnigene=;
private int holgerCandidate=-1;
private int predotar=-1;
private String omim=;
private String subLocWiemann=;
}
Can you help me ?
Thank you!
Chris
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: out of memory problem. Help!
- Get more memory - allocate more memory to the JVM (http://jakarta.apache.org/tomcat/faq/memory.html#adjust) - Don't place 20,000 ros of data in memory - Limit the size of your query -Tim Christophe Andreoli wrote: Hello ! I have a Struts/jsp Application Ich get an out of memory problem:javax.servlet.ServletException: Servlet execution threw an exception at - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: out of memory problem. Help!
Howdy, root cause java.lang.OutOfMemoryError It happens When the corresponding request returns more than 2-3 rows from the database, not every time Perhaps you should allocate your JVM more memory, by using the Java -Xmx parameter. Alternatively, consider a system design that retrieves a smaller, fixed number of rows instead of 2-3 and lets the user scroll, say 100 rows at a time. Yoav Shapira 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]
Re: out of memory problem. Help!
Shapira, Yoav wrote: Howdy, root cause java.lang.OutOfMemoryError It happens When the corresponding request returns more than 2-3 rows from the database, not every time Perhaps you should allocate your JVM more memory, by using the Java -Xmx parameter. I did it and I gave 512 Mb. It works better but why are the 2000 objects are not garbaged after each request ? Alternatively, consider a system design that retrieves a smaller, fixed number of rows instead of 2-3 and lets the user scroll, say 100 rows at a time. Yoav Shapira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: out of memory problem. Help!
Howdy, It works better but why are the 2000 objects are not garbaged after each request ? There's only one reason objects aren't garbage-collected in java: other objects are keeping references to them. You can inspect or profile your code to see what keeps references to what. Yoav Shapira 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]
RE: shared memory problem in Tomcat 4.1.24/Apache 2.0.47/mod_jk2 connection
Hi, FYI I have found the error in server.xml. The following attribute value was missing from the Connector element: protocolHandlerClassName=org.apache.jk.server.JkCoyoteHandler Not all JK2 setup instructions mention this. However, the error messages in /var/log/httpd/error_log persist, but it does not seem to affect the apache/tomcat connection. Thanks a lot. Cheers Mario -Original Message- From: Klaus Wienert [mailto:[EMAIL PROTECTED] Sent: 22. oktober 2003 18:18 To: Tomcat Users List Cc: [EMAIL PROTECTED] Subject: Re: shared memory problem in Tomcat 4.1.24/Apache 2.0.47/mod_jk2 connection Try the following: # workers2.properties [shm] file=/var/log/httpd/jk2.shm size=1048576 [channel.socket:localhost:8009] tomcatId=tomcat1 [ajp13:localhost:8009] channel=channel.socket:localhost:8009 [status:status] [uri:/examples/*] group=ajp13:localhost:8009 [uri:/jkstatus/*] group=status:status -- # jk2.properties # no entries here -- In server.xml add jvmRoute in Engine-Tag like this: Engine jvmRoute=tomcat1 name=Standalone defaultHost=localhost debug=0 Klaus - Original Message - From: Mario Juric [EMAIL PROTECTED] To: Tomcat User [EMAIL PROTECTED] Sent: Wednesday, October 22, 2003 8:20 AM Subject: shared memory problem in Tomcat 4.1.24/Apache 2.0.47/mod_jk2 connection I need some help in solving the following problem. I am trying to establish a simple Tomcat 4.1.24/Apache 2.0.47/mod_jk2 connection using the standard Tomcat examples webapp. The browser waits forever when I try to access http://localhost/examples/. I also get the the following errors two times in my /var/lo/httpd/error_log: [error] jk2_init() Can't find child XXX in scoreboard [error] mod_jk child init 1 -2 Similar problem descriptions I found in the Tomcat User mailing archive indicate that this may have something to do with the shared memory file (shm). I have setup up read/write permission for this file. Note that http://localhost/ (Apache default page) and http://localhost:8009/examples/ (Tomcat examples) work as expected. My OS is Mandrake Linux 9.1 and I use the following setup files: # workers2.properties [shm] file=/var/log/httpd/jk2.shm size=1048576 [channel.socket:localhost:8009] tomcatId=localhost:8009 port=8009 host=127.0.0.1 [ajp13:localhost:8009] channel=channel.socket:localhost:8009 [uri:/examples/*] worker=ajp13:localhost:8009 # jk2.properties handler.list=request,container,channelSocket channelSocket.port=8009 shm.file=/var/log/httpd/jk2.shm - 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: shared memory problem in Tomcat 4.1.24/Apache 2.0.47/mod_jk2 connection
I still have the same problem. This time I attached the status HTML page. It may provide a clue to the source of the problem. I thank you for the help. Cheers Mario -Original Message- From: Klaus Wienert [mailto:[EMAIL PROTECTED] Sent: 22. oktober 2003 18:18 To: Tomcat Users List Cc: [EMAIL PROTECTED] Subject: Re: shared memory problem in Tomcat 4.1.24/Apache 2.0.47/mod_jk2 connection Try the following: # workers2.properties [shm] file=/var/log/httpd/jk2.shm size=1048576 [channel.socket:localhost:8009] tomcatId=tomcat1 [ajp13:localhost:8009] channel=channel.socket:localhost:8009 [status:status] [uri:/examples/*] group=ajp13:localhost:8009 [uri:/jkstatus/*] group=status:status -- # jk2.properties # no entries here -- In server.xml add jvmRoute in Engine-Tag like this: Engine jvmRoute=tomcat1 name=Standalone defaultHost=localhost debug=0 Klaus - Original Message - From: Mario Juric [EMAIL PROTECTED] To: Tomcat User [EMAIL PROTECTED] Sent: Wednesday, October 22, 2003 8:20 AM Subject: shared memory problem in Tomcat 4.1.24/Apache 2.0.47/mod_jk2 connection I need some help in solving the following problem. I am trying to establish a simple Tomcat 4.1.24/Apache 2.0.47/mod_jk2 connection using the standard Tomcat examples webapp. The browser waits forever when I try to access http://localhost/examples/. I also get the the following errors two times in my /var/lo/httpd/error_log: [error] jk2_init() Can't find child XXX in scoreboard [error] mod_jk child init 1 -2 Similar problem descriptions I found in the Tomcat User mailing archive indicate that this may have something to do with the shared memory file (shm). I have setup up read/write permission for this file. Note that http://localhost/ (Apache default page) and http://localhost:8009/examples/ (Tomcat examples) work as expected. My OS is Mandrake Linux 9.1 and I use the following setup files: # workers2.properties [shm] file=/var/log/httpd/jk2.shm size=1048576 [channel.socket:localhost:8009] tomcatId=localhost:8009 port=8009 host=127.0.0.1 [ajp13:localhost:8009] channel=channel.socket:localhost:8009 [uri:/examples/*] worker=ajp13:localhost:8009 # jk2.properties handler.list=request,container,channelSocket channelSocket.port=8009 shm.file=/var/log/httpd/jk2.shm - 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: shared memory problem in Tomcat 4.1.24/Apache 2.0.47/mod_jk2 connection
Sorry, It looks as if html attachements are not accepted by the list server. I try to attach it as a zip-file. -Original Message- From: Mario Juric [mailto:[EMAIL PROTECTED] Sent: 23. oktober 2003 08:59 To: 'Tomcat Users List' Subject: RE: shared memory problem in Tomcat 4.1.24/Apache 2.0.47/mod_jk2 connection I still have the same problem. This time I attached the status HTML page. It may provide a clue to the source of the problem. I thank you for the help. Cheers Mario -Original Message- From: Klaus Wienert [mailto:[EMAIL PROTECTED] Sent: 22. oktober 2003 18:18 To: Tomcat Users List Cc: [EMAIL PROTECTED] Subject: Re: shared memory problem in Tomcat 4.1.24/Apache 2.0.47/mod_jk2 connection Try the following: # workers2.properties [shm] file=/var/log/httpd/jk2.shm size=1048576 [channel.socket:localhost:8009] tomcatId=tomcat1 [ajp13:localhost:8009] channel=channel.socket:localhost:8009 [status:status] [uri:/examples/*] group=ajp13:localhost:8009 [uri:/jkstatus/*] group=status:status -- # jk2.properties # no entries here -- In server.xml add jvmRoute in Engine-Tag like this: Engine jvmRoute=tomcat1 name=Standalone defaultHost=localhost debug=0 Klaus - Original Message - From: Mario Juric [EMAIL PROTECTED] To: Tomcat User [EMAIL PROTECTED] Sent: Wednesday, October 22, 2003 8:20 AM Subject: shared memory problem in Tomcat 4.1.24/Apache 2.0.47/mod_jk2 connection I need some help in solving the following problem. I am trying to establish a simple Tomcat 4.1.24/Apache 2.0.47/mod_jk2 connection using the standard Tomcat examples webapp. The browser waits forever when I try to access http://localhost/examples/. I also get the the following errors two times in my /var/lo/httpd/error_log: [error] jk2_init() Can't find child XXX in scoreboard [error] mod_jk child init 1 -2 Similar problem descriptions I found in the Tomcat User mailing archive indicate that this may have something to do with the shared memory file (shm). I have setup up read/write permission for this file. Note that http://localhost/ (Apache default page) and http://localhost:8009/examples/ (Tomcat examples) work as expected. My OS is Mandrake Linux 9.1 and I use the following setup files: # workers2.properties [shm] file=/var/log/httpd/jk2.shm size=1048576 [channel.socket:localhost:8009] tomcatId=localhost:8009 port=8009 host=127.0.0.1 [ajp13:localhost:8009] channel=channel.socket:localhost:8009 [uri:/examples/*] worker=ajp13:localhost:8009 # jk2.properties handler.list=request,container,channelSocket channelSocket.port=8009 shm.file=/var/log/httpd/jk2.shm - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] jkstatus.zip Description: Zip compressed data - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: shared memory problem in Tomcat 4.1.24/Apache 2.0.47/mod_jk2 connection
I could not find any mistake. It should work fine. The connection is not in errorState and the scoreBoard seems to work. Sorry, no idea Klaus - Original Message - From: Mario Juric [EMAIL PROTECTED] To: 'Tomcat Users List' [EMAIL PROTECTED] Sent: Thursday, October 23, 2003 9:04 AM Subject: RE: shared memory problem in Tomcat 4.1.24/Apache 2.0.47/mod_jk2 connection Sorry, It looks as if html attachements are not accepted by the list server. I try to attach it as a zip-file. -Original Message- From: Mario Juric [mailto:[EMAIL PROTECTED] Sent: 23. oktober 2003 08:59 To: 'Tomcat Users List' Subject: RE: shared memory problem in Tomcat 4.1.24/Apache 2.0.47/mod_jk2 connection I still have the same problem. This time I attached the status HTML page. It may provide a clue to the source of the problem. I thank you for the help. Cheers Mario -Original Message- From: Klaus Wienert [mailto:[EMAIL PROTECTED] Sent: 22. oktober 2003 18:18 To: Tomcat Users List Cc: [EMAIL PROTECTED] Subject: Re: shared memory problem in Tomcat 4.1.24/Apache 2.0.47/mod_jk2 connection Try the following: # workers2.properties [shm] file=/var/log/httpd/jk2.shm size=1048576 [channel.socket:localhost:8009] tomcatId=tomcat1 [ajp13:localhost:8009] channel=channel.socket:localhost:8009 [status:status] [uri:/examples/*] group=ajp13:localhost:8009 [uri:/jkstatus/*] group=status:status -- # jk2.properties # no entries here -- In server.xml add jvmRoute in Engine-Tag like this: Engine jvmRoute=tomcat1 name=Standalone defaultHost=localhost debug=0 Klaus - Original Message - From: Mario Juric [EMAIL PROTECTED] To: Tomcat User [EMAIL PROTECTED] Sent: Wednesday, October 22, 2003 8:20 AM Subject: shared memory problem in Tomcat 4.1.24/Apache 2.0.47/mod_jk2 connection I need some help in solving the following problem. I am trying to establish a simple Tomcat 4.1.24/Apache 2.0.47/mod_jk2 connection using the standard Tomcat examples webapp. The browser waits forever when I try to access http://localhost/examples/. I also get the the following errors two times in my /var/lo/httpd/error_log: [error] jk2_init() Can't find child XXX in scoreboard [error] mod_jk child init 1 -2 Similar problem descriptions I found in the Tomcat User mailing archive indicate that this may have something to do with the shared memory file (shm). I have setup up read/write permission for this file. Note that http://localhost/ (Apache default page) and http://localhost:8009/examples/ (Tomcat examples) work as expected. My OS is Mandrake Linux 9.1 and I use the following setup files: # workers2.properties [shm] file=/var/log/httpd/jk2.shm size=1048576 [channel.socket:localhost:8009] tomcatId=localhost:8009 port=8009 host=127.0.0.1 [ajp13:localhost:8009] channel=channel.socket:localhost:8009 [uri:/examples/*] worker=ajp13:localhost:8009 # jk2.properties handler.list=request,container,channelSocket channelSocket.port=8009 shm.file=/var/log/httpd/jk2.shm - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
shared memory problem in Tomcat 4.1.24/Apache 2.0.47/mod_jk2 connection
I need some help in solving the following problem. I am trying to establish a simple Tomcat 4.1.24/Apache 2.0.47/mod_jk2 connection using the standard Tomcat examples webapp. The browser waits forever when I try to access http://localhost/examples/. I also get the the following errors two times in my /var/lo/httpd/error_log: [error] jk2_init() Can't find child XXX in scoreboard [error] mod_jk child init 1 -2 Similar problem descriptions I found in the Tomcat User mailing archive indicate that this may have something to do with the shared memory file (shm). I have setup up read/write permission for this file. Note that http://localhost/ (Apache default page) and http://localhost:8009/examples/ (Tomcat examples) work as expected. My OS is Mandrake Linux 9.1 and I use the following setup files: # workers2.properties [shm] file=/var/log/httpd/jk2.shm size=1048576 [channel.socket:localhost:8009] tomcatId=localhost:8009 port=8009 host=127.0.0.1 [ajp13:localhost:8009] channel=channel.socket:localhost:8009 [uri:/examples/*] worker=ajp13:localhost:8009 # jk2.properties handler.list=request,container,channelSocket channelSocket.port=8009 shm.file=/var/log/httpd/jk2.shm
Re: shared memory problem in Tomcat 4.1.24/Apache 2.0.47/mod_jk2 connection
Try the following: # workers2.properties [shm] file=/var/log/httpd/jk2.shm size=1048576 [channel.socket:localhost:8009] tomcatId=tomcat1 [ajp13:localhost:8009] channel=channel.socket:localhost:8009 [status:status] [uri:/examples/*] group=ajp13:localhost:8009 [uri:/jkstatus/*] group=status:status -- # jk2.properties # no entries here -- In server.xml add jvmRoute in Engine-Tag like this: Engine jvmRoute=tomcat1 name=Standalone defaultHost=localhost debug=0 Klaus - Original Message - From: Mario Juric [EMAIL PROTECTED] To: Tomcat User [EMAIL PROTECTED] Sent: Wednesday, October 22, 2003 8:20 AM Subject: shared memory problem in Tomcat 4.1.24/Apache 2.0.47/mod_jk2 connection I need some help in solving the following problem. I am trying to establish a simple Tomcat 4.1.24/Apache 2.0.47/mod_jk2 connection using the standard Tomcat examples webapp. The browser waits forever when I try to access http://localhost/examples/. I also get the the following errors two times in my /var/lo/httpd/error_log: [error] jk2_init() Can't find child XXX in scoreboard [error] mod_jk child init 1 -2 Similar problem descriptions I found in the Tomcat User mailing archive indicate that this may have something to do with the shared memory file (shm). I have setup up read/write permission for this file. Note that http://localhost/ (Apache default page) and http://localhost:8009/examples/ (Tomcat examples) work as expected. My OS is Mandrake Linux 9.1 and I use the following setup files: # workers2.properties [shm] file=/var/log/httpd/jk2.shm size=1048576 [channel.socket:localhost:8009] tomcatId=localhost:8009 port=8009 host=127.0.0.1 [ajp13:localhost:8009] channel=channel.socket:localhost:8009 [uri:/examples/*] worker=ajp13:localhost:8009 # jk2.properties handler.list=request,container,channelSocket channelSocket.port=8009 shm.file=/var/log/httpd/jk2.shm - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Pls help me on config of the memory problem
Hi, How to set the maximum number of threads or clients that the server can deal with simultonously? Running java bean takes much memory, so I want to control the number of users who can run it at the same time. I use Apache2, Tomcat4.1 and mod-Jk2 under win2k. Thx, Minger __ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: memory problem (SOLVED)
The upgrade to IBMJava2-14 seems to have solved the memory problem. My site (RedHat 7.1, Tomcat 4.1.12, Apache/1.3.19) has been running for several days, getting hit approximately 10 times the normal amount (due to a script I wrote) and the memory has not climbed above 133 Megs. Using IBMJava2-13, it would have climbed above 500 Megs within a day. Hope this helps. Steve -Original Message- From: Turoff, Steve Sent: Thursday, January 16, 2003 12:12 PM To: Tomcat Users List Subject: RE: memory problem I get the same problem with tomat 4.1 and IBM jdk1.3. Yesterday I upgraded to IBM jdk1.4. Haven't experienced an OutOfMemory yet, but it's still a little too early to tell. I'll keep you updated. Steve -Original Message- From: Kristján Bjarni Guðmundsson [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 16, 2003 7:26 AM To: Tomcat Users List Subject: Re: memory problem I wouldn't upgrade to SUN 1.4, it has the same but different problem: http://developer.java.sun.com/developer/bugParade/bugs/4724129.html rf [EMAIL PROTECTED] wrote on 16.01.2003 12:14:48: I get OutofMemory with tomcat 4.0.6 and sun's jdk1.3. From the archives I found this is due to a bug in the sun's jdk 1.3 JVM, and people suggest to upgrade to 1.4 Does IBM's jdk1.3 too gives the same problem or is it only the Sun's? Thanks, Rf __ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
memory problem
I get OutofMemory with tomcat 4.0.6 and sun's jdk1.3. From the archives I found this is due to a bug in the sun's jdk 1.3 JVM, and people suggest to upgrade to 1.4 Does IBM's jdk1.3 too gives the same problem or is it only the Sun's? Thanks, Rf __ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: memory problem
I wouldn't upgrade to SUN 1.4, it has the same but different problem: http://developer.java.sun.com/developer/bugParade/bugs/4724129.html rf [EMAIL PROTECTED] wrote on 16.01.2003 12:14:48: I get OutofMemory with tomcat 4.0.6 and sun's jdk1.3. From the archives I found this is due to a bug in the sun's jdk 1.3 JVM, and people suggest to upgrade to 1.4 Does IBM's jdk1.3 too gives the same problem or is it only the Sun's? Thanks, Rf __ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: memory problem
I get the same problem with tomat 4.1 and IBM jdk1.3. Yesterday I upgraded to IBM jdk1.4. Haven't experienced an OutOfMemory yet, but it's still a little too early to tell. I'll keep you updated. Steve -Original Message- From: Kristján Bjarni Guðmundsson [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 16, 2003 7:26 AM To: Tomcat Users List Subject: Re: memory problem I wouldn't upgrade to SUN 1.4, it has the same but different problem: http://developer.java.sun.com/developer/bugParade/bugs/4724129.html rf [EMAIL PROTECTED] wrote on 16.01.2003 12:14:48: I get OutofMemory with tomcat 4.0.6 and sun's jdk1.3. From the archives I found this is due to a bug in the sun's jdk 1.3 JVM, and people suggest to upgrade to 1.4 Does IBM's jdk1.3 too gives the same problem or is it only the Sun's? Thanks, Rf __ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Memory problem
Hello, I had to integrate Tomcat with IIS for a bank. It has been working well since recently, a problem appears with the memory used by the inetinfo process. In fact, the size of the memory used by the inetinfo process (which I can visualize in the task manager) increases continuously and after a while, it reaches a maximum value for which every thing is blocked. I have to restart the IIS service (with the www publication service) in order that the inetinfo process returns to its initial size value (7 Mb). I noticed this strange behavior especially when using https requests. When looking to the isapi.log logs, I have these errors: [jk_isapi_plugin.c (716)]: HttpExtensionProc error, service() failed [jk_isapi_plugin.c (498)]: jk_ws_service_t::write, WriteClient failed But I don't know if the saturation of the inetinfo process is caused by these errors, or by another thing ? Can you please tell me if it is a bug in the isapi filter ? how can I solve rapidly this problem ? Thanks in advance for your answer, Best Regards, Zeina
TOMCAT - MEMORY PROBLEM
Hi all, I have installed tomcat4.1.12 / Apache 1.3.27 with JDK 1.3.04 in Linux I have 1GB RAM...when I start the server and check the memory usage it shows 100MB use so balance 900MB is there but day by day the memory consumption is increasing and after 5 days I saw 550MB used when I checked the processes using ps -aux command I found lot of jdk1.3 processes and it keeps on increasingMy assumption is jdk processes are not getting released.how this can be solved ... is there any explicit way to release unwanted processes...why this happens details below 5:25pm up 5 days, 3:41, 3 users, load average: 0.00, 0.00, 0.00 123 processes: 122 sleeping, 1 running, 0 zombie, 0 stopped CPU states: 0.3% user, 0.1% system, 0.0% nice, 3.0% idle Mem: 1028864K av, 434108K used, 594756K free, 48K shrd, 91604K buff Swap: 2096472K av, 0K used, 2096472K free 163456K cached USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND root 9651 0.0 10.2 278088 105460? SJan10 0:01/usr/local/jdk1.3 THANKS IN ADVANCE FOR HELP Laxmikanth * Disclaimer: The information in this e-mail and any attachments is confidential / privileged. It is intended solely for the addressee or addressees. If you are not the addressee indicated in this message, you may not copy or deliver this message to anyone. In such case, you should destroy this message and kindly notify the sender by reply email. Please advise immediately if you or your employer does not consent to Internet email for messages of this kind. * -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: TOMCAT - MEMORY PROBLEM
I have a very similar problem: sleeping processes (threads) increasing, free memory decreasing... And still couldn't get a solution from the list... Currently I have to restart tomcat every night! Joao Filipe Placido -Original Message- From: Laxmikanth M.S. [mailto:[EMAIL PROTECTED]] Sent: terça-feira, 14 de Janeiro de 2003 9:23 To: [EMAIL PROTECTED] Subject: TOMCAT - MEMORY PROBLEM Hi all, I have installed tomcat4.1.12 / Apache 1.3.27 with JDK 1.3.04 in Linux I have 1GB RAM...when I start the server and check the memory usage it shows 100MB use so balance 900MB is there but day by day the memory consumption is increasing and after 5 days I saw 550MB used when I checked the processes using ps -aux command I found lot of jdk1.3 processes and it keeps on increasingMy assumption is jdk processes are not getting released.how this can be solved ... is there any explicit way to release unwanted processes...why this happens details below ** ** ** ** 5:25pm up 5 days, 3:41, 3 users, load average: 0.00, 0.00, 0.00 123 processes: 122 sleeping, 1 running, 0 zombie, 0 stopped CPU states: 0.3% user, 0.1% system, 0.0% nice, 3.0% idle Mem: 1028864K av, 434108K used, 594756K free, 48K shrd, 91604K buff Swap: 2096472K av, 0K used, 2096472K free 163456K cached USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND root 9651 0.0 10.2 278088 105460? S Jan10 0:01/usr/local/jdk1.3 ** ** ** ** THANKS IN ADVANCE FOR HELP Laxmikanth * Disclaimer: The information in this e-mail and any attachments is confidential / privileged. It is intended solely for the addressee or addressees. If you are not the addressee indicated in this message, you may not copy or deliver this message to anyone. In such case, you should destroy this message and kindly notify the sender by reply email. Please advise immediately if you or your employer does not consent to Internet email for messages of this kind. * -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: TOMCAT - MEMORY PROBLEM
If your jsp pages are uncompiled I have found a bug with the jasper-compiler stuff, but it should be fixed in 4.1.19 -Original Message- From: Joao Filipe Placido [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 14, 2003 9:36 AM To: 'Laxmikanth M.S.'; '[EMAIL PROTECTED]' Subject: RE: TOMCAT - MEMORY PROBLEM I have a very similar problem: sleeping processes (threads) increasing, free memory decreasing... And still couldn't get a solution from the list... Currently I have to restart tomcat every night! Joao Filipe Placido -Original Message- From: Laxmikanth M.S. [mailto:[EMAIL PROTECTED]] Sent: terça-feira, 14 de Janeiro de 2003 9:23 To: [EMAIL PROTECTED] Subject: TOMCAT - MEMORY PROBLEM Hi all, I have installed tomcat4.1.12 / Apache 1.3.27 with JDK 1.3.04 in Linux I have 1GB RAM...when I start the server and check the memory usage it shows 100MB use so balance 900MB is there but day by day the memory consumption is increasing and after 5 days I saw 550MB used when I checked the processes using ps -aux command I found lot of jdk1.3 processes and it keeps on increasingMy assumption is jdk processes are not getting released.how this can be solved ... is there any explicit way to release unwanted processes...why this happens details below ** ** ** ** 5:25pm up 5 days, 3:41, 3 users, load average: 0.00, 0.00, 0.00 123 processes: 122 sleeping, 1 running, 0 zombie, 0 stopped CPU states: 0.3% user, 0.1% system, 0.0% nice, 3.0% idle Mem: 1028864K av, 434108K used, 594756K free, 48K shrd, 91604K buff Swap: 2096472K av, 0K used, 2096472K free 163456K cached USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND root 9651 0.0 10.2 278088 105460? S Jan10 0:01/usr/local/jdk1.3 ** ** ** ** THANKS IN ADVANCE FOR HELP Laxmikanth * Disclaimer: The information in this e-mail and any attachments is confidential / privileged. It is intended solely for the addressee or addressees. If you are not the addressee indicated in this message, you may not copy or deliver this message to anyone. In such case, you should destroy this message and kindly notify the sender by reply email. Please advise immediately if you or your employer does not consent to Internet email for messages of this kind. * -- To unsubscribe, e-mail: mailto:tomcat-user- [EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: TOMCAT - MEMORY PROBLEM
Same problem here, no solution yet. I have checked and checked for leaks in our application using all kinds of tools, but can't find anything when running on a windowns development server. Haven't had the resources to try profiling the application running on the production linux server because we have too many hosts and the system runs out of native threads when using a profiler. Brandon -Original Message- From: John Trollinger [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 14, 2003 8:45 AM To: 'Tomcat Users List' Subject: RE: TOMCAT - MEMORY PROBLEM If your jsp pages are uncompiled I have found a bug with the jasper-compiler stuff, but it should be fixed in 4.1.19 -Original Message- From: Joao Filipe Placido [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 14, 2003 9:36 AM To: 'Laxmikanth M.S.'; '[EMAIL PROTECTED]' Subject: RE: TOMCAT - MEMORY PROBLEM I have a very similar problem: sleeping processes (threads) increasing, free memory decreasing... And still couldn't get a solution from the list... Currently I have to restart tomcat every night! Joao Filipe Placido -Original Message- From: Laxmikanth M.S. [mailto:[EMAIL PROTECTED]] Sent: terça-feira, 14 de Janeiro de 2003 9:23 To: [EMAIL PROTECTED] Subject: TOMCAT - MEMORY PROBLEM Hi all, I have installed tomcat4.1.12 / Apache 1.3.27 with JDK 1.3.04 in Linux I have 1GB RAM...when I start the server and check the memory usage it shows 100MB use so balance 900MB is there but day by day the memory consumption is increasing and after 5 days I saw 550MB used when I checked the processes using ps -aux command I found lot of jdk1.3 processes and it keeps on increasingMy assumption is jdk processes are not getting released.how this can be solved ... is there any explicit way to release unwanted processes...why this happens details below ** ** ** ** 5:25pm up 5 days, 3:41, 3 users, load average: 0.00, 0.00, 0.00 123 processes: 122 sleeping, 1 running, 0 zombie, 0 stopped CPU states: 0.3% user, 0.1% system, 0.0% nice, 3.0% idle Mem: 1028864K av, 434108K used, 594756K free, 48K shrd, 91604K buff Swap: 2096472K av, 0K used, 2096472K free 163456K cached USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND root 9651 0.0 10.2 278088 105460? S Jan10 0:01/usr/local/jdk1.3 ** ** ** ** THANKS IN ADVANCE FOR HELP Laxmikanth * Disclaimer: The information in this e-mail and any attachments is confidential / privileged. It is intended solely for the addressee or addressees. If you are not the addressee indicated in this message, you may not copy or deliver this message to anyone. In such case, you should destroy this message and kindly notify the sender by reply email. Please advise immediately if you or your employer does not consent to Internet email for messages of this kind. * -- To unsubscribe, e-mail: mailto:tomcat-user- [EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: TOMCAT - MEMORY PROBLEM
I too am having the same problem. I believe in my case, the problem may stem from the fact that Tomcat 4.1.x maintains a reference to every JSP page that has ever been requested. My site has hundreds of JSP pages, several of which I believe are dynamic (Can someone clarify what makes a JSP page dynamic). Since my current JSP pages are really just content (the HTML is provided by including a header.jsp and a footer.jsp on each page), the solution might be to convert them all to XML docs and then use a single JSP and XSLT to create the HTML. I'm hoping to get some clarification on this and in the meantime am working on testing this theory. I'll keep you updated. Steve -Original Message- From: Brandon Cruz [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 14, 2003 11:24 AM To: Tomcat Users List Subject: RE: TOMCAT - MEMORY PROBLEM Same problem here, no solution yet. I have checked and checked for leaks in our application using all kinds of tools, but can't find anything when running on a windowns development server. Haven't had the resources to try profiling the application running on the production linux server because we have too many hosts and the system runs out of native threads when using a profiler. Brandon -Original Message- From: John Trollinger [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 14, 2003 8:45 AM To: 'Tomcat Users List' Subject: RE: TOMCAT - MEMORY PROBLEM If your jsp pages are uncompiled I have found a bug with the jasper-compiler stuff, but it should be fixed in 4.1.19 -Original Message- From: Joao Filipe Placido [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 14, 2003 9:36 AM To: 'Laxmikanth M.S.'; '[EMAIL PROTECTED]' Subject: RE: TOMCAT - MEMORY PROBLEM I have a very similar problem: sleeping processes (threads) increasing, free memory decreasing... And still couldn't get a solution from the list... Currently I have to restart tomcat every night! Joao Filipe Placido -Original Message- From: Laxmikanth M.S. [mailto:[EMAIL PROTECTED]] Sent: terça-feira, 14 de Janeiro de 2003 9:23 To: [EMAIL PROTECTED] Subject: TOMCAT - MEMORY PROBLEM Hi all, I have installed tomcat4.1.12 / Apache 1.3.27 with JDK 1.3.04 in Linux I have 1GB RAM...when I start the server and check the memory usage it shows 100MB use so balance 900MB is there but day by day the memory consumption is increasing and after 5 days I saw 550MB used when I checked the processes using ps -aux command I found lot of jdk1.3 processes and it keeps on increasingMy assumption is jdk processes are not getting released.how this can be solved ... is there any explicit way to release unwanted processes...why this happens details below ** ** ** ** 5:25pm up 5 days, 3:41, 3 users, load average: 0.00, 0.00, 0.00 123 processes: 122 sleeping, 1 running, 0 zombie, 0 stopped CPU states: 0.3% user, 0.1% system, 0.0% nice, 3.0% idle Mem: 1028864K av, 434108K used, 594756K free, 48K shrd, 91604K buff Swap: 2096472K av, 0K used, 2096472K free 163456K cached USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND root 9651 0.0 10.2 278088 105460? S Jan10 0:01/usr/local/jdk1.3 ** ** ** ** THANKS IN ADVANCE FOR HELP Laxmikanth * Disclaimer: The information in this e-mail and any attachments is confidential / privileged. It is intended solely for the addressee or addressees. If you are not the addressee indicated in this message, you may not copy or deliver this message to anyone. In such case, you should destroy this message and kindly notify the sender by reply email. Please advise immediately if you or your employer does not consent to Internet email for messages of this kind. * -- To unsubscribe, e-mail: mailto:tomcat-user- [EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Tomcat memory problem ?
Hi all, my system is this: I have a solaris machine (2GB RAM) with apache 1.3.19 and two instances of Tomcat 4.0.3 in a load balancer configuration. I started all three days ago: this morning I have found the two Tomcat dead. All my servlets didn't respond and all the system was dead. It's terrible. Did someone ever have this problem? Often I read in the mail list that there is some problem in memory in Tomcat: is it true? Does someone know something? Bye Laura -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: My growing memory problem resolved
Hei Eric,
thank you for your reply,
i will answer your questions below:
eric chacon wrote:
Wolle,
I think the problem may lie in your JVM: Setting a reference to the object
to null does not automatically free the memory--it just allows the garbage
collector to clear it whenever it runs.
In many (most?) JVMs, garbage collection is single-threaded. It may run at
a fairly low priority.
this was tested with JDK1.3.0_02 (Hotspot Server/client) and IBMJava2_1.3
Therefore, under stress testing, it is possible for you to eat up a lot of
memory before the garbage collector has a chance to pool it.
Yes, of course, I gave it a half day an nothing becomes free.
I had also see, that all process was cloesd (tool top under Linux).
One way to test this would be to let your process run under high load, and
then stop your load and watch over time to see if the memory is released.
If, in fact, it is a garbage collection problem, you have a couple of
choices: 1) upgrade your JVM and see if that helps. 2) pool your Heavy
Objects: create a store of them, and re-use them.
I have done something else,
I have synchronize the Object and use create only on Object:
class Servlet extends HttpServlet{
HeavyObject ho = null;
public doPost(request,response) throws IOException{
if (ho != null){
ho = new HeavyObject();
}
}
}
that works,
so the Object will only created once, but I have to synchronize the Object.
If you're doing load balancing/workload management, this might cause some
problems (you'll need to persist your objects to a common database), but if
everything's running on one machine, pooling might be an easy, convenient
solution.
Cheers,
Eric
thanks and Greetings,
Michael
From: Wolle [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: tomcatUser [EMAIL PROTECTED]
Subject: My growing memory problem resolved
Date: Mon, 07 May 2001 03:45:55 +0200
Hello ,
i have posted for a few day's a problem thats the Memory usage will
extremly grow up when I refresh a page very often
The Problem was, that I creat a heavy memory Object on each refresh.
Normally I have 81 processes run at all, when execute the stress-test
the processcount will rise till ~ 230. And each new Prcoesses will creat
a new Object.
When I stop the stress-test, the processcount becomes normal (~ 100) ,
but the memory usage won't fall.
But the new created Object have now refernces that points to them.
But why they don't becomes free My code is somthing like this:
public class servlet1 extends HttpServlet{
..
...
..
..
public void doPost(HttpServletRequest request,HttpServletResponse
response)
throws IOException{
try{
HeavyObject ho = new HeavyObject();
}
finally{
ho = null; // for testing implementet, but this gives the
memory not free, also
}
}
}
Is this a Bug in Tomcat ? Or is it a Bug from me ? Or som Java
misunderstood ?
Why will the Object not becomes free, when some of the Threads will be
closed ,
and the only reference is in the closed Thread ?
Greetings,
Michael
_
Get your FREE download of MSN Explorer at http://explorer.msn.com
AW: My growing memory problem resolved
You have to separate two things:
- memory usage inside the vm
this is what you see if you print out:
Runtime.getRuntime().totalMemory()
Runtime.getRuntime().freeMemory()
You have hardly any control about the
execution of the garbage collector. The
only contract that you can take for granted,
is that any JVM will do the garbage collection,
if it runs out of memory. All other things
(calling system.gc(), terminating a method,
setting all references to an object to null) are
just hints for the JVM that can be ignored.
From the java doc of System.gc():
Calling the gc method suggests that the Java
Virtual Machine expend effort toward recycling
unused object
- memory usage of the vm
this is what you see with top/ps/task manager
Even if all objects are garbage collected, that doesn't
mean that the size of the JVM shrinks, it is possible
that only the free memory inside the JVM grows for each
byte that is garbage collected. Wether the JVM is able to
decrease it's memory footprint is up to the JVM and the
underlying operating system.
-Ursprüngliche Nachricht-
Von: Wolle [mailto:[EMAIL PROTECTED]]
Gesendet: Montag, 7. Mai 2001 03:46
An: tomcatUser
Betreff: My growing memory problem resolved
Hello ,
i have posted for a few day's a problem thats the Memory usage will
extremly grow up when I refresh a page very often
The Problem was, that I creat a heavy memory Object on each refresh.
Normally I have 81 processes run at all, when execute the
stress-test
the processcount will rise till ~ 230. And each new Prcoesses
will creat
a new Object.
When I stop the stress-test, the processcount becomes normal (~ 100) ,
but the memory usage won't fall.
But the new created Object have now refernces that points to them.
But why they don't becomes free My code is somthing like this:
public class servlet1 extends HttpServlet{
..
...
..
..
public void doPost(HttpServletRequest request,HttpServletResponse
response)
throws IOException{
try{
HeavyObject ho = new HeavyObject();
}
finally{
ho = null; // for testing implementet, but this gives the
memory not free, also
}
}
}
Is this a Bug in Tomcat ? Or is it a Bug from me ? Or som Java
misunderstood ?
Why will the Object not becomes free, when some of the Threads will be
closed ,
and the only reference is in the closed Thread ?
Greetings,
Michael
My growing memory problem resolved
Hello ,
i have posted for a few day's a problem thats the Memory usage will
extremly grow up when I refresh a page very often
The Problem was, that I creat a heavy memory Object on each refresh.
Normally I have 81 processes run at all, when execute the stress-test
the processcount will rise till ~ 230. And each new Prcoesses will creat
a new Object.
When I stop the stress-test, the processcount becomes normal (~ 100) ,
but the memory usage won't fall.
But the new created Object have now refernces that points to them.
But why they don't becomes free My code is somthing like this:
public class servlet1 extends HttpServlet{
..
...
..
..
public void doPost(HttpServletRequest request,HttpServletResponse
response)
throws IOException{
try{
HeavyObject ho = new HeavyObject();
}
finally{
ho = null; // for testing implementet, but this gives the
memory not free, also
}
}
}
Is this a Bug in Tomcat ? Or is it a Bug from me ? Or som Java
misunderstood ?
Why will the Object not becomes free, when some of the Threads will be
closed ,
and the only reference is in the closed Thread ?
Greetings,
Michael
RE: My growing memory problem resolved
Hi,
This is a guess, I suggest reviewing the garbage collection rules for the
JVM. I know that you're on the right track by assigning null to the object,
but this does not guarantee that the object will be garbage collected, and
there is no way to guarantee garbage collection will run according to the
specification. Garbage collection is a low priority thread that only
executes with the JVM thinks it has sufficient time to perform the process.
I am also wondering if you store your heavy object in the session, as doing
so would cause a reference to the heavy object to exist for the durration of
the session of each thread. If you are storing the heavy object to the
session, then you'll want a session.remove(ho); statement in your finally
clause.
Other than that, I cannot think of anything else to do...
-Original Message-
From: Wolle [mailto:[EMAIL PROTECTED]]
Sent: Sunday, May 06, 2001 6:46 PM
To: tomcatUser
Subject: My growing memory problem resolved
Hello ,
i have posted for a few day's a problem thats the Memory usage will
extremly grow up when I refresh a page very often
The Problem was, that I creat a heavy memory Object on each refresh.
Normally I have 81 processes run at all, when execute the stress-test
the processcount will rise till ~ 230. And each new Prcoesses will creat
a new Object.
When I stop the stress-test, the processcount becomes normal (~ 100) ,
but the memory usage won't fall.
But the new created Object have now refernces that points to them.
But why they don't becomes free My code is somthing like this:
public class servlet1 extends HttpServlet{
..
...
..
..
public void doPost(HttpServletRequest request,HttpServletResponse
response)
throws IOException{
try{
HeavyObject ho = new HeavyObject();
}
finally{
ho = null; // for testing implementet, but this gives the
memory not free, also
}
}
}
Is this a Bug in Tomcat ? Or is it a Bug from me ? Or som Java
misunderstood ?
Why will the Object not becomes free, when some of the Threads will be
closed ,
and the only reference is in the closed Thread ?
Greetings,
Michael
Memory problem
I am trying to run tomcat-3.2 on windows 95 platform and could not do. It said 'running out of environment space'. Any idea what should I do ? [EMAIL PROTECTED]
Re: Memory problem
If you right click on your Icon on your desktop and go to properties you can set the enviorment space to a much larger number. Another cure to this is to go to this site and use this .exe to launch tomcat. Cool little program I use in NT. http://www.geocities.com/jdrudnicki/ -- Pete -- - Original Message - From: ssarkar To: [EMAIL PROTECTED] Sent: Sunday, December 31, 2000 9:04 AM Subject: Memory problem I am trying to run tomcat-3.2 on windows 95 platform and could not do. It said 'running out of environment space'. Any idea what should I do ? [EMAIL PROTECTED]
RE: Increasing memory problem (i hope this helps)
could you tell me more about the thread pooling, please? Where do I get
some
information? How does Tomcat handle the requests?
Thank you.
Kai
I hope this helps.
The PROBLEM:
Tomcat is a multi-threaded servlet container, this means that the requests
needs to be executed by some thread, when a new requests arrives a new
thread
starts and serves the request. This is very problmatic coz' of this it is
hard
to limit the resource consumptio, i.e if 300 requests arrive concurrently
tomcat will open 300 threads and serve them, this causes tomcat to allocate
more resources(CPU, memory,..) than it should and leads to low performance
and
crashes.(for that matter memory problems with Oracle were coz' of this).
THE SOLUTION: Having a thread pool, instead of allocating new threadsl
whenvever they need a thread they ask for it from the pool and and when they
are done
the thread is returned to the pool. Thread management techniques such as:
1) Keeping threads open and reusing them over and over again, this saves
trouble associated with creating and destructing threads continuously.
2) setting an upper bound on the number of concurrent threads used, this
solves the resource allocation problem.
Shuklix
Ps: This is a excerpt from a write up which i had read, had kept this
a small write up for my reference. Sorry author for not being able to
give
you due credit.
Hello Shuklix,
could you tell me more about the thread pooling, please? Where do I get some
information? How does Tomcat handle the requests?
Thank you.
Kai
Saurabh Shukla wrote:
YOu can also try Thread Pooling in tomcat, it might be help.
SHuklix
-Original Message-
From: Julio Serje (@canada.com) [mailto:[EMAIL PROTECTED]]
Sent: Sunday, November 26, 2000 10:08 PM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: Increasing memory problem
Hi, Kai.
The problem you are experiencing is a difficult one, as it relates to the
way you allocate and de-allocate your resources in a way the garbage
collector can determine that a resource is not needed anymore.
You say that you're using jdbc. You should make sure that you are properly
(and explicitly) deallocating all resources you create.
a) Connections to the database. If you're not using a connection pool,
make
sure your connections are closed.
b) ResultSets AND statements. This is a common problem, you must close()
them in order to let the garbage collector do its work.
example:
rset.close();
stmt.close();
conn.close();
Julio
- Original Message -
From: Kai Müller [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Friday, November 24, 2000 12:35 PM
Subject: Increasing memory problem
Hi everybody!
My problem is the following:
after I start my application (JSPs read from MySQL) with Tomcat 3.1 the
used memory of the java processes increases and the number of java
processes themselves increases if I reload the same site (2 per second),
reload, reload, reload ;-)
The performance goes down, and sometimes Tomcat crashes. The HTML sent
to the browser is large (about 350 kB). I get several errors
(OutOfMemory, Response has already been committed,...) and I am
absolutely confused about it now.
Can anybody help me ? Do you need further information ?
With kind regards
Kai Müller
The input.jsp is the following and a global entry for all requests,
which are handled and forward on a JSP page with the HTML-Codes.
%@ page errorPage="/error/errorpage.jsp" %
%@ page import="javax.servlet.*" %
%@ page import="javax.servlet.http.*" %
%
response.setDateHeader("Expires",0);
response.setHeader("Pragma","no-cache");
response.setHeader("Cache-Control","no-cache,must-revalidate");
%
jsp:useBean
id="requestProc"
class="TheRequestClass"
scope="session"
%
requestProc.initialize(config.getServletContext(), session);
%
/jsp:useBean
jsp:useBean
id="pageController"
class="ThePageControllerClass"
scope="session"
/jsp:useBean
%
requestProc.processRequest(request);
String next = pageController.getNextPage(request);
getServletConfig().getServletContext().getRequestDispatcher("/" +
next).forward(request, response);
%
-
--
Mediadom audiovisuelle Medien GmbH
Merheimer Str. 151
D-50733 Koeln
Tel.: 0221 / 917 11 80
Fax: 0221 / 917 11 81
Internet: http://www.mediadom.de
--
Mediadom audiovisuelle Medien GmbH
Merheimer Str. 151
D-50733 Koeln
Tel.: 0221 / 917 11 80
Fax: 0221 / 917 11 81
Internet: http://www.mediadom.de
Re: Increasing memory problem (i hope this helps)
See below. Saurabh Shukla wrote: could you tell me more about the thread pooling, please? Where do I get some information? How does Tomcat handle the requests? Thank you. Kai I hope this helps. The PROBLEM: Tomcat is a multi-threaded servlet container, this means that the requests needs to be executed by some thread, when a new requests arrives a new thread starts and serves the request. This is very problmatic coz' of this it is hard to limit the resource consumptio, i.e if 300 requests arrive concurrently tomcat will open 300 threads and serve them, this causes tomcat to allocate more resources(CPU, memory,..) than it should and leads to low performance and crashes.(for that matter memory problems with Oracle were coz' of this). THE SOLUTION: Having a thread pool, instead of allocating new threadsl whenvever they need a thread they ask for it from the pool and and when they are done the thread is returned to the pool. Thread management techniques such as: 1) Keeping threads open and reusing them over and over again, this saves trouble associated with creating and destructing threads continuously. 2) setting an upper bound on the number of concurrent threads used, this solves the resource allocation problem. Shuklix Ps: This is a excerpt from a write up which i had read, had kept this a small write up for my reference. Sorry author for not being able to give you due credit. To amplify this explanation slightly: Tomcat allows you to configure the use of a thread pool, and limit the maximum number of simultaneous requests by limiting the maximum number of threads that are allowed in the pool. The details of how to do this (in server.xml) depend on which version of Tomcat you are talking about. It actually makes no functional difference to your applications whether Tomcat is using a thread pool or creating threads on the fly -- the only differences will be performance related. In particular, you can limit the total number of threads even if you are creating them on the fly, by simply maintaining a reference count of how many active threads there are, and refusing to create one if you are at the maximum already. But, that all being said, threads are the servlet container's problem to manage. The application developer, thankfully, needs to worry only about their application (including the fact that a particular servlet can be accessed by more than one thread at the same time -- but you don't have to worry about *how* that happens). Craig McClanahan
Re: Increasing memory problem
Hi!
thank you for your help!
In the meantime I found a stupid error in my code, which only appeared when
the amount read from the database got larger.
It was a "new "on the wrong place inside of the handler that selected data
from the database...
Kai
Saurabh Shukla wrote:
YOu can also try Thread Pooling in tomcat, it might be help.
SHuklix
-Original Message-
From: Julio Serje (@canada.com) [mailto:[EMAIL PROTECTED]]
Sent: Sunday, November 26, 2000 10:08 PM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: Increasing memory problem
Hi, Kai.
The problem you are experiencing is a difficult one, as it relates to the
way you allocate and de-allocate your resources in a way the garbage
collector can determine that a resource is not needed anymore.
You say that you're using jdbc. You should make sure that you are properly
(and explicitly) deallocating all resources you create.
a) Connections to the database. If you're not using a connection pool, make
sure your connections are closed.
b) ResultSets AND statements. This is a common problem, you must close()
them in order to let the garbage collector do its work.
example:
rset.close();
stmt.close();
conn.close();
Julio
- Original Message -
From: Kai Müller [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Friday, November 24, 2000 12:35 PM
Subject: Increasing memory problem
Hi everybody!
My problem is the following:
after I start my application (JSPs read from MySQL) with Tomcat 3.1 the
used memory of the java processes increases and the number of java
processes themselves increases if I reload the same site (2 per second),
reload, reload, reload ;-)
The performance goes down, and sometimes Tomcat crashes. The HTML sent
to the browser is large (about 350 kB). I get several errors
(OutOfMemory, Response has already been committed,...) and I am
absolutely confused about it now.
Can anybody help me ? Do you need further information ?
With kind regards
Kai Müller
The input.jsp is the following and a global entry for all requests,
which are handled and forward on a JSP page with the HTML-Codes.
%@ page errorPage="/error/errorpage.jsp" %
%@ page import="javax.servlet.*" %
%@ page import="javax.servlet.http.*" %
%
response.setDateHeader("Expires",0);
response.setHeader("Pragma","no-cache");
response.setHeader("Cache-Control","no-cache,must-revalidate");
%
jsp:useBean
id="requestProc"
class="TheRequestClass"
scope="session"
%
requestProc.initialize(config.getServletContext(), session);
%
/jsp:useBean
jsp:useBean
id="pageController"
class="ThePageControllerClass"
scope="session"
/jsp:useBean
%
requestProc.processRequest(request);
String next = pageController.getNextPage(request);
getServletConfig().getServletContext().getRequestDispatcher("/" +
next).forward(request, response);
%
-
--
Mediadom audiovisuelle Medien GmbH
Merheimer Str. 151
D-50733 Koeln
Tel.: 0221 / 917 11 80
Fax: 0221 / 917 11 81
Internet: http://www.mediadom.de
--
Mediadom audiovisuelle Medien GmbH
Merheimer Str. 151
D-50733 Koeln
Tel.: 0221 / 917 11 80
Fax: 0221 / 917 11 81
Internet: http://www.mediadom.de
Re: Increasing memory problem
Hello Shuklix,
could you tell me more about the thread pooling, please? Where do I get some
information? How does Tomcat handle the requests?
Thank you.
Kai
Saurabh Shukla wrote:
YOu can also try Thread Pooling in tomcat, it might be help.
SHuklix
-Original Message-
From: Julio Serje (@canada.com) [mailto:[EMAIL PROTECTED]]
Sent: Sunday, November 26, 2000 10:08 PM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: Increasing memory problem
Hi, Kai.
The problem you are experiencing is a difficult one, as it relates to the
way you allocate and de-allocate your resources in a way the garbage
collector can determine that a resource is not needed anymore.
You say that you're using jdbc. You should make sure that you are properly
(and explicitly) deallocating all resources you create.
a) Connections to the database. If you're not using a connection pool, make
sure your connections are closed.
b) ResultSets AND statements. This is a common problem, you must close()
them in order to let the garbage collector do its work.
example:
rset.close();
stmt.close();
conn.close();
Julio
- Original Message -
From: Kai Müller [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Friday, November 24, 2000 12:35 PM
Subject: Increasing memory problem
Hi everybody!
My problem is the following:
after I start my application (JSPs read from MySQL) with Tomcat 3.1 the
used memory of the java processes increases and the number of java
processes themselves increases if I reload the same site (2 per second),
reload, reload, reload ;-)
The performance goes down, and sometimes Tomcat crashes. The HTML sent
to the browser is large (about 350 kB). I get several errors
(OutOfMemory, Response has already been committed,...) and I am
absolutely confused about it now.
Can anybody help me ? Do you need further information ?
With kind regards
Kai Müller
The input.jsp is the following and a global entry for all requests,
which are handled and forward on a JSP page with the HTML-Codes.
%@ page errorPage="/error/errorpage.jsp" %
%@ page import="javax.servlet.*" %
%@ page import="javax.servlet.http.*" %
%
response.setDateHeader("Expires",0);
response.setHeader("Pragma","no-cache");
response.setHeader("Cache-Control","no-cache,must-revalidate");
%
jsp:useBean
id="requestProc"
class="TheRequestClass"
scope="session"
%
requestProc.initialize(config.getServletContext(), session);
%
/jsp:useBean
jsp:useBean
id="pageController"
class="ThePageControllerClass"
scope="session"
/jsp:useBean
%
requestProc.processRequest(request);
String next = pageController.getNextPage(request);
getServletConfig().getServletContext().getRequestDispatcher("/" +
next).forward(request, response);
%
-
--
Mediadom audiovisuelle Medien GmbH
Merheimer Str. 151
D-50733 Koeln
Tel.: 0221 / 917 11 80
Fax: 0221 / 917 11 81
Internet: http://www.mediadom.de
--
Mediadom audiovisuelle Medien GmbH
Merheimer Str. 151
D-50733 Koeln
Tel.: 0221 / 917 11 80
Fax: 0221 / 917 11 81
Internet: http://www.mediadom.de
RE: Increasing memory problem
YOu can also try Thread Pooling in tomcat, it might be help.
SHuklix
-Original Message-
From: Julio Serje (@canada.com) [mailto:[EMAIL PROTECTED]]
Sent: Sunday, November 26, 2000 10:08 PM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: Increasing memory problem
Hi, Kai.
The problem you are experiencing is a difficult one, as it relates to the
way you allocate and de-allocate your resources in a way the garbage
collector can determine that a resource is not needed anymore.
You say that you're using jdbc. You should make sure that you are properly
(and explicitly) deallocating all resources you create.
a) Connections to the database. If you're not using a connection pool, make
sure your connections are closed.
b) ResultSets AND statements. This is a common problem, you must close()
them in order to let the garbage collector do its work.
example:
rset.close();
stmt.close();
conn.close();
Julio
- Original Message -
From: Kai Müller [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Friday, November 24, 2000 12:35 PM
Subject: Increasing memory problem
Hi everybody!
My problem is the following:
after I start my application (JSPs read from MySQL) with Tomcat 3.1 the
used memory of the java processes increases and the number of java
processes themselves increases if I reload the same site (2 per second),
reload, reload, reload ;-)
The performance goes down, and sometimes Tomcat crashes. The HTML sent
to the browser is large (about 350 kB). I get several errors
(OutOfMemory, Response has already been committed,...) and I am
absolutely confused about it now.
Can anybody help me ? Do you need further information ?
With kind regards
Kai Müller
The input.jsp is the following and a global entry for all requests,
which are handled and forward on a JSP page with the HTML-Codes.
%@ page errorPage="/error/errorpage.jsp" %
%@ page import="javax.servlet.*" %
%@ page import="javax.servlet.http.*" %
%
response.setDateHeader("Expires",0);
response.setHeader("Pragma","no-cache");
response.setHeader("Cache-Control","no-cache,must-revalidate");
%
jsp:useBean
id="requestProc"
class="TheRequestClass"
scope="session"
%
requestProc.initialize(config.getServletContext(), session);
%
/jsp:useBean
jsp:useBean
id="pageController"
class="ThePageControllerClass"
scope="session"
/jsp:useBean
%
requestProc.processRequest(request);
String next = pageController.getNextPage(request);
getServletConfig().getServletContext().getRequestDispatcher("/" +
next).forward(request, response);
%
-
--
Mediadom audiovisuelle Medien GmbH
Merheimer Str. 151
D-50733 Koeln
Tel.: 0221 / 917 11 80
Fax: 0221 / 917 11 81
Internet: http://www.mediadom.de
Increasing memory problem
Hi everybody!
My problem is the following:
after I start my application (JSPs read from MySQL) with Tomcat 3.1 the
used memory of the java processes increases and the number of java
processes themselves increases if I reload the same site (2 per second),
reload, reload, reload ;-)
The performance goes down, and sometimes Tomcat crashes. The HTML sent
to the browser is large (about 350 kB). I get several errors
(OutOfMemory, Response has already been committed,...) and I am
absolutely confused about it now.
Can anybody help me ? Do you need further information ?
With kind regards
Kai Müller
The input.jsp is the following and a global entry for all requests,
which are handled and forward on a JSP page with the HTML-Codes.
%@ page errorPage="/error/errorpage.jsp" %
%@ page import="javax.servlet.*" %
%@ page import="javax.servlet.http.*" %
%
response.setDateHeader("Expires",0);
response.setHeader("Pragma","no-cache");
response.setHeader("Cache-Control","no-cache,must-revalidate");
%
jsp:useBean
id="requestProc"
class="TheRequestClass"
scope="session"
%
requestProc.initialize(config.getServletContext(), session);
%
/jsp:useBean
jsp:useBean
id="pageController"
class="ThePageControllerClass"
scope="session"
/jsp:useBean
%
requestProc.processRequest(request);
String next = pageController.getNextPage(request);
getServletConfig().getServletContext().getRequestDispatcher("/" +
next).forward(request, response);
%
-
--
Mediadom audiovisuelle Medien GmbH
Merheimer Str. 151
D-50733 Koeln
Tel.: 0221 / 917 11 80
Fax: 0221 / 917 11 81
Internet: http://www.mediadom.de
RE: Increasing memory problem
Give tomcat more memory..
check up your startup file for that..
Shuklix
-Original Message-
From: Kai Müller [mailto:[EMAIL PROTECTED]]
Sent: Friday, November 24, 2000 11:05 PM
To: [EMAIL PROTECTED]
Subject: Increasing memory problem
Hi everybody!
My problem is the following:
after I start my application (JSPs read from MySQL) with Tomcat 3.1 the
used memory of the java processes increases and the number of java
processes themselves increases if I reload the same site (2 per second),
reload, reload, reload ;-)
The performance goes down, and sometimes Tomcat crashes. The HTML sent
to the browser is large (about 350 kB). I get several errors
(OutOfMemory, Response has already been committed,...) and I am
absolutely confused about it now.
Can anybody help me ? Do you need further information ?
With kind regards
Kai Müller
The input.jsp is the following and a global entry for all requests,
which are handled and forward on a JSP page with the HTML-Codes.
%@ page errorPage="/error/errorpage.jsp" %
%@ page import="javax.servlet.*" %
%@ page import="javax.servlet.http.*" %
%
response.setDateHeader("Expires",0);
response.setHeader("Pragma","no-cache");
response.setHeader("Cache-Control","no-cache,must-revalidate");
%
jsp:useBean
id="requestProc"
class="TheRequestClass"
scope="session"
%
requestProc.initialize(config.getServletContext(), session);
%
/jsp:useBean
jsp:useBean
id="pageController"
class="ThePageControllerClass"
scope="session"
/jsp:useBean
%
requestProc.processRequest(request);
String next = pageController.getNextPage(request);
getServletConfig().getServletContext().getRequestDispatcher("/" +
next).forward(request, response);
%
-
--
Mediadom audiovisuelle Medien GmbH
Merheimer Str. 151
D-50733 Koeln
Tel.: 0221 / 917 11 80
Fax: 0221 / 917 11 81
Internet: http://www.mediadom.de
