Hi all, the MTHCM has two shutdown attributes, one for the connection manager and one for the ReferenceQueueThread. If I am not mistaken, these attributes should be declared 'volatile' since they are used from different threads? The ReferenceQueueThread wakes up every second just to check the shutdown status. If the attribute is declared volatile and RQT.shutdown() modified to interrupt the thread, would that work without polling?
MTHCM.shutdownAll() might be a bit unsafe since it iterates over a WeakHashMap and does not handle ConcurrentModifcation- Exception: http://java.sun.com/j2se/1.4.2/docs/api/java/util/WeakHashMap.html MTHCM.shutdownAll() synchronizes on the map for all the weak references. I assume this to be an optimization rather than a requirement to prevent deadlocks. Is that correct? cheers, Roland --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
