Hi there, I have a question concerning the best practice in the setup of a
broker network with Oracle and ActiveMQ.
I am actually facing a case where during consumption of messages, the number
of connection open by the brokers to the database, is huge, and eventually
will block the listener from
Is there a way, either with filters or timeouts on queues, to get my hands on
any messages that have been sitting in the queue for "too long"?
My situtation/plan is to have a queue with multiple consumers. Each
consumer will be using a selector to decide which messages to consume.
Under ideal c
AFAIK the expired message will be moved into the DeadLetterQueue.
Since you're able to configure the DLQ it should be possible to do
what you want (using AMQ5).
There's an open issue with expired message not being processed until
someone tries to consume them (The bug was AMQ-1112 I think). So sinc
That was my first expectation - that they would go to the DLQ but they never
appeared to go there. Perhaps the bug you mention is the reason. Having
found this behaviour I went and did some searching - the outcome was that it
sounded like brokers were expected to destroy the expired messages.
I
Hi All,
When is the ActiveMQ 5.0 stable version is expected to release.
Thanks and Regards,
Gokulal.K
--
View this message in context:
http://www.nabble.com/ActiveMQ-5.0-Release-Date--tf4353522s2354.html#a12405041
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Hi,
We have been having cases recently were people cannnot connect to our
ActiveMQ (4.1) when using proxies. After lots of digging, i have found that
the issue may be in this class:
org.apache.activemq.transport.tcp.TcpTransport and especially in the
connect() method. There we call remoteAddress.
I'm having trouble getting my head around some of ActiveMQs authorization
settings. I have a relatively specific use case I'm trying to meet, but
can't quite figure out what the appropriate permission settings are. The
read and write permissions I understand. The admin and temporary destination
pe
Another fly in the ointment is how should the Advisory destinations be
permissioned for the client group?
--
View this message in context:
http://www.nabble.com/Authorization-Security-Question-tf4354381s2354.html#a12407602
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
If all else fails, you can perhaps use a QueueBrowser to monitor the messages
on the queue.
ttmdev
DominicTulley wrote:
>
> That was my first expectation - that they would go to the DLQ but they
> never appeared to go there. Perhaps the bug you mention is the reason.
> Having found this beh
Possibly you could just create consumers where effectively (not real code):
sendTime < now() - 10min
and just create a new consumer, receive until there's nothing left, then try
again a minute later.
you'd be able to yank from one queue and re-publish to another. I'd bet you
could do this with c
10 matches
Mail list logo