On Tue, Aug 17, 2010 at 2:36 PM, Martin C. wrote:
> Hi,
>
> thanks for the very fast answer.
>
> On Tue, Aug 17, 2010 at 8:48 PM, Bruce Snyder wrote:
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>
>> The memoryUsage above should limit the entire broker to 256mb of
>>
On Tue, 2010-08-17 at 18:17 -0700, oliver2010 wrote:
> I am using Activemq in .net (c#)
> I wan't to monitor consumers and producers's count and their ip addresss
> where they connected.
> I download apache.nms and apache.nms.activemq.
> And Wants to realize the monitoring through Advisory Messag
I am using Activemq in .net (c#)
I wan't to monitor consumers and producers's count and their ip addresss
where they connected.
I download apache.nms and apache.nms.activemq.
And Wants to realize the monitoring through Advisory Messages.
But I can't find the corresponding function in Apache.nms.
Schema validation is the default with spring 3. Elements in the broker
sequence must follow alphabetical ordering 2 validate.
On Tuesday, August 17, 2010, Joe Niski wrote:
> Greetings again, Dejan:
>
> I tried setting up another Remote broker using the 5.40 release, just
> dropping my existing c
Greetings again, Dejan:
I tried setting up another Remote broker using the 5.40 release, just dropping
my existing configuration files into place.
I'm getting this parsing error on startup:
ERROR: java.lang.RuntimeException: Failed to execute start task. Reason:
org.springframework.beans.factor
As a followup: We were looking over the release notes for AMQ 5.4
today, and a co-worker noticed https://issues.apache.org/activemq/browse/AMQ-2833
. This allows Stomp clients to indicate text vs byte messages via a
new custom Stomp header. This is perfect for our situation, and we're
loo
Hi,
thanks for the very fast answer.
On Tue, Aug 17, 2010 at 8:48 PM, Bruce Snyder wrote:
>>
>>
>>
>>
>>
>>
>>
>
> The memoryUsage above should limit the entire broker to 256mb of
> memory. I just tested this by lowering the memoryUsage limit to 15mb
On Tue, Aug 17, 2010 at 10:52 AM, Martin C. wrote:
>
> Hi,
>
> I'm a little bit confused by all the memory limit options available in
> ActiveMQ, maybe someone could help me. I primarily send non-persistent
> messages, and I'd like them to be spooled to disk in case a global memory
> limit is reac
On Tue, Aug 17, 2010 at 11:44 AM, Bruce Snyder wrote:
> On Tue, Aug 17, 2010 at 2:53 AM, p-fx wrote:
>>
>> Hello.
>> I am using ActiveMQ as message Broker with something like 140 Topics.
>> I am facing a problem that the broker keeps old messages, instead of
>> discarding them in order to send ne
On Tue, Aug 17, 2010 at 2:53 AM, p-fx wrote:
>
> Hello.
> I am using ActiveMQ as message Broker with something like 140 Topics.
> I am facing a problem that the broker keeps old messages, instead of
> discarding them in order to send new messages (so clients gets old data
> instead of current data
use a comma separated list of destination names in the singular
constructor-arg to the topic should do it, it will form a composite
destination. see:
http://activemq.apache.org/composite-destinations.html
something like:
On 17 August 2010 14:53, BenXS wrote:
>
> I setup a Bean which cur
Will do, thanks for the reply.
Two additional bits of information:
- I should have said that I'm using AMQ 5.3.0, not 5.0.3
- here's the NPE stacktrace i'm seeing in my Remote broker activemq.log:
Aug-17 16:43:08,973 DEBUG [DemandForwardingBridge.serviceLocalException]: The
local Exception was:
Hi,
I'm a little bit confused by all the memory limit options available in
ActiveMQ, maybe someone could help me. I primarily send non-persistent
messages, and I'd like them to be spooled to disk in case a global memory
limit is reached.
Basically, I'd like to set a global limit of 256MB for all
The Apache ActiveMQ team is pleased to announce the release of Apache
ActiveMQ 5.4.0.
This is a maintenance release, bringing together close to 300 resolved
issues and many new features.
Full details and download link can be found in the release page:
http://activemq.apache.org/activemq-540-releas
I setup a Bean which currently listens successfully to exactly ONE Topic
"montopic20".
The SpringXML setup for this bean in activemq.xml is as shown below.
How can I let the same Bean listen to multiple different topics in parallel?
In other words: Which minimal changes do I have to apply to the
I setup a Bean which currently listens successfully to exactly ONE Topic
"montopic20".
The SpringXML setup for this bean in activemq.xml is as shown below.
How can I let the same Bean listen to multiple different topics in parallel?
In other words: Which minimal changes do I have to apply to the
As far as I read there were some problems in the past with setting a prefetch
size of 0 resp. 1.
As a result none or all msgs are sent in such a case.
Is this bug fixed meanwhile?
Ben
--
View this message in context:
http://old.nabble.com/prefetch-size%3D0-and-%3D1-bugs-are-fixed--tp29449259p2
Hi Joe,
this sounds like a bug. Did you tested it with some newer version of
ActiveMQ (as there was a lot of work in that area since 5.0.3)
Can you test newly released 5.4.0
http://repo1.maven.org/maven2/org/apache/activemq/apache-activemq/5.4.0/
and see if the problem still exists?
If it's stil
Have a peek at the one of the redelivery test cases[1] to see how
redelivery works. There is only the DLQ in activemq. Also, peek at the
solution in AMQ-2710[2] which may provide some more insight.
[1]
http://svn.apache.org/viewvc/activemq/trunk/activemq-core/src/test/java/org/apache/activemq/Red
Are the clients acking the sent messages?
On Aug 17, 2010, at 3:27 AM, p-fx wrote:
>
> NO.
> I am using MemoryPersistent and sending as NON_PERSISTENT (configured on
> producer).
>
>
> vanir wrote:
>>
>> have you enabled by persistence.?.This might keep the old messages..
>>
>>
>> p-fx wrot
Not sure, that does seem like a bug as it is not what I would expect
either. I had a quick look at the code and it seems like
keepDurableSubsActive may be responsible for this behavior because
when keepDurableSubsActive is (default) true, new messages are
dispatched to the consumer when it is disco
NO.
I am using MemoryPersistent and sending as NON_PERSISTENT (configured on
producer).
vanir wrote:
>
> have you enabled by persistence.?.This might keep the old messages..
>
>
> p-fx wrote:
>>
>> Hello.
>> I am using ActiveMQ as message Broker with something like 140 Topics.
>> I am facing
have you enabled by persistence.?.This might keep the old messages..
p-fx wrote:
>
> Hello.
> I am using ActiveMQ as message Broker with something like 140 Topics.
> I am facing a problem that the broker keeps old messages, instead of
> discarding them in order to send new messages (so clients
Hi,
Is there a possibility of the activeMQ events (UP/DOWN/OnMessage) be called
out of order i..e if the timing between the UP & DOWN events are too close
will the transportInterrupted & transportresumed be called out of order..?
--
View this message in context:
http://old.nabble.com/Out-of-O
Hello.
I am using ActiveMQ as message Broker with something like 140 Topics.
I am facing a problem that the broker keeps old messages, instead of
discarding them in order to send new messages (so clients gets old data
instead of current data).
How do I configure the broker not to keep old messages
25 matches
Mail list logo
