1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<html>
<head>
<meta HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<meta NAME="Author" CONTENT="Jon S. Stevens">
<title>Upgrading Apache JServ</title>
</head>
<body BGCOLOR="#FFFFFF">
<p align="center"><a href="http://java.apache.org/" target="_top"><img SRC="images/java-apache-project.gif" BORDER="0" WIDTH="609"
HEIGHT="100" ALT="The Java Apache Project"></a></p>
<h1 align="center">Upgrading Apache JServ</h1>
<blockquote>
This document should help describe some of the changes that one will need
to be aware of while upgrading Apache JServ from an older version to a newer
version. The official <a href="./changes.html">ChangeLog</a> has a more
complete and in depth revision history of the changes.
<h2>From 1.0 to 1.1</h2>
<strong>Unix configure changes</strong>:
<ol>
<li><strong>Apache configure related:
--activate-module=src/modules/jserv/libjserv.a</strong>
Use this to configure Apache now instead of src/modules/jserv/mod_jserv.c.</li>
<li><strong>Apache 1.2.x support completely removed</strong> We have removed all
support for Apache 1.2.x. Apache 1.3.x has been out for quite some time now and
we feel that it is best that you upgrade to the latest version. We also had several
bugs as a result of bugs in Apache 1.2.x that have been resolved in Apache 1.3.x.</li>
<li><strong>READ the INSTALL document</strong> The
<a href="./install/howto.unix_install.html">INSTALL</a> document has been re-written
to reflect the changes below. It is a good idea to read over this document again.</li>
<li><strong>--with-apache-install</strong> is deprecated in favor of
having a working APXS installation. You should now use --with-apxs instead.</li>
<li><strong>--with-jsdk</strong> Please use --with-JSDK now instead of --with-jsdk</li>
<li><strong>--with-JSDK</strong> You <strong>must</strong> specify this parameter if the JSDK 2.0 is
not installed in /usr/local/JSDK2.0. Having it in your CLASSPATH will not work anymore.</li>
<li><strong>--with-javac</strong> It is now possible to use a different java compiler
such as <a href="http://www.alphaworks.ibm.com/tech/jikes">IBM's Jikes compiler</a></li>
<li><strong>--enable-apache-config</strong> This option will attempt to configure
Apache for use with Apache JServ during the Apache JServ configure process by running
Apache's config.status script. By default it is on for static and will turn itself off
for DSO compilation.</li>
<li><strong>make install</strong> Be sure to verify that the jserv.properties is properly
pointing to the new ApacheJServ.jar file that is installed by 'make install' and not
the old one.</li>
<li><strong>Copied vs. Symlinked</strong> The C files for Apache JServ are now copied
to the apache_src/modules/jserv/ directory instead of being symlinked. Not particularly
important, but something to note.</li>
</ol>
<strong>Windows installer changes</strong>:
<p>
TBD
<p>
<hr noshade size="1" width="80%">
<p>
<strong>jserv.conf</strong>:
<ol>
<li><strong>ApJServDefaultProtocol</strong> is now ajpv12. Please only use this and not
ajpv11. If you are having problems with the upgrade, this is the
<strong>FIRST</strong> place to look since our error messages are probably not
very helpful in this case.</li>
<li><strong>ApJServMount</strong> The sample configuration files now have an entry for
/servlets and /servlet.</li>
<li><strong>ApJServVMTimeout</strong> The sample configuration files now have an entry for
this setting. It is the amount of time to give the VM to start up as well as the amount
of time between pings. If it takes longer than N number of seconds to get a response
from the JVM, then restart it. Busy or slow servers should increase this setting.</li>
</ol>
<strong>jserv.properties</strong>:
<ol>
<li><strong>wrapper.protocol</strong> is now ajpv12. Please only use this and not
ajpv11. If you are having problems with the upgrade, this is the
<strong>FIRST</strong> place to look since our error messages are probably not
very helpful in this case.</li>
<li><strong>bindaddress</strong> This is a new feature that allows you to bind an
instance of the Java portion of Apache JServ to a single IP address
and port. By default this is "localhost" which resolves to 127.0.0.1.</li>
<li><strong>Thread Pool</strong> There is now an implementation of a thread pool.
Since this has not been a heavily tested feature, it is off by default. If you
choose to turn it on, your <a href="mailto:stefano@apache.org">feedback</a>
on it would be most appreciated. The result of using a thread pool should be
increased performance. The default configuration files from the distribution
have example settings.</li>
<li><strong>Logging</strong> The logging features of Apache JServ are now
tuned a bit better to provide logging information only when needed. Please
update your configuration files to reflect the changes in the default configuration
files from the distribution.</li>
</ol>
<strong>zone.properties</strong>:
<ol>
<li><strong>session.useCookies</strong> This is a new feature which allows one
to configure whether or not to use cookies for session tracking. If this is set to
false, then cookies will never be used and response.encodeUrl() will always encode
the session information into the URL.</li>
</ol>
</blockquote>
<p align="center"><font SIZE="-1">Copyright (c) 1997-99 <a HREF="http://java.apache.org/">The
Java Apache Project</a>.<br>
$Id: upgrade.html,v 1.6 1999/10/15 00:23:59 jonbolt Exp $<br>
All rights reserved.</font></p>
</body>
</html>
|
