Revision as of 22:40, 12 November 2009

Preliminaries

Before installation, there are several changes that you'll need to know in order to migrate to Resin 4.0:

The required JDK version is now Java 1.6. As of this writing, Java 1.5 and earlier have reached the end of service life. Make sure you use the JDK -- the JRE is not sufficient.
The build process for compiling the Resin JNI and installing Resin have changed. Before Resin 4.0, you would install Resin by unpacking the distribution directly in the filesystem. Resin 4.0's configure script now creates makefiles that install all the necessary files in standard locations for Linux/Unix. There is also a .deb package for Ubuntu available. Windows installation is unchanged.
The main configuration file has been renamed from resin.conf to resin.xml.

As a general recommendation for migration, we suggest starting with a clean installation of Resin 4.0, including using the sample configuration. By beginning with the sample configuration and modifying it to match your deployment setup, you'll be much more likely to configure the server correctly. This approach is usually much easier than starting with your existing configuration and modifying to make it compatible with the new version.

Migrating from Resin 3.0

Starting Resin

One of the major changes from Resin 3.0 to Resin 4.0 is the introduction of the Resin Watchdog which changes the way in which Resin is started and managed during runtime. The httpd.sh and httpd.exe executables no longer exist. The Watchdog documentation linked above has in-depth details, but essentially Resin now runs with two Java processes, the main Resin process and the Watchdog. This architecture introduces many advantages for management and reliability, but changes the way that Resin is started and how the Java process is managed.

Example Resin 4.0 command line

java -jar $RESIN_HOME/lib/resin.jar -conf /etc/resin/resin.xml -root-directory=/var/www -server app-a start

JVM arguments

JVM arguments for the main Resin process are now set within the resin.xml file instead of being passed via a script. Any JVM arguments on the command line actually go to the Watchdog process.

Linux/Unix

If you are using Linux, a sample init.d script for Resin is

Binding to port 80

Windows

Logging

Converting clustered setups

Filters

Rewrite filter

JMS

Hessian

Deprecated features

Migrating from Resin 3.1

Starting Resin 4.0

For the most part, Resin 4.0 is started the same way as Resin 3.1. One exception is if you start Resin attached to the terminal. In general, you should run a Resin server using the "start" command, but

@@ Line 1: / Line 1: @@
+=Preliminaries=
+Before installation, there are several changes that you'll need to know in order to migrate to Resin 4.0:
+# The required JDK version is now Java 1.6.  As of this writing, Java 1.5 and earlier have reached the end of service life.  Make sure you use the JDK -- the JRE is not sufficient.
+# The [http://caucho.com/resin/install/install.xtp build process] for compiling the Resin JNI and installing Resin have changed.  Before Resin 4.0, you would install Resin by unpacking the distribution directly in the filesystem.  Resin 4.0's configure script now creates makefiles that install all the necessary files in standard locations for Linux/Unix.  There is also a .deb package for Ubuntu available.  Windows installation is unchanged.
+# The main configuration file has been renamed from resin.conf to resin.xml.
+As a general recommendation for migration, we suggest starting with a clean installation of Resin 4.0, including using the sample configuration.  By beginning with the sample configuration and modifying it to match your deployment setup, you'll be much more likely to configure the server correctly.  This approach is usually much easier than starting with your existing configuration and modifying to make it compatible with the new version.
 =Migrating from Resin 3.0=
 ==Starting Resin==
-One of the major changes from Resin 3.0 to Resin 4.0 is the introduction of the [http://caucho.com/resin/admin/watchdog.xtp Resin Watchdog] which changes the way in which Resin is started and managed during runtime.  The httpd.sh and httpd.exe executables no longer exist.
+One of the major changes from Resin 3.0 to Resin 4.0 is the introduction of the [http://caucho.com/resin/admin/watchdog.xtp Resin Watchdog] which changes the way in which Resin is started and managed during runtime.  The httpd.sh and httpd.exe executables no longer exist.  The Watchdog documentation linked above has in-depth details, but essentially Resin now runs with two Java processes, the main Resin process and the Watchdog.  This architecture introduces many advantages for management and reliability, but changes the way that Resin is started and how the Java process is managed.
+Example Resin 4.0 command line
+ java -jar $RESIN_HOME/lib/resin.jar -conf /etc/resin/resin.xml -root-directory=/var/www -server app-a start
+==JVM arguments==
+JVM arguments for the main Resin process are now set within the resin.xml file instead of being passed via a script.  Any JVM arguments on the command line actually go to the Watchdog process.
+==Linux/Unix==
+If you are using Linux, a sample init.d script for Resin is
+Binding to port 80
+===Windows===
-JDK version
 ==Logging==
@@ Line 12: / Line 34: @@
 ==Hessian==
 ==Deprecated features==
+=Migrating from Resin 3.1=
+==Starting Resin 4.0==
+For the most part, Resin 4.0 is started the same way as Resin 3.1.  One exception is if you start Resin attached to the terminal.  In general, you should run a Resin server using the "start" command, but

Migrating from Resin 3.0 to Resin 4.0

From Resin 3.0