thank you very much. is it possible for client to send a message back
to the front of the queue? I mean if consumer A can't process this
message, it create a new message(the new message's content is the same
as the old one) and put it to the front of the queue(so it can be
consumed soon). I know I can set message priority. But I don't know
whether it's performant.
On Mon, Mar 3, 2014 at 5:47 PM, Rob Davies <rajdav...@gmail.com> wrote:
> Beanstalkd might be a better fit for your use case - it's job based - and
> iirc allows the client to reject jobs
>
>
>> On 3 Mar 2014, at 09:41, Li Li <fancye...@gmail.com> wrote:
>>
>> thank you. I want to know now is that to achieve my goal(as I
>> described before), is it suitable to use activemq(or activemq+camel).
>> if it's very hard to implement with activemq(+camel), I will try other
>> solutions. or any other solutions are very welcomed. I could use any
>> related solution(e.g. rabbitmq or other message related system)
>>
>>> On Mon, Mar 3, 2014 at 5:14 PM, Noel OConnor <noel.ocon...@gmail.com> wrote:
>>> Rather than trying to change activemq you could look at implementing
>>> something with activemq and camel to provide this custom dispatch and
>>> redelivery mechanism.
>>>
>>> But as artnaseef stated it wouldn't be a simple solution.
>>>
>>>
>>>> On Mon, Mar 3, 2014 at 6:41 PM, Li Li <fancye...@gmail.com> wrote:
>>>>
>>>> sorry to hear that. I need this feature very much. is it possible to
>>>> "extend" activemq to achive this? is it difficult to modify the
>>>> dispatch logic of activemq?
>>>>
>>>>> On Mon, Mar 3, 2014 at 1:56 PM, artnaseef <a...@artnaseef.com> wrote:
>>>>> JMS does not provide such a method. You could use one queue per consumer
>>>> and have a consumer send the message back to an input queueon failure, but
>>>> it would get complex since a way of knowing which consumers rejected the
>>>> message would need to be tracked with the message, as well as knowing all
>>>> the consumers and their queues.
>>>>>
>>>>>
>>>>> Sent from my iPhone
>>>>>
>>>>>> On Mar 2, 2014, at 9:36 PM, "Li Li [via ActiveMQ]" <
>>>> ml-node+s2283324n4678441...@n4.nabble.com> wrote:
>>>>>>
>>>>>> hi all,
>>>>>> can a queue message consumer "refuse" a message after receive a
>>>> message?
>>>>>> because a client don't know the message in advance.
>>>>>> onMessage(Message msg){
>>>>>> if(CannotProcess(msg)){
>>>>>> //refuse this message
>>>>>> }
>>>>>> }
>>>>>> what I need is: if the message can't be processed by one client, it
>>>>>> can be sent to another consumer.
>>>>>> if all consumer "refuse" this message, then this message will be
>>>>>> removed to dead letter queue or to the end of the queue.
>>>>>>
>>>>>>
>>>>>> If you reply to this email, your message will be added to the
>>>> discussion below:
>>>> http://activemq.2283324.n4.nabble.com/can-a-client-refuse-a-message-tp4678441.html
>>>>>> To start a new topic under ActiveMQ - User, email
>>>> ml-node+s2283324n234180...@n4.nabble.com
>>>>>> To unsubscribe from ActiveMQ - User, click here.
>>>>>> NAML
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> View this message in context:
>>>> http://activemq.2283324.n4.nabble.com/can-a-client-refuse-a-message-tp4678441p4678446.html
>>>>> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>>>>
