FWIW, you generally don't have to increase the system limits as a whole to get around this problem. There is a command called ulimit that lets you increase a specific sessions files open limit from the default of 1024.
When you say good-sized, what does that mean in terms of tables, etc? Have you tried generating the OM just using the Torque generator package? This would help determine if it's Torque or something else. > -----Original Message----- > From: Thomas Fischer [mailto:[EMAIL PROTECTED] > Just a wild guess : Have you tried to use velocity 1.3.1 for > the generator ? Henning has reported memory leaks of velocity > 1.4 that were not there in velocity 1.3.1, so velocity's > internal structure seems to have changed. > > NB: The generator does not need to run on the same machine as > the runtime. So you can also change the os limits on a > development machine used to generate the om model, and still > keep the original os limits on the production machine. > > Thomas > > Helge Weissig <[EMAIL PROTECTED]> schrieb am 24.04.2006 19:52:32: > > > When running the torque generator for a good-sized turbine > project, we > > run into the system limit of 1024 open file descriptors > with the stack > > trace as below, which occurs in the torque-data-model target. lsof > > indicates that the process is keeping all {Base}Foo{Peer} and > > associated map classes open. We are still using the ant > build based on > > the turbine TDK, so the previously suggested solutions do > not seem to > > be applicable for us. Library versions are torque-gen-3.2 and > > velocity-1.4. Any advise would be greatly appreciated. We > would prefer > > to solve this without changing the OS limits. OS is FC4, kernel > > 2.6.15-1.1831_FC4smp. Java is gij version 4.0.2. > > Duke CE Privacy Statement Please be advised that this e-mail and any files transmitted with it are confidential communication or may otherwise be privileged or confidential and are intended solely for the individual or entity to whom they are addressed. If you are not the intended recipient you may not rely on the contents of this email or any attachments, and we ask that you please not read, copy or retransmit this communication, but reply to the sender and destroy the email, its contents, and all copies thereof immediately. Any unauthorized dissemination, distribution or copying of this communication is strictly prohibited. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
