Hi Pinaki! Yes, there is a ulimit -n command, but most userers lack of the rights to change it at runtime ;)
So it's better to configure it properly in limits.conf. And thanks for the test-howto! My problem was that I did not find a way to properly reproduce the String NULL -> "" bug with derby, so I thought it's easier to show the bug in a small project on it's own. LieGrue, strub --- Pinaki Poddar <[email protected]> schrieb am Do, 6.5.2010: > Von: Pinaki Poddar <[email protected]> > Betreff: Re: AW: AW: Slice: OutOfMemoryError shortly after pounding 1000+ > threads to the system. > An: [email protected] > Datum: Donnerstag, 6. Mai, 2010 01:04 Uhr > > Hi Mark, > > 1. Thanks for contributing the test case. I had > cannibalized the test > scenario in an existing test case (TestBasicFieldNullity). > Further instructions on developing tests for OpenJPA > can be found here > [1]. > > 2. We will add the file limit instruction for the > unixoid users. There used > to be a > $ ulimit -n <file limit> > command in unix -- is not it available in Linux? > > > [1] http://openjpa.apache.org/writing-test-cases-for-openjpa.html > > ----- > Pinaki > -- > View this message in context: > http://openjpa.208410.n2.nabble.com/Spring-3-0-2-OpenJPA-2-0-Slice-OutOfMemoryError-shortly-after-pounding-1000-threads-to-the-system-tp5000822p5011556.html > Sent from the OpenJPA Users mailing list archive at > Nabble.com. >
