yep, there is a durable topic consumer waiting for them

Alistair


-- 
mov eax,1
mov ebx,0
int 80h




On 21 Sep 2011, at 12:20, Gary Tully wrote:

> topic messages are only persisted to the store if there are durable
> consumers/subscriptions
> 
> On 21 September 2011 11:04, Alistair Young <alistair.yo...@uhi.ac.uk> wrote:
>> I should say, the messages go to a topic on the broker and are then routed 
>> by camel to another topc. Would camel be dropping the messages? Would they 
>> not be logged in the kahadb store no matter what though?
>> 
>> Alistair
>> 
>> 
>> --
>> mov eax,1
>> mov ebx,0
>> int 80h
>> 
>> 
>> 
>> 
>> On 21 Sep 2011, at 10:25, Alistair Young wrote:
>> 
>>> I doubt it. In a batch of three messages sent in 2 seconds, one disappeard. 
>>> Is there a default throttle limit perhaps on the broker? But surely that 
>>> would cause the producer to error out or something?
>>> 
>>> ------------------------------------
>>> Alistair Young
>>> Àrd-Innleadair air Bathar-Bog
>>> UHI@Sabhal Mòr Ostaig
>>> 
>>> 
>>> 
>>> 
>>> On 21 Sep 2011, at 09:59, Torsten Mielke wrote:
>>> 
>>>> Any chance you can reproduce this behavior in a little JUnit test case?
>>>> 
>>>> 
>>>> 
>>>> On Sep 21, 2011, at 10:15 AM, Alistair Young wrote:
>>>> 
>>>>>> There was no producer, broker or connection crash while the msg was in 
>>>>>> transit?
>>>>> no, the logs show it was up and sending
>>>>> 
>>>>>> The msg does not have an expiration time?
>>>>> 
>>>>> no
>>>>> 
>>>>>> Are you certain that no consumer has got the msg already?
>>>>> 
>>>>> yes, there's no record of it arriving at the consumer and no log of it in 
>>>>> the kahadb data store
>>>>> 
>>>>> the producer sent 49 messages in 2 seconds.The 43rd and 46th messages 
>>>>> disappeared. They never reached the broker it would seem.
>>>>> 
>>>>> ------------------------------------
>>>>> Alistair Young
>>>>> Àrd-Innleadair air Bathar-Bog
>>>>> UHI@Sabhal Mòr Ostaig
>>>> 
>>>> 
>>>> 
>>>> 
>>> 
>> 
>> 
> 
> 
> 
> -- 
> http://fusesource.com
> http://blog.garytully.com

Reply via email to