Hi,
looking at the available releases (Apache & FUSE) I see that the FUSE
release does not contain the plugin.
Therefore you can't use the FUSE release.
However using the Apache ActiveMQ release
http://www.apache.org/dyn/closer.cgi?path=%2Factivemq%2Fapache-activemq%2F5.3.2%2Fapache-activemq-5.
Hi,
>From the 2.paragraph of your details I would say that if you want your all
consumers to receive all the same sent messages then you should use topics
instead of queues.
Cheers,
Felix
Keith Thornhill-3 wrote:
>
> Hi all,
>
> is there any documentation for best practices when setting up
Hi Gary,
thanks for the quick reply. In fact, my Broker was mis-configured. I started
a Broker with the default config and it connects perfectly.
You actually don't need to restrict the log level of activemq. You can leave
it do DEBUG (and of course not using JMS appender).
But you need to have
Hi,
although this topic seems to be outdated and I have read the documentation :
is there a solution/hint to this issue ?
Unfortunately, I'm experiencing the same with the following log4j config :
laser.conversion.pattern=%d{HH:mm:ss} [%-20t] %-5p %-20c{1} ==> %m%n
# two appenders have been con
Hi,
I currently have a similar problem which occurs from time to time and which
is really a big problem:
With a producer throwing out rather large messages 1MB
> Thank for your reply
>
> fehm wrote:
>>
>> 1. Unless you have switched message persistency off, messages
The 'size' in the statistics you see is the total number of messages which
have been sent to this topic. Unsurprisingly, for topics it is the same as
enqueueCount.
I can only image these numbers to differ when you have a queue instead of
topic. Then, the size represents the number of message in t
Hi,
walec51 wrote:
>
> Does the mean that all the messages are still stored somewhere ?
>
> My recovery policy is .
>
> I'm experiencing a memory leak in ActiveMQ and I'm trying to find out
> whats cosing it. The funny thing is that when I delete all the topics and
> queue on the server the
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 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
Hi abakar,
This example below will read all message from a queue (until it is empty).
Make sure that no producer runs.
If you need to delete all messages you can also use jconsole
(http://activemq.apache.org/jmx.html) to empty the queue (operation
"purge").
Felix
import javax.jms.Connection;
obviously stop.
> But with the cache at connection level you'll see reconnection-attempts
> from spring and as soon as the server is available again a new
> connection is made. With the cache at 'auto' (consumer) no new messages
> appear once the conne
Hi Arjen,
did you try to enable failover transport mechanism :
http://activemq.apache.org/failover-transport-reference.html
This will enable the client to reconnect in case of disconnection. the
default transport url you use will NOT automatically reconnect.
Cheers,
Felix
Arjen van der Meijde
Hi,
while playing with setting the prefetch value for consumers I noticed two
unclear situations:
1) From my understanding from
http://activemq.apache.org/slow-consumer-handling.html I can use the
PrefetchRatePendingMessageLimitStrategy to control the connected clients
prefetch limit (even they
Hi Dan,
If you play with message expiration make sure that your
consumer/broker/producer have the same time since the TimeTtoLive of the
message is set relative to your producer. If you broker is in the future
relative to your producer and the gap is greater than your TTL you won't see
any messag
Hi,
did you meanwhile tried the 5.3 stable release ?
Cheers,
Felix
Champax wrote:
>
> Yes, i had read this post.
>
> But i was thinking the workaround (bean, #ref) was working for store and
> temp files.
>
> Whatever, tests i perform are targeting production environnement, and a
> snapsho
Hi,
you may want to try to enable dynamicOnly=true in the NetworkConnector
properties.
please check here (http://activemq.apache.org/networks-of-brokers.html).
Cheers,
Felix
Carlos Quiroz wrote:
>
> Hi
>
> I have been trying to use a network of brokers to get load balancing and
> scale h
ttach your code and click the assign to
> apache checkbox
>
> cheers,
>
> Rob
>
> On 31 Jul 2009, at 16:43, fehm wrote:
>
>>
>> Hi,
>>
>> I was wondering that one or the other might find the attached plugin
>> useful.
>> It allows t
Hi,
I was wondering that one or the other might find the attached plugin useful.
It allows to enforce the persistence mode for incoming messages.
This case comes handy, whenever the connecting clients are not respecting
(or forgetting) message policies.
In our case, one client connected and s
Hi,
I'm currently fighting a bit with having 5000+ topics and persistence
enabled for an ActiveMQ 5.3 Broker. In fact, in this scenario is not a
problem with persistence is switched off. The broker has no problems (well
if you give him enough memory, say >1Gb) to handle all the topics even when
a
Hi,
sometimes opening the eyes a bit more have great effect. Indeed, I missed
out the correct name of the class to use.
Thanks a lot!
Felix
Jose Luna-2 wrote:
>
>
>
>
>
>
> - Original Message
>> From: fehm
>> To: users@activemq.apache.org
&
Hi,
I have some difficulties installing the DLQ broker plugin as stated on the
plugin installation howto page :
http://activemq.apache.org/interceptors.html . Does somebody has the correct
way how to do this ?
I thought this is enough :
..
but then I get :
Hi,
I'm looking for a policyEntry attribute which allows to limit the number of
Producers per Topic/Queue. Same for the maximim size of a single message.
I'm not sure if the PolicyEntry.maxProducerToAudit which is referenced by
AbstractPendingMessageCursor.java is the right thing. I tried it with
Hi,
seems like its still a problem in 5.2.0 (fuse 5.2.0.2).
The problem is quite easy to reproduce:
1.Limit the memoryUsage in activemq.xml to -say- 50MB.
2.set producer flow control=false and disable saving messages to disk.
2.Start one producer publishing non-persistent messages with TTL=5sec
23 matches
Mail list logo