Introscope Workstation does not start
Article ID: 8887
Updated On:
Products
Issue/Introduction
When starting Workstation from a Windows machine, the login screen is not displayed and there are no events occurring.
The "logfile" was added to log4j.logger.Workstation in IntroscopeWorkstation.properties. However, there is no output in the log file.
Environment
Cause
If sufficient Java heap space can not be reserved, it may be interrupted before Workstation starts up.
In that case, log is not output because Workstation is not running.
If the maximum heap size value of "lax.nl.java.option.additional" of "Introscope_Workstation.lax" can not be reserved at the time of starting, it will end.
Example: lax.nl.java.option.additional=-client -Xms1638m -Xmx1638m -Dsun.java2d.noddraw=true
Resolution
Tune the maximum heap size (-Xmx m) of "lax.nl.java.option.additional" in "Introscope_Workstation.lax".
Example: lax.nl.java.option.additional=-client -Xms1331m -Xmx1331m -Dsun.java2d.noddraw=true
Since it is not possible to get errors in the log, check the reservation error of the Java heap area from the command prompt.
The method of confirmation is either of the methods below.
1. Start Workstation and check it.
2. Add "-Xmx1640m" directly to the Java command and confirm it.
1. Start Workstation and check it.
This starts Workstation from the command prompt.
procedure:
a) Ctrl + double click "Introscope_Workstation.exe under <Workstation_HOME> in Explorer.
b) Check the command prompt message.
normal:
When starting normally after the startup message, and the login screen is launched.
error:
If it can not be started, the following message is output, it can be confirmed that continuous Java heap area can not be reserved and Workstation did not start up.
"Error occurred during initialization of VM Could not reserve enough space for 1572864KB object heap [press enter to close this window]"
Example:
------------------------------------------------------------------
cwd: C:\CA APM\IntroscopeWorkstation10.5.1.8
cmd: "C:\CA APM\IntroscopeWorkstation10.5.1.8\jre\bin\java.exe" -client -Xms1536 m -Xmx1536m -Dsun.java2d.noddraw=true -classpath "C:\CA APM\IntroscopeWorkstatio n10.5.1.8\launcher.jar;C:\CA APM\IntroscopeWorkstation10.5.1.8;C:\CA APM\Introsc opeWorkstation10.5.1.8\lax.jar;" com.zerog.lax.LAX "C:/CA APM/IntroscopeWorkstat ion10.5.1.8/Introscope_Workstation.lax" "C:/Users/user/AppData/Local/Temp/lax6E62.tmp"
Error occurred during initialization of VM Could not reserve enough space for 1572864KB object heap [press enter to close this window]
------------------------------------------------------------------
2. Add "-Xmx1640m" directly to the Java command and confirm it.
Execute the maximum heap size (-Xmx) value of "lax.nl.java.option.additional" directly with the Java command.
procedure:
a) Launch a command prompt.
Windows+r -->cmd.exe
b) Change to <WS_HOME>\jre\bin by change directory.
C:\> cd <WS_HOME>\jre\bin
c) Execute "java -Xmx1640m -version" with Java command.
C:\<WS_HOME>\jre\bin> java -Xmx1640m -version
d) Check the command prompt message.
Can not be reserved Java heap area.
------------------------------------------------------------------
C:\CA APM\IntroscopeWorkstation10.5.1.8\jre\bin>java -Xmx1638m -version Error occurred during initialization of VM Could not reserve enough space for 1677312KB object heap
------------------------------------------------------------------
Can be reserved Java heap area.
------------------------------------------------------------------
C:\CA APM\IntroscopeWorkstation10.5.1.8\jre\bin>java -Xmx1331m -version java version "1.8.0_112"
Java(TM) SE Runtime Environment (build 1.8.0_112-b15) Java HotSpot(TM) Client VM (build 25.112-b15, mixed mode)
------------------------------------------------------------------
Additional Information
Reference description:
Frequently Asked Questions About the Java HotSpot VM
Why can't I get a larger heap with the 32-bit JVM?
The maximum theoretical heap limit for the 32-bit JVM is 4G. Due to various additional constraints such as available swap, kernel address space usage, memory fragmentation, and VM overhead, in practice the limit can be much lower. On most modern 32-bit Windows systems the maximum heap size will range from 1.4G to 1.6G. On 32-bit Solaris kernels the address space is limited to 2G.
Feedback
