Re: Read timed out error on web services
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.comwrote: 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
Re: Read Timed out error on web services
It appears like you have more of a communication issue with the external web service than a problem with it not working at all - the later which would have been easier to trouble shoot than a sporadic communication issue. Does the error display on the user console? Or is it a error that shows in the arjavaplugin log? If it's an error that displays on the user console, does it have an associated ARERR returned? Where I am headed at is basically filter error handling.. This will not 'resolve' your problem or even help you 'circumvent' it, but will help you not show a meaningless error to the user. You would be able to display something more meaningful like This system is kinda gone bonkers at the moment - please try later. That might actually amuse the users instead of pissing them off :-) This article might help if you are not familiar with the concept. https://communities.bmc.com/docs/DOC-17166 Joe _ From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of lisa bumshteyn Sent: Friday, May 24, 2013 11:25 AM To: arslist@ARSLIST.ORG Subject: Read Timed out error on web services ** 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
Re: Read Timed out error on web services
Hey Joe, There's already error handling implemented to catch the error. The bigger issues is the plugin bouncing when the issue occurs. I'd like to be able to get away with config changes, whether it be tweaking the Plugin-Filter-API-Threads or something else, rather then patching their midtier or server because of how outdated they are. They're not prepared for upgrading yet, and with patching, should we run into bigger issues than they currently have (currently their system is pretty stable), BMC won't likely be of much help. If you have any suggestions, please let me know. Thanks, Lisa On Sat, May 25, 2013 at 6:23 AM, Joe D'Souza jdso...@shyle.net wrote: ** It appears like you have more of a communication issue with the external web service than a problem with it not working at all – the later which would have been easier to trouble shoot than a sporadic communication issue. ** ** Does the error display on the user console? Or is it a error that shows in the arjavaplugin log? ** ** If it’s an error that displays on the user console, does it have an associated ARERR returned? Where I am headed at is basically filter error handling.. ** ** This will not ‘resolve’ your problem or even help you ‘circumvent’ it, but will help you not show a meaningless error to the user. You would be able to display something more meaningful like “This system is kinda gone bonkers at the moment – please try later.” That might actually amuse the users instead of pissing them off J ** ** This article might help if you are not familiar with the concept. ** ** https://communities.bmc.com/docs/DOC-17166 ** ** Joe ** ** -- *From:* Action Request System discussion list(ARSList) [mailto: arslist@ARSLIST.ORG] *On Behalf Of *lisa bumshteyn *Sent:* Friday, May 24, 2013 11:25 AM *To:* arslist@ARSLIST.ORG *Subject:* Read Timed out error on web services ** ** ** 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. ** ** _ARSlist: 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
Re: Read Timed out error on web services
One thought that comes to mind is increasing the AR Filter Plugin threads. I do not remember off hand what that parameter is but you should find it in the Admin guide under the ar.conf section of the guide. This would help if your time out is because a thread is not available. Joe _ From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of lisa bumshteyn Sent: Saturday, May 25, 2013 4:23 PM To: arslist@ARSLIST.ORG Subject: Re: Read Timed out error on web services ** Hey Joe, There's already error handling implemented to catch the error. The bigger issues is the plugin bouncing when the issue occurs. I'd like to be able to get away with config changes, whether it be tweaking the Plugin-Filter-API-Threads or something else, rather then patching their midtier or server because of how outdated they are. They're not prepared for upgrading yet, and with patching, should we run into bigger issues than they currently have (currently their system is pretty stable), BMC won't likely be of much help. If you have any suggestions, please let me know. Thanks, Lisa On Sat, May 25, 2013 at 6:23 AM, Joe D'Souza jdso...@shyle.net wrote: ** It appears like you have more of a communication issue with the external web service than a problem with it not working at all - the later which would have been easier to trouble shoot than a sporadic communication issue. Does the error display on the user console? Or is it a error that shows in the arjavaplugin log? If it's an error that displays on the user console, does it have an associated ARERR returned? Where I am headed at is basically filter error handling.. This will not 'resolve' your problem or even help you 'circumvent' it, but will help you not show a meaningless error to the user. You would be able to display something more meaningful like This system is kinda gone bonkers at the moment - please try later. That might actually amuse the users instead of pissing them off :-) This article might help if you are not familiar with the concept. https://communities.bmc.com/docs/DOC-17166 Joe _ From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of lisa bumshteyn Sent: Friday, May 24, 2013 11:25 AM To: arslist@ARSLIST.ORG Subject: Read Timed out error on web services ** 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. _ARSlist: Where the Answers Are and have been for 20 years_ _ARSlist: 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
Read timed out error on web services
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
Read Timed out error on web services
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
Re: Read Timed out error on web services
Hi, You should also try and use something like Wireshark along with your 3rd party tool, and forward the result of the dump to a network expert when you get this timeout. I bet he will see some incomplete TCP streams or other low level funny things, like packets lost in the wild. On Fri, May 24, 2013 at 5:24 PM, lisa 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. _ARSlist: 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
