Hello, I just recently discovered the JRA-Tool from Bea which is capable to display the type and the count of locking on objects of different classes. (It basically shows the name of the class the object which has been locked on was an instance of).
I found some parts of my application that caused excessive locking and fixed that (running under Jetty) - however when running my servlet under Tomcat 5.5.12 I see tons of uncontended thin locks on instances of java.lang.Vector, none of the beeing ever contended. Since I don't use vector I guess this happens somewhere inside of tomcat. I know uncontended locks are fast, however they can be a scaliability problem on multiprocessor systems where a lot of system-bus communication is caused (like my target system is a 8x dual opteron which is VERY sensitive for this type of bottleneck). Any ideas where this locks could come from, could it be that Vector was choosen maybe accidentially somewhere instead of ArrayList? Thank you in advance, lg Clemens --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
