Troubleshooting
Problem
Currently published recommendations for setting Prepared Statement Cache sizes for IBM® WebSphere® Application Server might result in very large Application Server memory footprints, and in extreme cases, OutOfMemory errors or crashes of the Java™ process.
These are memory utilization considerations needed for applications with very large prepared statement cache sizes.
Document Location
Worldwide
[{"Line of Business":{"code":"LOB77","label":"Automation Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"ARM Category":[{"code":"a8m50000000CdYAAA0","label":"J2C-ConnectionPooling-JDBCDrivers-\u003EConnection Pooling-J2C-DB Connections-\u003EConnection Pooling"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Version(s)"}]
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.
Was this topic helpful?
Document Information
More support for:
WebSphere Application Server
Component:
J2C-ConnectionPooling-JDBCDrivers->Connection Pooling-J2C-DB Connections->Connection Pooling
Software version:
All Version(s)
Document number:
6410242
Modified date:
03 March 2025
UID
ibm16410242
Manage My Notification Subscriptions