tag:blogger.com,1999:blog-6416385526593383847.post2039959261288297407..comments2024-03-13T00:53:59.549-04:00Comments on Raastech Blog: com.oracle.bpel.client.delivery.ReceiveTimeOutException in 50% of instances in a BPEL Process Manager clusterAhmed Aboulnagahttp://www.blogger.com/profile/17300393989634195878noreply@blogger.comBlogger1125tag:blogger.com,1999:blog-6416385526593383847.post-28031830209884449762010-07-16T14:18:04.689-04:002010-07-16T14:18:04.689-04:00Hi Ahmed,I had the same thing happening aswell. Th...Hi Ahmed,<br><br>I had the same thing happening aswell. The reason for this is that synchronous bpel process instances 'wait' through a local JVM mutex. So even if you 'cluster' your bpel container with multiple JVM's on one machine, you can experience this problem. We discussed this aswell on Mark Kelderman's blog: http://orasoa.blogspot.com/2010/03/bpel-10g-clustering-with-jgroups-on.html<br>To prevent thread starvationin the JVM, there is a timeout parameter maxsyncwait of 45 seconds. So after 45 seconds the synchronous process instance will timeout.<br><br>regards,<br>Tony van EschTonyhttp://www.blogger.com/profile/13685591077545818250noreply@blogger.com