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"

Reply via email to