The callbacks of TreeCacheListener run synchronous with the underlying method that causes the event.
Locks generated by this underlying call are still held while the callback-method is being executed. e.g. there's a put(...) being executed. During the execution of the put a Node is being created. Due to the transaction-isolation-level this newly created node is locked in write-mode. After this the TreeCacheListener's nodeCreated-method is being called. After return of this method-call the put-method continues to execute. This behaviour might (will) change in the future, since it causes problems when a TreeCacheListener tryies to process the callbacks asynchronously. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3856055#3856055 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3856055 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
