JRE Update: Difference between revisions

From SEPsesam
(Redirected to Troubleshooting Guide.)
 
(14 intermediate revisions by 6 users not shown)
Line 1: Line 1:
== After Update from JRE 6 to JRE 7 Sesam Server on Windows systems will not startup ==
#REDIRECT [[Troubleshooting_Guide#Graphical_User_Interface_.28GUI.29_problems|Troubleshooting Guide]]
== After updating Java to a newer major version SEP sesam Server will not start ==


{{Box Hint|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 ===
=== Indication ===


After a customer has updated his Java istallation from major version 6 to version 7, the Sesam server does not startup, this manual will explains how to fix this issue.
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.
This only concerns customers with Sesam installations on Windows based operating systems.


=== Cause of the problem ===
=== Cause of the problem ===


The Sesam server configuration file:
The SEP sesam Server configuration file:


  <sesam_install_dir>/var/ini/sm.ini
  <sesam_install_dir>\var\ini\sm.ini


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


  [JAVA]
  [JAVA]
Line 18: Line 21:
  java_interpreter=C:\Program Files\Java\jre6\bin\java  
  java_interpreter=C:\Program Files\Java\jre6\bin\java  


After the update from JRE 6 to JRE 7, this path is not present on the system anymore, this causes the Sesam startup to fail.
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 ===
=== Solution ===


In order to resolve the issue edit this configuration file and change the path to point to the JRE 7 installation, usually this Path is:
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\jre6\bin\java  
  C:\Program Files\Java\<big>jre7</big>\bin\java


change the configuration file to:
Change the configuration file to something like this:


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


Starting the Sesam Service should work after the change has been commited to the configuration file.
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 aswell as the desktop icons, both include the path to the JRE installation and have to be changed to make the GUI startup possible, see this screenshot:
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:


[[File:jreupdate.jpg]]
[[File: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
[http://www.oracle.com/technetwork/java/javase/7u51-relnotes-2085002.html 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:
* Complete deinstall SEP sesam Server
* Complete deinstall Java JRE 7u51
* Download an older Java JRE Version (for example: Java JRE 7u45)
** Java Download Archive for older Versions: http://www.oracle.com/technetwork/java/javase/downloads/java-archive-downloads-javase7-521261.html#jdk-7u45-oth-JPR
* Install an older Java JRE Version (for example: Java JRE 7u45)
* Install SEP sesam server

Latest revision as of 12:49, 29 September 2017

Redirect to:

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:

Retrieved from "https://wiki.sep.de/wiki/index.php?title=JRE_Update&oldid=48085"