BookmarkSubscribeRSS Feed
🔒 This topic is solved and locked. Need further help from the community? Please sign in and ask a new question.
jaredlam
Fluorite | Level 6

I'm installing SAS 9.4 on Linux (Centos 7).

 

I'm getting "Java proxy is not responding" error when bringing up sas.

 

running "proc javainfo; run;" gets:

 

ERROR: The Java proxy is not responding.
ERROR: Proc javainfo did not run correctly.
NOTE: PROCEDURE JAVAINFO used (Total process time):
      real time           1.00 seconds
      cpu time            0.00 seconds


  2?
ERROR: The Java child process terminated unexpectedly: status 262.
ERROR: WIFSIGNALED 1 WIFEXITED 0 WEXITSTATUS 1 WTERMSIG 6.

 

 

Any ideas?

 

Thanks,

Jared

1 ACCEPTED SOLUTION

Accepted Solutions
alexal
SAS Employee

@Resa,

 

The problem is with Linux kernel and the fix will be provided by Red Hat.

View solution in original post

18 REPLIES 18
alexal
SAS Employee

@jaredlam,

 

Please run the following SAS program and show me an output:

 

options set=TKJNI_OPT_TRACE="y" ;
%put LD_LIBRARY_PATH is: %sysget(LD_LIBRARY_PATH) ;
proc javainfo ; run ;
proc options option=jreoptions ; run ;
SuperTommy
Calcite | Level 5

@alexal

 

I am having the same issue on RHEL 7.3. I have contacted SAS support and submitted my details. Here is my output from the requested SAS code.

 

1                                                          The SAS System                               15:48 Tuesday, June 27, 2017

NOTE: Copyright (c) 2002-2012 by SAS Institute Inc., Cary, NC, USA. 
NOTE: SAS (r) Proprietary Software 9.4 (TS1M4) 
NOTE: This session is executing on the Linux 3.10.0-514.21.2.el7.x86_64 (LIN X64) platform.



NOTE: Updated analytical products:
      
      SAS/STAT 14.2

NOTE: Additional host information:

 Linux LIN X64 3.10.0-514.21.2.el7.x86_64 #1 SMP Sun May 28 17:08:21 EDT 2017 x86_64 Red Hat Enterprise Linux Server release 7.3 
      (Maipo) 

You are running SAS 9. Some SAS 8 files will be automatically converted 
by the V9 engine; others are incompatible.  Please see 
http://support.sas.com/rnd/migration/planning/platform/64bit.html

PROC MIGRATE will preserve current SAS file attributes and is 
recommended for converting all your SAS libraries from any 
SAS 8 release to SAS 9.  For details and examples, please see
http://support.sas.com/rnd/migration/index.html


This message is contained in the SAS news file, and is presented upon
initialization.  Edit the file "news" in the "misc/base" directory to
display site-specific news and information in the program log.
The command line option "-nonews" will prevent this display.




NOTE: SAS initialization used:
      real time           0.01 seconds
      cpu time            0.02 seconds
      
NOTE: A byte-order mark in the file "/home/tommy/autoexec.sas" (for fileref "#LN00006") indicates that the data is 
      encoded in "utf-8".  This encoding will be used to process the file.

NOTE: AUTOEXEC processing beginning; file is /home/tommy/autoexec.sas.

NOTE: Libref CMS was successfully assigned as follows: 
      Engine:        V9 
      Physical Name: /analysis/data/cms/preclean_lds_2016_v3/sas_data
NOTE: Libref MYLIB was successfully assigned as follows: 
      Engine:        ODBC 
      Physical Name: 

NOTE: AUTOEXEC processing completed.

1          options set=TKJNI_OPT_TRACE="y" ;
2          %put LD_LIBRARY_PATH is: %sysget(LD_LIBRARY_PATH) ;
LD_LIBRARY_PATH is: 
/usr/lib64//lib:/opt/microsoft/msodbcsql/lib64:/opt/sas9.4/SASHome/Secure/sasexe:/opt/sas9.4/SASHome/SASODBCDriversfortheWebInfrastr
ucturePlatformDataServer/9.4/Driver:/opt/sas9.4/SASHome/SASPrivateJavaRuntimeEnvironment/9.4/jre/lib/amd64/server:/opt/sas9.4/SASHom
e/SASPrivateJavaRuntimeEnvironment/9.4/jre/lib/amd64:/opt/sas9.4/SASHome/SASFoundation/9.4/sasexe
2                                                          The SAS System                               15:48 Tuesday, June 27, 2017

