topic Failed to initialize JVM in SAS EG when running Proc Groovy in Administration and Deployment

Failed to initialize JVM in SAS EG when running Proc Groovy

keerthi78890976 — Wed, 19 Jun 2019 13:55:38 GMT

Hi All,

I am facing the below mentioned issue when running the code from SAS EG & Foundation. Could you please help. Java is installed on the linux machines & RDP.

proc groovy classpath="/sas/sashome/SASVersionedJarRepository/eclipse/plugins/groovy_2.4.6_2.4.6.0_SAS_20180801105132/groovy-all.jar";

ERROR: Failed to start the JVM.
ERROR: Failed to initialize the JVM.

Re: Failed to initialize JVM in SAS EG when running Proc Groovy

alexal — Wed, 19 Jun 2019 14:02:34 GMT

@keerthi78890976 ,

Please run the code from the "Full Code" tab on the SAS Note at http://support.sas.com/kb/42/575.html and reply with the entire SAS log attached.

Re: Failed to initialize JVM in SAS EG when running Proc Groovy

keerthi78890976 — Tue, 25 Jun 2019 09:25:29 GMT

1 ;*';*";*/;quit;run;
2 OPTIONS PAGENO=MIN;
3 %LET _CLIENTTASKLABEL='Program (3)';
4 %LET _CLIENTPROCESSFLOWNAME='Process Flow';
5 %LET _CLIENTPROJECTPATH='';
6 %LET _CLIENTPROJECTPATHHOST='';
7 %LET _CLIENTPROJECTNAME='';
8 %LET _SASPROGRAMFILE='';
9 %LET _SASPROGRAMFILEHOST='';
10
11 ODS _ALL_ CLOSE;
12 OPTIONS DEV=PNG;
13 GOPTIONS XPIXELS=0 YPIXELS=0;
14 FILENAME EGSR TEMP;
15 ODS tagsets.sasreport13(ID=EGSR) FILE=EGSR
16 STYLE=HtmlBlue
17 STYLESHEET=(URL="file:///C:/Program%20Files/SASHome/SASEnterpriseGuide/7.1/Styles/HtmlBlue.css")
18 NOGTITLE
19 NOGFOOTNOTE
20 GPATH=&sasworklocation
21 ENCODING=UTF8
22 options(rolap="on")
23 ;
NOTE: Writing TAGSETS.SASREPORT13(EGSR) Body file: EGSR
24
25 GOPTIONS ACCESSIBLE;
26 /*** BEGIN ***/
27 %macro getpaths ;
28 options set=TKJNI_OPT_TRACE="y" ;
29 %put TS Site: &SYSSITE ;
30 %put OS: &SYSSCP &SYSSCPL ;
31 %put SAS Mode: &SYSPROCESSNAME ;
32 %put Host: &SYSTCPIPHOSTNAME ;
33 %put SAS Version: &sysvlong ;
34 %put User: &SYSUSERID ;
35 %put SASROOT: %sysget(SASROOT) ;
36 %put JAVA_HOME is: %sysget(JAVA_HOME) ;
37 %put CLASSPATH is: %sysget(CLASSPATH) ;
38 %put PATH is: %sysget(PATH) ;
39 %put DISPLAY is set as: %sysget(DISPLAY);
40
41 %if %index(&sysscp, SUN) or %index(&sysscp,LIN) %then %do ;
42 %put LD_LIBRARY_PATH is: %sysget(LD_LIBRARY_PATH) ;
43 %put LD_LIBRARY_PATH_64 is: %sysget(LD_LIBRARY_PATH_64) ;
44 %end ;
45
46 %else %if %index(&sysscp, AIX) %then %do ;
47 %put LIBPATH is: %sysget(LIBPATH) ;
48 %put IBM_JAVA_OPTIONS: %sysget(IBM_JAVA_OPTIONS) ;
49 %end ;
50
51 %else %if %index(&sysscp, HP) %then %do ;
52 %put SHLIB_PATH is: %sysget(SHLIB_PATH) ;
53 %end ;
54 %else %do;
55 %put SAS is not on a recognized Unix platform ;
56 %end ;
57
2 The SAS System 08:26 Wednesday, June 19, 2019

