<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
<font size="-1"><font face="Arial">Thanks much, Tim. That helps me
make a decision. I always assign a message id so I can use
message de-duplication at the subscriber side. I may use message
command idempotence in some cases.<br>
<br>
Kind regards,<br>
<br>
Vaughn<br>
<br>
--<br>
</font></font><br>
On 4/13/2011 8:02 AM, Tim Fox wrote:
<blockquote cite="mid:4DA5ACEC.7080509@rabbitmq.com" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
RabbitMQ clients don't expose any sort of XA/JTA interface so
enlisting a Rabbit local tx in a larger global XA tx won't be
possible.<br>
<br>
You can probably find other ways to ensure atomicity by some kind
of resend approach and detecting duplicates.<br>
<br>
On -10/01/37 20:59, Vaughn Vernon wrote:
<blockquote cite="mid:%3C4DA3D5BA.9080403@shiftmethod.com%3E"
type="cite">
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<font size="-1"><font face="Arial">Hey,<br>
<br>
How do you recommend handling the case where a local
application database transaction may commit or rollback, and
you don't want to publish the event unless it commits? In
other words:<br>
<br>
1 - application transaction begins<br>
2 - application writes to database<br>
3 - rmq message published (publish must succeed for
application transaction to succeed)<br>
4 - application transaction commits; however, issue occurs,
transaction does not complete; must prevent rmq publish<br>
<br>
</font></font><font size="-1"><font face="Arial">Can't move #3
after #4 because the possibility exists that rmq publish
will fail and message will never be published.</font></font><br>
<font size="-1"><font face="Arial"><br>
This points to 2pc of application and rmq, but unavailable
for the application database. BTW, does rmq 2pc with other
databases?<br>
<br>
Vaughn<br>
<br>
--<br>
<br>
</font></font>
<pre wrap=""><fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
rabbitmq-discuss mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:rabbitmq-discuss@lists.rabbitmq.com">rabbitmq-discuss@lists.rabbitmq.com</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss">https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</a>
</pre>
</blockquote>
<br>
<pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
rabbitmq-discuss mailing list
<a class="moz-txt-link-abbreviated" href="mailto:rabbitmq-discuss@lists.rabbitmq.com">rabbitmq-discuss@lists.rabbitmq.com</a>
<a class="moz-txt-link-freetext" href="https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss">https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</a>
</pre>
</blockquote>
</body>
</html>