[jBPM] - Re: jBPM5 - Can't Scale, Won't Scale
by Herman Post
Herman Post [https://community.jboss.org/people/hbpost] created the discussion
"Re: jBPM5 - Can't Scale, Won't Scale"
To view the discussion, visit: https://community.jboss.org/message/776514#776514
--------------------------------------------------------------
With respect to incomplete process instances, we have one main process per kSession, and it is possible to determine if the process instance is active by call ProcessInstance.getState(). Our client applications know which sessions belong to them and interact with the session and process and tasks until the process becomes completed.
Timers seem to present challanges to scalabilty though. For us it means we have to keep sessions with active processes in memory and manage them, and simply use the persistence mechanism for recovery from failure. Clustering seems like alot of headache. So what you're left with for scalabilty is some active grid solution where client requests are routed to the proper server. I believe this is the solution Mauricio has been working on.
We too would be interested in further discussion on this.
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/776514#776514]
Start a new discussion in jBPM at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
13 years, 5 months
[jBPM] - Cannot Add Task
by tmmaluleke
tmmaluleke [https://community.jboss.org/people/tmmaluleke] created the discussion
"Cannot Add Task"
To view the discussion, visit: https://community.jboss.org/message/776157#776157
--------------------------------------------------------------
Hello,
I'm trying to run my project and I ecounted this problem what may be the course of this Error: please help?
org.jbpm.task.service.CannotAddTaskException: Server-side Exception: There are no known Business Administrators, task cannot be created according to WS-HT specification
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
at java.lang.reflect.Constructor.newInstance(Unknown Source)
at org.jbpm.task.service.responsehandlers.AbstractBaseResponseHandler.createSideException(AbstractBaseResponseHandler.java:73)
at org.jbpm.task.service.responsehandlers.AbstractBlockingResponseHandler.waitTillDone(AbstractBlockingResponseHandler.java:48)
at org.jbpm.process.workitem.wsht.BlockingAddTaskResponseHandler.getTaskId(BlockingAddTaskResponseHandler.java:38)
at register.ProcessTest.main(ProcessTest.java:74)
cheers
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/776157#776157]
Start a new discussion in jBPM at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
13 years, 5 months
[jBPM] - jBPM 5.3 - simple workflow w/ non-terminating end event that terminates the process
by eodsf
eodsf [https://community.jboss.org/people/eodsf] created the discussion
"jBPM 5.3 - simple workflow w/ non-terminating end event that terminates the process"
To view the discussion, visit: https://community.jboss.org/message/776288#776288
--------------------------------------------------------------
https://community.jboss.org/servlet/JiveServlet/showImage/2-776288-19879/... https://community.jboss.org/servlet/JiveServlet/downloadImage/2-776288-19...
Hi,
My company is evaluating jBPM, and I'm coming up to speed on it. While trying out some things in the Eclipse modeler & testing w/ unit tests, I've run into some issues w/ early experimentation. This is likely to be the first of some posts as I try to model what we need in our business execution & find out what is feasible.
The above is an example of a simple workflow I have that have that terminates early before I can send in an event that will trigger the 'Main task'; acc.to the documentation '
A Signal Event should have no incoming connections and one outgoing connection' (http://docs.jboss.org/jbpm/v5.1/userguide/ch05.html), suggesting that this workflow should wait for a signal event of the type expected before executing the 'Main task' and then terminating. What I am seeing in my unit test is that after executing the 'Initial' task, the process instance is in a 'STATE_COMPLETE' (2) state. Further code that signals events w/ the expected event type (ksession1.signalEvent(....)) does not trigger execution of the 'Main task' (nor does it throw any exceptions or errors).
Some snippets from my test & log below :
|
|
| ProcessInstance pi = ksession1.startProcess("unknownQC"); |
|
|
|
|
|
|
| long pid = pi.getId(); |
|
|
| System.out.println("Process instance started ... id = " + pid); |
|
|
|
|
|
|
| boolean stillActive = ProcessInstance.STATE_COMPLETED != pi.getState(); |
|
|
| System.out.println("Process still active ? " + stillActive + " : state = " + pi.getState()); |
|
|
|
|
Retreiving session ... id = 61
BEFORE RULEFLOW STARTED process:Sample Process[id=unknownQC]
BEFORE PROCESS NODE TRIGGERED node:StartProcess[id=1] process:Sample Process[id=unknownQC]
BEFORE PROCESS NODE EXITED node:StartProcess[id=1] process:Sample Process[id=unknownQC]
BEFORE PROCESS NODE TRIGGERED node:Initial[id=2] process:Sample Process[id=unknownQC]
>>>>>>> Completing job
>>>>>>> Process Id = 79
>>>>>>> Work Item Id = 218
>>>>>>> Work Item Name = Jbpm
Work Item parameter = WORKFLOW_PROCESS_NAME value = unknownQC
Work Item parameter = WORKFLOW_TASK_HANDLER value = jobAccepted
Work Item parameter = WORKFLOW_TASK_NAME value = Job Accepted
BEFORE PROCESS NODE EXITED node:Initial[id=2] process:Sample Process[id=unknownQC]
BEFORE PROCESS NODE TRIGGERED node:End[id=11] process:Sample Process[id=unknownQC]
BEFORE PROCESS NODE EXITED node:End[id=11] process:Sample Process[id=unknownQC]
BEFORE RULEFLOW COMPLETED process:Sample Process[id=unknownQC]
AFTER RULEFLOW COMPLETED process:Sample Process[id=unknownQC]
AFTER PROCESS NODE TRIGGERED node:End[id=11] process:Sample Process[id=unknownQC]
AFTER PROCESS NODE TRIGGERED node:End[id=11] process:Sample Process[id=unknownQC]
AFTER PROCESS NODE TRIGGERED node:Initial[id=2] process:Sample Process[id=unknownQC]
AFTER PROCESS NODE TRIGGERED node:Initial[id=2] process:Sample Process[id=unknownQC]
AFTER PROCESS NODE TRIGGERED node:StartProcess[id=1] process:Sample Process[id=unknownQC]
AFTER PROCESS NODE TRIGGERED node:StartProcess[id=1] process:Sample Process[id=unknownQC]
AFTER RULEFLOW STARTED process:Sample Process[id=unknownQC]
Process instance started ... id = 79
Process still active ? false : state = 2
Should this workflow work as expected ? Am I missing something obvious ?
The above btw is a simplifcation of a larger workflow I'm working on, which will require being able to accept multiple events of any type (and multiple of the same tyoe) at any time before terminating if an event of a certain type is receievd ... but baby steps, I want to know why the above doesn't work so I can plan accordingly on what constructs I have at my disposal.
Thanks !
PS. I'm placing this in the jBPM 5.2 category b/c there is no 5.3 one (can somone add that please?), and taggint it w/ jBPM 5.3.0.final
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/776288#776288]
Start a new discussion in jBPM at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
13 years, 5 months
[JBoss Web Services] - Modifying published web service name in JBoss 6
by Brad Maxwell
Brad Maxwell [https://community.jboss.org/people/bcmaxwel] created the discussion
"Modifying published web service name in JBoss 6"
To view the discussion, visit: https://community.jboss.org/message/776280#776280
--------------------------------------------------------------
Hi all,
I'm converting a project from JBoss 4.2.3 to JBoss 6 and having some trouble with the published web service name.
In 4.2.3, the annotations below would result in a URL of:
http://localhost:8080/AuthServices/AuthorizationServiceBean http://localhost:8080/AuthServices/AuthorizationServiceBean
@WebContext(contextRoot = "AuthServices")
@WebService(portName = "AuthorizationServicePort", serviceName = "AuthorizationServiceService", targetNamespace = "urn:xxx.authorization", endpointInterface = "com.xxx.authorization.services.AuthorizationService")
@Stateless
public class AuthorizationServiceBean extends AbstractService implements AuthorizationService
In 6, this gives a URL of:
http://localhost:8080/AuthServices/AuthorizationServiceService/Authorizat... http://localhost:8080/AuthServices/AuthorizationServiceService/Authorizat...
If I remove the "serviceName" attribute, it sets the URL back to what it used to be.
@WebService(portName = "AuthorizationServicePort", targetNamespace = "urn:xxx.authorization", endpointInterface = "com.xxx.authorization.services.AuthorizationService" )
@WebContext(contextRoot = "AuthServices", authMethod="BASIC")
@Stateless
public class AuthorizationServiceBean extends AbstractService implements AuthorizationService
However, the published name goes from "AuthorizationServiceService" in 4.2.3 to "AuthorizationServiceBeanService" in 6.1.
WSDL from 4.2.3 = <definitions name="AuthorizationServiceService" targetNamespace="urn:xxx.authorization">
WSDL from 6.1 = <wsdl:definitions name="AuthorizationServiceBeanService" targetNamespace="urn:xxx.authorization">
And my client, of course, says:
Exception in thread "main" javax.xml.ws.WebServiceException: {urn:choicepoint.authorization}AuthorizationServiceService is not a valid service. Valid services are: {urn:xxx.authorization}AuthorizationServiceBeanService
Since we've got a lot of clients who would be impacted by this having to change this, I'd like to be able to force it back to the old name. Is there a way to do this?
Thanks in advance,
Brad
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/776280#776280]
Start a new discussion in JBoss Web Services at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
13 years, 5 months
