Thomas, you are right. I saw the code, but still I cannot explain why these 57 threads are doing the same thing and been waiting for at least 5 seconds.
Our deployment is a Linux Red Hat Enterprise 2.6.18-194.el5 running in a 4 6-core machines (24 cores) with 34 GB RAM. Jackrabbit 2.0 any suggestions? 2010/10/7 Patricio Echagüe <[email protected]> > Thanks for the response. > > They are all different thread ids. > > What would it be the best way to avoid so many threads getting blocked > there? > > > On Wed, Oct 6, 2010 at 11:44 PM, Thomas Müller <[email protected]>wrote: > >> Hi, >> >> > We have more than 50 threads waiting here. >> >> Is it the same thread number for each of the 50 stack traces, or is it >> multiple distinct threads? >> >> Looking at the code, if getInstance() is called concurrently from >> multiple threads, each time a new SeededSecureRandom is created, which >> is not needed. It would be a bit better to ensure only one >> SeededSecureRandom() instance is created. When I anyway change that, I >> will also add a bit more entropy to the alternative seed algorithm, >> similar to >> http://code.google.com/p/h2database/source/browse/trunk/h2/src/main/org/h2/util/MathUtils.java#109 >> >> Regards, >> Thomas >> > > > > -- > Patricio.- > -- Patricio.-
