[JBoss jBPM] - How to approach error handling in a Process? Thoughts and c
by james1969
I am working on a high volume application where JPBM is being used to manage assets that need to be programatically modified. I currently have 1 workflow for every asset type. Within each workflow, I'm using nodetype 'node' where each node executes a basic operation (ActionHandler with code to do the operation) on the asset programatically (no human intervention).
Because these are automated processes and each node has a predefined operation on the asset, I have to handle error conditions. My thought is to have a generic global error node to transition to if any exceptions are thrown in each node. But I have found that you can only transition to nodes defined within a process definition. So in my scenario with multiple process definitions, I would need to define an error node in each process. So my thought about having 1 global error node won't work.
Another thought is to define an 'error process'. Is there a way to jump from one process instance to a completely different and new process instance? So for example, I'm currently executing in process A instance A1 and I come across an exception, can I create a new process instance B1 of process B and transition from A1 to B1?
Comments and thoughts please?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3979205#3979205
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3979205
19 years, 8 months
[EJB/JBoss] - EJB: isModified - behavior change from 3.2.6 to 4.0
by smohan
Hi,
I couldn't find any FAQ/Documentation that describes this so I am creating a new topic. Please point me to appropriate documentation if it exists.
We were running jboss 3.2.6 with 2.0 EJBs for a while and were using the isModified() method explicitly in ejbStore() to determine if a bean should be stored. The beans managed their own persistence (BMP). Recently we switched to 4.0.3SP1 and observed that the ejbStore() is no longer being called, which I traced back to the isModified returning false. This is documented behavior and as per jboss documentation this behavior should have existed after 3.2.3. Did this actually change after 3.2.6?
In the standardjboss.xml, I see that <call-ejb-store-on-clean> is no longer part of the BMP container configuration, while it was set to true in 3.2.6. Again according to documentation, this is true by default, so I guess it shouldn't matter. Does this mean that even though isModified() returns false, ejbStore will be called? I don't see this happening. I set the element "call-ejb-store-on-clean" explicitly to true in standardjboss.xml for BMP configurations. The ejbStore() still doesn't get called - I verified this by installing breakpoints in isModified() (where it stops to get a value of false) and in ejbStore (which is not executed).
I am running jboss in cluster mode (although I currently have only one node) with the EJBs configured to be have clustered element set to true in jboss.xml.
I will really appreciate if you would let me know whether it is a new issue/already known issue. If my understanding of the issue is incorrect or I am looking at the wrong place, would you please let me know of the same.
Thanks for your time,
Sachin Mohan.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3979202#3979202
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3979202
19 years, 8 months