Seems like i keep having the issue even after increasing the limit. I
wonder what does the 'WriteChecker message really means. And why can't the
connection remain stable? Is there a way to automatically recycle the
connection to keep it fresh?
Any suggestions appreciated.
On Mon, Dec 24, 2012
Can you attach a JConsole screenshot of the Broker MBean attributes?
Does this happen with just one destination or with all?
The Inactivity Monitor WriteChecker is doing exactly what you pursue:
keeping the connection alive by sending pings back and forth.
It doesn't report errors, so it looks
Thanks. I'll have to look into how to get the JConsole screenshot as I've
never done it before. Do you think there might be something wrong with the
my listener? I suspect the broker is working fine but the listener is the
one that is dying. I'll try to debug with the JConsole. Thanks!
On Tue,
You are setting a tempUsage limit of 2 kilobytes. Maybe you expected 2000
to mean megabytes, but the unit is bytes. See Javadoc [1].
In a non-persistent broker, the role of tempUsage is to buffer up
non-persistent messages when consumers can't keep up. The temp storage
implementation (PListStore)
Thanks!
I'll set it as follows:
broker.getSystemUsage().getTempUsage().setLimit(1024l*64l);
And see how it goes.
On Mon, Dec 24, 2012 at 12:03 PM, Raul Kripalani r...@evosent.com wrote:
You are setting a tempUsage limit of 2 kilobytes. Maybe you expected 2000
to mean megabytes, but the