NOTE: PROCEDURE JAVAINFO used (Total process time):
      real time           1.00 seconds
      cpu time            0.00 seconds
      
jecreatjvm skCreateJavaVM: bufL 116 strSize 1 proxyData->dftBufSz 2124
jecreatjvm skCreateJavaVM: extHandle 7f452404d520 argc 16 argv 7f4533490dc0 bufT 7f450303ecb0 trace 1 timeout 60 dftBufSz 2124
jecreatjvm initProxy: extHandle 7f452404d520
TKPOSjniipc createIPC_ ipc channel p 0x7f4533490fa0 (sem 0x13001b memory 0x1f80001 m 0x7f453362a000) bufsz 2124
jecreatjvm initProxy: m->bufsz 2124
jecreatjvm skCreateJavaVM: proxyData m->bufsz 2124
jecreatjvm skCreateJavaVM: m 7f453362a000 m->flags 81
client:  send slot 0x7f4533490fa0 routine 200 len 956
client:  send signals 0x13001b state 0
client:  send now find 0x13001b state 1
client:  receiveTO ipcID 0x7f4533490fa0 state 0
client:...rtn 200 rc (jlong)0x0, len 956
ERROR: The Java proxy is not responding.
jejvm stopProxy p 7f4533490e60
jeipc jipcTerm: extHandle 7f452404d520
jeipc jipcTerm: exiting
ERROR: Proc javainfo did not run correctly.
         jpmain main: serverIPC 0x7ffd3dc53630 ipcID 0x7fc9a17b9d80
         jpmain main: LIBPATH = NULL
         jpmain main: _CEE_RUNOPTS = NULL
         jpmain main: DISPLAY = localhost:17.0
         jpmain main: TKJNI_OPT_JVMOPTS = NULL
         jpmain main: TKJNI_OPT_STDOUT = NULL
         jpmain main: TKJNI_OPT_STDERR = NULL
         jpmain main: argc = 5
         jpmain main: argv[0] = /opt/sas9.4/SASHome/SASFoundation/9.4/utilities/bin/jproxy
         jpmain main: argv[1] = 1245211
         jpmain main: argv[2] = 33030145
         jpmain main: argv[3] = 1245211
         jpmain main: argv[4] = 33030145
         jpmain main: m 0x7fc9a0fae000 m->flags 0x85
         jpmain main: message loop calling jpreceive
         jpipc jpreceive: entering with semId 0x13001b comm_t@ 0x7fc9a17b9d80 msg@ 0x7fc9a0fae000
         jpipc jpreceive: semId 0x13001b rtn 200 state before: 1
         jpipc jpreceive: semId 0x13001b errno 0 rc 0 state after: 0
         jpmain main: calling createJVM()
         jpcreatjvm createArgs: vm_args 0x7ffd3dc53550 argc 16 argv 0x7fc9a17ba090 envCnt 0 optCnt 16 options 0x7fc9a17ba120
         jpcreatjvm createArgs:  options[0].optionString = -Dsas.tkjni
         jpcreatjvm createArgs:  options[0].extraInfo = (nil)
         jpcreatjvm createArgs:  options[1].optionString = -Djava.awt.headless=true
         jpcreatjvm createArgs:  options[1].extraInfo = (nil)
         jpcreatjvm createArgs:  options[2].optionString = -Dfile.encoding=ISO8859_1
         jpcreatjvm createArgs:  options[2].extraInfo = (nil)
         jpcreatjvm createArgs:  options[3].optionString = 
-DPFS_TEMPLATE=/opt/sas9.4/SASHome/SASFoundation/9.4/misc/tkjava/qrpfstpt.xml
         jpcreatjvm createArgs:  options[3].extraInfo = (nil)
         jpcreatjvm createArgs:  options[4].optionString = 
-Djava.class.path=/opt/sas9.4/SASHome/SASVersionedJarRepository/eclipse/plugins/sas.launcher.jar
         jpcreatjvm createArgs:  options[4].extraInfo = (nil)
         jpcreatjvm createArgs:  options[5].optionString = 
-Djava.security.auth.login.config=/opt/sas9.4/SASHome/SASFoundation/9.4/misc/tkjava/sas.login.config
         jpcreatjvm createArgs:  options[5].extraInfo = (nil)
         jpcreatjvm createArgs:  options[6].optionString = 
