Hi All,
I am facing an issue in time outs. One of my step in process model, I have configured to relative timeout (by setting the varible in pipeline) with a join AND condition. It was working fine some time ago. All of a sudden I started seeing the weird behavior of not getting time outs. It simply waits for the document to arrive(the other transition leading into the wait step) and never gets time out.

Scenario of the steps:

Wait step:

In transitions: one recieved document, one transaction step
Out transitions: timeout, successful on condition, failure on condition
timer setting: relative timeout (variable from from the step)

webMethods Process engine:7.1.1 v

I have increased the process engine logs and found the following entries (timeout = 10000 millisecs)

2009-01-29 14:09:40 EST [PRT.0101.0346T] (T58) checking process status
2009-01-29 14:09:40 EST [PRT.0101.0348T] (T58) status = STAT_RUNNING
2009-01-29 14:09:40 EST [PRT.0101.0349T] (T58) step iteration = 1
2009-01-29 14:09:40 EST [PRT.0101.0350T] (T58) starting step timeout
2009-01-29 14:09:40 EST [PRT.0101.0351T] (T58) timeout duration: 0
2009-01-29 14:09:40 EST [PRT.0101.0352T] (T58) timeout step: S62
2009-01-29 14:09:40 EST [PRT.0101.0145T] Creating timer entry for join timeout
2009-01-29 14:09:40 EST [PRT.0101.0137T] Constructing timeout with pid=61041660ee3811dd8efdf78c8cd3d2e6:1, mid=SelSonexProductMasterProcess/SelSonexProductMasterProcess, sid=S59, timerEntry=>>>BasicData:pid=61041660ee3811dd8efdf78c8cd3d2e6:1,sid=S59,firedAt=0,dueRelative=10000,type=1,classification=joinTimeout,threadId=61041660ee3811dd8efdf78c8cd3d2e6:1S59<<<
2009-01-29 14:09:40 EST [PRT.0101.0138T] Creating timeout timer
2009-01-29 14:09:40 EST [PRT.0101.0448T] (10000) starting join timeout
2009-01-29 14:09:40 EST [PRT.0101.0125T] Starting relative timeout for pid=61041660ee3811dd8efdf78c8cd3d2e6:1, sid=S59: 10,000
2009-01-29 14:09:40 EST [PRT.0101.0353T] (T58) evaluating join
2009-01-29 14:09:40 EST [PRT.0101.0001T] -----------------------------
2009-01-29 14:09:40 EST [PRT.0101.0428T] (T58) PRT queue processing for step S59
2009-01-29 14:09:40 EST [PRT.0101.0429T] (T58) process instance ID: 61041660ee3811dd8efdf78c8cd3d2e6:1
2009-01-29 14:09:40 EST [PRT.0101.0435T] (T58) 1 events in the queue
2009-01-29 14:09:40 EST [PRT.0101.0436T] (T58) event names: [TX-FROM-S37]
2009-01-29 14:09:40 EST [PRT.0101.0437T] (T58) join string: (and TX-FROM-S37 TX-FROM-S66)
2009-01-29 14:09:40 EST [PRT.0101.0438T] (T58) join state: {}
2009-01-29 14:09:40 EST [PRT.0101.0439T] (T58) join result: (jr)
2009-01-29 14:09:40 EST [PRT.0101.0001T] -----------------------------
2009-01-29 14:09:40 EST [PRT.0101.0356T] (T58) nothing to do for this step yet
2009-01-29 14:09:40 EST [PRT.0101.0336T] (T58) ending synchronous execution of step S59

Also I see some other database errors after this , not sure whether they are related to timer but the table name is PRTPROCLOCK.

2009-01-29 14:18:50 EST [PRT.0101.0512T] *** Database Storage problem. Exception: java.sql.SQLException: [wm-cjdbc36-0007][SQLServer JDBC Driver][SQLServer]Violation of PRIMARY KEY constraint ‘PK__PRTPROCLOCK__2CB38214’. Cannot insert duplicate key in object ‘dbo.PRTPROCLOCK’.
2009-01-29 14:18:50 EST [PRT.0101.0512T] *** Database Storage problem. Exception: java.sql.SQLException: [wm-cjdbc36-0007][SQLServer JDBC Driver][SQLServer]Violation of PRIMARY KEY constraint ‘PK__PRTPROCLOCK__2CB38214’. Cannot insert duplicate key in object ‘dbo.PRTPROCLOCK’.
2009-01-29 14:18:50 EST [PRT.0101.0512T] *** Database Storage problem. Exception: java.sql.SQLException: [wm-cjdbc36-0007][SQLServer JDBC Driver][SQLServer]Violation of PRIMARY KEY constraint ‘PK__PRTPROCLOCK__2CB38214’. Cannot insert duplicate key in object ‘dbo.PRTPROCLOCK’.
2009-01-29 14:18:50 EST [PRT.0101.0512T] *** Database Storage problem. Exception: java.sql.SQLException: [wm-cjdbc36-0007][SQLServer JDBC Driver][SQLServer]Violation of PRIMARY KEY constraint ‘PK__PRTPROCLOCK__2CB38214’. Cannot insert duplicate key in object ‘dbo.PRTPROCLOCK’.
2009-01-29 14:18:50 EST [PRT.0101.0512T] *** Database Storage problem. Exception: java.sql.SQLException: [wm-cjdbc36-0007][SQLServer JDBC Driver][SQLServer]Violation of PRIMARY KEY constraint ‘PK__PRTPROCLOCK__2CB38214’. Cannot insert duplicate key in object ‘dbo.PRTPROCLOCK’.
2009-01-29 14:18:50 EST [PRT.0101.0512T] *** Database Storage problem. Exception: java.sql.SQLException: [wm-cjdbc36-0007][SQLServer JDBC Driver][SQLServer]Violation of PRIMARY KEY constraint ‘PK__PRTPROCLOCK__2CB38214’. Cannot insert duplicate key in object ‘dbo.PRTPROCLOCK’.

Not sure of the PRTPROCLOCK table and how wM Process engine works in runtime.

Any help is much appreciated !

regards
Sai Arun

Dear, we are facing same issue. Can you please provide inputs…