<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body bgcolor="#ffffff" text="#000000">
<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>
</body>
</html>