tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andoni <andonil...@eurokom.ie>
Subject Upgrade woes!
Date Sun, 10 Oct 2004 16:34:10 GMT
Hello,

I am desperately trying to upgrade my machine from Tomcat 4.0.4 to Tomcat 4.1.24.

This went fairly smoothly, I had made all possible mistakes in previous aborted attempts.
I was left with a perfectly working Tomcat but then found my attempts to upgrade from MOD_JK
to MOD_JK2 had caused problems. Apache now won't start for me unless I revert to Mod_JK. Unfortunately
the documentation online for Mod_jk does not answer my simple question:

1. Is my default jk2.properties file in which everything is commented out good enough?
2. Should this file be included somewhere or is it's presence in the catalina.home/conf directory
enough.
3. Should I be using Jk2 with Apache 1.3.26 or should I just stick with Jk?
4. Do the settings that I have by default in workers2.properties look right and do I really
need a mapping for each webapp now?

Any help would be much appreciated (as ever).

Andoni.


# My workers2.properties looks like:
#######################################################################################

[shm]
file=/apache/logs/shm.file
size=1048576

[lb:lb]
info=Default load balancer.
debug=0

# Example socket channel, override port and host.
[channel.socket:localhost:8009]
port=8009
host=127.0.0.1
group=lb

# define the worker
[ajp13:localhost:8009]
channel=channel.socket:localhost:8009

# Uri mapping
[uri:/examples/*]
group=lb
#worker=ajp13:localhost:8009

#[status:]
#info=Status worker, displays runtime informations

#[uri:/jkstatus/*]
#info=Display status information and checks the config file for changes.
#group=status:

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message