Monitoring and configuring mid tier memory

This topic describes the memory-related issues for .

Allocating enough memory for your application and the mid tier

If there is not enough memory allocated to your application server to run your  application on the , the application server will produce out-of-memory exceptions. (You can see this in the application server log file.)

To avoid out-of-memory exceptions

1. Shut down your application server.
2. Allocate enough memory to the application server.
3. Restart the application server.
4. If the Enable Cache Persistence check box is selected in the BMC Remedy Mid Tier Configuration Tool, flush the cache.
   For more information, see Configuring the Cache Settings page.

Monitoring mid-tier memory use and performance in real time

To monitor mid-tier memory use and performance in real time through a web server, such as Tomcat, perform the following procedure. By default, real-time mid-tier monitoring is disabled.

To monitor mid-tier memory use and performance in real time in Tomcat

1. Add the following parameters to the Java Virtual Machine (JVM) started by the mid-tier JavaServer Pages (JSP) or servlet engine.
   • To monitor the mid tier on the mid-tier host:
     At the At the command-line prompt, set the JAVA_OPTS environment variable as follows, and then start Tomcat:
     set JAVA_OPTS=-
     Dcom.sun.management.jmxremote
     Alternatively, add that parameter to the JAVA_OPTS entry in the TomcatInstallDir/bin/catalina.bat file, and then restart Tomcat.
   • To monitor the mid tier remotely:
     At the command-line prompt, set the JAVA_OPTS environment variable as follows, and then start Tomcat:
     set JAVA_OPTS=-
     Dcom.sun.management.jmxremote.authenticate
     =false
     -Dcom.sun.management.jmxremote.ssl=false
     -Dcom.sun.management.jmxremote
     -Dcom.sun.management.jmxremote.port=portNumber
     portNumber is the port number to connect to your JMX Remote Method Invocation (RMI) connector. Specify an unused port number.
     Alternatively, add those parameters to the JAVA_OPTS entry in the TomcatInstallDir/bin/catalina.bat file, and then restart Tomcat.
2. To enable real-time monitoring, select the Enable Mid Tier Performance MBean check box on the General Settings page In the BMC Remedy Mid Tier Configuration Tool. See Configuring-general-mid-tier-settings.
3. Restart the .
   You can monitor the performance by analyzing the entries in the armidtier.log file. For more information, see Mid-Tier-logging.

Configuring Apache Tomcat after installing 

When you are not using out-of-the-box Apache Tomcat provided by BMC and when there is a huge load on Apache Tomcat, the Apache Tomcat might stop responding due to OutOfMemory error. To overcome this issue, you must modify the JAVA_OPTS="$JAVA_OPTS -XX:MaxMetaspaceSize parameter.

For Windows:

1. From the Microsoft Windows Start menu, select Programs > BMC Software > AR System 1 > BMC Remedy Mid Tier > Configure Tomcat.
2. On the Java tab, select Java Option section.
3. Set the JAVA_OPTS="$JAVA_OPTS -XX:MaxMetaspaceSize parameter to 512m.

For UNIX: 

Specify the value of JAVA_OPTS="$JAVA_OPTS -XX:MaxMetaspaceSize parameter to 512m in the catalina.sh file under Apache Tomcat installation directory.