Problem Note 30720: "JVM exited unexpectedly while stopping the application" errors in the SAS Analytics Platform Server log
If the SAS
® Analytics Platform Server is performing slowly, or if SAS
® Enterprise Miner 5.x projects appear to hang while diagrams are being run, check the SAS Analytics Platform Server log for this error:
"JVM exited unexpectedly while stopping the application"
To find the SAS Analytics Platform Server log:
WINDOWS:
If the SAS Analytics Platform Server is installed as a service, go to
!SASROOT\SASAPCore\logs and look for "wrapper.log".
If the SAS Analytics Platform Server was started from Start > Programs > SAS > SAS Analytics Platform > Start AP Server, look in the "Start AP Server" window for the error message.
UNIX:
Go to !SASROOT/SASAPCore/bin and look for nohup.out (if the output has been sent to nohup). An alternate location is the !SASROOT/SASAPCore/logs directory.
Follow the steps below to address this error message:
WINDOWS:
1. Stop all SAS services by going to Start > Run > services.msc and stop all SAS services (SAS Lev1...)
2. Modify these files:
a. Go to !SASROOT\SASAPCore\apps\EnterpriseMiner\bin and edit the em.ini file. Go to the "CommandLineArgs" section and change the settings to -Xms256m -Xmx1024m.
b. Go to !SASROOT\SASAPCore\bin and edit the apstart.ini. Go to the "CommandLineArgs" section and change the settings to -Xms256m -Xmx1024m.
c. Go to !SASROOT/SASAPCore\conf and edit the wrapper.conf file. Add this line (under the Java Additional Parameters section):
wrapper.java.additional.9=-Djava.rmi.dgc.leaseValue=10000 (This number may be different than nine).
3. Open a DOS prompt by going to Start > Run > cmd. Then, change directories (cd) to !SASROOT\SASAPCore\bin.
Once in that directory, at the command line type:
AnalyticsPlatformService.bat remove (this replaces the wrapper.conf file)
Hit Enter and then type:
AnalyticsPlatformService.bat install
4. Restart the SAS Services.
UNIX:
1. Stop all running SAS Servers (Object Spawner, SAS Analytics Platform, SAS® Metadata Server).
MetadataServer:
Change directories to ../../Lev1/SASMain/MetadataServer.
./MetadataServer.sh stop
Object Spawner:
Change directories to ../../Lev1/SASMain/ObjectSpawner.
./ObjectSpawnwer.sh stop
SAS Analytics Platform Server:
Change directories to !SASROOT/SASAPCore/bin
./apserver stop
2. Modify these files:
a. Go to !SASROOT/SASAPCore/apps/EnterpriseMiner and edit Em.ini file. Change the -Xmx settings to be -Xmx1024.
b. Go to !SASROOT/SASAPCore/bin and edit the apstart.ini. Change the -Xmx settings to be -Xmx1024.
c. Go to !SASROOT/SASAPCore/conf and edit the wrapper.conf file. Add this line:
wrapper.java.additional.9=-Djava.rmi.dgc.leaseValue=10000 (This number may be different than nine).
3. Restart the SAS Servers:
MetadataServer:
Change directories to ../../Lev1/SASMain/MetadataServer.
./MetadataServer.sh start
Object Spawner:
Change directories to ../../Lev1/SASMain/ObjectSpawner.
./ObjectSpawnwer.sh start
SAS Analytics Platform Server:
Change directories to !SASROOT/SASAPCore/bin
./apserver start
Operating System and Release Information
| SAS System | SAS Enterprise Miner | Microsoft® Windows® for 64-Bit Itanium-based Systems | 5.2 | | 9.1 TS1M3 SP4 | |
| Microsoft Windows Server 2003 Datacenter 64-bit Edition | 5.2 | | 9.1 TS1M3 SP4 | |
| Microsoft Windows Server 2003 Enterprise 64-bit Edition | 5.2 | | 9.1 TS1M3 SP4 | |
| Microsoft Windows 2000 Advanced Server | 5.2 | | 9.1 TS1M3 SP4 | |
| Microsoft Windows 2000 Datacenter Server | 5.2 | | 9.1 TS1M3 SP4 | |
| Microsoft Windows 2000 Server | 5.2 | | 9.1 TS1M3 SP4 | |
| Microsoft Windows 2000 Professional | 5.2 | | 9.1 TS1M3 SP4 | |
| Microsoft Windows NT Workstation | 5.2 | | 9.1 TS1M3 SP4 | |
| Microsoft Windows Server 2003 Datacenter Edition | 5.2 | | 9.1 TS1M3 SP4 | |
| Microsoft Windows Server 2003 Enterprise Edition | 5.2 | | 9.1 TS1M3 SP4 | |
| Microsoft Windows Server 2003 Standard Edition | 5.2 | | 9.1 TS1M3 SP4 | |
| Microsoft Windows XP Professional | 5.2 | | 9.1 TS1M3 SP4 | |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
| Type: | Problem Note |
| Priority: | medium |
| Date Modified: | 2008-01-16 14:24:41 |
| Date Created: | 2007-12-07 16:59:58 |
