Tim --
Thanks. It looks like this was an issue with 1.1 but is fixed in trunk. Is
there any indication when the next release will be?
Thanks,
Ted C.
Timothy Bish wrote:
>
> On Fri, 2009-11-20 at 16:50 -0800, Ted C. wrote:
>> Please disregard this. We are see deadlocks in our application b
Hi Bruce
It would be good to have a full documentation.
But my today problem would be to be able to detect a "global pause" due to a
producer flow control behaviour.
It would be nicer if I could understand all the attribute values of the
Queue or Topic MBeans ...
Eric-AWL
bsnyder wrote:
>
On Tue, Nov 24, 2009 at 3:16 AM, moreno9000 wrote:
>
> Yes,
> I want to discard sent messages if number of pending messages
> exceed a predefined limit.
> The reasons for this choice are:
>
> AMQ side: I'd like to prevent problems due to a queue with
> a high number of pending messages. In 5.1 rel
On Tue, 2009-11-24 at 07:55 -0800, jhakim wrote:
> I would like to create a large (40+ MB) MapMessage, get its byte[], compress
> the bytes, and send it across the wire as a BytesMessage. On the receiving
> side, I would like to read the byte[], uncompress, and create the original
> MapMessage from
I would like to create a large (40+ MB) MapMessage, get its byte[], compress
the bytes, and send it across the wire as a BytesMessage. On the receiving
side, I would like to read the byte[], uncompress, and create the original
MapMessage from the byte[].
We have been using this strategy with grea
Thanks for the pointers. I checked them. I got the answer for my [1]. So, if my
queue name is 'myqueue', then URL is going to be
http://host:port/queue/myqueue, right?
I am still looking for credentials stuff...I couldn't able to find it.
I don't want to use JMS. The reason is that I like to pu
I misunderstood.
I don't know when (surely, not this week) but I promise to apply
my little test (a Producer that sends thousands of msg to a
queue with a memoryLimit expressed) to 5.4 SNAPSHOT.
I'll post a new thread with results (in both case: deterministic
or not deterministic behaviour)
Mo
On Tue, Nov 24, 2009 at 3:06 AM, moreno9000 wrote:
>
> I can't switch to 5.4-SNAPSHOT cause we (we=company where I work)
> are in production.
> The choice is between 5.1 AMQ version (the one used till now) and the
> latest stable AMQ release (5.3).
> Sorry.
Gary is asking if it's possible for you
Yes,
I want to discard sent messages if number of pending messages
exceed a predefined limit.
The reasons for this choice are:
AMQ side: I'd like to prevent problems due to a queue with
a high number of pending messages. In 5.1 release I saw that
consumers stop receving messages from a queue with
I can't switch to 5.4-SNAPSHOT cause we (we=company where I work)
are in production.
The choice is between 5.1 AMQ version (the one used till now) and the
latest stable AMQ release (5.3).
Sorry.
Gary Tully wrote:
>
> Re: deterministic memory usage, could you try a 5.4-SNAPSHOT. Usage should
>
Hi,
I wrote a little helper which does that job using the JMX interface. Please
check the attachment.
cheers,
Felix
http://old.nabble.com/file/p26493002/DestinationCleaner.java
DestinationCleaner.java
-
Felix Ehm,
www.cern.ch
--
View this message in context:
http://old.nabble.com/Auto-
Hi,
take a look at this article for more info:
http://activemq.apache.org/rest.html
and be sure to check web demos http://activemq.apache.org/web-samples.html
BTW. If you're using Java you'll have much better messaging experience using
JMS API.
Cheers
--
Dejan Bosanac - http://twitter.com/dejanb
Hi Danilo,
just as a remark (which has not really to do with your problem) :
you may want to set memoryUsage to a lower value, since I think this is the
size AMQ will use to keep messages in memory. If you set your JVM size to
the same, you may not have space left for other objects
(connection/to
13 matches
Mail list logo
