On our client production site, they have conducted a sniffing test between the IS 6.0.1 machine and another server which sends and receives transactions via HTTP. It is found that ocassionally for some transactions, the HTTP acknowledgement sent by IS back to the server using the pub.flow:setResponse service takes more than 10 secs. We’ve followed Tech Support’s advise to clean up the WMSESSION and WMERROR tables. However, the issue still persists. It seems that even though the setResponse service execution time was logged to be almost instantaneous using debugLog, it took longer to leave the IS server and reach the invoking remote server.
The sniffing exercise has concluded that network traffic between IS and the other server wasn’t an issue since it was measured and found to be underutilized during the sniffing exercise. The flow service invoked by the remote server also DOES NOT perform any database activity BEFORE invoking setResponse.