You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by Ziying Sherwin <sh...@lhc.nlm.nih.gov> on 2003/09/23 20:55:03 UTC
our attempt to build tomcat 4.1.27 from source on Solaris 2.8
Dear tomcat Colleagues,
We have been trying to build tomcat 4.1.27 from source, which we downloaded
from the cvs repository (cvs.apache.org) onto a SPARC computer
running Solaris 2.8, using j2sdk 1.4.0. Unfortunately, the installation
failed, and we are hoping to find helpful insights to get us back on the road.
We have successfully installed the pre-built binary for tomcat, but strongly
prefer to build it from source. We posted several messages to the mailing
list several weeks ago, asking for help, but received no replies.
Here is a detailed summary of what we did, and the outcome.
FIrst, we installed the following related packages:
ant 1.5.3-1
jaf 1.0.2
Java XML Pack Fall 01 FCS Bundle
javamail 1.3
jdbc 2.0
JMX 1.2
JNDI 1.2.1
jsse 1.0.2
jta 1.0.1
xerces 2.4.0
We downloaded the following tomcat modules from the indicated locations:
commons-beanutils-1.6.1 (http://www.apache.org/dist/jakarta/commons/beanutils/binaries/commons-beanutils-1.6.1.tar.gz)
commons-collections-2.1 (http://www.apache.org/dist/jakarta/commons/collections/binaries/collections-2.1.tar.gz)
commons-digester-1.4.1 (http://www.apache.org/dist/jakarta/commons/digester/binaries/commons-digester-1.4.1.tar.gz)
commons-dbcp-1.0 (http://jakarta.apache.org/builds/jakarta-commons/release/commons-dbcp/v1.0/commons-dbcp-1.0.zip)
commons-fileupload-1.0 (http://www.apache.org/dist/jakarta/commons/fileupload/commons-fileupload-current.tar.gz)
commons-logging-1.0.2 (http://jakarta.apache.org/builds/jakarta-commons/release/commons-logging/v1.0.2/commons-logging-1.0.2.tar.gz)
commons-modeler-1.0 (http://jakarta.apache.org/builds/jakarta-commons/release/commons-modeler/v1.0/commons-modeler-1.0.tar.gz)
commons-pool-1.0.1 (http://jakarta.apache.org/builds/jakarta-commons/release/commons-pool/v1.0.1/commons-pool-1.0.1.tar.gz)
struts (http://jakarta.apache.org/builds/jakarta-struts/release/v1.0.2/jakarta-struts-1.0.2.tar.gz)
We also obtained the cvs versions of "jakarta-tomcat-connectors" and
"jakarta-tomcat-jasper" from the jakarta site from which we obtained tomcat.
We customized the build properties by editing the file build.properties to
reflect the correct paths to all the packages.
However, when we started to build the package using command "ant dist", we
observed the following error messages:
build-only:
[javac] Compiling 79 source files to /src/tomcat_4.1.27/jasper/build/shared/classes
[javac] /src/tomcat_4.1.27/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/JspC.java:71: package javax.servlet does not exist
[javac] import javax.servlet.ServletException;
[javac] ^
[javac] /src/tomcat_4.1.27/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/Options.java:66: package javax.servlet does not exist
[javac] import javax.servlet.ServletConfig;
[javac] ^
[javac] /src/tomcat_4.1.27/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/Options.java:67: package javax.servlet does not exist
[javac] import javax.servlet.ServletContext;
[javac] ^
[javac] /src/tomcat_4.1.27/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/servlet/JspCServletContext.java:73: package javax.servlet does not exist
[javac] import javax.servlet.RequestDispatcher;
[javac] ^
[javac] /src/tomcat_4.1.27/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/servlet/JspCServletContext.java:74: package javax.servlet does not exist
[...]
/src/tomcat_4.1.27/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler/JspUtil.java:105: cannot resolve symbol
[javac] symbol : class ExpressionEvaluatorImpl
[javac] location: class org.apache.jasper.compiler.JspUtil
[javac] private static ExpressionEvaluatorImpl expressionEvaluator
[javac] ^
[javac] /src/tomcat_4.1.27/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler/JspUtil.java:627: cannot resolve symbol
[javac] symbol : class FunctionMapper
[javac] location: class org.apache.jasper.compiler.JspUtil
[javac] FunctionMapper functionMapper,
[javac] ^
[javac] Note: Some input files use or override a deprecated API.
[javac] Note: Recompile with -deprecation for details.
[javac] 100 errors
BUILD FAILED
file:/src/tomcat_4.1.27/jakarta-tomcat-jasper/jasper2/build.xml:127: Compile failed; see the compiler error output for details.
There is no mention of jasper in the file BUILDING.txt which came with the
source distribution. Is jasper required by the tomcat build? If not, is there
a way to disable it? How can we build jasper from source?
Thanks in advance for any insights into our problems!
Best Regards,
Ziying Sherwin (sherwin@nlm.nih.gov)
Rick Rodgers (rodgers@nlm.nih.gov)
Re: AJP13 in TC 3.3.2-dev
Posted by Henri Gomez <hg...@apache.org>.
Bill Barker a écrit :
> ----- Original Message -----
> From: "Henri Gomez" <hg...@apache.org>
> To: "Tomcat Developers List" <to...@jakarta.apache.org>
> Sent: Wednesday, September 24, 2003 1:42 AM
> Subject: AJP13 in TC 3.3.2-dev
>
>
>
>>Did we still use in TC 3.3.2-dev the Ajp13 code in
>>org.apache.tomcat.modules.server or the one in JTC ?
>>
>
>
> I only ever use the j-t-c Coyote connectors personally. I don't recall that
> there has been an official decision, but I'd be +1 to deprecating
> o.a.t.m.server.
+1 to depreciate or even better to remove it from TC 3.3.2 dev.
Also I'd like to see Coyote/HTTP 1.1 connector used in TC 3.3.2
by default ;)
Re: AJP13 in TC 3.3.2-dev
Posted by Henri Gomez <hg...@apache.org>.
Bill Barker a écrit :
> ----- Original Message -----
> From: "Henri Gomez" <hg...@apache.org>
> To: "Tomcat Developers List" <to...@jakarta.apache.org>
> Sent: Wednesday, September 24, 2003 1:42 AM
> Subject: AJP13 in TC 3.3.2-dev
>
>
>
>>Did we still use in TC 3.3.2-dev the Ajp13 code in
>>org.apache.tomcat.modules.server or the one in JTC ?
>>
>
>
> I only ever use the j-t-c Coyote connectors personally. I don't recall that
> there has been an official decision, but I'd be +1 to deprecating
> o.a.t.m.server.
+1 to depreciate or even better to remove it from TC 3.3.2 dev.
Also I'd like to see Coyote/HTTP 1.1 connector used in TC 3.3.2
by default ;)
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
Re: AJP13 in TC 3.3.2-dev
Posted by Bill Barker <wb...@wilshire.com>.
----- Original Message -----
From: "Henri Gomez" <hg...@apache.org>
To: "Tomcat Developers List" <to...@jakarta.apache.org>
Sent: Wednesday, September 24, 2003 1:42 AM
Subject: AJP13 in TC 3.3.2-dev
> Did we still use in TC 3.3.2-dev the Ajp13 code in
> org.apache.tomcat.modules.server or the one in JTC ?
>
I only ever use the j-t-c Coyote connectors personally. I don't recall that
there has been an official decision, but I'd be +1 to deprecating
o.a.t.m.server.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
>
AJP13 in TC 3.3.2-dev
Posted by Henri Gomez <hg...@apache.org>.
Did we still use in TC 3.3.2-dev the Ajp13 code in
org.apache.tomcat.modules.server or the one in JTC ?
AJP13 in TC 3.3.2-dev
Posted by Henri Gomez <hg...@apache.org>.
Did we still use in TC 3.3.2-dev the Ajp13 code in
org.apache.tomcat.modules.server or the one in JTC ?
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
JK add-ons to fix problems with HUNG tomcats...
Posted by Henri Gomez <hg...@apache.org>.
Hi to all,
After the yesterday post of David Rees (mod_jk does not detect a hung
Tomcat), I take a look at ajp/jk and make some works to fix the problem.
In fact the problem is in jk since the begining as jk use sockets in
blocking mode.
The works I conducted :
- Modify ajp protocol on java side to accept a PING message (0x08).
This message will be answered by low level ajp layer by a ..
PONG(0x09).
- On the jk (not jk2 for now) I added 3 optional timeouts :
a connect_timeout, which when set will send a PING request
after connection and wait for PONG reply up to connect_timeout ms.
a prepost_timeout, which when set will send a PING request before
trying to send the real request to tomcat.
in fine I added the long awaited reply_timeout, which will make
jk wait up to reply_timeout ms before failing in error.
With such 3 timeouts (optional in workers.properties), we should be
able to detect any problem with remote tomcats and as such make a
better use of tomcat clusters via Load-Balancing.
If nobody object, I'll commit it this afternoon CET for review and
comments.
Note, that by default jk works as before....
JK add-ons to fix problems with HUNG tomcats...
Posted by Henri Gomez <hg...@apache.org>.
Hi to all,
After the yesterday post of David Rees (mod_jk does not detect a hung
Tomcat), I take a look at ajp/jk and make some works to fix the problem.
In fact the problem is in jk since the begining as jk use sockets in
blocking mode.
The works I conducted :
- Modify ajp protocol on java side to accept a PING message (0x08).
This message will be answered by low level ajp layer by a ..
PONG(0x09).
- On the jk (not jk2 for now) I added 3 optional timeouts :
a connect_timeout, which when set will send a PING request
after connection and wait for PONG reply up to connect_timeout ms.
a prepost_timeout, which when set will send a PING request before
trying to send the real request to tomcat.
in fine I added the long awaited reply_timeout, which will make
jk wait up to reply_timeout ms before failing in error.
With such 3 timeouts (optional in workers.properties), we should be
able to detect any problem with remote tomcats and as such make a
better use of tomcat clusters via Load-Balancing.
If nobody object, I'll commit it this afternoon CET for review and
comments.
Note, that by default jk works as before....
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
Re: our attempt to build tomcat 4.1.27 from source on Solaris 2.8
Posted by Bill Barker <wb...@wilshire.com>.
It doesn't look like you got the servletapi-4 project (or it is in the wrong
place). Try doing:
ant download
to make certain that you've got all of the jars you need to build Tomcat.
If you are behind a firewall, you'll need to set the values of 'proxy.host'
and 'proxy.port' in your build.properties file first.
I build Tomcat 4.1.x from source on Solaris pretty regularly, so it
definately can be done ;-).
"Ziying Sherwin" <sh...@lhc.nlm.nih.gov> wrote in message
news:Pine.GSO.4.21.0309231454090.19227-100000@hume.nlm.nih.gov...
>
> Dear tomcat Colleagues,
>
> We have been trying to build tomcat 4.1.27 from source, which we
downloaded
> from the cvs repository (cvs.apache.org) onto a SPARC computer
> running Solaris 2.8, using j2sdk 1.4.0. Unfortunately, the installation
> failed, and we are hoping to find helpful insights to get us back on the
road.
> We have successfully installed the pre-built binary for tomcat, but
strongly
> prefer to build it from source. We posted several messages to the mailing
> list several weeks ago, asking for help, but received no replies.
>
> Here is a detailed summary of what we did, and the outcome.
> FIrst, we installed the following related packages:
>
> ant 1.5.3-1
> jaf 1.0.2
> Java XML Pack Fall 01 FCS Bundle
> javamail 1.3
> jdbc 2.0
> JMX 1.2
> JNDI 1.2.1
> jsse 1.0.2
> jta 1.0.1
> xerces 2.4.0
>
> We downloaded the following tomcat modules from the indicated locations:
>
> commons-beanutils-1.6.1
(http://www.apache.org/dist/jakarta/commons/beanutils/binaries/commons-beanu
tils-1.6.1.tar.gz)
> commons-collections-2.1
(http://www.apache.org/dist/jakarta/commons/collections/binaries/collections
-2.1.tar.gz)
> commons-digester-1.4.1
(http://www.apache.org/dist/jakarta/commons/digester/binaries/commons-digest
er-1.4.1.tar.gz)
> commons-dbcp-1.0
(http://jakarta.apache.org/builds/jakarta-commons/release/commons-dbcp/v1.0/
commons-dbcp-1.0.zip)
> commons-fileupload-1.0
(http://www.apache.org/dist/jakarta/commons/fileupload/commons-fileupload-cu
rrent.tar.gz)
> commons-logging-1.0.2
(http://jakarta.apache.org/builds/jakarta-commons/release/commons-logging/v1
.0.2/commons-logging-1.0.2.tar.gz)
> commons-modeler-1.0
(http://jakarta.apache.org/builds/jakarta-commons/release/commons-modeler/v1
.0/commons-modeler-1.0.tar.gz)
> commons-pool-1.0.1
(http://jakarta.apache.org/builds/jakarta-commons/release/commons-pool/v1.0.
1/commons-pool-1.0.1.tar.gz)
> struts
(http://jakarta.apache.org/builds/jakarta-struts/release/v1.0.2/jakarta-stru
ts-1.0.2.tar.gz)
>
> We also obtained the cvs versions of "jakarta-tomcat-connectors" and
> "jakarta-tomcat-jasper" from the jakarta site from which we obtained
tomcat.
>
> We customized the build properties by editing the file build.properties to
> reflect the correct paths to all the packages.
>
> However, when we started to build the package using command "ant dist", we
> observed the following error messages:
>
> build-only:
> [javac] Compiling 79 source files to
/src/tomcat_4.1.27/jasper/build/shared/classes
> [javac]
/src/tomcat_4.1.27/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper
/JspC.java:71: package javax.servlet does not exist
> [javac] import javax.servlet.ServletException;
> [javac] ^
> [javac]
/src/tomcat_4.1.27/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper
/Options.java:66: package javax.servlet does not exist
> [javac] import javax.servlet.ServletConfig;
> [javac] ^
> [javac]
/src/tomcat_4.1.27/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper
/Options.java:67: package javax.servlet does not exist
> [javac] import javax.servlet.ServletContext;
> [javac] ^
> [javac]
/src/tomcat_4.1.27/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper
/servlet/JspCServletContext.java:73: package javax.servlet does not exist
> [javac] import javax.servlet.RequestDispatcher;
> [javac] ^
> [javac]
/src/tomcat_4.1.27/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper
/servlet/JspCServletContext.java:74: package javax.servlet does not exist
> [...]
>
/src/tomcat_4.1.27/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper
/compiler/JspUtil.java:105: cannot resolve symbol
> [javac] symbol : class ExpressionEvaluatorImpl
> [javac] location: class org.apache.jasper.compiler.JspUtil
> [javac] private static ExpressionEvaluatorImpl
expressionEvaluator
> [javac] ^
> [javac]
/src/tomcat_4.1.27/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper
/compiler/JspUtil.java:627: cannot resolve symbol
> [javac] symbol : class FunctionMapper
> [javac] location: class org.apache.jasper.compiler.JspUtil
> [javac] FunctionMapper
functionMapper,
> [javac] ^
> [javac] Note: Some input files use or override a deprecated API.
> [javac] Note: Recompile with -deprecation for details.
> [javac] 100 errors
>
> BUILD FAILED
> file:/src/tomcat_4.1.27/jakarta-tomcat-jasper/jasper2/build.xml:127:
Compile failed; see the compiler error output for details.
>
> There is no mention of jasper in the file BUILDING.txt which came with the
> source distribution. Is jasper required by the tomcat build? If not, is
there
> a way to disable it? How can we build jasper from source?
>
> Thanks in advance for any insights into our problems!
>
> Best Regards,
>
> Ziying Sherwin (sherwin@nlm.nih.gov)
> Rick Rodgers (rodgers@nlm.nih.gov)
Re: our attempt to build tomcat 4.1.27 from source on Solaris 2.8
Posted by Bill Barker <wb...@wilshire.com>.
It doesn't look like you got the servletapi-4 project (or it is in the wrong
place). Try doing:
ant download
to make certain that you've got all of the jars you need to build Tomcat.
If you are behind a firewall, you'll need to set the values of 'proxy.host'
and 'proxy.port' in your build.properties file first.
I build Tomcat 4.1.x from source on Solaris pretty regularly, so it
definately can be done ;-).
"Ziying Sherwin" <sh...@lhc.nlm.nih.gov> wrote in message
news:Pine.GSO.4.21.0309231454090.19227-100000@hume.nlm.nih.gov...
>
> Dear tomcat Colleagues,
>
> We have been trying to build tomcat 4.1.27 from source, which we
downloaded
> from the cvs repository (cvs.apache.org) onto a SPARC computer
> running Solaris 2.8, using j2sdk 1.4.0. Unfortunately, the installation
> failed, and we are hoping to find helpful insights to get us back on the
road.
> We have successfully installed the pre-built binary for tomcat, but
strongly
> prefer to build it from source. We posted several messages to the mailing
> list several weeks ago, asking for help, but received no replies.
>
> Here is a detailed summary of what we did, and the outcome.
> FIrst, we installed the following related packages:
>
> ant 1.5.3-1
> jaf 1.0.2
> Java XML Pack Fall 01 FCS Bundle
> javamail 1.3
> jdbc 2.0
> JMX 1.2
> JNDI 1.2.1
> jsse 1.0.2
> jta 1.0.1
> xerces 2.4.0
>
> We downloaded the following tomcat modules from the indicated locations:
>
> commons-beanutils-1.6.1
(http://www.apache.org/dist/jakarta/commons/beanutils/binaries/commons-beanu
tils-1.6.1.tar.gz)
> commons-collections-2.1
(http://www.apache.org/dist/jakarta/commons/collections/binaries/collections
-2.1.tar.gz)
> commons-digester-1.4.1
(http://www.apache.org/dist/jakarta/commons/digester/binaries/commons-digest
er-1.4.1.tar.gz)
> commons-dbcp-1.0
(http://jakarta.apache.org/builds/jakarta-commons/release/commons-dbcp/v1.0/
commons-dbcp-1.0.zip)
> commons-fileupload-1.0
(http://www.apache.org/dist/jakarta/commons/fileupload/commons-fileupload-cu
rrent.tar.gz)
> commons-logging-1.0.2
(http://jakarta.apache.org/builds/jakarta-commons/release/commons-logging/v1
.0.2/commons-logging-1.0.2.tar.gz)
> commons-modeler-1.0
(http://jakarta.apache.org/builds/jakarta-commons/release/commons-modeler/v1
.0/commons-modeler-1.0.tar.gz)
> commons-pool-1.0.1
(http://jakarta.apache.org/builds/jakarta-commons/release/commons-pool/v1.0.
1/commons-pool-1.0.1.tar.gz)
> struts
(http://jakarta.apache.org/builds/jakarta-struts/release/v1.0.2/jakarta-stru
ts-1.0.2.tar.gz)
>
> We also obtained the cvs versions of "jakarta-tomcat-connectors" and
> "jakarta-tomcat-jasper" from the jakarta site from which we obtained
tomcat.
>
> We customized the build properties by editing the file build.properties to
> reflect the correct paths to all the packages.
>
> However, when we started to build the package using command "ant dist", we
> observed the following error messages:
>
> build-only:
> [javac] Compiling 79 source files to
/src/tomcat_4.1.27/jasper/build/shared/classes
> [javac]
/src/tomcat_4.1.27/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper
/JspC.java:71: package javax.servlet does not exist
> [javac] import javax.servlet.ServletException;
> [javac] ^
> [javac]
/src/tomcat_4.1.27/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper
/Options.java:66: package javax.servlet does not exist
> [javac] import javax.servlet.ServletConfig;
> [javac] ^
> [javac]
/src/tomcat_4.1.27/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper
/Options.java:67: package javax.servlet does not exist
> [javac] import javax.servlet.ServletContext;
> [javac] ^
> [javac]
/src/tomcat_4.1.27/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper
/servlet/JspCServletContext.java:73: package javax.servlet does not exist
> [javac] import javax.servlet.RequestDispatcher;
> [javac] ^
> [javac]
/src/tomcat_4.1.27/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper
/servlet/JspCServletContext.java:74: package javax.servlet does not exist
> [...]
>
/src/tomcat_4.1.27/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper
/compiler/JspUtil.java:105: cannot resolve symbol
> [javac] symbol : class ExpressionEvaluatorImpl
> [javac] location: class org.apache.jasper.compiler.JspUtil
> [javac] private static ExpressionEvaluatorImpl
expressionEvaluator
> [javac] ^
> [javac]
/src/tomcat_4.1.27/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper
/compiler/JspUtil.java:627: cannot resolve symbol
> [javac] symbol : class FunctionMapper
> [javac] location: class org.apache.jasper.compiler.JspUtil
> [javac] FunctionMapper
functionMapper,
> [javac] ^
> [javac] Note: Some input files use or override a deprecated API.
> [javac] Note: Recompile with -deprecation for details.
> [javac] 100 errors
>
> BUILD FAILED
> file:/src/tomcat_4.1.27/jakarta-tomcat-jasper/jasper2/build.xml:127:
Compile failed; see the compiler error output for details.
>
> There is no mention of jasper in the file BUILDING.txt which came with the
> source distribution. Is jasper required by the tomcat build? If not, is
there
> a way to disable it? How can we build jasper from source?
>
> Thanks in advance for any insights into our problems!
>
> Best Regards,
>
> Ziying Sherwin (sherwin@nlm.nih.gov)
> Rick Rodgers (rodgers@nlm.nih.gov)
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org