Sorted. Configuration. Will have to spend a bit of time getting the ar.conf files cleaned up - they tend to get somewhat chaotic in time.
On 7 August 2013 15:04, Dave Barber <[email protected]> wrote: > And yes, the plugin-log-level is set to 100. > > > On 7 August 2013 15:03, Dave Barber <[email protected]> wrote: > >> Hi Kiran, >> >> The plugin is definitely being loaded (from the plugin log) : >> */ARFILTERAPI Plug-In Loaded: ARSYS.ARF.WEBSERVICE version 1 >> */ ARPluginSetProperties defined >> */ ARPluginInitialization defined >> */ ARPluginTermination defined >> */ ARPluginCreateInstance defined >> */ ARPluginDeleteInstance defined >> */ ARPluginEvent undefined >> */ ARFilterApiCall defined >> >> And checking processes shows the arplugin server at least "existing". >> Nothing untoward in the error log. >> arsystem 12367 12356 0 13:50:51 pts/1 0:00 grep test >> arsystem 25748 25730 0 14:47:40 ? 0:41 ./arplugin -s >> remedy-app-test-1 -i /apps/rem-app-test-1 >> >> Regards >> >> Dave >> >> >> >> On 7 August 2013 11:48, Hullule, Kiran <[email protected]> wrote: >> >>> ** >>> >>> You mentioned this is 7.0.1 version if that is the case then you don’t >>> expect log4_pluginsvr.xml file . as per your description you are using WSDL >>> it means you are using AR Webservice plugin.. you need to check in plugin >>> logs whether or not this webservice plugin (Alias Name: >>> REMEDY.ARF.WEBSERVICE) is loaded or not.. if not check Server-Plugin-Alias >>> parameter value… see if you can make the server name resolvable to the >>> client machine (for testing purpose if you are running that specific run >>> process using Active Link) , if you are using Filter run process then just >>> check the Plugin-port mentioned or not for webservice plugin alias.**** >>> >>> ** ** >>> >>> *From:* Action Request System discussion list(ARSList) [mailto: >>> [email protected]] *On Behalf Of *Dave Barber >>> *Sent:* Wednesday, August 07, 2013 4:11 PM >>> >>> *To:* [email protected] >>> *Subject:* Re: Plugin server troubleshooting (7.01)**** >>> >>> ** ** >>> >>> ** **** >>> >>> ** ** >>> >>> Interesting, log4j_pluginsvr.xml doesn't appear to exist on any of our >>> test environments.**** >>> >>> The 9760 error appears when trying to run a process via the user tool >>> (creates a record, a filter then consumes a WSDL).**** >>> >>> ** ** >>> >>> On 6 August 2013 16:19, Grooms, Frederick W <[email protected]> >>> wrote:**** >>> >>> ** **** >>> >>> Java log is set from a different place {AR Install >>> Dir}/pluginsvr/log4j_pluginsvr.xml**** >>> >>> **** >>> >>> You also didn’t mention where you are seeing the 9760 error**** >>> >>> **** >>> >>> Fred**** >>> >>> **** >>> >>> **** >>> >>> *From:* Action Request System discussion list(ARSList) [mailto: >>> [email protected]] *On Behalf Of *Hullule, Kiran >>> *Sent:* Tuesday, August 06, 2013 10:11 AM >>> *To:* [email protected] >>> *Subject:* Re: Plugin server troubleshooting (7.01)**** >>> >>> **** >>> >>> ** **** >>> >>> You need to enabled plugin-log-level to “All” from server admin console. >>> Also check whether you have server name resolvable and plugin port is >>> mentioned correctly.**** >>> >>> **** >>> >>> *From:* Action Request System discussion list(ARSList) [ >>> mailto:[email protected] <[email protected]>] *On Behalf Of *Dave >>> Barber >>> *Sent:* Tuesday, August 06, 2013 8:38 PM >>> *To:* [email protected] >>> *Subject:* Plugin server troubleshooting (7.01)**** >>> >>> **** >>> >>> ** **** >>> >>> I'm rebuilding a couple of our test servers into a server group for >>> testing of some issues around our live migration from 7.0.1 to 7.6.04. All >>> environments are running on Solaris, AR 7.0.1 patch 012 and Oracle 10g.* >>> *** >>> >>> **** >>> >>> Server group configuration was (for the most part) easy enough, however >>> I'm having issues getting the plugin server running. The plugin server has >>> never been in regular/active use on either of these server, and awkwardly >>> I've never had to do any in-depth diagnosis of the plugin server (its >>> always worked on the live system - with the exception of the 7.6.04 >>> migration). So services appear to start without issue - plugin server >>> starts, nothing in its error log.**** >>> >>> -- STARTUP**** >>> >>> (ARNOTE 0) >>> ARMonitor child process (pid:25601) started. >>> ./arplugin >>> .... >>> Action Request System(R) Plug-In Server Version 7.0.01 Patch 012 >>> 201010211330 >>> Copyright (c) 2001 - 2006 BMC Software, Inc. >>> All rights reserved. >>> >>> Loaded Web Services plugin properly**** >>> >>> - arplugin log file**** >>> >>> <PLGN> <TID: 000001> <RPC ID: 0000000000> <Queue: Dispatcher> >>> <Client-RPC: 000000> /* Tue Aug 06 2013 14:47:41.3884 >>> */<ARSYS.ARDBC.CONFIGFILE> <FINEST> Entering ARPluginInitialization >>> <PLGN> <TID: 000001> <RPC ID: 0000000000> <Queue: Dispatcher> >>> <Client-RPC: 000000> /* Tue Aug 06 2013 14:47:41.3890 >>> */<ARSYS.ARDBC.CONFIGFILE> <CONFIG> Configuration File >>> /apps/rem-app-test-1/conf/ar.conf >>> <PLGN> <TID: 000001> <RPC ID: 0000000000> <Queue: Dispatcher> >>> <Client-RPC: 000000> /* Tue Aug 06 2013 14:47:41.3892 >>> */<ARSYS.ARDBC.CONFIGFILE> <FINEST> Entering ConfigDeletePlaceHolders >>> (/apps/rem-app-test-1/conf/ar.conf) >>> <PLGN> <TID: 000001> <RPC ID: 0000000000> <Queue: Dispatcher> >>> <Client-RPC: 000000> /* Tue Aug 06 2013 14:47:41.3900 >>> */<ARSYS.ARDBC.CONFIGFILE> <FINEST> Leaving ConfigDeletePlaceHolders >>> <PLGN> <TID: 000001> <RPC ID: 0000000000> <Queue: Dispatcher> >>> <Client-RPC: 000000> /* Tue Aug 06 2013 14:47:41.3902 >>> */<ARSYS.ARDBC.CONFIGFILE> <FINEST> Leaving ARPluginInitialization >>> <PLGN> <TID: 000047> <RPC ID: 0000000000> <Queue: Dispatcher> >>> <Client-RPC: 000000> /* Tue Aug 06 2013 14:47:41.3968 */<ARSYS.ARDBC.LDAP> >>> <FINEST> Entering ARPluginCreateInstance >>> <PLGN> <TID: 000047> <RPC ID: 0000000000> <Queue: Dispatcher> >>> <Client-RPC: 000000> /* Tue Aug 06 2013 14:47:41.3971 */<ARSYS.ARDBC.LDAP> >>> <FINEST> Leaving ARPluginCreateInstance >>> <PLGN> <TID: 000047> <RPC ID: 0000000000> <Queue: Dispatcher> >>> <Client-RPC: 000000> /* Tue Aug 06 2013 14:47:41.3973 >>> */<ARSYS.ARDBC.CONFIGFILE> <FINEST> Entering ARPluginCreateInstance >>> <PLGN> <TID: 000047> <RPC ID: 0000000000> <Queue: Dispatcher> >>> <Client-RPC: 000000> /* Tue Aug 06 2013 14:47:41.3975 >>> */<ARSYS.ARDBC.CONFIGFILE> <FINEST> Leaving ARPluginCreateInstance**** >>> >>> To be honest its driving me a bit potty - I've compared all that I know >>> of the configuration between one of our other environments and cannot >>> figure out why the plugin server is failing (we just get a message claiming >>> "ARERR 9760 Cannot establish a network connection to the AR System Plug-in >>> server". The plugin port is defined as it is on all of our other test (and >>> live) environments.**** >>> >>> No other logs available (no sign of the arjavaplugin log on this 7.0.1 >>> instance, should it be there?).**** >>> >>> Regards >>> >>> Dave**** >>> >>> **** >>> >>> **** >>> >>> _ARSlist: "Where the Answers Are" and have been for 20 years_ **** >>> >>> ** ** >>> >>> _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"
