cancel
Showing results for 
Search instead for 
Did you mean: 

Error in Apache Tomcat - service doesn´t start

Former Member
0 Kudos

Hello,

I installed the SAP BOP BI PLATFORM 4.0 SP05 (Patch03)... but now when I try to start the Apache Tomcat service (services.msc) in Windows Server 2008 (R2) it show me the following error:

Windows could not start the Apache Tomcat service on Local Computer.

Error 1067: The process terminated unexpectedly.

I checket the log files in tomcat logs directory (<drive>:\SAPBO\Tomcat6\logs) and I see the following error in file stdout.log:

2013-10-26 03:40:48 Commons Daemon procrun stdout initialized

Error occurred during initialization of VM

Incompatible minimum and maximum heap sizes specified

Do you know how can I change the heap sizes memories (minimim and maximum) in SBOP BI PLATFORM 4.0 ?

Can you help me please?

Best regards,

samid

Accepted Solutions (1)

Accepted Solutions (1)

joo_migueldimas
Active Participant
0 Kudos

Hello samid,

I faced the same error, a few months ago... and what you need to do to solve this error is simple, you need to change the initial and maximum memory values of Tomcat.

For this you must to do the following:

1) Click the Windows START menu > All Programs > Tomcat > Tomcat Configuration

2) Select Java tab

3) Change the value of Initial memory pool to 2048

4) Change the value of Maximum memory pool to 3072

5) Apply the changes

6) Try to start again the service of Apache Tomcat service in Windows Services (services.msc)

Kind regards,

João Dimas

Former Member
0 Kudos

Hello,

This wasn´t related with Java virtual machine version, the error was related with Java memory (Initial and maximum).

Thanks João Dimas, that solution solved my problem!

Thank you,

samid

Answers (3)

Answers (3)

tedelam
Discoverer
0 Kudos

go into the tomcat directory in 'Program Files (x86)\SAP BusinessObjects\tomcat\logs' and look at the stdout.log, look for WARNING, correct what it is complaining about in here and you should be ok to start Tomcat

Former Member
0 Kudos
jimguo
Advisor
Advisor
0 Kudos

Hi,

The initial memory pool for Tomcat is more than the maximum memory

pool. The issue should be resolved by removing the initial memory pool

value.

Thanks.

Jim