On Fri, 20 Apr 2007, Mladen Turk wrote:
So, have you tried to put the JkWorkersFile outside the vhost?
I've moved everything outside except the JkMount stuff. The worker is now
seen, and I'm now seeing a different error message, so that's progress.
Thanks very much for your help.
On Fri, 20 Apr 2007, Mladen Turk wrote:
Faheem Mitha wrote:
Ok, thanks for your help. This is the portion of the log generated by
mod_jk, which I presume is what is relevant. The formatting is not optimal,
but I can try to wrap it if desired.
The server wide directives:
JkWorkersFile
On Fri, 20 Apr 2007, Rainer Jung wrote:
Please post the log parts (debug log level) which appear when starting
apache. Those are the lines that show, how mod_jk parses your
workers.properties, and which internal objects it generates out of it.
Hi Rainer,
Ok, thanks for your help. This is t
which made it look like it
was commented. Anyway, it is definitely uncommented now, but the error
persists.
Faheem Mitha wrote:
wc_get_worker_for_name::jk_worker.c (111): did not find a worker
ajp13_worker
This means that the ajp13_worker is not listed in worker.list=
Could it be anything
On Thu, 19 Apr 2007, Rainer Jung wrote:
Debugging: via JkLogLevel debug, try to check, if your configured objects
appear in the debug log and of course you are free to post the log.
Hi Rainer,
Thanks for your message.
The relevant output from /var/log/apache2/mod_jk.log is appended below:
. Any other ideas about this? Debugging
strategies?
Thanks. Faheem.
Faheem Mitha wrote:
Hi,
I'm trying to set up Apache to talk to Tomcat using the mod_jk connector.
However, I get the following error in the log, /var/log/apache2/
Hi,
I'm trying to set up Apache to talk to Tomcat using the mod_jk connector.
However, I get the following error in the log, /var/log/apache2/mod_jk.log
jk_handler::mod_jk.c (1986): Could not find a worker for worker
name=ajp13_worker
Apparently it cannot find the definition (or whatever) fo
On Tue, 17 Apr 2007, Faheem Mitha wrote:
On Tue, 17 Apr 2007, Faheem Mitha wrote:
On Tue, 17 Apr 2007, David Smith wrote:
Ahhh the joy of *nix operating systems. Way back in the distant past of
unix systems, someone decided it was a bad idea to allow any user on the
system to bind to
On Tue, 17 Apr 2007, Faheem Mitha wrote:
On Tue, 17 Apr 2007, David Smith wrote:
Ahhh the joy of *nix operating systems. Way back in the distant past of
unix systems, someone decided it was a bad idea to allow any user on the
system to bind to the well known low ports (1 - 1024) where
On Tue, 17 Apr 2007, Paul Singleton wrote:
David Smith wrote:
Ahhh the joy of *nix operating systems. Way back in the distant past of
unix systems, someone decided it was a bad idea to allow any user on the
system to bind to the well known low ports (1 - 1024) where officially
sanctioned s
On Tue, 17 Apr 2007, David Smith wrote:
Ahhh the joy of *nix operating systems. Way back in the distant past of unix
systems, someone decided it was a bad idea to allow any user on the system to
bind to the well known low ports (1 - 1024) where officially sanctioned
services (POP, SMTP, FTP
On Tue, 17 Apr 2007, Erik Melkersson wrote:
Are you starting it as non-root? Only root has the ability to bind to
ports <1024.
I expect this is the problem. The process is running as user tomcat5.5.
Faheem.
---
Hi,
I can now get tomcat to run an ssl connector at port 8443 (Debian
default), but doesn't work if I try to run it at 443.
The log says:
Apr 17, 2007 12:31:19 AM org.apache.catalina.startup.Catalina start
SEVERE: Catalina.start:
LifecycleException: service.getName(): "Catalina"; Protocol
On Mon, 16 Apr 2007, David Smith wrote:
If you add the address attribute to your tomcat connectors in server.xml,
tomcat will bind specifically to those interfaces. See
http://tomcat.apache.org/tomcat-5.5-doc/config/http.html for documentation on
this.
--David
Hi,
Thanks to David and o
Hello everyone,
I have a machine on which I want to run both apache (2.2) and tomcat (5.5)
simultaneously and independently, both at port 443.
To be more precise, say I have a machine with the two IP names
foo.org and bar.org
Then I want to run apache at foo.org:443, and tomcat at bar.org:4
15 matches
Mail list logo
