Workflow and ParallelSplit

Next topic

Author	Message
Pierre c	Thursday 17 June 2010 3:22:21 am Hey, I have some questions about workflow and the ParallelSplit . I would like to run two node in my work flow in parallel. I used the ezcWorkflowNodeParallelSplit but my class myServiceObject1 and myServiceObject2 were'nt executed with thread My code without myServiceObject1/myServiceObject2 class $split = new ezcWorkflowNodeParallelSplit(); $workflow->startNode->addOutNode( $split ); $nodeExec1 = new ezcWorkflowNodeAction(array('class' => 'myServiceObject1')); // create nodes for the first branch of execution here.. $nodeExec2 = new ezcWorkflowNodeAction(array('class' => 'myServiceObject2')); // create nodes for the second branch of execution here.. $split->addOutNode( $nodeExec1 ); $split->addOutNode( $nodeExec2 ); $disc = new ezcWorkflowNodeDiscriminator(); $disc->addInNode( $nodeExec1 ); $disc->addInNode( $nodeExec2 ); $disc->addOutNode( $workflow->endNode ); How i could use thread ? You can see the .dot file here http://www.hostingpics.net/viewer.php?id=474745Test_041_012.jpg
Pierre c	Monday 21 June 2010 12:41:43 am Hello, nobody has been used the workflow with thread yet ? Did you know if workflow with thread function only with the worker modules in Apache conf.

Author

Message

Thursday 17 June 2010 3:22:21 am

Hey,

I have some questions about workflow and the ParallelSplit . I would like to run two node in my work flow in parallel. I used the ezcWorkflowNodeParallelSplit but my class myServiceObject1 and myServiceObject2 were'nt executed with thread

My code without myServiceObject1/myServiceObject2 class

$split = new ezcWorkflowNodeParallelSplit();
$workflow->startNode->addOutNode( $split );

$nodeExec1 = new ezcWorkflowNodeAction(array('class' => 'myServiceObject1')); // create nodes for the first branch of execution here..
$nodeExec2 = new ezcWorkflowNodeAction(array('class' => 'myServiceObject2')); // create nodes for the second branch of execution here..

$split->addOutNode( $nodeExec1 );
$split->addOutNode( $nodeExec2 );

$disc = new ezcWorkflowNodeDiscriminator();
$disc->addInNode( $nodeExec1 );
$disc->addInNode( $nodeExec2 );
$disc->addOutNode( $workflow->endNode );

How i could use thread ?

You can see the .dot file here http://www.hostingpics.net/viewer.php?id=474745Test_041_012.jpg

Pierre c

Monday 21 June 2010 12:41:43 am

Hello,

nobody has been used the workflow with thread yet ? Did you know if workflow with thread function only with the worker modules in Apache conf.

eZ debug

Timing:	Jan 18 2025 02:59:23
Script start
Timing:	Jan 18 2025 02:59:23
Module start 'layout'
Timing:	Jan 18 2025 02:59:23
Module start 'content'
Timing:	Jan 18 2025 02:59:23
Module end 'content'
Timing:	Jan 18 2025 02:59:23
Script end

Main resources:

Total runtime	0.0142 sec
Peak memory usage	4,096.0000 KB
Database Queries	3

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0052	589.0469	152.6250
Module start 'layout'	0.0052	0.0022	741.6719	39.4453
Module start 'content'	0.0074	0.0050	781.1172	89.2109
Module end 'content'	0.0124	0.0018	870.3281	30.3047
Script end	0.0142		900.6328

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0023	16.0369	14	0.0002
Check MTime	0.0010	7.1022	14	0.0001
Mysql Total
Database connection	0.0008	5.7417	1	0.0008
Mysqli_queries	0.0022	15.3022	3	0.0007
Looping result	0.0000	0.0703	1	0.0000
Template Total	0.0015	10.3	1	0.0015
Template load	0.0008	5.5576	1	0.0008
Template processing	0.0007	4.6958	1	0.0007
Override
Cache load	0.0006	3.9879	1	0.0006
General
dbfile	0.0003	2.2876	8	0.0000
String conversion	0.0000	0.0351	4	0.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

Usage	Requested template	Template	Template loaded	Edit	Override
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 1 Number of unique templates used: 1

Time used to render debug report: 0.0001 secs