Could not find the root cause. So as a workaround i am restarting my broker programatically when the memory limit reaches above 80% [broker.getSystemUsage().getMemoryUsage().getPercentUsage() ]
My client (browser) refreshs automatically if the server doesnt send data for 15 secs. The above workaround works fine for me. :-) I shall update once i find the right fix .... SelvarajAM wrote: > > Below is the o/p of netstat > > tcp 0 0 *:8084 *:* > LISTEN > tcp 0 92531 pri:8084 > ::ffff:10.161.:boinc-client FIN_WAIT1 > tcp 1 0 pri:48292 pri:8084 > ESTABLISHED > tcp 0 0 pri:8084 > ::ffff:10.161.:availant-mgr ESTABLISHED > tcp 0 0 pri:8084 pri:48292 > ESTABLISHED > warning, got duplicate tcp line. > warning, got duplicate tcp line. > > > The o/p is same both the client was fine and when it encountered error. > > Can you give an example of xml configuartion on how to configure for > prefetch limit for consumer. > > I tried the following. But did not work. > > <transportConnector name="StompNio" > uri="stomp://0.0.0.0:8084?jms.dispatchAsync=true&jms.prefetchSize=10"/> > > Kindly see the jconsole for subscription attributes. > Once the client fails, the MessageCountAwaitingAcknowledge starts > increasing. > > Dont why it waits for acknowledgement. Kindly shed some light on it > > > http://old.nabble.com/file/p26302014/Subscription.jpg > :-D:-D:-D:-D:-D:-D:-D:-D:-D:-D:-D -- View this message in context: http://old.nabble.com/Activemq-broker-hangs-when-stomp-client-disconnects-unexpectedly-tp26283384p26335328.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.