iliar with the native apr connector
have any suggestions? Thanks.
,
Josh.
-Original Message-
From: Martin Gainty [mailto:[EMAIL PROTECTED]
Sent: Thursday, May 25, 2006 5:15 PM
To: Tomcat Users List
Subject: Re: Native connector startup problem
Looks more like AJP port is bound ..grep thru htt
inty [mailto:[EMAIL PROTECTED]
> Sent: Friday, May 26, 2006 8:26 AM
> To: Tomcat Users List
> Subject: Re: Native connector startup problem
>
> Good Morning Josh-
> You asked Yoav Shapira (from Apache) on a very similar topic
> and he provided a suggestion last November I woul
message without making a copy. Thank you.
- Original Message -
From: "Fenlason, Josh" <[EMAIL PROTECTED]>
To: "Tomcat Users List" ; "Martin Gainty" <[EMAIL
PROTECTED]>
Sent: Friday, May 26, 2006 9:04 AM
Subject: RE: Native connector startup problem
ng is the shutdown port and the ajp
port. I know that nothing else is using those ports. Thanks.
,
Josh.
> -Original Message-
> From: Marc Farrow [mailto:[EMAIL PROTECTED]
> Sent: Friday, May 26, 2006 8:08 AM
> To: Tomcat Users List
> Subject: Re: Native connector startup pr
se ports. Thanks.
,
Josh.
> -Original Message-
> From: Marc Farrow [mailto:[EMAIL PROTECTED]
> Sent: Friday, May 26, 2006 8:08 AM
> To: Tomcat Users List
> Subject: Re: Native connector startup problem
>
> I am making a blind stab in the dark here, but it seems as
> th
sday, May 25, 2006 5:15 PM
> To: Tomcat Users List
> Subject: Re: Native connector startup problem
>
> Looks more like AJP port is bound ..grep thru http*.conf ,
> find the AJPPort specifier (usually 8009) then netstat -a |
> grep ThatPort (then go after the process id) If that doesn
---
> From: Martin Gainty [mailto:[EMAIL PROTECTED]
> Sent: Thursday, May 25, 2006 5:15 PM
> To: Tomcat Users List
> Subject: Re: Native connector startup problem
>
> Looks more like AJP port is bound ..grep thru http*.conf ,
> find the AJPPort specifier (usually 8009) then ne
Looks more like AJP port is bound ..grep thru http*.conf , find the AJPPort
specifier (usually 8009) then
netstat -a | grep ThatPort
(then go after the process id)
If that doesnt solve it shutdown Tomcat/ shutdown Apache, and start Apache /
start Tomcat
If that doesnt solve it you may have to
