Hey James!
Sure I am! I do commit the transaction on every 1000 messages or 2 seconds
if no messages were received.
Thats why it usually works, but there is the sometimes case :)
James.Strachan wrote:
are you sure you are acknowledging the messages (either using auto-ack
mode, committing
Hello,
I want messages send by producer to the queue to be non persistent.
For this, I'm setting JMSDeliveryMode to DeliveryMode.NON_PERSISTENT.
However, this still makes the message persistent as seen via JMX. Only
calling setDeliveryMode(DeliveryMode.NON_PERSISTENT) makes the message
to be non
Hi Tim,
thx for the hint.
I don't know why, but somehow i thought that activemq would use some kind
auto-negotiation mechanism.:-)
Now i added a new connector on a different port like you said:
transportConnector name=stomp uri=stomp://localhost:61613/
But if i use a connector like that
rajdavies wrote:
nothing to be worried about - you've just encountered a half finished
implementation of duplex network connections. Hopefully this is fixed
in today's snapshot
Using the latest snapshot (from august 5), I still encounter this problem. I
also sometimes receive
Hi,
just checked the source code and looks like JMSDeliveryMode message
header is completely ignored. ActiveMQSession has the following code:
protected void send(ActiveMQMessageProducer producer,
ActiveMQDestination destination, Message message, int deliveryMode,
int priority, long
Now i added a new connector on a different port like you said:
transportConnector name=stomp uri=stomp://localhost:61613/
But if i use a connector like that one, isn't specifying the wireFormat in
tcp://172.18.117.126:61613?wireFormat=stomptransport.useAsyncSend=false
redundant?
Hello,
I'm using Apache ActiveMQ 4.1.1 with the default configuration. I
noticed that in some cases JMX expoded purge() method does not
actually purge messages from the queue.
I'm not yet able to reproduce the situation, so I'll just describe
some details. My producer side is standard Java
Hi,
I've done some tests of consumer priority and exclusive and I found that if
I start 2 consumers on the same queue (the first with a priority = 2 and the
second =1), the first will consume all messages.
It's the same thing whit consumer.exclusive.
So what's the difference between the 2.
I've
Is there anyway to remotely tell a queue to clear or reset itself?
For that matter, how would one do that locally?
--
Elliotte Rusty Harold
[EMAIL PROTECTED]
On 8/6/07, Elliotte Harold [EMAIL PROTECTED] wrote:
Is there anyway to remotely tell a queue to clear or reset itself?
For that matter, how would one do that locally?
There's a brief FAQ entry:
http://activemq.apache.org/how-do-i-purge-a-queue.html
You can use the operations on the MBeans...
Yes, we are using only queues with persistent messaging, rather than durable
topic subscriptions since we have only a single consumer per message. So,
it is normal to see the ACTIVEMQ_ACKS table empty?
Thanks,
Qian
James.Strachan wrote:
The ACKS table is only used for durable topic
On 8/6/07, Qian Su [EMAIL PROTECTED] wrote:
Yes, we are using only queues with persistent messaging, rather than durable
topic subscriptions since we have only a single consumer per message. So,
it is normal to see the ACTIVEMQ_ACKS table empty?
Yes - as I said that table is not used for
Hello
I have been trying out TransportListener in my application, I basically have
Class1 - that has the producer and acts as the Transport Listener.
Class2 - that uses the consumer to receive the messages, this acts as a
Transport Listener too.
When i bring the broker down the Class1 that
13 matches
Mail list logo
