The Java Plugin Server can be restarted manually following one of these processes:

1- Restarting the Java Plugin Server process using the AR System Server Group Console
(This first method is the recommended by BMC).
2- At OS level killing the Java Plugin Server process and let the armonitor process to restart it.

VIDEO




STEPS

1- Restart the Java Plugin Server using the AR System Server Group Console
Note: This is applicable for both AR System single Server environments and Server Groups.

a) Login into the application with an Administrator user.

b) Go to the Applications Floating menu > Remedy Management Console > AR System Server Group Console *
* Available from AR version 18.05 onwards. For lower versions of ARS use the method 2.

     

c) Go to Manage Processes

     


d) Check the following steps:

   1- You can select which processes to list and for which servers, depending if you want to restart the Java Plugin Server
    for one or more AR Servers.
    For this example the steps are for one AR Server.
    Note: The screenshots show a BMC Internal Testing Host Name, obviously you will see your own AR Server(s).
    Select Host.

   2- Select the AR Server (Host Name) from the drop down menu.

   3- Select the process line belonging to the Java Plugin Server which is BMC:DefaultJavaPluginServer

   4- Select the Operation: Restart

   5- Press the Execute/Run button. 



e) The Java Plugin Server process will restart. It takes a couple of seconds so you may see the error ARERR 8760 displayed:

     

This is normal and as soon as you refresh the page it will disappear.

The Java Plugin Server has now been restarted.


2- Restart the Java Plugin Server at OS level killing the main Java process running the Java Plugin Server

Unix/Linux
To restart the Java Plugin Server in Linux we need to find out the Process ID of the running Java process belonging to the Java Plugin Server.
Depending the version of AR being used there are 2 different ways.

For AR Server versions up to 9.1.03.x
1- Locate the armonitor.conf file (usually at /etc/arsystem/[serverName]/armonitor.conf)

2- Check the entry for the main Java Plugin server. This will be the java command line which is for the ARPluginServerMain
Example:
......
/usr/lib/jvm/java-1.7.0-openjdk.x86_64/jre/bin/java -Xmx512m -classpath /opt/bmc/ARSystem/pluginsvr:/opt/bmc/ARSystem/pluginsvr/arpluginsvr90_build001.jar:/opt/bmc/ARSystem/approval/bin/armaskingImpl90_build001.jar:/opt/bmc/ARSystem/api/lib/arcmnapp90_build001.jar com.bmc.arsys.pluginsvr.ARPluginServerMain -x {AR Server Name} -i /opt/bmc/ARSystem
​......

3- Locate the same java process running in the Unix/Linux box. This can be done doing the following:
    a) Type in the Shell:
          ps -ef|grep java|grep ServerMain
    b) The result will be the running java process belonging to the main Remedy Java Plugin server.
          Example:
             # ps -ef|grep java|grep ServerMain
             root     28497 27322  0 Jun15 ?        02:52:19 ./java -Xmx512m -classpath          
             /opt/bmc/ARSystem/pluginsvr:/opt/bmc/ARSystem/pluginsvr/arpluginsvr90_build001.jar:/opt/bmc/ARSystem/approval/bin/armaskingImpl90_build001.jar:/opt/bmc/ARSystem/api/lib/arcmnapp90_build001.jar
             com.bmc.arsys.pluginsvr.ARPluginServerMain -x {AR Server Name} -i /opt/bmc/ARSystem
             #

4- To kill the process use the KILL command against the Java Plugin Server PID:
          Example (following the above):
          kill -9 28497

5- The Java process will be restarted right away by AR Armonitor. We can check if the related Java process is running by typing again:
          ps -ef|grep java|grep ServerMain

6- The running Remedy Java Plugin server process will be displayed this time having a different PID which is as expected.
          Example:
             # ps -ef|grep java|grep ServerMain
             root     12528 11317  0 Jun15 ?        02:52:19 ./java -Xmx512m -classpath          
             /opt/bmc/ARSystem/pluginsvr:/opt/bmc/ARSystem/pluginsvr/arpluginsvr90_build001.jar:/opt/bmc/ARSystem/approval/bin/armaskingImpl90_build001.jar:/opt/bmc/ARSystem/api/lib/arcmnapp90_build001.jar
             com.bmc.arsys.pluginsvr.ARPluginServerMain -x {AR Server Name} -i /opt/bmc/ARSystem
             #
7- The Remedy Java Plugin server has now been restarted.

