[JBoss jBPM] - Exception Handling in Nodes
by jgreiner
I have a question on Exception Handling in Nodes. When you have some nodes that are doing database updates/inserts and the update or insert fails the JBPM Process Instance stays stuck on that node. Basically any exception that may occur in a nodes action handler. Please note that these are not Task Nodes.
Somehow I need to move the process to a Task Node or Wait State so a user could look at the exception (database down, database full, or bad code) and take the appropriate action.
Hopefully that describes the situation clearly. My question is what is the best practice here. Couple of my ideas are....
1) Cancel that process instance and start a new process instance for exceptions of this type (ones that happen inside of action handlers).
2) Create a Task Node to act as a bucket for these exceptions. (If I do this I would like to avoid having transitions from every node to this one)
3) Create Exception Handlers. (Really not sure how this works only doc I found on this was a small blurb in the user doc)
Just wanted to see what direction people are taking with these types of exceptions.
Thanks
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4052140#4052140
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4052140
18Â years, 10Â months
[JBoss Messaging] - Re: JMS clients - JDK 1.4 compatibility
by timfox
JBAS 4.2.0 and later is Java 5 only.
This is a decision made by Red Hat / JBoss management and is outside my control. At some point JBAS has to drop support for Java 1.4 since otherwise it holds everything back and becomes difficult to support due ot the number of combinations. Most people are already using Java 5, and some are asking for Java 6 already.
JBM 1.3.0 codebase is *currently* Java 1.4 only, and the libraries are built with 1.4.
JBM 1.3.0 should run inside JBAS 4.0.x although it's not something we would recommend since it involves overwriting serveral jars in the AS with the newer version (see userguide). We don't test this configuration either, but it should work, and will allow you to use 1.4 clients. If you are also using EJB3 and/or webservices on your JBAS instance overwriting jars may cause problems with that.
Going ahead, JBM will probably become Java 5 only. Again, this is s we can take advantage of new features and not get held back in the past. It also allows us to align better with Red Hat messaging which is Java 5 only, so we'd have to change to Java 5 sooner rather than later anyway.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4052137#4052137
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4052137
18Â years, 10Â months