|> this is locked on getCacheLock(), and the passivation in case of stateful
|> stuff is slow (write to disk). getCacheLock locks the whole application.
|>
|> bad, right?
|>
|
|Duh! You're right, sorry. But, wait.....Aren't you doing a
|getCachLock() in
|PassivationJob as well? Same problem, just in a different place.
right, and that is bad...
|You still
|haven't convinced me. :)
what I mean is that the above code that does it, is "bad" and that we need
at least 2 threads to do it, the second one should lock on some lower
granularity lock not the global one,
what is clear in mind is
1- lock all + passivate write => bad.
2- at least 2 steps needed, 2 threads
oka?
marcf
|
|Bill
|
|
|
|_______________________________________________
|Jboss-development mailing list
|[EMAIL PROTECTED]
|http://lists.sourceforge.net/lists/listinfo/jboss-development
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
