There was a known issue where Web service API times out after 40 seconds. This was fixed in 7.5. Please collect API/SQL/Filter logging & check if you see the same issue. What's the default time out set for Plug-in?
The fix was provided to use Server-Plugin-Default-Timeout values which was earlier hard coded. I don't think this was fixed in 7.1code line. On Fri, May 24, 2013 at 5:06 PM, Yelizaveta Bumshteyn <lisa9...@gmail.com>wrote: > Hi All, > > Hoping to get some help here. The client has a web service from an > external system that they consume. For the most part it works well but > sporadically the response takes a while to come back, which results in the > "java.net.SocketTimeoutException: Read timed out" error. When the error > occurs, the Plugin server bounces. There's no rhyme or reason to which > requests take a while to respond and which ones are for the most part > instantaneous. The same request that failed can then be sent through in no > time without any issues. > > I've tried testing the web service through a 3rd party utility and I see > the same delay in responses periodically. However, it seems that in Remedy > that delay in response crashes the Plugin process. Raising the timeout > limit dodes not make a difference as it just takes longer to come back with > that message. > > Heres' some info about the system > Version: 7.1 Patch 5 > OS: Solaris > DB: Oracle 10.2 > > My thought was to play around with the Plugin-Filtr-API-Threads setting. > They currently have it set at 10 20. Any help would be appreciated. > > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > "Where the Answers Are, and have been for 20 years" > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