-Djava.security.policy=/opt/sas9.4/SASHome/SASFoundation/9.4/misc/tkjava/sas.policy
3                                                          The SAS System                               15:48 Tuesday, June 27, 2017

         jpcreatjvm createArgs:  options[6].extraInfo = (nil)
         jpcreatjvm createArgs:  options[7].optionString = -Djava.system.class.loader=com.sas.app.AppClassLoader
         jpcreatjvm createArgs:  options[7].extraInfo = (nil)
         jpcreatjvm createArgs:  options[8].optionString = 
-Dlog4j.configuration=file:/opt/sas9.4/SASHome/SASFoundation/9.4/misc/tkjava/sas.log4j.properties
         jpcreatjvm createArgs:  options[8].extraInfo = (nil)
         jpcreatjvm createArgs:  options[9].optionString = 
-Dsas.app.class.path=/opt/sas9.4/SASHome/SASVersionedJarRepository/eclipse/plugins/tkjava.jar
         jpcreatjvm createArgs:  options[9].extraInfo = (nil)
         jpcreatjvm createArgs:  options[10].optionString = 
-Dsas.ext.config=/opt/sas9.4/SASHome/SASFoundation/9.4/misc/tkjava/sas.java.ext.config
         jpcreatjvm createArgs:  options[10].extraInfo = (nil)
         jpcreatjvm createArgs:  options[11].optionString = 
-Dtkj.app.launch.config=/opt/sas9.4/SASHome/SASVersionedJarRepository/picklist
         jpcreatjvm createArgs:  options[11].extraInfo = (nil)
         jpcreatjvm createArgs:  options[12].optionString = -Duser.country=US
         jpcreatjvm createArgs:  options[12].extraInfo = (nil)
         jpcreatjvm createArgs:  options[13].optionString = -Duser.language=en
         jpcreatjvm createArgs:  options[13].extraInfo = (nil)
         jpcreatjvm createArgs:  options[14].optionString = -Dsas.root=/opt/sas9.4/SASHome/SASFoundation/9.4
         jpcreatjvm createArgs:  options[14].extraInfo = (nil)
         jpcreatjvm createArgs:  options[15].optionString = -Dsas.home=/opt/sas9.4/SASHome
         jpcreatjvm createArgs:  options[15].extraInfo = (nil)
         jpcreatjvm createArgs:  vm_args->version 65538
         jpcreatjvm createArgs:  vm_args->nOptions 16
         jpcreatjvm createArgs:  vm_args->options 0x7fc9a17ba120
         jpcreatjvm createArgs:  vm_args->ignoreUnrecognized 1
         #
         # A fatal error has been detected by the Java Runtime Environment:
         #
         #  SIGBUS (0x7) at pc=0x00007fc999f71561, pid=184295, tid=0x00007fc9a0f95740
         #
         # JRE version:  (7.0_111-b13) (build )
         # Java VM: Java HotSpot(TM) 64-Bit Server VM (24.111-b13 mixed mode linux-amd64 compressed oops)
         # Problematic frame:
         # j  java.lang.Object.<clinit>()V+0
         #
         # Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before 
starting Java again
         #
         # An error report file with more information is saved as:
         # /home/tommy/hs_err_pid184295.log
         #
         # If you would like to submit a bug report, please visit:
         #   http://bugreport.java.com/bugreport/crash.jsp
         #
ERROR: The Java child process terminated unexpectedly: status 262.
ERROR: WIFSIGNALED 1 WIFEXITED 0 WEXITSTATUS 1 WTERMSIG 6.
         jeipc jipcSuspend: extHandle 7f452404d520
         jeipc jipcSuspend: exiting
3          proc javainfo ; run ;


