ObjectWeb Consortium
Search ObjectWeb Mail Archive: 

Advanced Search - Powered by Google

Mail Archive Home | shark List | September 2004 Index

<--  Date Index  --> <--  Thread Index  -->

Re: [shark] Process must have some requester

Title: AW: [shark] Process must have some requester
yes, there is a possibility to access those processes either by getting all processes for the WfProcessMgr they are based on, or searching for them directly based on their Id (if it is known).
You didn't tell me if you've deleted the "Main" process (by the use of shark API, or by configuring DODSPersistenceManager to automatically delete processes after they are finished), because in that case it seems we have bug in shark that prevents you to terminate the process.
Asynchronous subflows are not bound to the subflow activity of the main process - after subflow activity in the "Main" process starts the subflow, it finishes its execution and "Main" process is following outgoing transition of this activity. If the subflow is Synchronous, the subflow activity is completed after it gets the notification of the subflow process that it is "closed".
Shark is a library, and it does not open its own threads, but runs inside the client thread. You can start subflows in parallel, but if they are fully automatic subflows (i.e. consisted only of Route or Tool agent activities) they will be actually executed sequentially. On the other side, If these subflows have manual activities, shark will instantiate the first subflow and execute it until it comes to the first manual activity. After that, it will execute the other one, also until it gets to the first manual activity. After that, these manual activities (from different subflows) can be executed from two client threads at a time.
----- Original Message -----
Sent: Wednesday, September 29, 2004 10:22 AM
Subject: AW: [shark] Process must have some requester

Hi Sasa,
you are right with your assumption. The subflows are asynchronous and the "Main" process already finished - because of a fault

inside our implementation - just before all subflows finished. After Correction - waiting for Finishing all subflows - it works.

And what i meant was, is there any Possibility - except recreate DB - to have access to the Subflow Processes, in such a case were

the "Main" Process is lost, so that I can abort/terminate those?

And some more additional questions, especially synchronous and asynchronous Subflows.
What ist exactly the difference between them?
We need to start two or more Subflows in parallel, which are of course should be executed in parallel and not in a
serial way. Is this possible?

Thanks, Manfred H.

-----Ursprüngliche Nachricht-----
Von: Sasa Bojanic [mailto:sasaboy@xxxxxxxxxxxxx]
Gesendet: Dienstag, 28. September 2004 17:11
An: Shark
Betreff: Re: [shark] Process must have some requester


from your description, I assume that you use asynchronous subflow.
Also, you are probably deleting the "Main" process from DB before asynchronous subflow finishes, and this is why you get this

If above assumptions are correct, it is a bug in Shark - it shouldn't throw such exception in the case of asynchronous subflows.

The workaround solution for you would be to not delete "Main" process from DB until asynchronous subflow processes that are started

from this process does not finish.

Thanks for reporting,

----- Original Message -----
From: <manfred.hagenauer@xxxxxxxxxxx>
To: <shark@xxxxxxxxxxxxx>
Sent: Wednesday, September 22, 2004 11:16 AM
Subject: [shark] Process must have some requester

> Hi everybody.
> During our tests with the Shark Engine, we are now blocked with following symptom.
> We tried to start a Workflow, which itself starts some subflows. If in some cases
> the "Main" workflow completes and the Subflows hangs up, its no more possible to abort or get any response from the remaining

Subflows. We tried also to abort the Processes via the ExecutionAdministration, but in any case we got a BaseException "Process must

have some requester". Only solution is to recreate the DB, so that we can Reload the XPDL Definition. And we think this is not the

best Solution.
> Our Idea is to use a new Requester for the "lost" one. But if, how can this be done?
> Any Idea, some other Comments are welcome.
> Best regards from Austria


> --
> You receive this message as a subscriber of the shark@xxxxxxxxxxxxx mailing list.
> To unsubscribe: mailto:shark-unsubscribe@xxxxxxxxxxxxx
> For general help: mailto:sympa@xxxxxxxxxxxxx?subject=help
> ObjectWeb mailing lists service home page: http://www.objectweb.org/wws

<--  Date Index  --> <--  Thread Index  -->

Reply via email to:

Powered by MHonArc.

Copyright © 1999-2005, ObjectWeb Consortium | contact | webmaster.