You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by Tom Riemer <to...@phinu.org> on 2002/10/18 23:15:55 UTC
Tomcat 4.1.12 - Apache2 attempt
Brzezinski, Paul J wrote:
>Excellent, that fixed the problem of ant spawning libtool w/cc.
>
>There are two other issues that popped up now:
>
>1. in the file jk_channel_socket.c in directory
>jakarta-tomcat-5.0.0-src/jakarta-tomcat-connectors/jk/native2/common must be
>compiled with -DBSD_COMP on Solaris 8.
>
>2. when building the native (as opposed to the native2) connectors, jni_md.h
>isn't found presumably because the -I${java.home}/../include/solaris isn't
>set in build.xml.
>
>
I can confirm that ant native fails in the exact same way with JDK1.3.1
on linux (using blackdown JDK 1.3.1) - it is not a problem
with build.xml - it seems like a fundamental problem with the JDK.
There is no reason
that the JDK includes should force you to know what platform you are on.
(That's counterintuitive
to everything Java is about)
Here are some other problems that I ran into on the connectors
build/tomcat build.
1. ant install doesn't exist in build.xml - I've had to manually (and I
must admit unsuccessfully) install
the mod_jk2.so by hand. It would be really lovely if someone would put
in ant install
as it says exists in the readme.
2. I have yet to make apache2 talk to tomcat 4.1 - I know that my
tomcat4.1 server
is set up correctly because I have an apache 1.3.?? talking to the
tomcat4.1 server,
however the apache2 install does not talk correctly to the tomcat4.1 server.
I tried to install the standard jk into apache - and that seemed to take
- it correctly
interprets the JkMounts - which implies that the jk module is being hit.
But any access
to the tomcat server just generates an internal server from the apache
server.
I tried to install the jk2 module into apache2 - that seemed to be more
of a problem.
It would be really helpful if someone would provide an example of
configuring the jk2
module on apache.
The other comment I'd like to make is the connectors need some sort of
clearer roadmap
to figure out which connector should be used with which variety of
apache/tomcat.
There seems to be 4 different connector types x 3-5 different servers -
its getting unwieldy
to figure out.
3. For some reason web.xml got a little bit more persnickety - I am not
sure whether
this is intentional and following some standard - or whether it was an
oversight. The elements
in web.xml now must be in a particular order - or the server won't
start. This wasn't too bad -
it just meant rearranging code....
4. One of the things that wasn't mentioned in the build instructions
for 4.1.12 is what version
of xerces/xalan should be used - I ended up using the most recent
version - but this has generated
some other problems. That may be the cause of my web.xml problem.
5. Interceptors.xml - There used to be a way to create your own Realm
object, and define
the interceptor in a file called interceptors.xml - this seems to have
gone away - and no longer
works. Is there a new way to do this in 4.1?
6. Jasper - the build.properties.exampe for tomcat indicates
${TOMCAT_HOME}/jasper2
as the path for jasper - only the directories in tomcat just refer to
jasper.
7. Catalina seems not to build with mbeans support even though I have
jmx installed.
There seem to be a number of optional libraries in the BUILDING.txt
- It seems reasonable to
make the default conf not use the optional libraries - i.e. leave
the code in the server.xml
but comment it out if it depends on an optional library.
Just my two cents,
Tom Riemer
>I did try to search bugzilla to see if these two issues are already being
>tracked, but didn't find anything, which could just be about me not knowing
>how to search the bug database...
>
>Comments, advice, feedback encouraged...
>
>Paul
>
>
>--
>mailto:Paul.Brzezinski@EDS.com
>Enterprise Distributed Capabilities
>EDS Corporation
>248-265-8283
>
>
>: -----Original Message-----
>: From: Henri Gomez [mailto:hgomez@apache.org]
>: Sent: Friday, October 18, 2002 4:16 AM
>: To: Tomcat Developers List
>: Subject: Re: [5]: ant native for Connectors fails:
>:
>:
>: Brzezinski, Paul J wrote:
>: > Trying to build Jakarta Tomcat Connectors from 5.0.0 source:
>: >
>: > In jakarta-tomcat-connectors/jk
>: >
>: > Ant native complains about cc not being found, on Solaris 8, I have
>: > gcc in /em/opt/bin/gcc. I have no idea how to tell ant
>: that it should
>: > use gcc or /em/opt/bin/gcc instead of cc, and no idea how
>: to configure
>: > the args to libtool that it should gcc instead of cc.
>: >
>: > I'd like to figure this out, but need assistance.
>: >
>: > Assuming this isn't a known bug, is this something that should be
>: > reported as a bug using bugzilla?
>:
>: You could put /em/opt/bin/ in PATH before compiling ?
>:
>: export PATH=/em/opt/bin:$PATH
>:
>: Or set the ant project property :
>:
>: buid.native.cc=/em/opt/bin/gcc
>:
>:
>:
>:
>:
>: --
>: To unsubscribe, e-mail:
>: <mailto:tomcat-dev-: unsubscribe@jakarta.apache.org>
>: For
>: additional commands,
>: e-mail: <ma...@jakarta.apache.org>
>:
>
>--
>To unsubscribe, e-mail: <ma...@jakarta.apache.org>
>For additional commands, e-mail: <ma...@jakarta.apache.org>
>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>