4          proc options option=jreoptions ; run ;

    SAS (r) Proprietary Software Release 9.4  TS1M4

 JREOPTIONS=(           -DPFS_TEMPLATE=/opt/sas9.4/SASHome/SASFoundation/9.4/misc/tkjava/qrpfstpt.xml         
4                                                          The SAS System                               15:48 Tuesday, June 27, 2017

-Djava.class.path=/opt/sas9.4/SASHome/SASVersionedJarRepository/eclipse/plugins/sas.launcher.jar         
-Djava.security.auth.login.config=/opt/sas9.4/SASHome/SASFoundation/9.4/misc/tkjava/sas.login.config         
-Djava.security.policy=/opt/sas9.4/SASHome/SASFoundation/9.4/misc/tkjava/sas.policy         
-Djava.system.class.loader=com.sas.app.AppClassLoader         
-Dlog4j.configuration=file:/opt/sas9.4/SASHome/SASFoundation/9.4/misc/tkjava/sas.log4j.properties         
-Dsas.app.class.path=/opt/sas9.4/SASHome/SASVersionedJarRepository/eclipse/plugins/tkjava.jar         
-Dsas.ext.config=/opt/sas9.4/SASHome/SASFoundation/9.4/misc/tkjava/sas.java.ext.config         
-Dtkj.app.launch.config=/opt/sas9.4/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
      

ERROR: Errors printed on pages 2,3.

NOTE: SAS Institute Inc., SAS Campus Drive, Cary, NC USA 27513-2414
NOTE: The SAS System used:
      real time           1.26 seconds
      cpu time            0.05 seconds

 

alexal
SAS Employee

@SuperTommy,

 

Thanks for your response. We are working on this problem. I will keep you posted.

SuperTommy
Calcite | Level 5

@alexal

 

If it is of any help it appears that this problem may be related to an update applied to prevent a certain exploit...

 

This user mentions SAS specifically:

https://forums.opensuse.org/showthread.php/525571-Application-unable-to-run-java-since-Kernel-and-gl...

 

This is Red Hat's response to the issue:

https://access.redhat.com/solutions/3091371

 

Red Hat's writeup on the vulnerability:

https://access.redhat.com/security/vulnerabilities/stackguard

 

Thanks for the help.

alexal
SAS Employee

Thanks. We are already aware of these reports and working on them together with R&D. I will keep you posted.

Resa
Pyrite | Level 9

Great find @SuperTommy!

 

We are experiencing the same issue on Red Hat version (uname -a  and cat /etc/redhat-release):

Linux zew-v-0a2f0b04.LINUX.SHELL.COM 2.6.32-696.3.2.el6.x86_64 #1 SMP Wed Jun 7 11:51:39 EDT 2017 x86_64 x86_64 x86_64 GNU/Linux

Red Hat Enterprise Linux Server release 6.8 (Santiago)

The result of <SASHome>//SASPrivateJavaRuntimeEnvironment/9.4/bin/java -fullversion is:

java full version "1.7.0_141-mockbuild_2017_05_02_23_51-b00"

Look forward to hearing about the fix @alexal

alexal
SAS Employee

@Resa,

 

The problem is with Linux kernel and the fix will be provided by Red Hat.

Resa
Pyrite | Level 9

@alexal, ok. Thanks for clarifying.

Was my bad, I misread/misunderstood your post "Thanks. We are already aware of these reports and working on them together with R&D. I will keep you posted." and missed the post in which you already indicated this to @jaredlam

Smiley Embarassed

alexal
SAS Employee

@Resa,

 

Not a problem.

jaredlam
Fluorite | Level 6
@SuperTommy and @alexal : Confirmed: Java Proxy seems to work by rolling back to a previous kernel version.
alexal
SAS Employee

@jaredlam,

 

Thanks for the confirmation. Anyway, we have to wait for the final solution from Red Hat.

 

bheinsius
Lapis Lazuli | Level 10

From https://access.redhat.com/solutions/3091371:

 

Resolution

The current workaround is to increase the Thread stack size of the JVM using -Xss2m. This will require you to restart the JVM.

Research is being performed on a permanent solution.

 

 

 

 

byronk
Fluorite | Level 6

Just replying here to add CENTOS 6.9 into the thread.   

We began having the same issues with the June 21st update.

 

Thanks!

 

jaredlam
Fluorite | Level 6

Here is my output:

 

[sas@sas01 ~]$ sas -nodms
NOTE: Copyright (c) 2002-2012 by SAS Institute Inc., Cary, NC, USA.
NOTE: SAS (r) Proprietary Software 9.4 (TS1M2)
      Licensed to x, Site x.
NOTE: This session is executing on the Linux 3.10.0-514.21.2.el7.x86_64 (LIN
      X64) platform.

 

NOTE: Updated analytical products:

      SAS/STAT 13.2

NOTE: Additional host information:

 Linux LIN X64 3.10.0-514.21.2.el7.x86_64 #1 SMP Tue Jun 20 12:24:47 UTC 2017
      x86_64 CentOS Linux release 7.3.1611 (Core)

You are running SAS 9. Some SAS 8 files will be automatically converted
by the V9 engine; others are incompatible.  Please see
http://support.sas.com/rnd/migration/planning/platform/64bit.html

PROC MIGRATE will preserve current SAS file attributes and is
recommended for converting all your SAS libraries from any
SAS 8 release to SAS 9.  For details and examples, please see
http://support.sas.com/rnd/migration/index.html


This message is contained in the SAS news file, and is presented upon
initialization.  Edit the file "news" in the "misc/base" directory to
display site-specific news and information in the program log.
The command line option "-nonews" will prevent this display.

 


NOTE: SAS initialization used:
      real time           0.06 seconds
      cpu time            0.01 seconds

  1? optioins^C
Select:
  1. Cancel Submitted Statements
  C. Cancel the dialog
  T. Terminate the SAS System
?T

Press
  Y to terminate this SAS session,
  N to continue.
?y

NOTE: SAS Institute Inc., SAS Campus Drive, Cary, NC USA 27513-2414
NOTE: The SAS System used:
      real time           13.20 seconds
      cpu time            0.01 seconds


[sas@sas01 ~]$ pwd
/home/sas
[sas@sas01 ~]$ ls
core.20581  hs_err_pid20581.log  sasuser.v94
[sas@sas01 ~]$ sas -nodms
NOTE: Copyright (c) 2002-2012 by SAS Institute Inc., Cary, NC, USA.
NOTE: SAS (r) Proprietary Software 9.4 (TS1M2)
      Licensed to x, Site x.
NOTE: This session is executing on the Linux 3.10.0-514.21.2.el7.x86_64 (LIN
      X64) platform.

 

NOTE: Updated analytical products:

      SAS/STAT 13.2

NOTE: Additional host information:

 Linux LIN X64 3.10.0-514.21.2.el7.x86_64 #1 SMP Tue Jun 20 12:24:47 UTC 2017
      x86_64 CentOS Linux release 7.3.1611 (Core)

You are running SAS 9. Some SAS 8 files will be automatically converted
by the V9 engine; others are incompatible.  Please see
http://support.sas.com/rnd/migration/planning/platform/64bit.html

PROC MIGRATE will preserve current SAS file attributes and is
recommended for converting all your SAS libraries from any
SAS 8 release to SAS 9.  For details and examples, please see
http://support.sas.com/rnd/migration/index.html


This message is contained in the SAS news file, and is presented upon
initialization.  Edit the file "news" in the "misc/base" directory to
display site-specific news and information in the program log.
The command line option "-nonews" will prevent this display.

 


NOTE: SAS initialization used:
      real time           0.07 seconds
      cpu time            0.02 seconds

  1? options set=TKJNI_OPT_TRACE="y";
  2? %put LD_LIBRARY_PATH is: %sysget(LD_LIBRARY_PATH);

LD_LIBRARY_PATH is:
      /opt/sas/Secure/sasexe:/opt/sas/SASODBCDriversfortheWebInfrastructurePla
      tformDataServer/9.4/Driver:/opt/sas/SASPrivateJavaRuntimeEnvironment/9.4
      /jre/lib/amd64/server:/opt/sas/SASPrivateJavaRuntimeEnvironment/9.4/jre/
      lib/amd64:/opt/sas/SASFoundation/9.4/sasexe::/opt/simba/googlebigqueryod
      bc/lib

  3? proc javainfo; run;

jecreatjvm skCreateJavaVM: bufL 116 strSize 1 proxyData->dftBufSz 2124
jecreatjvm skCreateJavaVM: extHandle 7fca9e4eae00 argc 17 argv 7fca9e508f80
bufT 7fca7e117cc0 trace 1 timeout 60 dftBufSz 2124
jecreatjvm initProxy: extHandle 7fca9e4eae00
TKPOSjniipc createIPC_ ipc channel p 0x7fca9e509150 (sem 0x28000 memory
0x28000 m 0x7fca9e624000) bufsz 2124
jecreatjvm initProxy: m->bufsz 2124
jecreatjvm skCreateJavaVM: proxyData m->bufsz 2124
jecreatjvm skCreateJavaVM: m 7fca9e624000 m->flags 81
client:  send slot 0x7fca9e509150 routine 200 len 893
client:  send signals 0x28000 state 0
client:  send now find 0x28000 state 1
client:  receiveTO ipcID 0x7fca9e509150 state 0
client:...rtn 200 rc (jlong)0x0, len 893
ERROR: The Java proxy is not responding.
jejvm stopProxy p 7fca9e509030
jeipc jipcTerm: extHandle 7fca9e4eae00
jeipc jipcTerm: exiting
ERROR: Proc javainfo did not run correctly.
NOTE: PROCEDURE JAVAINFO used (Total process time):
      real time           1.01 seconds
      cpu time            0.01 seconds


  4?
         jpmain main: serverIPC 0x7ffdc12156b0 ipcID 0xd01c40
         jpmain main: LIBPATH = NULL
         jpmain main: _CEE_RUNOPTS = NULL
         jpmain main: DISPLAY = NULL
         jpmain main: TKJNI_OPT_JVMOPTS = NULL
         jpmain main: TKJNI_OPT_STDOUT = NULL
         jpmain main: TKJNI_OPT_STDERR = NULL
         jpmain main: argc = 5
         jpmain main: argv[0] =
/opt/sas/SASFoundation/9.4/utilities/bin/jproxy
         jpmain main: argv[1] = 163840
         jpmain main: argv[2] = 163840
         jpmain main: argv[3] = 163840
         jpmain main: argv[4] = 163840
         jpmain main: m 0x7fc4378ea000 m->flags 0x85
         jpmain main: message loop calling jpreceive
         jpipc jpreceive: entering with semId 0x28000 comm_t@ 0xd01c40 msg@
0x7fc4378ea000
         jpipc jpreceive: semId 0x28000 rtn 200 state before: 1
         jpipc jpreceive: semId 0x28000 errno 0 rc 0 state after: 0
         jpmain main: calling createJVM()
         jpcreatjvm createArgs: vm_args 0x7ffdc12155d0 argc 17 argv 0xd01f50
envCnt 0 optCnt 17 options 0xd01fe0
         jpcreatjvm createArgs:  options[0].optionString = -Dsas.tkjni
         jpcreatjvm createArgs:  options[0].extraInfo = (nil)
         jpcreatjvm createArgs:  options[1].optionString =
-Djava.awt.headless=false
         jpcreatjvm createArgs:  options[1].extraInfo = (nil)
         jpcreatjvm createArgs:  options[2].optionString =
-Dfile.encoding=ISO8859_1
         jpcreatjvm createArgs:  options[2].extraInfo = (nil)
         jpcreatjvm createArgs:  options[3].optionString =
-DPFS_TEMPLATE=/opt/sas/SASFoundation/9.4/misc/tkjava/qrpfstpt.xml
         jpcreatjvm createArgs:  options[3].extraInfo = (nil)
         jpcreatjvm createArgs:  options[4].optionString =
-Djava.class.path=/opt/sas/SASVersionedJarRepository/eclipse/plugins/sas.launc
her.jar
         jpcreatjvm createArgs:  options[4].extraInfo = (nil)
         jpcreatjvm createArgs:  options[5].optionString =
-Djava.security.auth.login.config=/opt/sas/SASFoundation/9.4/misc/tkjava/sas.l
ogin.config
         jpcreatjvm createArgs:  options[5].extraInfo = (nil)
         jpcreatjvm createArgs:  options[6].optionString =
-Djava.security.policy=/opt/sas/SASFoundation/9.4/misc/tkjava/sas.policy
         jpcreatjvm createArgs:  options[6].extraInfo = (nil)
         jpcreatjvm createArgs:  options[7].optionString =
-Djava.system.class.loader=com.sas.app.AppClassLoader
         jpcreatjvm createArgs:  options[7].extraInfo = (nil)
         jpcreatjvm createArgs:  options[8].optionString =
-Djdk.lang.Process.allowAmbigousCommands=true
         jpcreatjvm createArgs:  options[8].extraInfo = (nil)
         jpcreatjvm createArgs:  options[9].optionString =
-Dlog4j.configuration=file:/opt/sas/SASFoundation/9.4/misc/tkjava/sas.log4j.pr
operties
         jpcreatjvm createArgs:  options[9].extraInfo = (nil)
         jpcreatjvm createArgs:  options[10].optionString =
-Dsas.app.class.path=/opt/sas/SASVersionedJarRepository/eclipse/plugins/tkjava
.jar
         jpcreatjvm createArgs:  options[10].extraInfo = (nil)
         jpcreatjvm createArgs:  options[11].optionString =
-Dsas.ext.config=/opt/sas/SASFoundation/9.4/misc/tkjava/sas.java.ext.config
         jpcreatjvm createArgs:  options[11].extraInfo = (nil)
         jpcreatjvm createArgs:  options[12].optionString =
-Dtkj.app.launch.config=/opt/sas/SASVersionedJarRepository/picklist
         jpcreatjvm createArgs:  options[12].extraInfo = (nil)
         jpcreatjvm createArgs:  options[13].optionString = -Duser.country=US
         jpcreatjvm createArgs:  options[13].extraInfo = (nil)
         jpcreatjvm createArgs:  options[14].optionString = -Duser.language=en
         jpcreatjvm createArgs:  options[14].extraInfo = (nil)
         jpcreatjvm createArgs:  options[15].optionString =
-Dsas.root=/opt/sas/SASFoundation/9.4
         jpcreatjvm createArgs:  options[15].extraInfo = (nil)
         jpcreatjvm createArgs:  options[16].optionString =
-Dsas.home=/opt/sas
         jpcreatjvm createArgs:  options[16].extraInfo = (nil)
         jpcreatjvm createArgs:  vm_args->version 65538
         jpcreatjvm createArgs:  vm_args->nOptions 17
         jpcreatjvm createArgs:  vm_args->options 0xd01fe0
         jpcreatjvm createArgs:  vm_args->ignoreUnrecognized 1
         #
         # A fatal error has been detected by the Java Runtime Environment:
         #
         #  SIGBUS (0x7) at pc=0x00007fc4314d33a1, pid=7997,
tid=140480722364224
         #
         # JRE version:  (7.0_51-b13) (build )
         # Java VM: Java HotSpot(TM) 64-Bit Server VM (24.51-b03 mixed mode
linux-amd64 compressed oops)
         # Problematic frame:
         # j  java.lang.Object.<clinit>()V+0
         #
         # Failed to write core dump. Core dumps have been disabled. To
