[JBoss jBPM] - Re: jBPM 3.1 beta 2 is not thread safe !
by kukeltje
"jonabbey" wrote :
| It appears that the problem is that the JbpmConfiguration class uses ThreadLocalStorage for the jbpmContextStacks.. If we attempt to hold a context open and call it from multiple threads, we'll see this error.
|
afaik, you are not supposed to keep them open
"jonabbey" wrote :
| Since RMI is not designed to map all calls from a client into a single thread, this means we can't reliably call JBPM methods without creating a worker thread on the server and using that for all processing from a single client.
|
make atomic calls, don't reuse contexts"jonabbey" wrote :
| I presume something similar is happening on the servlet side, where multiple servlet calls are winding up executing on different threads.
|
Each new request gets a new context
"jonabbey" wrote :
| I don't understand how this design feature can really work in a J2EE environment. Far better to give each client context its own JbpmContext object, synchronize the methods, and then let anyone call close() on it, without regard to what thread is doing the work.
Each client context (request) gets its own jbpm context in the webapp. Look at the servletfilters in 3.1 or the jsf jbpmbean in 3.2.
If I'm wrong somewhere, let me know. I'm still learning :-)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3967958#3967958
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3967958
19 years, 8 months
[JBoss jBPM] - Re: Alfresco has embedded jBPM
by kukeltje
Hi David,
Congratulations on successfully integrating jBPM in Alfresco and thanks for the compliments. It is my opinion though that the knowledge bla...bla..bla.. ;-) of te people overthere at Alfresco is also for a large part the reason implementing this went so smoothly. One of the disadvantages of open source is that anyone can use it, resulting in questions like 'what is tools.jar'
Ok, back to the subject. I'm yealous on on the amount of documentation you guys produce, the quality of it and the openness in the decisionprocess. The combination of Alfresco as it is now, jBPM, WCM and Chiba is a realy powerful combination and as you guys describe it, a platform for higer-level applications like claims management. I've spoken to one of your sales people before during my day job, but we should certainly get in touch again.
2 small questions.
regarding 2), is it a jbi compliant spi?
regarding 3), did you use the converters to convert jsf ui fields to create properly typed process variables?
For sharing the info on the ui/task dialog rendering, use the design forum or send me a direct mail (I think you still have that).
Looking forward to the preview.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3967952#3967952
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3967952
19 years, 8 months