SAP Knowledge Base Article - Preview

2715331 - Tomcat configured with JMX does not start after upgrade

Symptom

  • Tomcat configured with Java Management Extensions (JMX) does not start after upgrade.
  • It immediately goes into stopped state after starting.
  • Tomcat stderr.logs may show the following errors:
    IllegalStateException (under jmxremotelifecyclelistener)


Read more...

Environment

  • SAP BusinessObjects Business Intelligence Platform 4.x (BI 4.0 / 4.1 / 4.2)
  • Windows
  • Linux / Unix 

Product

SAP BusinessObjects Business Intelligence platform 4.0 ; SAP BusinessObjects Business Intelligence platform 4.1 ; SAP BusinessObjects Business Intelligence platform 4.2

Keywords

KBA , BI-BIP-DEP , Webapp Deployment, Networking, Vulnerabilities, Webservices , Problem

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.