For AR Server versions from 9.1.04.x and higher
For the different AR running processes ALIAS were introduced to facilitate the identification of such processes.
The grep command to be used will include the string - javapluginserver - since for the Java Plugin Server the ALIAs associated to it is: javapluginserver

This can be checked for example in the armonitor.log file which shows the alias name for all processes:
.................
*/ Processes are named as follows:
*/ Process Name [ARSERVER], Process ID [740], Process Command [/opt/java/bin/java -classpath /opt/java/lib/bmcext/* -jar /opt/bmc/ARSystem/bin/arserver.jar -s arserver01 -i /opt/bmc/ARSystem -l /etc/arsystem/arserver01]
*/ Process Name [javapluginserver], Process ID [1250], Process Command [/opt/java/bin/java  -classpath /opt/bmc/ARSystem/pluginsvr:/opt/java/lib/bmcext/*:/opt/bmc/ARSystem/pluginsvr/arpluginsvr91_build009.jar:/opt/bmc/ARSystem/api/lib/arcmnapp91_build009.jar com.bmc.arsys.pluginsvr.ARPluginServerMain -x arserver01 -i /opt/bmc/ARSystem -alias javapluginserver]
*/ Process Name [arplugin], Process ID [1271], Process Command [/opt/bmc/ARSystem/bin/arplugin -s arserver01 -i /opt/bmc/ARSystem -alias arplugin]
*/ Process Name [ardispatcher], Process ID [1301], Process Command [/opt/bmc/ARSystem/bin/arsvcdsp -s arserver01 -d /opt/bmc/ARSystem -alias ardispatcher]
*/ Process Name [fts_indexer], Process ID [1313], Process Command [/opt/java/bin/java  -classpath /opt/java/lib/bmcext/*:/opt/bmc/ARSystem/pluginsvr/fts/secondary:/opt/bmc/ARSystem/pluginsvr/fts/core:/opt/bmc/ARSystem/pluginsvr:/opt/bmc/ARSystem/pluginsvr/arpluginsvr91_build009.jar: com.bmc.arsys.pluginsvr.ARPluginServerMain -x arserver01 -i /opt/bmc/ARSystem -m -alias fts_indexer]
.................

The command is:
          ps -ef|grep java|grep javapluginserver

Example of the result:
...........
bash-4.2$ ps -ef|grep java|grep javapluginserver
bmcuser   1250   694  0 Oct17 ?        00:02:34 /opt/java/bin/java -classpath /opt/bmc/ARSystem/pluginsvr:/opt/java/lib/bmcext/*:/opt/bmc/ARSystem/pluginsvr/arpluginsvr91_build009.jar:/opt/bmc/ARSystem/api/lib/arcmnapp91_build009.jar com.bmc.arsys.pluginsvr.ARPluginServerMain -x arserver01 -i /opt/bmc/ARSystem -alias javapluginserver
...........
We proceed with the Kill command to stop the process.
For the above example:
          kill -9 1250

The armonitor process will restart the process right away.

b) Windows
1- Locate the armonitor.cfg file (usually at C:\Program Files\BMC Software\ARSystem\Conf)

2- Check the entry for the main Java Plugin server. This will be the java command line which is for the ARPluginServerMain
          Example:
              "....\Java\jre7\bin\java" -Xmx512m -classpath "....\BMC Software\ARSystem\pluginsvr;....\BMC Software\ARSystem\pluginsvr\arpluginsvr91_build001.jar;.....\BMC
             Software\ARSystem\approval\bin\armaskingImpl91_build001.jar;.....\BMC Software\ARSystem\arserver\api\lib\arcmnapp91_build001.jar" com.bmc.arsys.pluginsvr.ARPluginServerMain -x {AR Server Name} -i
              ".....\BMC Software\ARSystem" –m

3- To identify which java process in the Windows Task Manager belongs to this process mentioned above, the best way is to set the Task Manager Console this way:
          In the Task Manager > View > Select Columns…

          

4- Select the columns PID and Command Line

          

          
And press OK

5- Now we check and look the armonitor.cfg line for the main Java Plugin server and in the Task Manager’s Command Line column to identify it.

          

6- Once identified, note down the PID, for this example is 2432.

7- Right click on it and terminate the process.

8- The armonittor.exe will start the java process again under a different PID  as per the below scr.


         



The arjavaplugin.log file will also be updated. This is located at:
     .....\BMC Software\ARSystem\Arserver\Db\arjavaplugin.log for Windows, or
     .../opt/bmc/ARSystem/db/arjavaplugin.log for Linux.