<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<font size="-1"><font face="Arial">Hello,<br>
<br>
Would it be possible to get some input on this? I've read
through docs, wiki, faq, and archives and haven't found what I
need.<br>
<br>
Even if the answer is that this won't work it would help me.<br>
<br>
Thanks!<br>
<br>
Vaughn<br>
<br>
--<br>
</font></font><br>
On 4/11/2011 10:31 PM, Vaughn Vernon wrote:
<blockquote cite="mid:4DA3D5BA.9080403@shiftmethod.com" 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> </blockquote>
</body>
</html>