[JBoss jBPM] - Re: Stale state problem kills process instance?
by petia
Hi Ed,
Thanks for your reply. Maybe I misunderstood you, but I do not set the attribute async to anything at all. According to the specification, this attribute default value is "false". In my opinion this is a strange attribute to have for a Fork Node, but again according to the specification every Node has it.
So, without setting the async attribute and by using a Fork Node, I get a parallel split and the activities following the Fork Node are enabled (and possible to execute) in parallel. Nothing strange here.
Sorry, if I comments have caused confusion. The problem mentioned initially was that the engine sometimes generates an error message when Fork is used (and breaks down, i.e., a restart is needed). I observed that it only happens if one of the outgoing transitions from a Fork misses a name (which is the default setting). Note, that this is just an observation based on a problem I faced and a couple of examples I was running. I have not made any real "trouble shooting" of the problem. I just though my observation can help others.
Regards, Petia
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4171131#4171131
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4171131
17 years, 7 months
[JBoss jBPM] - Re: Stale state problem kills process instance?
by petia
Hi Ed,
Below is the example which works nicely for me. Note that, the fork and join have the default setting async="false". The transitions "to B1" and "to B2" going out from the Fork node, do not have any conditions specified. The only difference of this example, from a non-working example is that both transitions going out from the Fork node have names, i.e. "to B1" and "to B2" below.
I hope this helps, Petia
<?xml version="1.0" encoding="UTF-8"?>
|
| <process-definition xmlns="urn:jbpm.org:jpdl-3.2" name="Fork">
| <swimlane name="Initiator">
| <assignment actor-id="admin"></assignment>
| </swimlane>
|
| <start-state name="start-state1">
| <task name="start-task" swimlane="Initiator"></task>
| <transition to="taskA"></transition>
| </start-state>
|
| <task-node name="taskA">
| <task name="taskA" swimlane="Initiator"></task>
| <transition to="fork1"></transition>
| </task-node>
|
| <fork name="fork1">
| <transition to="taskB1" name="to B1"></transition>
| <transition to="taskB2" name="to B2"></transition>
| </fork>
|
| <task-node name="taskB1">
| <task name="taskB" swimlane="Initiator"></task>
| <transition to="join1"></transition>
| </task-node>
|
| <task-node name="taskB2">
| <task swimlane="Initiator" name="taskB2"></task>
| <transition to="join1"></transition>
| </task-node>
|
| <join name="join1">
| <transition to="end-state1"></transition>
| </join>
|
| <end-state name="end-state1"></end-state>
| </process-definition>
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4171118#4171118
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4171118
17 years, 7 months
[JBoss jBPM] - Re: add new user
by mputz
Petia,
the SQL 42601 error comes up because the SQL statements are missing the trailing semicolons (;).
| $ sed 's/$/;/g' jbpm.jpdl.postgresql.sql > jbpm.jpdl.postgresql.delimiter.sql
| $ psql -d <database> -U <dbuser> -W -f jbpm.jpdl.postgresql.delimiter.sql
|
Also, you'd need not only JBPM_ID_USER entries as outlined in the SQL snippet of Chapter 8.5.1 of the docs, but also entries in the JBPM_ID_GROUP and JBPM_ID_MEMBERSHIP table:
INSERT INTO JBPM_ID_GROUP VALUES(1,'G','sales','organisation',NULL);
| INSERT INTO JBPM_ID_GROUP VALUES(2,'G','admin','security-role',NULL);
| INSERT INTO JBPM_ID_GROUP VALUES(3,'G','hr','organisation',NULL);
| INSERT INTO JBPM_ID_GROUP VALUES(4,'G','user','security-role',NULL);
| INSERT INTO JBPM_ID_GROUP VALUES(5,'G','manager','security-role',NULL);
| INSERT INTO JBPM_ID_USER VALUES(1,'U','user','user(a)sample.domain','user');
| INSERT INTO JBPM_ID_USER VALUES(2,'U','manager','manager(a)sample.domain','manager');
| INSERT INTO JBPM_ID_USER VALUES(3,'U','admin','admin(a)sample.domain','admin');
| INSERT INTO JBPM_ID_USER VALUES(4,'U','shipper','shipper(a)sample.domain','shipper');
| INSERT INTO JBPM_ID_MEMBERSHIP VALUES(1,'M',NULL,NULL,2,4);
| INSERT INTO JBPM_ID_MEMBERSHIP VALUES(2,'M',NULL,NULL,3,4);
| INSERT INTO JBPM_ID_MEMBERSHIP VALUES(3,'M',NULL,NULL,1,4);
| INSERT INTO JBPM_ID_MEMBERSHIP VALUES(4,'M',NULL,NULL,4,4);
| INSERT INTO JBPM_ID_MEMBERSHIP VALUES(5,'M',NULL,NULL,4,3);
| INSERT INTO JBPM_ID_MEMBERSHIP VALUES(6,'M',NULL,NULL,2,3);
| INSERT INTO JBPM_ID_MEMBERSHIP VALUES(7,'M',NULL,NULL,3,3);
| INSERT INTO JBPM_ID_MEMBERSHIP VALUES(8,'M',NULL,NULL,3,2);
| INSERT INTO JBPM_ID_MEMBERSHIP VALUES(9,'M',NULL,NULL,2,2);
| INSERT INTO JBPM_ID_MEMBERSHIP VALUES(10,'M',NULL,NULL,2,5);
| INSERT INTO JBPM_ID_MEMBERSHIP VALUES(11,'M',NULL,'boss',2,1);
| INSERT INTO JBPM_ID_MEMBERSHIP VALUES(12,'M',NULL,NULL,1,1);
|
Finally, if you add a new user using the jbpm-console, you will also need to associate the new user entry with a group, eg. by default at least the 'user' group to be able to login.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4171057#4171057
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4171057
17 years, 7 months