Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <tomcat-user@jakarta.apache.org>
Message-Id: <5.2.1.1.0.20030720201756.00b25758@imap.web.de>
Date: Sun, 20 Jul 2003 20:18:38 +0200
To: "Tomcat Users List" <tomcat-user@jakarta.apache.org>
From: Simon Pabst <simon.pabst@web.de>
Subject: Re: mod_jk.conf-auto or /auto/mod_jk.conf (J. Turner)?
In-Reply-To: <3F1AB208.3A70E15D@Trendsetter.de>
References: <5.2.1.1.0.20030720153450.00b25780@imap.web.de>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
Content-Transfer-Encoding: quoted-printable
Sender: Simon.Pabst@web.de

Seems like your JkMount isn't working, since the error comes from Apache,
what does the auto generated mod_jk.conf look like?

At 17:15 20.07.2003 +0200, you wrote:
>Simon Pabst schrieb:
>
> > Coyote is not synonym for jk2, its just the new Tomcat Connector name,
> >
> > which you can use for HTTP (as in your case on port 8180),
> > and AJP13 connections for both mod_jk 1 and 2 (on 8009 with
> > protocolHandlerClassName=3D"org.apache.jk.server.JkCoyoteHandler").
> >
> > See=
 http://jakarta.apache.org/tomcat/tomcat-4.1-doc/config/connectors.html
> > for a list.
> >
> > So everything should be all right.
>
>Hi,
>
>2 listener elements in the server.xml were reversed. After correcting this=
 the
>auto-config (mod_jk.conf) is generated.
>
>NOW the mod_jk.conf is generated automatically under
>/usr/local/jakarta-tomcat4.1/conf/auto like you describe.
>
>"catalina.out" shows following:
>
>[INFO] Registry - -Loading registry information
>[INFO] Registry - -Creating new Registry instance
>[INFO] Registry - -Creating MBeanServer
>[INFO] Http11Protocol - -Initializing Coyote HTTP/1.1 on port 8180
>Starting service Tomcat-Standalone
>Apache Tomcat/4.1.24
>[INFO] Http11Protocol - -Starting Coyote HTTP/1.1 on port 8180
>[INFO] ChannelSocket - -JK2: ajp13 listening on 0.0.0.0/0.0.0.0:8009
>[INFO] JkMain - -Jk running ID=3D0 time=3D1/80
>config=3D/usr/local/jakarta-tomcat4.1/conf/jk2.properties
>
>So obviously jk seems to be initialized - I hope (Jk running ...)!
>
>Unfortunately restarting the apache server to make him include the=20
>mod_jk.conf does
>not result in being able to access the
>servlets now via port 80.
>Port 8180 access (www.MyDomain.com:8180/examples/servlets) does still work.
>
>Apache=B4s error.log shows following when I try to access
>www.MyDomain.com:80/examples/servlets
>
>[Sun Jul 20 14:38:08 2003] [notice] caught SIGTERM, shutting down
>[Sun Jul 20 14:38:09 2003] [notice] Apache/1.3.27 OpenSSL/0.9.7 (Unix)=20
>mod_jk/1.2.3
>configured -- resuming normal operations
>[Sun Jul 20 14:38:09 2003] [notice] suEXEC mechanism enabled (wrapper:
>/usr/local/apache/bin/suexec)
>[Sun Jul 20 14:38:09 2003] [notice] Accept mutex: flock (Default: flock)
>[Sun Jul 20 14:38:23 2003] [error] [client 200.234.162.51] File does not=20
>exist:
>/usr/local/apache/htdocs/examples/servlets/
>
>"mod_jk.log" is created under /tomcat/logs - but it is empty.
>
>Does anyone have a further hint or idea why I still cannot access the=20
>servlets via
>port 80?
>
>Thanks and regards
>
>Volker
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: tomcat-user-help@jakarta.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org