What is the load on the CDP process? How many ORCA calls are being invoked when you see the error?
I just invoked it once again, and this time also one time it failed (did not update the log files) and one time it succeeded without giving the response back to SoapUI.
The CPU usage is between 20-30%. I am making only one ORCA web service call at a time.
I recall stumbling on this issue - or similar issue - in an older version of AO, which was fixed in later service packs. When I say "older version of AO", I really mean "older" ... if I am not mistaking, this was a 7.6.0.x release. You are not happening to run such an old release by any chance are you? What version are you on?
Yes, the customer is having old version of AO - 7.6.00.01.
If that is the case, then what is the fix for this issue?
I'm digging thru my reported issues. The issue I had with the Webservices timing out was when running 7.6.01.00 and not 7.6.00.01 like yours; however, it may very welll be that the bug existed prior to 7.6.01.00 as well. In any case, the bug only occured when having APs in the GRID as well and had to do with where the workflow was being processed.
What I noticed in my case is that if the Orca WS request came in, and the workflow executed on the CDP, it worked. If however the WS request came in, but the workflow was assigned to one of the other peers, it would fail and time out.
Does your customer have one or more APs in his/her grid?
In my case, the issue was addressed in 7.6.01.01.
I would recommend - if at all possible - to upgrade to the latest AP version. (7.6.02.05). At a minimum, I recommend you upgrade to 7.6.01.01 since that version has a fix for this particular problem. This is of course assuming you are hitting the same issue I was hitting. I suppose an easy way for you to test this is by shutting down the APs and see if all WS now work.
The customer environment does not have an AP. It only has one CDP.
Ok. So your issue may not be the same.
If you have an opportunity to do so, I still recommend you upgrade to the latest version. 7.6.00.01 is starting to become very old and if all you have is a single CDP, the upgrade should be pretty straight forward. If that is not an option, you may want to submit a support ticket, though I would bet that BMC Support would ask you to upgrade as well.
Yes, I created a support ticket and they also recommended me to upgrade to latest version.
Can you check if it works. If you are calling ORCA webservice from SOAP UI then in the setting of SOAP UI you can increase the response time so that SOAPUI will wait some more time for the response. It can be possible that due to network dependancy it takes more time for response..
Thanks and regards,
Thanks for the response. I already increased the Socket Connection timeout to 600000 ms in SoapUI, but still it did not receive the response in this timeframe.
By the way, I am in the process of upgrading the AO platform to the latest vesion and will update you if this resolves my issue.
I upgraded customer AO platform to the latest 760205 and it solved the issue.