2008/12/11 Dixie :
>
> Does ActiveMQ build a .bindings file like SunMQ does.
What does .bindings do? Setup a JNDI context?
If so this might help
http://activemq.apache.org/jndi-support.html
--
James
---
http://macstrac.blogspot.com/
Open Source Integration
http://fusesource.com/
Does ActiveMQ build a .bindings file like SunMQ does. Kind of new to
ActiveMQ so keep the technical responses so a third grader could understand
them. =^D
--
View this message in context:
http://www.nabble.com/bindings-file-like-SunMQ-tp20964777p20964777.html
Sent from the ActiveMQ - User maili
Hi,
Using TimeToLive on message producer with redelivery mechanism seems to have
a problem. When message expires between delivery and first redelivery (after
first calling session recover() - CLINET_ACK) clinet stops to receive and
messages aren't post even to DLQ. Any further sending has no effec
Okay, thanks, that looks like something in the right direction, though I
think it will take me some time to understand camel and how to use it with
activemq.
Thanks again,
Marko
James.Strachan wrote:
>
> 2008/12/11 mmocnik <[EMAIL PROTECTED]>:
>>
>>
>>
>> James.Strachan wrote:
>>>
>>> 2008/12
2008/12/11 mmocnik <[EMAIL PROTECTED]>:
>
>
>
> James.Strachan wrote:
>>
>> 2008/12/11 mmocnik <[EMAIL PROTECTED]>:
>>>
>>>
>>> James.Strachan wrote:
> [...]
though I think putting redelivered messages at the tail of the queue
(so its dispatched last) is what you want - so resend
James.Strachan wrote:
>
> 2008/12/11 mmocnik <[EMAIL PROTECTED]>:
>>
>>
>> James.Strachan wrote:
>>>
[...]
>>> though I think putting redelivered messages at the tail of the queue
>>> (so its dispatched last) is what you want - so resending the message
>>> rather than rolling back & closin
2008/12/11 mmocnik <[EMAIL PROTECTED]>:
>
>
> James.Strachan wrote:
>>
>>> [...]
>> though I think putting redelivered messages at the tail of the queue
>> (so its dispatched last) is what you want - so resending the message
>> rather than rolling back & closing is probably more suitable
>>
> Yes,
James.Strachan wrote:
>
>> [...]
> though I think putting redelivered messages at the tail of the queue
> (so its dispatched last) is what you want - so resending the message
> rather than rolling back & closing is probably more suitable
>
Yes, that is what I want to achieve, but if I do it tha
Destination is null for some reason. There seems to be a "not null"
guard on every other use of destination save this one.
Can you raise a jira issue and supply as much info as you can about
the context of this exception?
The simple fix is to add the null check here also, but it is not clear
from
2008/12/11 James Strachan <[EMAIL PROTECTED]>:
> 2008/12/11 mmocnik <[EMAIL PROTECTED]>:
>>
>>
>>
>> James.Strachan wrote:
>>>
[...]
>>> Normally redelivery of the last message occurs - to avoid breaking
>>> order. Is that what you need?
>>>
>>> If you are not seeing this - are you closing & re
2008/12/11 mmocnik <[EMAIL PROTECTED]>:
>
>
>
> James.Strachan wrote:
>>
>>>[...]
>> Normally redelivery of the last message occurs - to avoid breaking
>> order. Is that what you need?
>>
>> If you are not seeing this - are you closing & recreating the
>> MessageConsumer on rollback?
>>
>
> Oh, oka
James.Strachan wrote:
>
>>[...]
> Normally redelivery of the last message occurs - to avoid breaking
> order. Is that what you need?
>
> If you are not seeing this - are you closing & recreating the
> MessageConsumer on rollback?
>
Oh, okay, that is what I am seeing.
But its not what I want
12 matches
Mail list logo