As rajdavies said, you can wait for v5.2, or you can check the queue size
before sending message frequently?
replyramdas wrote:
>
> Anything will do as long as we know the boundry condition. Let me know how
> can we do this. Thanks in advance, waiting for the reply
>
>
> regards
> Ramdas
>
Anything will do as long as we know the boundry condition. Let me know how
can we do this. Thanks in advance, waiting for the reply
regards
Ramdas
On 8/4/08, wuxz <[EMAIL PROTECTED]> wrote:
>
>
> Do you want to get an Exception been thrown when you call the
> Producer.send()
> method, or you ju
Do you want to get an Exception been thrown when you call the Producer.send()
method, or you just want to get an asynchronous advisory message?
Bala M wrote:
>
> Hi,
>
> Could you please explain usage of the elements "memoryUsage, storeUsage
> and tempUsage"? I searched this forum, but I am no
Re #1, see the following JIRA
https://issues.apache.org/activemq/browse/AMQ-1600
I am using AMQ 5.1, with a similar setup and except for the QueueSize issue,
everything seems to run okay for me. It sounds like there is a problem with
how the messages are being acknowledged.
I'd upgrade to 5.
There are some comments about blocked transport in slow consumer topic:
when using TCP there can be occasions when a network outage can result in a
blocked write. This can cause the entire broker to freeze - and the socket
may never be unblocked. Currently we have a Thread that checks for blocked
Topic's QueueSize and MemoryPercentUsage grow until the latter hits 100%,
and then no messages are delivered to consumers on the topic.
I'm having this same problem. It's a showstopper for us.
Why is a topic accumulating anything whatsoever? The messages aren't
persistent and have 5 second tim
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
what I find strange is that the encoding seems to work fine (so I can
send a message) but the crash happens on the receiving of a message.
The exception I get is
OpenwireStringSupport::readString - Encoding not supported
~FILE:
activemq
