Hi Jarl,
I tried even loopback.. But still facing the same issue.
I have configured below lines into ar.cfg file
Private-RPC-Socket: 390693 4 4
Plugin-Loopback-RPC-Socket: 390693
Environment details: Windows XP, remedy 6.3 patch 18. Mid Tier 6.3, .Net API
7.0
Thanks &Regards,
Gopala Krishna.Peela
_________________________________________________________
' BTGS ESG; Virtusa India (P) Ltd., India - 044-42002700- Extn 3253 [EMAIL
PROTECTED] <mailto:[EMAIL PROTECTED]>
________________________________
From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED]
On Behalf Of Jarl Grøneng
Sent: Monday, September 10, 2007 12:46 AM
To: [email protected]
Subject: Re: Error: Plug-In server is not responding
**
It was avaible in version 51.2 patch 1357....
http://developer.bmc.com/jiveProd/entry!default.jspa?categoryID=528&externalID=22&fromSearchPage=true
Face the same problem with Java FitlerAPI, and the loopback fixed the issue....
--
Jarl
On 9/7/07, Papolu, Appajee < [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> >
wrote:
**
Hi
This is a "loopback" scenario - client issues a call to Server; AR System
delegates call to a plug-in; which in turn calls back the Server again.
You should configure your Server as noted (in the "Configuring ... " document)
Plugin-Loopback-RPC-Socket :
The RPC socket number for the private server queue to which loopback
plug-in API calls should be directed. The acceptable values are in the
following ranges: 390621-390634, 390636-390669, and 390680-390694.
Loopback plug-ins (like the Report Creator plug-in) that make calls back
into AR System, will use this value to determine the queue to request. By
default, the API calls that the plug-in makes are directed to a queue that
corresponds with the call type. To be effective, the server must be
configured to have the designated private queue for this setting.
So, try some thing as below:
- Stop your AR Server
- Open your ar.cfg and add the following two lines (or, alter existing
content to reflect some thing similar to below)
Private-RPC-Socket: 390621 2 2
Plugin-Loopback-RPC-Socket : 390621
- Restart your AR Server
- Try your test scenario. It should work better even when the plug-in
issues calls back to the same AR Server.
Regards
Appajee
PS: this feature is at least available in 7.0 & greater, I am not quite sure
whether it was originally introduced in 6.3 or before. Give a quick try; if
things don't work quite right, I can try digging around some more on this.
________________________________
HI,
Please find below failure scenario where I have been facing issues with
remedy-.net integration.
Failure Scenario
1. Calling .NET Web Service from ARS Filter
2. There are .NET API Calls in .NET Web Service for Getting Entry and
Creating Entry (ARS filter and .NET Remedy API calls are belongs to same
Server).
I am getting below error while execution of the above 2 steps even the API
Calls executed successfully.
ARERR [8939] The AR System Plug-In server is not responding. Cannot connect to
the system at this time. Contact your AR System Administrator for assistance.
How to avoid the above error from the application.
Success Scenario
1. Calling .NET Web Service from ARS Filter
2. There are .NET API Calls in .NET Web Service for Getting Entry and
Creating Entry (ARS filter belongs to one server and .NET Remedy API calls made
on different Server).
Please help me on solving this issue.
Thanks &Regards,
Gopala Krishna.Peela
_________________________________________________________
' BTGS ESG; Virtusa India (P) Ltd., India - 044-42002700- Extn 3253
gopalakrishnap @virtusa.com <mailto:[EMAIL PROTECTED]>
---------------------------------------------------------------------------------------------
This message, including any attachments, contains confidential information
intended for a specific individual and purpose, and is intended for the
addressee only. Any unauthorized disclosure, use, dissemination, copying, or
distribution of this message or any of its attachments or the information
contained in this e-mail, or the taking of any action based on it, is strictly
prohibited. If you are not the intended recipient, please notify the sender
immediately by return e-mail and delete this message.
__20060125_______________________This posting was submitted with HTML in it___
__20060125_______________________This posting was submitted with HTML in it___
__20060125_______________________This posting was submitted with HTML in it___
---------------------------------------------------------------------------------------------
This message, including any attachments, contains confidential information
intended for a specific individual and purpose, and is intended for the
addressee only. Any unauthorized disclosure, use, dissemination, copying, or
distribution of this message or any of its attachments or the information
contained in this e-mail, or the taking of any action based on it, is strictly
prohibited. If you are not the intended recipient, please notify the sender
immediately by return e-mail and delete this message.
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the
Answers Are"
