Update the armonitor configuration file for plug-in server

If the plug-in server runs out of memory, you must update the armonitor configuration file to troubleshoot the issue. You must perform this activity only once on the staging production server.

Before you begin

Before you update the armonitor configuration file, ensure that:

• The jmx remote port is not used by any other process. 
• The heap dump directory has sufficient space. 

• You do not introduce any line breaks when using the code text illustrated in the following section. Use the code text without line breaks. Soft breaks are used in the examples only to facilitate readability.

To update the armonitor configuration file for the plug-in server

1. Take a backup of armonitor configuration file located at the following location:
   <Installation directory>\Conf 

2. Open the armonitor configuration file and search for the following AR Java plug-in server entry:
   

   -Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port=12555 -Dcom.sun.management.jmxremote.ssl=false
   -Dcom.sun.management.jmxremote.authenticate=false -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=<ARSystem Install Directory>\DB
   -XX:OnOutOfMemoryError="taskkill /PID %p /F"

3. Append the following flag to the plug-in entry:
   

   "...\Java\jre1.8.0_92\bin\java" -Xmx512m -Djava.net.preferIPv4Stack=true -Djava.net.preferIPv6Addresses=false -classpath "...\BMC Software\ARSystem\pluginsvr;...\ARSystem\pluginsvr\arpluginsvr7604_build002.jar" com.bmc.arsys.pluginsvr.ARPluginServerMain -x <server-name> -i "...\ARSystem" 

4. Save the changes and start the BMC Remedy AR System Server.
   

5.  Verify if the plugin server is up and running.

Related topics

• Overview of the portmapper service 
• Troubleshooting issues with plug-in servers
• Setting ports and RPC numbers