Presumably, some error occurred that led to ZPublisher aborting the transaction. Since transaction abort is never supposed to fail, perhaps ZPublisher doesn't use the same mechanism to report transaction abort failures.
Yeah, that makes sense but...
It looks like DCOracle2 needs to be more careful about propagating errors during the second phase of a transaction.
...some of the errors (ie, once the DA connection is trashed ;-) don't occur in those dodgy parts of the transaction, and yet there's still no errro logged in the error_log...
curiouser and curiouser...
Zope-Dev maillist - [EMAIL PROTECTED]
** No cross posts or HTML encoding! **
(Related lists - http://mail.zope.org/mailman/listinfo/zope-announce