index > Windows Workflow Foundation > State Machine Workflow sending an event to itself

State Machine Workflow sending an event to itself

Hi All,

lkurts

Hi,

lkurts

Hi,

I have tried implementing your solution and it worked well for the first time, later on my application got hung, when ever i try to re-execute next steps.

By the way, i am using ASP .Net app to host my workflow and ManualWorkflowSchedulerService to run my WF with in the web app.

I think, there might be some conflicts between the Thread that runs my web application and the thread (obtained from ThreadPool), which executes the event.

I have few queries in this regard,

- Are you using ASP .Net application as your host?
- If so, do you get similar kind of behavior from your application.
- Is there any way to resolve this issue

Thanks in advance for your time

Pavan Apuroop

Hi,

I am not using ASP.NET, I am using a simple console host. It is not quite clear from your post what do you mean by "hung". Could it be that the state machine workflow is just waiting for some event and is simply idle?

lkurts

The web page, i am running, works well for the first time, when used ThreadPool.QueueUserWorkItem(), but for the next activity onwards, it stops responding.

I guess, ManualWorkflowSchedulerService has some issues with ThreadPool class and here are some points to support my guess:

- ManualWorkflowScheduler service makes web app to donate its thread to workflow and waits for the workflow to return back its thread.

- But when we use ThreadPool, workflow picks up any thread available, and executes the event. This causes the workflow, not to return back the thread to webapp.

- But on front-end, it appears (as soon as the event finishes), that the workflow is finished its current execution and waits for next event.

- As the web app is still waiting for its donated thread, it stops responding to any other requests / responses till it gets back the donated thread.

- This causes the application to hang.

These are purely my guess.

Lets wait for any work around to resolve this issue.

Regards,

Pavan

Pavan Apuroop

reply 5