JRE Update

From SEPsesam
Jump to: navigation, search

After updating Java to a newer major version SEP sesam Server will not start

Note:

This mostly concerns customers with SEP sesam installations on Windows based operating systems.

Note that required Java version depends on SEP sesam version. For details on the required Java version, see Java Compatibility Matrix.

Indication

After a customer has updated his Java installation from major version 6 to version 7, the SEP sesam Server cannot start. This manual explains how to fix this issue.

Cause of the problem

The SEP sesam Server configuration file:

<sesam_install_dir>\var\ini\sm.ini

It includes a configuration section which initializes the path to the JRE virtual machine detected during installation of SEP sesam:

[JAVA]
java_exit_on_fail=no
java_interpreter=C:\Program Files\Java\jre6\bin\java 

After the update from JRE 6 to JRE 7, the configured path is not present on the system anymore; this causes the SEP sesam start to fail.

Solution

In order to resolve the issue edit this configuration file and change the path pointing to the old Java to the path of the new Java installation. Usually this Path is:

C:\Program Files\Java\jre7\bin\java

Change the configuration file to something like this:

[JAVA]
java_exit_on_fail=no
java_interpreter=C:\Program Files\Java\jre7\bin\java 

Starting the SEP sesam Service should work after the change has been saved to the configuration file.

Further steps include changing the Start menu items as well as the desktop icons. Both include the JRE installation path and have to be changed to make the GUI start possible, compare the following screenshot:

Jreupdate.jpg

SEP sesam RMI (GUI) Server will not start up with Java Version 7 Update 51

With Java™ SE Development Kit 7, Update 51 (JDK 7u51) the java policy requires the right to listen on port 11401!

See Update Release Notes - Java™ SE Development Kit 7, Update 51 (JDK 7u51) .

Solution

  • Open the file <SESAM_ROOT>/var/ini/sm_java.policy
  • Go to section
 // NET
 permission java.net.SocketPermission "*:*", "connect,resolve";
 permission java.net.SocketPermission "*:11301", "connect,accept,resolve";
 permission java.net.SocketPermission "*:11401", "connect,accept,resolve";
 permission java.net.SocketPermission "*:21", "connect,accept,resolve";


  • Change the line
permission java.net.SocketPermission "*:11401", "connect,accept,resolve";
  • to
permission java.net.SocketPermission "*:11401", "connect,accept,resolve,listen";

Solution for new SEP sesam Server Installations

Attention: This solution is only after a fresh SEP sesam Server installation was performed: