Suggested Rewording in ESB Programmers' Guide --------------------------------------------- Key: JBESB-2644 URL: https://jira.jboss.org/jira/browse/JBESB-2644 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation Environment: JBoss ESB Trunk Documentation Reporter: David Le Sage I have rewritten the following section from the ESB Programmers' Guide for inclusion in the SOA Platform Documentation. Can someone please check this for technical accuracy? Request that the ESB docs please be updated with this content as well. http://anonsvn.jboss.org/repos/labs/labs/jbossesb/trunk/product/docs/Prog... Revision: 26877 Chapter: Building and Using Services. Page 41. The subsection "Transactions" currently reads: ****** Some Couriers support transactional delivery semantics, e.g., InVM and JMS. The current delivery semantics for such Couriers is based on JMS transacted sessions, i.e., the message is placed on a queue within the scope of a transaction but not actually delivered until the enclosing transaction has committed; it is then pulled by the receiver in the scope of a separate transaction. Unfortunately for synchronous request/response interactions this can result in a timeout waiting for the response since the sender blocks waiting for the response before it can terminate the delivery transaction. ****** Suggested rewording: ***** Some Couriers, such as InVM and JMS, support transactional delivery semantics. The current delivery semantics for such a Courier is based on JMS transacted sessions. In other words, the message is placed in a queue within the scope of a transaction. However, it is not actually delivered until the enclosing transaction has been committed. It is then pulled by the receiver in the scope of a separate transaction. In the case of synchronous request/response interactions this can result in a timeout waiting for the response. This is because the sender blocks while waiting for the response and terminates the delivery transaction. JBossESB 4.5 onwards attempts to detect these blocking situations and will throw an IncompatibleTransactionScopeException exception. The application should catch this and act accordingly. ***** -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira