" since
>>>>> that was the prefix, and didn't work either.
>>>>> I worked around the problem by creating a broker plugin filter, and
>>>>> doing my operations in there
>>>>>
>>>>> Filip
>>>>>
gt; that was the prefix, and didn't work either.
>>>>> I worked around the problem by creating a broker plugin filter, and
>>>>> doing my operations in there
>>>>>
>>>>> Filip
>>>>>
>>>>> Hiram Chirino wrote:
>>>>>
>>>>>
>>>>>> I guess you want an entry for all topics or all queues right (since
>>>>>> the actually names are dynamic)?
>>>>>>
>>>>>> One way to do it might be to use topic='>' since that would match all
>>>>>> topics (temp topics are still topics). But I guess we should have
>>>>>> something a little bette than that.
>>>>>>
>>>>>> On Fri, May 9, 2008 at 7:45 PM, Filip Hanik - Dev Lists
>>>>>> <[EMAIL PROTECTED]> wrote:
>>>>>>
>>>>>>
>>>>>>
>>>>>>> is there a way to create a
>>>>>>> for temporary topics?
>>>>>>>
>>>>>>> Filip
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>
>
--
View this message in context:
http://www.nabble.com/create-policyentry-for-temp-topics-tp17158262p17943349.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
that's wasn't possible in our case, since the app was 3rd party, with no
source code, we needed to override the "persistent" on the server
Filip
Rob Davies wrote:
You can always ensure the messages sent on the temporary topics are
non-persistent - (by setting the delivery mode on the producer)
You can always ensure the messages sent on the temporary topics are
non-persistent - (by setting the delivery mode on the producer) - and
then set the DLQ strategy property processNonPersistent=false
cheers,
Rob
http://open.iona.com/products/enterprise-activemq
http://rajdavies.blogspot.co
that's absolutely doable, what you'd need to do is set
producerFlowControl="false" on your policy entries,
that's what we did.
then we setup the pendingMessageLimitStrategy to 1000, and our problem
was that when a message was discarded it went to the DLQ and eventually
caused OOME.
The Broke
are still topics). But I guess we should have
>>>> something a little bette than that.
>>>>
>>>> On Fri, May 9, 2008 at 7:45 PM, Filip Hanik - Dev Lists
>>>> <[EMAIL PROTECTED]> wrote:
>>>>
>>>>
>>>>> is there a way to create a
>>>>> for temporary topics?
>>>>>
>>>>> Filip
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>
>
--
View this message in context:
http://www.nabble.com/create-policyentry-for-temp-topics-tp17158262s2354p17342325.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Sure Badri,
our use case that we were dropping messages on the broker, so they go to
the Dead Letter Queue (DLQ),
however, for temporary topics, we didn't want that to happen, and since
I wasn't able to configure a policy for temp topics where we could plug
in a discarding DLQ, then we just did
5 PM, Filip Hanik - Dev Lists
>> <[EMAIL PROTECTED]> wrote:
>>
>>> is there a way to create a
>>> for temporary topics?
>>>
>>> Filip
>>>
>>>
>>
>>
>>
>>
>
>
>
--
View this message in context:
http://www.nabble.com/create-policyentry-for-temp-topics-tp17158262s2354p17329027.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
I couldn't get that to work properly, I even tried topic="ID>" since
that was the prefix, and didn't work either.
I worked around the problem by creating a broker plugin filter, and
doing my operations in there
Filip
Hiram Chirino wrote:
I guess you want an entry for all topics or all queues
I guess you want an entry for all topics or all queues right (since
the actually names are dynamic)?
One way to do it might be to use topic='>' since that would match all
topics (temp topics are still topics). But I guess we should have
something a little bette than that.
On Fri, May 9, 2008 at
is there a way to create a
for temporary topics?
Filip
11 matches
Mail list logo