Multiple Threads accessing transaction manager - causing dea

[baranowb]

Hi
I didnt find similar problem yet so Im posting in hope of some enlightment.
I have enviroment that makes large number of concurrent calls to transaction manager to fetch transaction - create, add transacted data, commit/rollback etc.
In this enviroment TX mgr can be accessed by large number of threads - depending on configuration.

What happens is lock on getTransaction operation inside of - propably, some sort of library.

Here is dump of locks: [img]http://mobicents-public.googlegroups.com/web/Trace_JT.JPG[/img]

Lock time is not long but it creates cascade of locks.

Does anyone has some insight into this?

[marklittle]

Why do you think this is causing problems? How large is the setup list that is being called?

[baranowb]

Hi Mark
What do You mean by "setup size" ?

[jhalliday]

Are you basically saying the lock contention on ThreadActionData._threadSetups is a performance problem for you?

It's not something that has shown up as an issue in the past, but we can certainly look at reducing that locking if needed. Each element in the list needs to be setup for each Thread, but the number of elements should be small. That's what Mark is referring to I think. Off the top of my head it's only JTS ORB interceptors - for JTA use the list is most likely empty, in which case the lock contention is just to access the size() method on the Vector!

[marklittle]

Yes, that's precisely what I mean. It should be 0 length most of the time. That's why I don't see how it can be a performance bottleneck.