cancel
Showing results for 
Search instead for 
Did you mean: 

Wily Introscope Enterprise Manager fails to start due to Java Heap

Former Member
0 Kudos

Hello All,

I just installed Wily Introscope for the first time. I have successfully installed it from the log below:

Summary

-


Installation: Successfulwith errors.

396 Successes

0 Warnings

1 NonFatalErrors

0 FatalErrors

I also confirm that the Introscope Enterprise Manager is started as a service.

However, when i try to launch enterprise by following the path All Programs > CA Wily > Introscope 8.2.3.5 > Introscope Enterprise Manager....

I get the error below:

3/29/11 07:11:46 PM PDT [ERROR] [Manager.Bootstrap] Load all Management Modules FAILED.

3/29/11 07:11:46 PM PDT [ERROR] [Manager] The EM failed to start. Java heap space

I have also adapted my Java Heap from 512 to 1024 in EMService.conf file but I still get same error. This was the recommendation in this related forum post -

Please help!!!!

Accepted Solutions (1)

Accepted Solutions (1)

allam_drebes
Advisor
Advisor
0 Kudos

Hi John,

Check note 1273028.

1273028 - Introscope 8 Release Notes

-


Release 8 SP2

Due to additional management module content the memory

consumption of the Enterprise Manager may increase. You may have

to increase the heap in Introscope_Enterprise_Manager.lax

(Unix)/EMService.conf(Windows). See installation guide.

-


You need to adapt the parameters -Xms and -Xmx in the Introscope_Enterprise_Manager.lax file.

Regards,

Allam Drebes

allam_drebes
Advisor
Advisor
0 Kudos

Hi again,

If you are tunning the EM in a Windows server, edit this parameters in the EMService.conf file.

Regards,

Allam

Edited by: Allam Drebes on Mar 29, 2011 2:47 PM

Former Member
0 Kudos

Hello,

Like I said, I have increased the value to 1024MB and still not starting.

The corresponding section of the EMService is pasted below:

#********************************************************************

  1. Wrapper Properties

#********************************************************************

  1. Java Application

wrapper.java.command=jre
bin
java.exe

wrapper.working.dir=.\

  1. Java Main class

wrapper.java.mainclass=org.tanukisoftware.wrapper.WrapperSimpleApp

  1. Java Classpath (include wrapper.jar) Add class path elements as

  2. needed starting from 1

wrapper.native_library=ServiceWrapper32

wrapper.java.classpath.1=./lib/ServiceWrapper32.jar

wrapper.java.classpath.2=./launcher.jar

#wrapper.java.classpath.3=

  1. Java Library Path (location of Wrapper.DLL or libwrapper.so)

wrapper.java.library.path.1=./lib

  1. Java Additional Parameters

  2. Note: On 64-bit Windows only, the first additional parameter must be: -Xrs

#wrapper.java.additional.1=

wrapper.java.additional.1=-Xrs

wrapper.java.additional.2=-Djava.awt.headless=false

  1. Initial Java Heap Size (in MB)

wrapper.java.initmemory=512

  1. Maximum Java Heap Size (in MB)

wrapper.java.maxmemory=1024

  1. Application parameters. Add parameters as needed starting from 1

wrapper.app.parameter.1=org.eclipse.core.launcher.Main

wrapper.app.parameter.2=-consolelog

wrapper.app.parameter.3=-noExit

wrapper.app.parameter.4=-product

wrapper.app.parameter.5=com.wily.introscope.em.product

wrapper.app.parameter.6=-install

wrapper.app.parameter.7=./product/enterprisemanager

wrapper.app.parameter.8=-configuration

wrapper.app.parameter.9=./product/enterprisemanager/configuration

  1. Number of seconds to allow between the time that the Wrapper launches

  2. the JVM process and the time that the JVM side of the Wrapper responds

  3. that the application has started. 0 means never time out. Defaults to 30 seconds.

wrapper.startup.timeout=300

Please help

allam_drebes
Advisor
Advisor
0 Kudos

Try to increase this paramaterer to 1024MB as well.

  1. Initial Java Heap Size (in MB)

wrapper.java.initmemory=512

Regards,

Allam

Former Member
0 Kudos

Hello,

Thank you for following up on my issue.

I have done that. However, the error in the log has changed to this:

"3/30/11 12:52:59 PM PDT [ERROR] [Manager.EMWebServer] The EM Webstart service could not be started :Unrecognized Windows Sockets error: 0: JVM_Bind"

Any ideas?

Thank you

allam_drebes
Advisor
Advisor
0 Kudos

Hi

Check if there is any program using the ports 8081 and 6001, the default port used by the EM.

The netstat -ano shows the proccess ID.

You can check which program is using it by the proccess ID, you can check it in the task manager.

Make sure that these ports are free.

Regards,

Former Member
0 Kudos

Hello Allam,

I checked with netstat -ano...and i have this excerpt.

TCP [::]:6001 [::]:0 LISTENING 2908

TCP [::]:8081 [::]:0 LISTENING 2908

I drilled down and saw that Java.exe is using it as shown below:

C:\Users\Administrator>tasklist|findstr 2908

java.exe 2908 Services 0 910,664 K

What should I do?

Thank you

Former Member
0 Kudos

Hello Allam,

I think the issue is related to the default port used by the EM.

This is what i did to make the EM start.

I killed the service using the command:

C:\Users\Administrator>taskkill /F /PID 2908

SUCCESS: The process with PID 2908 has been terminated.

and I relaunched the EM. Afterwards, I got the successfully message:

3/30/11 02:17:23 PM PDT [INFO] [Manager] Introscope Enterprise Manager started.

Thank you

allam_drebes
Advisor
Advisor
0 Kudos

Hi John,

I am glad to hear that you could solve the problem sucessfully.

Regards,

Allam

Former Member
0 Kudos

Hey Allam....you got yourself 10 Points already...lol!

Thanks again.

acclimation_argel
Participant
0 Kudos

Hi,

I tried doing this solution you posted but my Enterprise Manager still failed to start. The log shows the same error. What should I do?

The error is the unrecognized windows sockets error 0 jvm_bind.

Thanks!

Edited by: Argel Joseph Casupanan on Jun 25, 2011 5:44 PM

Answers (0)