enable core dumping, try "ulimit -c unlimited" before starting Java again
         #
         # An error report file with more information is saved as:
         # /home/sas/hs_err_pid7997.log
         #
         # If you would like to submit a bug report, please visit:
         #   http://bugreport.sun.com/bugreport/crash.jsp
         #
ERROR: The Java child process terminated unexpectedly: status 262.
ERROR: WIFSIGNALED 1 WIFEXITED 0 WEXITSTATUS 1 WTERMSIG 6.
         jeipc jipcSuspend: extHandle 7fca9e4eae00
         jeipc jipcSuspend: exiting


  5? proc options option=jreoptions; run ;

    SAS (r) Proprietary Software Release 9.4  TS1M2

 JREOPTIONS=(
-DPFS_TEMPLATE=/opt/sas/SASFoundation/9.4/misc/tkjava/qrpfstpt.xml
-Djava.class.path=/opt/sas/SASVersionedJarRepository/eclipse/plugins/sas.launc
her.jar
-Djava.security.auth.login.config=/opt/sas/SASFoundation/9.4/misc/tkjava/sas.l
ogin.config
-Djava.security.policy=/opt/sas/SASFoundation/9.4/misc/tkjava/sas.policy
   -Djava.system.class.loader=com.sas.app.AppClassLoader
-Djdk.lang.Process.allowAmbigousCommands=true
-Dlog4j.configuration=file:/opt/sas/SASFoundation/9.4/misc/tkjava/sas.log4j.pr
operties
-Dsas.app.class.path=/opt/sas/SASVersionedJarRepository/eclipse/plugins/tkjava
.jar
-Dsas.ext.config=/opt/sas/SASFoundation/9.4/misc/tkjava/sas.java.ext.config
      -Dtkj.app.launch.config=/opt/sas/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


  6?

suga badge.PNGThe SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment. 

Join SUGA 

CLI in SAS Viya

Learn how to install the SAS Viya CLI and a few commands you may find useful in this video by SAS’ Darrell Barton.

Find more tutorials on the SAS Users YouTube channel.

Discussion stats
  • 18 replies
  • 4727 views
  • 7 likes
  • 7 in conversation