hi
I wanna to know the relationships between DefaultMessageListenerContainer
(DMLC) CacheLevel configuration and PooledConnectionFactory in ActiveMQ.
...
failover:(tcp://localhost:
Hi,
I am evaluating ActiveMQ 5.3 and have a three node cluster with persistence
configured using kahaDB. I continuously published/consumed messages to the
brokers for a while. Then I stopped all the publishers and consumers and
purged all the messages through admin interface. I would expect ther
Hi,
My application has issues with activeMQ 5.3 when used with F5 Big-IP.
It is a J2SE application, running on Solaris and using Spring 2.5.
Messages are sent from the producer to the consumer through a Big-IP virtual
server.
If the application is run with activemq 5.1 or 5.2 and through the b
Dear all,
I'm currently having a topology problem and I'm not so sure it can be handle
in the current situation.
I want to use the topology attached in the mail.
Basically I've a client server application, and I'm using activeMQ for some
notifications.
* Every client is connected in static mode to
Thank you for the reply Dejan,
I started trying to get the standard broker configuration running in my
embedded broker while I was waiting for a response from the community. And I
can tell that jetty is starting up but I don't seem to be able to get to the
admin console, any ideas?
Thank you
D
Today, I don't use persistent messages at all, and just want to release
memory resources when messages are no longer valid.
Do you confirm me that the number of consumers (0 here), that is found into
Advisory messages, is not changed by this automatic behaviour ? It's
important for us to know th
You might also want to look into the DiscardingDLQBroker plugin.
See bottom of this page
http://activemq.apache.org/message-redelivery-and-dlq-handling.html
Joe
http://www.ttmsolutions.com
Eric-AWL wrote:
>
> Hi Joe.
>
> Thank you very much for your answer.
>
> Eric-AWL.
>
>
> Joe Ferna
Hi Joe.
Thank you very much for your answer.
Eric-AWL.
Joe Fernandez wrote:
>
> With AMQ 5.3, non-persistent messages that expire are automatically
> removed/deleted from their destination. Persistent messages are moved to
> the DLQ.
>
> By default, the destination sweeps occur every 30 sec
With AMQ 5.3, non-persistent messages that expire are automatically
removed/deleted from their destination. Persistent messages are moved to the
DLQ.
By default, the destination sweeps occur every 30 seconds. You can change
this default via the 'expireMessagesPeriod' property.
Joe
http://www.t
The test with prefetchLimit set to 1 has just completed successfully!!!
Just one last question.Suppose that prefetchLimit is 1 and one message is
sent to a queue that at the moment is not being used by the
DefaultMessageListenerContainer, than I would still have one message not
being processed un
Hi
I don't use persistance, I don't use transaction, I don't use
CLIENT_ACKNOWLEDGE, only automatic aknowledge.
I just saw in some JIRA recent exchanges that there seems to be an official
trick that automatically delete expired messages when there is no consumer
for a queue or a topic.
Can some
Hi,
Referring to the article:
http://activemq.apache.org/jms-bridge-with-oracle-aq.html
We are using this but we have the problem that if the network goes down
between the our local activeMQ broker and the remote oracleAQ broker, we
cannot recover.
Does anyone have an idea for how to use Activ
Hi,
you can not mix Jetty and Spring configuration.
Unfortunately, version 6 that we use in ActiveMQ does not support
xbean config for ssl connector. So you need to configure it using
plain spring config. Something like described here
http://coffeaelectronica.com/blog/2008/08/embedding-jetty-6-in
13 matches
Mail list logo
