10 Troubleshooting Suspense and Recycle Issues

Learn how to fix common problems that you may encounter when suspending and recycling pipeline event data records (EDRs) in Oracle Communications Billing and Revenue Management (BRM).

Topics in this document:

Increasing Heap Size to Avoid Performance Problems

If the searches you run in Suspense Management Center return particularly large results, your performance may slow noticeably, or you may get "Out of memory" error messages. The solution is to increase your maximum heap size. The exact amount varies significantly with your needs and system resources. If performance is poor or you get "Out of memory" messages frequently, start by doubling the maximum heap size to 128 MB. Remember, however, that making the heap size too large will degrade the performance of other processes.

Depending on whether you have a standalone or a WebStart BRM implementation, there are two ways to increase the maximum heap size.

To increase the heap size for standalone implementations:

  1. Edit the BRM_home/lib/runSMC.bat file to increase the heap size (memory allocation pool) to solve "Out of memory" messages.

    By default, Suspense Management Center has a maximum heap size of 64 MB. This variable is controlled by the -Xmx size entry in the Suspense Manager Center startup line in runSMC.bat. No -Xmx size entry is present in the startup line by default. To increase the heap size, add this entry and a number (in MBs) to the Suspense Management Center startup line.

    This example adds a 128 MB maximum heap size to Suspense Management Center:

    @start C:\PROGRA~1\COMMON~1\PORTAL~1\JRE\bin\javaw.exe -Xmx128m -cp ".;%SMCDIR%;%SMCDIR%\lib;%SMCDIR%\lib\suspensemgtmain.jar;%SMCDIR%\lib\pfc.jar;%SMCDIR%\3plibs\jh.jar;%SMCDIR%\lib\pcmext.jar;%SMCDIR%\lib\pcm.jar;%SMCDIR%\lib\Suspense_Management_Help_en.jar;%SMCDIR%\lib\Application_Center_Help_en.jar;" com.portal.appcenter.AppCenterMain suspensemgtsuite

    Note:

    Be sure to precede and follow the -Xmx size entry with a space.

  2. Stop and restart Suspense Management Center to make the change take effect.

To increase the heap size for WebStart implementations:

  1. Open your SuspenseManagement_locale.jnlp file.

  2. Change the j2se element to include a max-heap-size attribute.

    The default entry looks like this:

    <j2se version="1.4*"/>

    This sample entry changes the maximum heap size to 128 MBs:

    <j2se version="1.4*" max-heap-size="128m"/>

    Note:

    The maximum heap size specified in the JNLP file is used for all associated Suspense Management Center clients.

  3. Stop and restart Suspense Management Center to make the change take effect.

Unexpected Log Messages Caused by Missing MaxErrorRates Entry

Your pipeline output section must contain a MaxErrorRates registry section with at least one entry. If this entry is missing, your log files include a misleading message like this one: 

"16.11.2030 21:00:37 All checks are successful. File can be recycled."