Thank you, Jan
>
> > -Original Message-
> > From: Pavel Moravec [mailto:pmora...@redhat.com]
> > Sent: Friday, November 09, 2012 2:59 PM
> > To: users@qpid.apache.org
> > Subject: Re: Java client and message release or reject
> >
> > Hi Jan,
>
oravec [mailto:pmora...@redhat.com]
> Sent: Friday, November 09, 2012 2:59 PM
> To: users@qpid.apache.org
> Subject: Re: Java client and message release or reject
>
> Hi Jan,
> greping source code, I found just one possibility:
>
> ((AMQSession) ssn).rejectMessage((Ab
@qpid.apache.org
> Sent: Thursday, November 8, 2012 6:13:57 PM
> Subject: RE: Java client and message release or reject
>
> Does the Java client support message reject? I am not speaking about
> JMS API, but it seems that even internally there is no support for
> reject, just re
.cz]
> Sent: Thursday, November 08, 2012 6:14 PM
> To: users@qpid.apache.org
> Subject: RE: Java client and message release or reject
>
> Does the Java client support message reject? I am not speaking about JMS
> API, but it seems that even internally there is no support fo
ood.cz]
> Sent: Thursday, November 08, 2012 9:41 AM
> To: users@qpid.apache.org
> Subject: RE: Java client and message release or reject
>
> Hi Phil,
>
> I ommitted this in my question, I am using C++ broker.
>
> Currenlty I am testing a hack - casting JMS object to
Hi Gordon,
Yes, you're right - jmsSession.rollback() does result in an AMQP
message.release command.
Phil
On 8 November 2012 08:44, Gordon Sim wrote:
> On 11/08/2012 08:30 AM, Phil Harvey wrote:
>
>> The delivery count is incremented each time the message is rejected by the
>> client, eg when
On 11/08/2012 08:30 AM, Phil Harvey wrote:
The delivery count is incremented each time the message is rejected by the
client, eg when it explicitly calls session.rollback() after your
application code decides that its format is wrong.
Does that actually reject (in 0-10 parlance) or just release
Subject: Re: Java client and message release or reject
>
> Jan,
>
> I'm not sure which broker you're using. If you're using the Java Broker,
> note that you can configure it to send messages to the dead letter queue
> after N attempts with this sort of thing in you
Jan,
I'm not sure which broker you're using. If you're using the Java Broker,
note that you can configure it to send messages to the dead letter queue
after N attempts with this sort of thing in your virtualhosts.xml:
...
1
...
The delivery count is incremented each tim
On 11/07/2012 12:11 PM, Jan Bares wrote:
we are planning to reject messages that do not satisfy message contract (e.g.
message is of wrong format). The reject and DLQ seems to be the right solution
for this problem.
At present the only thing I can suggest is that you have the client
itself s
Wednesday, November 07, 2012 11:53 AM
> To: users@qpid.apache.org
> Subject: Re: Java client and message release or reject
>
> On 11/07/2012 09:09 AM, Jan Bares wrote:
> > how can I release or reject a message in Java client? JMS API has no
> methods like that. What is the sugge
On 11/07/2012 09:09 AM, Jan Bares wrote:
how can I release or reject a message in Java client? JMS API has no methods
like that. What is the suggested method?
What is/(are) the use case(s) where you need to explicitly release or
reject? Knowing that may help provide a better answer.
The Qpi
Hi,
how can I release or reject a message in Java client? JMS API has no methods
like that. What is the suggested method?
Thanks, Jan
DISCLAIMER
WOOD & Company Financial Services, a.s. and its branches are authorized and
regulated by the CNB as Home State regulator and in Poland by the KNF,
13 matches
Mail list logo
