Upgrade to 64bit Java 1.8 jre now RMI will not start

[James Mitchell]

Update the jre in $AW_HOME and tried to startso with following error message:

 

09:34:48.391 main: null ErrorMsg: AwE-9999 Internal error (11/22/20 9:34 AM)

Details: /u01/app/appworx/c/libnativecalls.so: /u01/app/appworx/c/libnativecalls.so: wrong ELF class: ELFCLASS32 (Possible cause: architecture word width mismatch)

nativecalls

Error creating rmiserver.lock file.

java.io.IOException: nativecalls library error

 

 

James Mitchell

Database Administrator

 

Division of Technology and Advanced Solutions

 

University Computer Center UC1640, Mail Stop 202

2801 W. Bancroft St.
Toledo, Ohio 43606-3390

419.530.3667

[e-mail]

 

[Richard_Blumlein_8490]

Hi James, 
Maybe I missed it but did not see the version of Application Manager you are using. We are currently on V9.3.1.
We had Appworx since 2006 I believe. I know it is picky on the Java you use. We started on AIX, and went to Oracle Linux
which is Red Hat based.  Be sure to check the compatibility docs on the Broadcom web site for the compatible Java levels. 
I think in the later releases OpenJDk works. 

I am still using Oracle Java 64 bit. I know when you get to Oracle Java 1.8 201, and higher there is issues with the Java needing the user keystores. AM V9.3.? came out with that. Before  we went to V9.3.1 we was at V9.1.1. We knew about this and removed the anon, and NULL parameters from the java.security file. 

java version "1.8.0_261"
Java(TM) SE Runtime Environment (build 1.8.0_261-b12)
Java HotSpot(TM) 64-Bit Server VM (build 25.261-b12, mixed mode)

I would suggest if all this does not work, open a ticket with support. But be sure to check the compatibility docs for your release. 

Best of luck, Happy thanksgiving. 

Rich

[James Mitchell]

Thanks for the reply but I figured it out.  Had to update the $AW_HOME/c/*.so libraries.

 

Jim