The exception only happened to the clients that have more results returned, but the results are no more than 40. For the other clients, the same page will run fine. The exception will go away after the tomcat server is restarted. For querying a db, I just used: Criteria crit = new Criteria(); Crit.add(..) listObject = ClassPeer.doSelect(crit); for update , I used intake like: Group group = IntakeHelper.getIntakeGroup(context, INTAKE_GROUP); group.setProperties(classobject); classobject.save(); since I do not use Connection con = .... There is no such Con.close() statement in the code
Do you think I should have Connection con = ..... statement whenever I query a db? Thanks for your helps. -----Original Message----- From: Tony Oslund [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 20, 2006 9:44 AM To: Turbine Users List Subject: RE: java.lang.OutOfMemoryError I am not sure if you have found the source of the memory problem, but here are a few thoughts, since it appears that it might be database related. Are there any conditions under which you are not releasing one or more database connections? Is it possible that a "CallableStatement" or a "ResultSet" is not being closed. When I have done this myself, it can be easily overlooked and can cause some very strange appearing bugs including out of memory errors. It is a little tough shooting in the dark... One obvious thing that might help pinpoint the problem is to know if it happens the first time the code is executed (say right after a fresh restart with a single user), or if the problem occurs only after the code is executed repeatedly, by the same user, multiple users, etc. If you have found the source of the problem, it would be interesting to hear about it. Best of luck. -----Original Message----- From: jill han [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 19, 2006 8:15 AM To: Turbine Users List Subject: RE: java.lang.OutOfMemoryError Yes, I am querying a database, but not with large amounts of data. Such exception will go away after I restart the tomcat server. -----Original Message----- From: AFrieze [mailto:[EMAIL PROTECTED] Sent: Monday, December 18, 2006 5:11 PM To: Turbine Users List Subject: Re: java.lang.OutOfMemoryError jill han wrote: > What could cause java.lang.OutOfMemoryError ? > The application is built on turbine/torque/velocity. > > Thanks in advance > > Jill > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > Jill I have encountered this problem in several different situations. Are you querying a database and/or dealing with large amounts of XML data? If the problem is space related, you should probably increase the amount of memory java can use. Example) If you are using linux as your O/S and tomcat as your server, you could add this line to your Catalina.sh file. export JAVA_OPTS=${JAVA_OPTS}'-Xmx512m -Xms128m' Hope this helps AFrieze --------------------------------------------------------------------- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
