[esb-issues] [JBoss JIRA] Created: (JBESB-3630) org.jboss.soa.esb.listeners.ScheduleListener does not initiate ActionProcessingPipeline as transacted therefore transaction handling has error.

org.jboss.soa.esb.listeners.ScheduleListener does not initiate ActionProcessingPipeline as transacted therefore transaction handling has error. ----------------------------------------------------------------------------------------------------------------------------------------------- Key: JBESB-3630 URL: https://issues.jboss.org/browse/JBESB-3630 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.10, 4.9 Environment: Windows 7, Java version "1.6.0_22", JBossAS 5.1.0GA Reporter: Peer Bech Hansen When org.jboss.soa.esb.listeners.ScheduleListener instantiates and initializes the ActionProcessingPipeline, it never specifies if the ActionProcessingPipeline should be transacted or not. This means that it will never be transacted. This causes that the pipline never throws a RuntimeException back to the ScheduleListener, hence will never mark a transaction to be rolled back. Have a look at line 90 in http://anonsvn.jboss.org/repos/labs/labs/jbossesb/tags/JBESB_4_10/product... ActionProcessingPipeline is instantiated and initialized but the message setTransactional is not called. Have a look at line 692 in http://anonsvn.jboss.org/repos/labs/labs/jbossesb/tags/JBESB_4_10/product... This line will never be executed as the boolean variable 'throwRuntime' is always false for the schedule process. All this leads to the problem that line 123 of ScheduleListener.java is always executed, and the transaction is never rolled back. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira