The producer would not wait unless the broker is configured for straight
through processing. By default dispatch is asynchronous.
This looks like a disk limit. With the route started there is twice as much
disk io b/c each message will be persisted twice. By default a producer
waits till the messa
Realized that Camel config is not appearing in email readers, so here is the
route:
http://camel.apache.org/schema/spring";>
Q1 to Q2
Dejan Bosanac writes:
> Take a look at StompTest.testDurableUnsub()
>
> https://fisheye6.atlassian.com/browse/activemq/trunk/activemq-core/src/test/java/org/apache/activemq/transport/stomp/StompTest.java?hb=true
>
>
> It contains some example that should work. If it's not working, can you
> pleas
embedded activemq:
org.apache.activemq
activemq-camel
5.2.0
191 messages were sent but when the consumer reconnected after 3 days they
weren't there.
Alistair
--
mov eax,1
mov ebx,0
int 80h
On 27 May 2011, at 15:04, Gary Tully wrote:
> what version and what sort of message rate
what version and what sort of message rate. So how many messages would
have accumulated?
On 27 May 2011 13:00, Alistair Young wrote:
> Hi there,
>
> I have a durable topic consumer that was killed by a power outage while
> consuming messages. It was down for 3 days and when it reconnected, all t
Take a look at StompTest.testDurableUnsub()
https://fisheye6.atlassian.com/browse/activemq/trunk/activemq-core/src/test/java/org/apache/activemq/transport/stomp/StompTest.java?hb=true
It contains some example that should work. If it's not working, can you
please provide a similar test case
I would start with a simple use case and verify from trace level
logging that everything is as expected with respect to transaction
demarcation and connection pooling.
But note, that the RA should do its own pooling and transaction
management as the contracts between j2e and a resource manager (RA
Timothy Bish
writes:
> Refer to the ActiveMQ documentation on Stomp here:
> http://activemq.apache.org/stomp.html
>
> Note the discussion at the bottom of the page for the subscription name
> property,
>
> "For durable topic subscriptions you must specify the same clientId on
> the connection and
I suspect that, because I am using a connection pool with the RA adapter,
somewhere somehow the transaction information is not cleared when the
connection is returned to the pool. In another post earlier, I had another
error:
Caused by: javax.jms.JMSException: The resource is allready being used in
Update:
I have browsed the stomp connector sources and managed to unsubscribe
by specifying subscription name in id: header, but the durable
subscription is still not gone from the console, and after subscribing
again i get all messages in duplicate.
UNSUBSCRIBE
destination:/topic/COMMAND.broa
On Fri, 2011-05-27 at 13:04 +0200, Aleksandar Ivanisevic wrote:
>
> Hi,
>
> what is the status on durable topic subscriptions under STOMP? Should
> STOMP unsubscribe remove the durable subscription or not?
>
> according to
>
> http://mail-archives.apache.org/mod_mbox/activemq-users/200808.mbox
Hi there,
I have a durable topic consumer that was killed by a power outage while
consuming messages. It was down for 3 days and when it reconnected, all the
remaining messages on the topic had disappeared. It only received messages on
the topic after it reconnected. I've since shut it down, wa
Hi,
what is the status on durable topic subscriptions under STOMP? Should
STOMP unsubscribe remove the durable subscription or not?
according to
http://mail-archives.apache.org/mod_mbox/activemq-users/200808.mbox/%3c19181282.p...@talk.nabble.com%3E
and
https://issues.apache.org/jira/browse/
I'll answer my own question. It is NOT possible to use the IBM sender and
receiver channels in a JMS scenario. They are purely an IBM invention and
not part of the JMS spec. This is what I had thought all along. I had hoped
that perhaps some of the abstraction levels introduced on top of JMS might
In almost similar scenario, I put TimeToLive properties in the messages.
In they aren't consumed after certain periods, it will go to default queue
(ActiveMQ.DLQ if i'm not mistaken)
On Thu, May 26, 2011 at 6:26 PM, Aneesh wrote:
> Hi
>
> Am pretty new to ActiveMQ and i am now looking for a sol
a slow consumer will keep at maximum "prefetch" number messages from
other consumers. The dispatch loop will ignore any "full" consumers.
I think setting prefetch to 0 will alleviate the symptom you are seeing.
http://activemq.apache.org/what-is-the-prefetch-limit-for.html
On 27 May 2011 09:38, Na
Hi ,
I know an alternate solution for ur problem.
use JMX . ur producer periodically checks for the size of the queue and
if the number of messages is greater than some 'count' ( specified by user
) , producer will wait until the number of messages goes below the 'count' .
take a loo
Hi all ,
Can anyone tell me how to change the mesage dispatch policy in apache
activeMQ ( am using version 5.4.2).
As all of u know , default dispatch policy is RoundRobin. But the
problem with that policy is , if one consumer goes down or is blocked for
some reason , other consumer
18 matches
Mail list logo