Hi Joe, yes I did, and it made things even worst. From a crash once in a while, we crashed systematically each time.
It seems that the problem is linked to the FIFO being full on the other system. Which make the responce to the APIFilter call too long. I will probably have to increase the time out from 60 sec to 120 secs. Not a good solution for my users ... But I don't see what else can be done Pascale Boyer Analyste Expert Remedy Vidéotron Technologie Inc Développement produits affaires & service corporatifs 800, de la Gauchetière, Ouest niveau 1, local 1130 Montréal, (Québec) H5K 1K6 Tél.: (514) 380-7841 Courriel: [EMAIL PROTECTED] Joe DeSouza <[EMAIL PROTECTED]> Envoyé par : "Action Request System discussion list(ARSList)" <[email protected]> 2008-08-25 16:41 Veuillez répondre à [email protected] A [email protected] cc Objet Re: Help please - ARPlugin crashes on WebService call ** Pascal, Have you set the Plugin-Filter-API-Threads parameter in the ar.conf file? If not I would suggest setting it.. I had a similar problem a few days ago that went away as soon as I set this parameter with a min setting of 1 and a max setting of 15.. This is what I have in my configuration file now.. Plugin-Filter-API-Threads: 1 15 You will need to restart the AR System server after you set this or at least run the arsignal -c to re read the configuration file.. Let me know if this helps.. Cheers Joe ----- Original Message ---- From: Pascale Boyer <[EMAIL PROTECTED]> To: [email protected] Sent: Monday, August 25, 2008 4:07:49 PM Subject: Help please - ARPlugin crashes on WebService call ** Hi all, We are suddenly experiencing problems with the arplugin. Everything was running smoothly for the past several weeks and now suddenly we get the message ARERR [8939] Le serveur AR System Plug-In ne répond pas. Impossible de se connecter au système pour le moment. Adressez-vous à l'administrateur AR System pour assistance. Which can be translated by the AR System Plug-in isn't responding. unable to connect to the system. Contact your AR System Administrator. I put the logs to 400 and this is all I can see: </ns1:createWorkOrderReq> </soapenv:Body> </soapenv:Envelope> <PLGN> <TID: 000018> <RPC ID: 0000000011> <Queue: ARFILTERAPI> <Client-RPC: 390695> /* lun août 25 2008 15:48:04.4986 */<> <F INE> About to invoke <PLGN> <TID: 000018> <RPC ID: 0000000011> <Queue: ARFILTERAPI> <Client-RPC: 390695> /* lun août 25 2008 15:48:09.6164 */<> <F INE> java.net.SocketTimeoutException: Read timed out <PLGN> <TID: 000018> <RPC ID: 0000000011> <Queue: ARFILTERAPI> <Client-RPC: 390695> /* lun août 25 2008 15:48:09.6226 */-CALL FAIL If we call the webservice outside ARS, everything works perfectly fine and quickly. I had some arplugin threads hoping that it would help ... Just more crashes... Not sure if by increasing the timeout from 60 sec to higher is an option... don't think the client will appreciate the wait. Anyone as a clue? Homegrown apps ARS 7.01 patch 004 Oracle 9i Solaris Appache /tomcat Thanks for the help Pascale Boyer Analyste Expert Remedy Vidéotron Technologie Inc Développement produits affaires & service corporatifs 800, de la Gauchetière, Ouest niveau 1, local 1130 Montréal, (Québec) H5K 1K6 Tél.: (514) 380-7841 Courriel: [EMAIL PROTECTED] __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" html___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
