An application will exit when no more non-daemon threads exist. I don't know whether the failover thread is a daemon or non-daemon thread, but you could attach a debugger to your producer and connect to the iterate() method of the Task created in FailoverTransport.FailoverTransport.FailoverTransport(). (Yes, that name is correct; the class FailoverTransport has an inner class also named FailoverTransport, and the Task is created in its constructor. I don't know why the inner class was given the same name as its containing class.) When you hit your breakpoint, check if the currentThread's isDaemon() method and you'll know.
On Tue, Oct 14, 2014 at 12:37 AM, bansalp <bpradee...@gmail.com> wrote: > Hi, > > I am not expecting my producer to exist after it looses connection from > broker. I want my client to stop when I want them to stop, but with > producer > its not happening. I had to do a kill -9 pid to stop the process (kill pid > is not working). Am unable to understand this behaviour of producer. > > Can't I stop producer when its waiting to try to reconnect to a broker? > > > Thanks, > > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Unable-to-stop-producer-tp4686340p4686364.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
