[JBoss jBPM] - How to handle Process Instances that have not completed?
by james1969
We are using JPBM with a JMS Q at the start and end of the workflow engine. So basically a workflow process instance is created when a message arrives on the incoming Q, and work is carried out for that message and when the workflow completes, a status message is placed on the outgoing Q. None of our workflows involved human intervention, they are all automated. Each workflow instance is created and executed by a worker thread that is listening on the input Q.
When we do a build to production, we have to bounce our servers, so when this happens, any processes that are in mid-workflow execution will stopped and not complete due to server shutdown. So this leaves us with a handful of process instances that did not complete.
So I have to create a way of finding all outstanding process instances that are not complete and restart them. So here are my questions:
1. Is JBPM smart enough to pick up where it left off with a given process that is already in progress but did not complete? Or do I have to determine where i left off, and restart that process at the node of choice?
2. Or should I just find the processes that has not complete and extract the relavent data and start a new process instance all together?
3. Or is there a better way to approach this issue all together?
thanks,
James
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4004024#4004024
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4004024
19 years, 3 months
[JBoss jBPM] - Re: Question: hierarchical model (graph nesting) ?
by estaub
Maurice,
I think you're looking for a level of metadata that's not at all present in jBPM.
A more general case of what you're looking for is a reusable node template, which has defined inputs and outputs that are bound in a given process definition to specific values (sometimes process variables, sometimes other things). Extending this, you might consider "stencils" (a la Visio) that are collections of such node templates that apply to a specific application domain.
This is all blue sky - maybe Ronald will say whether there's any work being considered in this direction.
You need to think carefully about whether a subprocess will do what you need. The fact that it has a separate process identity may complicate your life, depending on how you need to do things like externally monitor the process state. If you want to investigate the state of the outer process down to the states within the inner process, there's extra work involved.
-Ed Staub
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4004018#4004018
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4004018
19 years, 3 months
[JBoss Seam] - Can't get the Seam Exception Handling feature to work.
by whuang
I try to setup Seam to handle all JSF exceptions and redirect to a generic error page, but still when exceptions occur, it is not redirecting in to my generic error page.
Based on the Seam doc, I config my exceptions.xml in WEB-INF
<!DOCTYPE exceptions PUBLIC
| "-//JBoss/Seam Exceptions Configuration DTD 1.1//EN"
| "http://jboss.com/products/seam/exceptions-1.1.dtd">
|
| <exceptions>
| <exception>
| <redirect view-id="/error/error.xhtml">Unexpected failure</redirect>
| <end-conversation/>
| </exception>
|
| </exceptions>
and on web.xml
<!-- =================================================================== -->
| <!-- Seam -->
| <!-- =================================================================== -->
| <listener>
| <listener-class>org.jboss.seam.servlet.SeamListener</listener-class>
| </listener>
|
| <!-- Propagate conversations across redirects -->
| <filter>
| <filter-name>Seam Redirect Filter</filter-name>
| <filter-class>org.jboss.seam.servlet.SeamRedirectFilter</filter-class>
| </filter>
| <filter-mapping>
| <filter-name>Seam Redirect Filter</filter-name>
| <servlet-name>Faces Servlet</servlet-name>
| </filter-mapping>
|
| <!-- Needed to ensure safe tx cleanup when using Seam-managed sessions/persistence contexts -->
| <filter>
| <filter-name>Seam Exception Filter</filter-name>
| <filter-class>org.jboss.seam.servlet.SeamExceptionFilter</filter-class>
| </filter>
| <filter-mapping>
| <filter-name>Seam Exception Filter</filter-name>
| <url-pattern>/*</url-pattern>
| </filter-mapping>
|
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4004003#4004003
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4004003
19 years, 3 months