SAP Knowledge Base Article - Public

1631710 - Tomcat will not start

Symptom

Apache Tomcat will not start.

Reviewing Tomcat.log shows us the following:

13-09-11 05:52:22:357 - {ERROR} [/InfoViewApp].[action] Thread [http-8080-Processor14];  Servlet.service() for servlet action threw exception
java.lang.IllegalStateException
 at org.apache.catalina.connector.ResponseFacade.sendError(ResponseFacade.java:418)
 at javax.servlet.http.HttpServletResponseWrapper.sendError(HttpServletResponseWrapper.java:117)
 at com.businessobjects.sdk.credential.WrappedServletResponse.sendError(WrappedServletResponse.java:30)
 at com.wedgetail.idm.sso.AbstractAuthenticator.writeAuthenticationChallenge(AbstractAuthenticator.java:1936)
 at com.wedgetail.idm.sso.MechChecker.authenticate(MechChecker.java:147)
 at com.wedgetail.idm.sso.AbstractAuthenticator.authenticate(AbstractAuthenticator.java:1444)
 at com.wedgetail.idm.sso.AbstractAuthenticator.checkAuthenticationOnly(AbstractAuthenticator.java:1330)
 at com.wedgetail.idm.sso.AbstractAuthenticator.checkAuthentication(AbstractAuthenticator.java:1139)
 at com.wedgetail.idm.sso.AuthFilter.doFilter(AuthFilter.java:148)
 at com.businessobjects.sdk.credential.WrappedResponseAuthFilter.doFilter(WrappedResponseAuthFilter.java:66)
 at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
 at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
 at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
 at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
 at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
 at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
 at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
 at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
 at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
 at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
 at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
 at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
 at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
 at java.lang.Thread.run(Thread.java:595)

Environment

  • Business Objects Enterprise 3.1 with Tomcat55
  • Crystal Reports Server 2008 with Tomcat55

Reproducing the Issue

Attempt to start Apache Tomcat using the Central Configuration Manger

Cause

Apache Tomcat's Java Max heap size was set too high in the Tomcat Configuration console. It was set to 2048 MB.

Resolution

  1. Open the Tomcat Configuration (found in Start Menu > Programs > Tomcat > Tomcat Configuration).
  2. Browse to the Java tab.
  3. Set the Initial Memory Pool Size to 1024.
  4. Set the Maximum Memory Pool size to 1024.
  5. Click OK to save your changes.
  6. Restart Apache Tomcat using the Central Configuration Manager.

Keywords

KBA , BI-BIP-ADM , BI Servers, security, Crystal Reports in Launchpad , Problem

Product

SAP Crystal Server XI