IBM Support

Increasing the maximum JVM heap size of the WebSphere Message Broker HTTP listener

Troubleshooting


Problem

The broker-wide listener process (biphttplistener) handles both inbound requests and outbound replies for the HTTPInput and HTTPReply nodes across an entire broker. By default, this listener is started with a maximum JVM heap size of 192MB. It is possible, based on inbound request rates and message sizes, that the default maximum size is not sufficient.

Symptom

If the JVM heap of the HTTP listener attempts to grow beyond the maximum JVM heap size, Java OutOfMemory errors are reported through several files in the common/errors directory of your broker's workpath:
heapdump.date.time.pid.0001.phd
javacore.date.time.pid.0002.txt
Snap.date.time.pid.0003.trc

The stderr/console file of your HTTP listener will also include the error: "java.lang.OutOfMemoryError".
This can be found, here:
{MQSI_WORKPATH}/components/<broker>/httplistener/

[{"Product":{"code":"SSKM8N","label":"WebSphere Message Broker"},"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Component":"Biphttplistener","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"},{"code":"PF035","label":"z\/OS"}],"Version":"8.0;7.0;6.1","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Log InLog in to view more of this document

This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.

Document Information

Modified date:
28 April 2025

UID

swg21626362

Page Feedback