This *is* the 4.2-SNAPSHOT (13 march) release. (I did send that info in a
followup - sorry for the confusion). Maybe I should file a Jira on this?
The initial reason for me using the 4.2 snapshot in the first place, was
that I wanted to verify another fix that was done after 4.1.0.
Now, I just
On 3/14/07, Thomas Gagné <[EMAIL PROTECTED]> wrote:
We have a similar problem with very large messages > 1MB and built a
stream over them so that whenever the buffer hits 20KB it flushes the
message to the client with a header indicating there's more. That
allows the client to construct a stream
We have a similar problem with very large messages > 1MB and built a
stream over them so that whenever the buffer hits 20KB it flushes the
message to the client with a header indicating there's more. That
allows the client to construct a stream on their queue and read the
response in 20KB chunks.
Hi,
There has to be some queue/topic using up the memory buffers of the
broker. I would look all the subscriptions as see if any of them have
not acked back messages.
On 3/14/07, RickardS <[EMAIL PROTECTED]> wrote:
OK, I raised the usageManager increased jvm heap limit, but that only
postpone
On 3/14/07, RickardS <[EMAIL PROTECTED]> wrote:
OK, I raised the usageManager increased jvm heap limit, but that only
postpones the time for block. Looking at the values presented about the
queue through JMX, the consumer seems to be up to speed and the queue is
close to 0 all the time, but "mem
OK, I raised the usageManager increased jvm heap limit, but that only
postpones the time for block. Looking at the values presented about the
queue through JMX, the consumer seems to be up to speed and the queue is
close to 0 all the time, but "memoryPercentageUsed" is always increasing and
eventu
Oh I forgot. I think I noticed a similar effect in an earlier release a
couple of months ago, so today in this test, I used
apache-activemq-4.2-20070313.102814-31.zip .
Best regards,
Rickard
RickardS wrote:
>
> Hello,
>
> I tried to run the Producer and Consumer examples, but using a message
