Hope you don't mind, I've removed the call to Thread.setName in com.sun.jini.ThreadPool

As a result threads will be less descriptive, unfortunately setName isn't thread safe, it's final and cannot be overridden. Thread.getName is only thread safe if a Thread's name isn't changed after publication.

ThreadPool was the only instance of Thread.setName in River.

Regards,

Peter.

Reply via email to