ChrisS wrote:
Rainer Jung wrote:
Unfortunately I have some difficulties to understand, what you want
to tell me:
Ok Rainer that solves that one, I do have a built in Apache Solaris 10
What solves what?
dist this is:
bash-3.00# /usr/apache2/bin/httpd -l
Compiled in modules:
core.c
prefork.c
http_core.c
mod_so.c
bash-3.00# /usr/apache2/bin/httpd -v
Server version: Apache/2.0.63
Server built: Feb 5 2008 11:13:45
bash-3.00#
Please recommend! almost forgot thanks helluvalot.
Not sure, what you mean by recommend? I was suggesting 2.2.x, you
have a 2.0.x. That's not exactly the same :) Quite possible, that
it's more important for you to use a Solaris bundled httpd instead of
a self build one. If that is a wise decision depends on the
importance Apache httpd has for you. If it is really important, I
would not necessarily rely on the OS delivering company to provide
needed updates in time.
Would this config suffice mate!!!
I don't get this, it's a question with exclamation marks, hmmmmm
ps I really wanted to get this sorted for a mate in work, we have a
clustered setup not clustering between Tomcat nodes on a 1.3.39
setup, there are also session sharing issues with deployed apps, the
idea was to lab the problem and try to find a resolve.
Aha, so then it makes sense to use the same versions, you also have
in production.
I would need to check the SSL status exactly but this is
running/serving SSL requests on a Sparc SunBlaze server. Would the
binary dist of mod_jk (current) work with this environment ? this
being a great deal saner than this one I am using
Which binary dist? The one from the ASF download page? Yes, that one
will need an EAPI httpd, i.e. one build with ssl support.
Will this be saner? Not sure. Our binary dist is build with gcc and
the httpd we are talking about might be build with Sun Studio (not
sure, if we are talking about yet another httpd).
Regards,
Rainer
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
The binary distribution referred to is mod_jk, I remember seeing one
in the mirrors for a Sparc installation only! isn't there one for x86
or is that something going on between the Org and Sun Microsystems?
Some typos in my response apologies only human still!
Would or could you recommend that the version I have: apache 2.0.63 be
able to work with the jk_mod current connector module? I provide the
output of 2.0.63 so that you may be able to see whether or not,
compiling the mod_jk source against it would work. Or do I have to do
something else like for example download another huge package to
compile it with.
This is an Org and I recognise that so I keep in the frame of mind
that if someone helps me then the favor is returned further down the
line (I call this ethics and nice manners)
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Apache 2.0.63 Solaris 10 x86 works!
Steps taken:
0. Got loads of help from the guys at users@tomcat.apache.org (thanks guys!)
1. Download Sun Studio 11for x86 and install as su - root. (Refer to
www.sun.com for this)
2. Include /opt/SUNWspro/bin in the PATH environment variable
(PATH=/opt/SUNWspro:$PATH)
3. Download Tomcat from http://tomcat.apache.org/ i am using 5.5.20.0 as
of this writing.
Install Tomcat (see http://tomcat.apache.org for this)
4. svn checkout tomcatconnectors JK 1.2.26 refer to (google,
http://tomcat.apache.org, etc ... for this) Subversion(svn) can be
downloaded from http://www.sunfreeware.com. Apparently this release of
mod_jk fixes some session sharing issues amongst other important issues
between TomcatNodes(well thats how I read it anyway). Apache ant is
required to build this so download that also(and follow instructions for
using it). In order to use buildconf.sh you will require. autoconf,
automake, autoheader, aclocal, libtoolize these can all be found at
www.sunfreeware.com perl is also required. Make sure the fresh installs
are referenced from the PATH variable. On my system these live in
/usr/local/bin. Also make sure that /usr/sfw/bin isn't referenced in the
PATH along with CC= not being set, don't forget to export ;).
5. When everything is set run buildconf.sh check the top_builddir
variable in common and apache-2.0 subdirectories this should be:
top_builddir = .. (note the spaces I think under common this was:
top_builddir=.. this threw an error and took a while to track down)
6. Once step was completed I ran configure against apxs in the desired
apache directory e.g. ./configure --with-apxs=/usr/apache2/bin/apxs
This worked! I did try this against apache-1.3.39 dist but to no avail
apparently symbol reference: ap_ctx_get was missing in the symbol
table. When trying to run: /usr/apache/bin/apachectl start. Furthermore
I ran nm "/usr/apache/bin/httpd | grep ap_ctx_get" to establish this and
was told by one of the guru's that SSL was required to be included for
this to work in apache-1.3.39. It was also recommended that I move to a
2.2.8 distribution. Although I hesitated at this because time was
getting past me and I had spent too long with this build already. So
looking at the "/www/connectors/jk/native/apache-2.0" directory showed
me that apache-2.0 was one of the subdirectories. So working off
intuition I tried 2.0.63 instead and this worked.
TODO: Check that this revised tomcatconnector mod_jk does what I need.
Which is session sharing between two Tomcat Nodes in a clustered load
balancing scenario.
ps If I can help out give me a ping ;)
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
