Axton, We think this is a defect in armonitor with command lines that have exactly (or multiples) of 10 arguments. We fill fix the defect.
But in the mean time, if you're seeing this problem, you can workaround the issue by removing the option -m at the end of the monitor entry. [This option is not used by the Java plug-in server itself, and is retained just for backward compatibility for C plug-ins that may use it for whatever reason]. java -Xmx512m -classpath /usr/ar/sundev71/pluginsvr:/usr/ar/sundev71/pluginsvr/arpluginsvr71.jar com.bmc.arsys.plugin vr.ARPluginServerMain -x sundev71 -i /usr/ar/sundev71 Or, may be you can add an extra argument to ensure your command line does not 10 items, for example as in: java -DNoTenArgsNow="HaHaHa" -Xmx512m -classpath /usr/ar/sundev71/pluginsvr:/usr/ar/sundev71/pluginsvr/arpluginsvr71.jar com.bmc.arsys.plugin vr.ARPluginServerMain -x sundev71 -i /usr/ar/sundev71 -m AR System Plugin Server Version 7.1.00 Build 200708221849 Regards Appajee -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Axton Sent: Sunday, September 09, 2007 3:53 PM To: [email protected] Subject: New Java Plugin Server Problems Having trouble getting the new java based plugin server started under armonitor. armonitor.log shows the following: Sun Sep 9 18:21:46 2007 Failure occurred during execl() (ARERR 33) Sun Sep 9 18:21:46 2007 Bad address : ./java Sun Sep 9 18:21:46 2007 (ARNOTE 0) Sun Sep 9 18:21:46 2007 ARMonitor child process (pid:25366) started. ./java Sun Sep 9 18:21:46 2007 (ARNOTE 0) Sun Sep 9 18:21:46 2007 ARMonitor child process (pid:25366) died with 0. ./java ... Sun Sep 9 18:21:46 2007 Failure occurred during execl() (ARERR 33) Sun Sep 9 18:21:46 2007 Bad address : ./java Sun Sep 9 18:21:46 2007 (ARNOTE 0) Sun Sep 9 18:21:46 2007 Tried 4 restarts in 30 seconds. I give up at Sun Sep 9 18:21:46 2007 If I manually start the process with the command listed in armonitor, all seems well; the process starts and continues running. [EMAIL PROTECTED] /usr/ar/sundev71/bin]$ java -Xmx512m -classpath /usr/ar/sundev71/pluginsvr:/usr/ar/sundev71/pluginsvr/arpluginsvr71.jar com.bmc.arsys.plugin vr.ARPluginServerMain -x sundev71 -i /usr/ar/sundev71 -m AR System Plugin Server Version 7.1.00 Build 200708221849 This is on Solaris 10 sparc64x2 with a remote Oracle 10g instance running on linux x86-32x2. This only seems to be an issue when using libumem as the memory management library (enabled by setting the following at the top of the arsystem script): UMEM_DEBUG=default UMEM_LOGGING=transaction LD_PRELOAD=libumem.so.1 export UMEM_DEBUG UMEM_LOGGING LD_PRELOAD Without this, it starts just fine. Some system information: [EMAIL PROTECTED] /usr/ar/sundev71/bin]$ which java /usr/bin/java [EMAIL PROTECTED] /usr/ar/sundev71/bin]$ java -version java version "1.5.0_12" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_12-b04) Java HotSpot(TM) Server VM (build 1.5.0_12-b04, mixed mode) [EMAIL PROTECTED] /usr/ar/sundev71/bin]$ /usr/java/bin/java -version java version "1.5.0_12" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_12-b04) Java HotSpot(TM) Server VM (build 1.5.0_12-b04, mixed mode) [EMAIL PROTECTED] /usr/ar/sundev71/bin]$ uname -a SunOS sundev01 5.10 Generic_118833-33 sun4u sparc SUNW,Sun-Fire-280R # psrinfo -v Status of virtual processor 0 as of: 09/09/2007 18:40:17 on-line since 09/03/2007 03:06:09. The sparcv9 processor operates at 900 MHz, and has a sparcv9 floating point processor. Status of virtual processor 1 as of: 09/09/2007 18:40:17 on-line since 09/03/2007 03:06:11. The sparcv9 processor operates at 900 MHz, and has a sparcv9 floating point processor. [EMAIL PROTECTED] /usr/ar/sundev71/bin]$ cat /etc/arsystem/sundev71/armonitor.conf Monitor-directory: /usr/ar/sundev71 SNMP-agent-enabled: F #/usr/ar/sundev71/bin/arsnmpd --server sundev71 -f -c /usr/ar/sundev71/conf/arsnmpd.conf udp:161 /usr/ar/sundev71/bin/arserverd -s sundev71 -i /usr/ar/sundev71 -l /etc/arsystem/sundev71 /usr/ar/sundev71/bin/arsvcdsp -s sundev71 -d /usr/ar/sundev71 #/usr/ar/sundev71/bin/arservdsd -s sundev71 -i /usr/ar/sundev71 /usr/ar/sundev71/bin/arplugin -s sundev71 -i /usr/ar/sundev71 java -Xmx512m -classpath /usr/ar/sundev71/pluginsvr:/usr/ar/sundev71/pluginsvr/arpluginsvr71.jar com.bmc.arsys.pluginsvr.ARPluginServerMain -x sundev71 -i /um /usr/ar/sundev71/apps/aremail/emaild.sh start [EMAIL PROTECTED] /usr/ar/sundev71/bin]$ file /usr/ar/sundev71/bin/armonitor /usr/ar/sundev71/bin/armonitor: ELF 32-bit MSB executable SPARC Version 1, dynamically linked, stripped [EMAIL PROTECTED] /usr/ar/sundev71/bin]$ file /usr/ar/sundev71/pluginsvr /usr/ar/sundev71/pluginsvr: directory [EMAIL PROTECTED] /usr/ar/sundev71/bin]$ file /usr/ar/sundev71/pluginsvr/libarpluginjni71.so /usr/ar/sundev71/pluginsvr/libarpluginjni71.so: ELF 32-bit MSB dynamic lib SPARC Version 1, dynamically linked, not stripped [EMAIL PROTECTED] /usr/ar/sundev71/bin]$ file /usr/ar/sundev71/pluginsvr/libarjni71.so /usr/ar/sundev71/pluginsvr/libarjni71.so: ELF 32-bit MSB dynamic lib SPARC Version 1, dynamically linked, not stripped The question I have, is how do I start all the processes under armonitor with libumem, with the exception of the java based plugin server, until these issues are resolved? Axton Grams ________________________________________________________________________ _______ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
