Workflow service hangs up when EventScript is running

Alexander_Poltavtsev

I developed web-service, that imprints registration number into body of document, attached to the workflow. My web-service uses .NET versions of WorkflowService to determine ID of Attachments container and DocumentManagementService to download document and add new imprinted version to it. I also developed CLR stored procedure for MS SQL Server, that calls my web-service. When I executed my stored procedure from SQL Server Management Studio everything works fine. I developed the workflow EventScript, that calls my stored procedure, using CAPI.Exec and assigned it to the step of my workflow. When I start to test this, I found the following: the EventScript successfully calls my stored procedure, which successfully calls my web-service. Then web-service calls  WorkflowService.GetProcessData(...) method and everything stops untill timeout occurs. This doesn,t happens if I call stored procedure (or my web-service) directly. The error is reproducible when I run Builder or Livelink Server so it's doesn't connected with single- or multithreading execution, so I can make conclusion, that EventScript execution prevents execution of WorkflowService and I receive some kind of deadlock. Am I right and does somebody faced with similiar issues with Enterprise Web Services 9.7.1?

P.S. I use SQL Server 2008 R2 and WCF 3.5

Kyle_Swidrovich

Quoted Alexandre Poltavtsev (poltavtseva@terralink.ru) on 2011/06/21 02:40:

I developed web-service, that imprints registration number into body of document, attached to the workflow. My web-service uses .NET versions of WorkflowService to determine ID of Attachments container and DocumentManagementService to download document and add new imprinted version to it. I also developed CLR stored procedure for MS SQL Server, that calls my web-service. When I executed my stored procedure from SQL Server Management Studio everything works fine. I developed the workflow EventScript, that calls my stored procedure, using CAPI.Exec and assigned it to the step of my workflow. When I start to test this, I found the following: the EventScript successfully calls my stored procedure, which successfully calls my web-service. Then web-service calls  WorkflowService.GetProcessData(...) method and everything stops untill timeout occurs. This doesn,t happens if I call stored procedure (or my web-service) directly. The error is reproducible when I run Builder or Livelink Server so it's doesn't connected with single- or multithreading execution, so I can make conclusion, that EventScript execution prevents execution of WorkflowService and I receive some kind of deadlock. Am I right and does somebody faced with similiar issues with Enterprise Web Services 9.7.1?

P.S. I use SQL Server 2008 R2 and WCF 3.5

Hello Alexandre,

Debugging this in Builder will be difficult due to the fact that Builder is single threaded and you are asking it to run two separate operations -- the Event Script + callback into Livelink via SQL stored procedure to GetProcessData.

Your best troubleshooting route will probably be to enable thread and connect logging (Debug=2 in [general], wantLogs=TRUE in [options]) and see how far Content Server gets in the logs before it hangs.  That may point you in the right direction.

Kyle