Symptom
- How to increase the -Xmx value to increase the JAVA heap size of Tomcat in BI 4.x?
- Tomcat is crashing.
- Receiving out of memory errors in Tomcat logs.
- Current allocated memory does not fit the platform needs.
- Slow application performance during peak usage times.
- High JVM garbage collection activity observed in logs.
- Repeated "java.lang.OutOfMemoryError: Java heap space" exceptions.
- Frequent occurrences of "503 Service Unavailable" errors during peak usage.
- BI services timing out or failing to respond within expected timeframes.
- Inability to run administrative tasks or schedule BI reports during high load periods.
Read more...
Environment
- SAP BusinessObjects Business Intelligence platform 4.x
- All supported Windows operating systems
- All supported Tomcat web application servers
Product
SAP BusinessObjects Business Intelligence platform 4.1 ; SAP BusinessObjects Business Intelligence platform 4.2 ; SAP BusinessObjects Business Intelligence platform 4.3
Keywords
Tomcat memory, crash, hang, Maximum memory pool, windows, BI4, BI 4, application server, Heap size, JVM settings, OutOfMemoryError, Peak usage, Resource consumption, BI System monitoring. , KBA , BI-BIP-DEP , Webapp Deployment, Networking, Vulnerabilities, Webservices , How To
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.
SAP Knowledge Base Article - Preview