Dan Diephouse wrote:
But if someone is using just a generated client should they really
have to
call Bus.shutdown()? Maybe we should add some shutdown hooks so
Bus.shutdown() is called automatically when someone exits the JVM.
I'd say that's a good idea. In the particular case of the RM timer we
can workaround by creating the timer with a daemon thread, but the
general problem of releasing resources remains.
Andrea.
- Dan
On 3/13/07, Andrea Smyth <[EMAIL PROTECTED]> wrote:
Bharath Ganesh wrote:
>Hi
>
>I could see a Timer created at org.apache.cxf.ws.rm.RMManager using the
default Timer constructor. This causes the associate timer thread to
run as
a non-daemon thread.
>
>Since this timer is never cancelled, the thread to be there forever,
stopping the VM from exiting. (Matters a lot at the JAX-WS client side)
>
>This needs to be fixed.
>
>Thanks
>-Bharath
>http://www.bharathganesh.com
>
>
Hi Barath,
This timer is canceled - in the RMManager's @PreDestroy annotated
shutdown method, which is called when the the bus is shutdown. Do you
call Bus.shutdown() in your application?
Andrea.
