activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pesochinskiy, Vadim \(MSCIBARRA\)" <>
Subject RE: Bad message problem
Date Fri, 23 Jun 2006 02:11:51 GMT
<HTML xmlns:eXclaimer="" xmlns:msxsl="urn:schemas-microsoft-com:xslt"
<META http-equiv="Content-Type" content="text/html; charset=UTF-16">

<DIV id=idOWAReplyText53959 dir=ltr>
<DIV dir=ltr><FONT face=Arial color=#000000 size=2>Answering my own question.
hope AMQ complies with this. Thanks.</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV dir=ltr>
<DIV><FONT face=Arial size=2>Abstract from JMS spec 1.1</FONT></DIV>
<DIV><I><FONT face="Times New Roman" size=4>
<P align=left><FONT face="Courier New" 
<P align=left><FONT face="Courier New">If a client receives a message with the

</FONT><I><FONT face="Courier New">JMSRedelivered </FONT></I><FONT

face="Courier New">indicator set, it is likely, </FONT><FONT 
face="Courier New">but not guaranteed, that this message was delivered but not 
acknowledged in </FONT><FONT face="Courier New">the past. In general, a provider

must set the </FONT><I><FONT face="Courier New">JMSRedelivered </FONT></I><FONT

face="Times New Roman"><FONT face="Courier New">message header </FONT><FONT

face="Courier New">field of a message whenever it is redelivering a message. If 
the field is set to </FONT><FONT face="Courier New">true, it is an indication
the consuming application that the message may </FONT><FONT 
face="Courier New">have been delivered in the past and that the application 
should take extra </FONT><FONT face="Courier New">precautions to prevent 
duplicate processing. See Section 4.4.11, &#8220;Message </FONT><FONT 
face="Courier New">Acknowledgment,&#8221; for more information. </FONT><FONT

face="Courier New">This header field has no meaning on send and is left 
unassigned by the </FONT><FONT face="Courier New">sending 
<DIV dir=ltr><BR>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> Pesochinskiy, Vadim 
(MSCIBARRA)<BR><B>Sent:</B> Thu 6/22/2006 9:13 PM<BR><B>To:</B><BR><B>Subject:</B> Bad message 
<DIV dir=ltr>
<DIV><FONT face=Arial color=#000000 size=2>Hi!</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>I have following problem.&nbsp;I have to use

reliable delivery and I have to make sure that each message is processed. If I 
have a bad message which&nbsp;kills the consumer ;-) (I know this is stupid, but 
consumer is JNI call to C++ and it is outside of my control&nbsp;...).&nbsp;If 
transaction is not committed the message will not leave the queue and it will 
kill&nbsp;next consumer which will try&nbsp;to process it&nbsp;(another instance

of consumer of the same type). Is there any mechanism which will help me to 
solve this type of problems? E.g. maximum number of retries to process a message 
before it is dumped. </FONT><FONT face=Arial size=2>Thanks a lot.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>- Vadim.</FONT></DIV></DIV></DIV>
<P CLASS="BulletedList" STYLE="MARGIN: 0in 0in 0pt; TEXT-INDENT: 0in; mso-list: none; tab-stops:
.5in"><SPAN STYLE="FONT-SIZE: 8pt; COLOR: gray; mso-bidi-font-family: Arial"><FONT
FACE="Arial">NOTICE: If received in error, please destroy and notify sender.<SPAN STYLE="mso-spacerun:
yes">&nbsp; </SPAN>Sender does not waive confidentiality or privilege, and use
is prohibited.</FONT></SPAN></P>

View raw message