58 proc javainfo ;
59 run ;
60
61 proc options option=jreoptions ;
62 run ;
63
64 %mend ;
65
66 %getpaths ;
TS Site: 70095169
OS: LIN X64 Linux
SAS Mode: Object Server
Host: compute1p.magicaws.com
SAS Version: 9.04.01M6P110718
User: MAGIC\keerthi.palapolu
SASROOT: /sas/sashome/SASFoundation/9.4
JAVA_HOME is: /sas/sashome/SASPrivateJavaRuntimeEnvironment/9.4/jre
WARNING: The argument to macro function %SYSGET is not defined as a system variable.
CLASSPATH is:
PATH is: /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/opt/mssql-tools/bin:/root/bin
DISPLAY is set as: localhost:10.0
LD_LIBRARY_PATH is:
/usr/lib64/:/sas/sashome/SASODBCDriversfortheWebInfrastructurePlatformDataServer/9.4/Driver/:/opt/microsoft/msodbcsql17/lib64/:/sas/
sqlanywhere17/install/lib64:/sas/sashome/SASFoundation/9.4/sasexe/
WARNING: The argument to macro function %SYSGET is not defined as a system variable.
LD_LIBRARY_PATH_64 is:
NOTE: PROCEDURE JAVAINFO used (Total process time):
real time 1.00 seconds
cpu time 0.00 seconds

ERROR: Proc javainfo did not run correctly.

SAS (r) Proprietary Software Release 9.4 TS1M6

JREOPTIONS=( -DPFS_TEMPLATE=/sas/sashome/SASFoundation/9.4/misc/tkjava/qrpfstpt.xml
-Djava.class.path=/sas/sashome/SASVersionedJarRepository/eclipse/plugins/sas.launcher.jar
-Djava.security.auth.login.config=/sas/sashome/SASFoundation/9.4/misc/tkjava/sas.login.config
-Djava.security.policy=/sas/sashome/SASFoundation/9.4/misc/tkjava/sas.policy
-Djava.system.class.loader=com.sas.app.AppClassLoader
-Dlog4j.configuration=file:/sas/sashome/SASFoundation/9.4/misc/tkjava/sas.log4j.properties
-Dsas.app.class.path=/sas/sashome/SASVersionedJarRepository/eclipse/plugins/tkjava.jar
-Dsas.ext.config=/sas/sashome/SASFoundation/9.4/misc/tkjava/sas.java.ext.config
-Dtkj.app.launch.config=/sas/sashome/SASVersionedJarRepository/picklist )
Specifies the Java Runtime Environment options for SAS.
NOTE: PROCEDURE OPTIONS used (Total process time):
real time 0.00 seconds
cpu time 0.00 seconds

67 /**** END ****/
68
69 GOPTIONS NOACCESSIBLE;
70 %LET _CLIENTTASKLABEL=;
71 %LET _CLIENTPROCESSFLOWNAME=;
72 %LET _CLIENTPROJECTPATH=;
73 %LET _CLIENTPROJECTPATHHOST=;
74 %LET _CLIENTPROJECTNAME=;
75 %LET _SASPROGRAMFILE=;
3 The SAS System 08:26 Wednesday, June 19, 2019

76 %LET _SASPROGRAMFILEHOST=;
77
78 ;*';*";*/;quit;run;
79 ODS _ALL_ CLOSE;
80
81
82 QUIT; RUN;
83

Re: Failed to initialize JVM in SAS EG when running Proc Groovy

nhvdwalt — Tue, 25 Jun 2019 09:35:44 GMT

Hi @keerthi78890976

I had this years ago at a customer site, so I don't have the details anymore. The problem was an update that was done to Red Hat that caused the issue.

Was this working before ? Was there any updates to Linux (assuming) ?

Re: Failed to initialize JVM in SAS EG when running Proc Groovy

SimonDawson — Tue, 25 Jun 2019 10:11:01 GMT

The wall clock of 1 second on the proc run time smells like a timeout. This would be a fun track for some one.

Re: Failed to initialize JVM in SAS EG when running Proc Groovy

alexal — Tue, 25 Jun 2019 10:52:53 GMT

@keerthi78890976 ,

Thanks for your response. Have you recently changed LD_LIBRARY_PATH? Show me /sas/sashome/SASFoundation/9.4/bin/sasenv_local from that server.

Re: Failed to initialize JVM in SAS EG when running Proc Groovy

keerthi78890976 — Fri, 28 Jun 2019 16:30:45 GMT

Added export LD_LIBRARY_PATH=/usr/lib64/:/sas/sashome/SASPrivateJavaRuntimeEnvironment/9.4/jre/lib/amd64/server/

Re: Failed to initialize JVM in SAS EG when running Proc Groovy

warnerjonn — Mon, 08 Feb 2021 06:11:42 GMT

There is not enough virtual memory space requested by an application thus the application fails to start. This usually happens during the application startup phase. Applications reserve a large amount of virtual memory for the JVM heap space during the startup phase. Java on Windows uses an initial size of 16 Megabyte and a maximum of 64 Megabyte.

Most of the time you can fix this problem by uninstalling the Java runtime and then reinstalling it all over again. You can also try increasing the amount of system memory allocated to the Java virtual machine by setting an environment variable.