I thought this issue could be related to JBPM-702. Unfortunately that issue was fixed in 3.2.4/3.3.0, hence 3.2.5/3.3.1 contains the fix already. Some more database issues were fixed in 3.2.6. Please try again with that version and tell us how it goes. Note that 3.2.6.SP1 is the latest release in the 3.x series. As Ronald already mentioned, the 3.3 branch is abandoned; originally it was a vehicle for new features. Due to resource constraints however, disruptive additions were pushed to 4.0 and incremental updates were backported to 3.2. HTH View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4242870#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...