yesnid wrote:
>
> So would a non zero TTL be required for the eviction to work?
>
> Thank you.
>
Yes, a non-zero TTL is required to expire the message. The
messageEvictionStrategy is used only to remove expired messages.
--
View this message in context:
http://www.nabble.com/Queue-Pol
So would a non zero TTL be required for the eviction to work?
Thank you.
jbekas wrote:
>
>
> yesnid wrote:
>>
>> I have tried this with a TTL of 0 essentially infinite for the message
>> and for non-zero values, but neither yielded any results for me. Also My
>> queue that I am trying to ev
yesnid wrote:
>
> I have tried this with a TTL of 0 essentially infinite for the message and
> for non-zero values, but neither yielded any results for me. Also My queue
> that I am trying to evict from has no consumer on it, does that make a
> difference, I am beginning to suspect from other po
Hello,
All I did was take the examples from the link I posted, and place them into
the default activeMQ configuration file: (see below)
I have tried this with a TTL of 0 essentially infinite for the message and
for non-zero values, but neither yielded any results for me. Also My queue
that I am
yesnid wrote:
>
> I am trying to get an eviction policy as described here:
>
> http://activemq.apache.org/slow-consumer-handling.html
>
> working for the Queues on my broker, I have attempted several
> configurations of different types and don't seem to be having any luck
> getting messages to
Hello. Has anyone used the 1.1 binaries for NMS and NMS.ActiveMQ from trunk
and the failover: protocol?
I'm experiencing a lot of slowness and I've found at least one comment (on
item in issue tracker) stating the same.
http://issues.apache.org/activemq/browse/AMQNET-26?focusedCommentId=47183&p
Hello all,
I am trying to get an eviction policy as described here:
http://activemq.apache.org/slow-consumer-handling.html
working for the Queues on my broker, I have attempted several configurations
of different types and don't seem to be having any luck getting messages to
expire is there som
I found it!!
ActiveMQSession.INDIVIDUAL_ACKNOWLEDGE
Doctor, you are genious!
Thanks!
--
View this message in context:
http://www.nabble.com/Subscribe-%2B-Client-aknowledge-problem-tp23020938p23021595.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Ok, here what I read about receive();
"The standard behavior of this method is to cause the session to acknowledge
all messages that have been consumed by any consumer in the session since
the last time the method was invoked."
So how can I aknowledge only one message? Does using com.sun.messagi
My code:
QueueConnection s_queueConnection =
s_connectionFactory.createQueueConnection();
Session m_queueSessionConsume = s_queueConnection.createQueueSession(false,
Session.CLIENT_ACKNOWLEDGE);
Queue m_queue = m_queueSessionConsume.createQueue("MyQueue");
m_queueReceiver = m_queueSessionConsume
I have a queue,
I have a producer that sends messages to it,
And I have a consumer that synchronously reads messages (by
MessageConsumer.receive()) and acknowledges it if message is correct (my own
validation), then going to listen next messages. If it is not correct, then
it doesn't call aknowled
You'll probably have an object that implements Broker or extends
BrokerFilter. That object's addConnection() method is passed a reference to
a ConnectionContext object. Use that object's getConnection() method to get
the corresponding Connection object, which has a getRemoteAddress() method
that
Hi there,
Does anyone know if it is possible to determine what interface a connection
came in on while inside a JAAS plugin? I would like to know if the client
has connected from within a local machine and, if so, assume authorisation.
However if the client has connected from an outside address,
13 matches
Mail list logo
