I could reproduce this with your suggestions of throwing an exception in an ActionHandler.
But only if I signal this from a custom application, not from within the default jBPM 3.2
web app. So I suspect this is a configuration issue. I'll try to dig deeper and let
you know when I find something...
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4048245#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...