What to check when troubleshooting AR Java Plugin Server issues. |
This knowledge article may contain information that does not apply to version 21.05 or later which runs in a container environment. Please refer to Article Number 000385088 for more information about troubleshooting BMC products in containers. Legacy ID:KA288928 The AR Plugin Server loads plugins which extend the functionality of ARSystem to features written in java, and provide a vehicle to communicate with other products.
There is a C version - arplugin.exe or arplugin - and a Java version. This article is on the Java version. To troubleshoot AR Java Plugin Server itself, the following are the steps you need to check:
1. Verify the java version. This is crucial as the wrong java version on the AR Server will cause unexpected results. Open a Command Prompt session (Windows) or a bash console (Linux,Unix) and type java -version to get the current Java version being used. Examples: [Windows] C:\Users\Administrator>java -version java version "1.8.0_92" Java(TM) SE Runtime Environment (build 1.8.0_92-b14) Java HotSpot(TM) 64-Bit Server VM (build 25.92-b14, mixed mode) C:\Users\Administrator> [Linux, Unix] -bash-4.2# java -version java version "1.7.0_85" OpenJDK Runtime Environment (rhel-2.6.1.2.el7_1-x86_64 u85-b01) OpenJDK 64-Bit Server VM (build 24.85-b03, mixed mode) -bash-4.2# 2 armonitor.cfg/armonitor.conf file. Verify the AR Plugin server is started. The line in armonitor.cfg/armonitor.conf will specify java and include com.bmc.arsyst.pluginsvr.ARPluginServerMain in the commandline. Examples: [Windows] - ...\BMC Software\ARSystem\Conf "C:\Program Files\Java\jre1.8.0_92\bin\java" -Xmx512m -classpath "C:\Program Files\BMC Software\ARSystem\pluginsvr;C:\Program Files\BMC Software\ARSystem\pluginsvr\arpluginsvr91_build002.jar;C:\Program Files\BMC Software\ARSystem\approval\bin\armaskingImpl91_build002.jar;C:\Program Files\BMC Software\ARSystem\arserver\api\lib\arcmnapp91_build002.jar" com.bmc.arsys.pluginsvr.ARPluginServerMain -x {Server_Name} -i "C:\Program Files\BMC Software\ARSystem" -m [Linux, Unix] - /etc/arsystem/{servername} /data1/java/x64/jdk1.8.0_60/jre/bin/java -Xmx2048m -Djava.net.preferIPv4Stack=true -Djava.net.preferIPv6Addresses=false -classpath /data1/bmc/ARSystem/pluginsvr:/data1/bmc/ARSystem/pluginsvr/arpluginsvr91_build001.jar:/data1/bmc/ARSystem/approval/bin/armaskingImpl91_build001.jar:/data1/bmc/ARSystem/api/lib/arcmnapp91_build001.jar com.bmc.arsys.pluginsvr.ARPluginServerMain -x {Server_Name} -i /data1/bmc/ARSystem 3. armonitor.log file. Verify the java process did not die. If it does, it may indicate the AR Plugin Server is dying. 4. pluginsvr_config.xml file.
This file is located under <ar_install_dir>\pluginsvr folder for the Java Plugin Server running with AR Server. Open this file and check the following:
> What is the java port number mentioned, <port>9999</port> Valid values: unused port from 1024 to 64000 Default value: 9999 > Check if this port is available and not blocked. > If this port number is already being used by another process or blocked in your environment, you will have to assign a new port number which is available and un-used and restart AR Server service > Check that all the “<pathelement” tags have a relative path and no variable name like $AR_INSTALL_DIR$, etc. > Check that the jar files mentioned with the “<pathelement type="location">” and “<filename>” tag do exists and have all the required permissions. > Make sure that “<server_name>” has a valid AR Server short name and “<server_port>” has the correct AR TCP port number. NOTE: There are typically several instances of the Java Plugin Server running on the system. For example, Atrium Core launches two separate instances, and each has a different location for pluginsvr_config.xml, and run on different default ports: 9555 and 9556. If the Plugin Server is loaded and running properly, there may still be issues with particular plugins. Below are next steps for issues related to plugins. 5. Review the arjavaplugin.log to find the errors/exceptions.
The file will be located under <ar_install_dir>\db (Unix)
<ar_install_dir>/ARServer/db (Windows)
6. If arjavaplugin.log also does not give any clear picture then enable the Java Plugin server in Debug mode. Check these articles depending your ARS version to know how to do this: - AR system version 8.x or lower: Remedy - Server - v8.x How to enable java plugin logging in DEBUG mode - AR system version 9.x or higher: Remedy - Server - v.9.x How to enable DEBUG Java Plugin Server Logging in AR System |