Voice Browser service OUT_OF_MEMORY exceptions

If the Voice Browser service terminates with an OUT_OF_MEMORY exception (indicated by an alarm in Management Station), verify the following to help pinpoint the cause and possible solution:

• Did you assign a 1-port role to a host then modify it to start more than one Voice Browser service instance? These roles are used primarily for demos and development purposes, not for deployment. Assign another role with a greater port density.
• Try increasing the JVM heap size allocated to the Voice Browser service. What you increase it to depends the number of ports each Voice Browser service instance has. The default is -Xmx384m (384 MB), a reasonable upper bound for an average application deployed with 23 ports. For instances with 46 ports, try -Xmx512m. Export the role file, edit the -Xmx option on the Voice Browser service command line, then reapply the new role.

  Make sure that the host has enough physical memory to support the increased heap size, otherwise caller experience will likely suffer, as manifested by timeouts, stuttering, misrecognitions, and so on.

  Increasing the heap size also increases the risk of long pauses during Java heap processing. If you increase the heap size beyond 1024 MB and it still is not enough, consider reducing the number of ports per Voice Browser service instance and doubling the number of instances. For example, instead of four Voice Browser service instances with 46 ports each, customize the role to run eight instances of 23 ports each.