Hi Gary, Unfortunately I could not reproducer it again, I will post the ThreadDump as soon as I encounter it.
--Kaustubh On Thu, Aug 4, 2011 at 8:20 PM, Gary Tully <gary.tu...@gmail.com> wrote: > the thread dump of the broker is key, I found that issue with stomp > where the connections are terminated very quickly and uncleanly. Your > thread dump may indicate a different problem, as in there may be some > message send in progress or a dispatch... it depends very much on > configuration. > > Post a thread dump of your scenario if you reproduce it. > > On 4 August 2011 13:06, kaustubh khasnis <kaustubh.khas...@gmail.com> > wrote: > > Hi, > > Thanks for the fix Gary, I will definitely try it out. > > > > But I looked at the patch and it looks like the fix is more like if "at > the > > startup of transportconnector, if it is already running, shut it down". > I > > am not sure if it will sort the problem of being stuck up at shut down. > > Please correct me if I am wrong. > > > > --Kaustubh > > On Thu, Aug 4, 2011 at 3:09 PM, Gary Tully <gary.tu...@gmail.com> wrote: > > > >> take a thread dump of the broker and have a peek at > >> https://issues.apache.org/jira/browse/AMQ-3435, that fix may be what > >> you need. > >> > >> On 4 August 2011 07:53, kaustubh khasnis <kaustubh.khas...@gmail.com> > >> wrote: > >> > Hi, > >> > I have created an embedded broker and having 10 producers pushing > >> messages > >> > over 1 topic and 10 consumer consuming it. while shutting down the > broker > >> I > >> > get following warning: > >> > The connection to '<ip address:port>' is taking a long time to > shutdown. > >> > and the broker is stuck(it doesn't shut down). > >> > > >> > Can anyone help me with this? > >> > > >> > --Kaustubh > >> > > >> > >> > >> > >> -- > >> http://fusesource.com > >> http://blog.garytully.com > >> > > > > > > -- > http://fusesource.com > http://blog.garytully.com >
