mod_jk Error ...

[Stephane Plante]

Hi,

I came across this error in "mod_jk.log":

[jk_ajp13_worker.c (228)]: connection_tcp_get_message: Error -
jk_tcp_socket_recvfull failed


Can anyone tell me what this means?

There is a bug posted for this error but there doesn't seem to be a fix yet.
Here's the link: http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10487

Thanks,

Stephane


--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

mod_jk error

[Will Glass-Husain]

Hi,
 
I'm using mod_jk 
with Apache 1.3 and Tomcat 3.2.1.
 
My httpd.conf 
includes the auto generated mod_jk config file.  I believe I'm using ajp13 
protocol.  But my mod_jk.log file keeps filling up with this 
message:
 
   
[jk_ajp12_worker.c (596)]: ajpv12_handle_response, error writing back to 
server




Incidentally, the 
behavior of the server seems fine.  Should I be worried about this error 
message?
Thanks, 
WILL
_Forio 
Business SimulationsWill Glass-Husain(415) 440-7500 phone(415) 
235-4293 mobile
[EMAIL PROTECTED]www.forio.com
 

mod_jk error

[Jason Koeninger]

Anyone had any experience with this one?

[Fri Jul 06 14:53:19 2001]  [jk_ajp12_worker.c (522)]: 
ajpv12_handle_response, no value supplied

I have an application that's working fine in most cases, 
but I get Apache errors in the browser with this in my 
mod_jk log when something goes wrong.

Apache 1.3.19, Tomcat 3.3m3

Thanks,

Jason Koeninger
J&J Computer Consulting
http://www.jjcc.com

Mod_jk error

[Lakshminarayanan Ramakrishnan]

Title: Mod_jk error






Hi 


This is what is available in mod_kk error log when i start Apache with tomcat every time


[jk_connect.c (143)]: jk_open_socket, connect() failed errno = 61

[jk_ajp12_worker.c (152)]: In jk_endpoint_t::service, Error sd = -1


What does this mean?


Pls Help


Thanx


Lax

Mod_jk error

[Simmons, Donald]

I am getting an error message when starting apache - No such file or directory: Error 
while opening the workers
The message is being issued from mod_jk.so. Has anyone seen this problem and if so 
what is the resolution. I am running Apache and Tomcat on Red Hat 6.2 LINUX. Thanks 
much.

dj

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

mod_jk error

[Adam Denenberg]

I have been digging everywhere and can not find the answer to this error
that I am getting.

 Has anyone seen this error, and resolved it, or found the root of its
cause?

 [Fri Feb 28 21:13:27 2003]  [jk_worker.c (136)]: wc_get_worker_for_name,
done did not found a worker

Thanks
Adam


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Mod_JK error

[BATCHELOR, SCOTT \(CONTRACTOR\)]

Can anyone give me an idea of what might be causing this?  I have searched the 
web to no avail.

[jk_ajp_common.c (1250)]: Tomcat is down or network problems. No response has 
been sent to the client (yet)
[Tue Jun 07 13:46:09 2005]  [jk_ajp_common.c (1449)]: ERROR: Receiving from 
tomcat failed, recoverable operation. err=0
[Tue Jun 07 13:46:09 2005]  [jk_ajp_common.c (783)]: ERROR: can't receive the 
response message from tomcat, network problems or tomcat is down (some 
IP:8012), err=-131

Thanks,

SB

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: mod_jk error

[Carsten Burstedde]

Hi Nicholas,

> I have always assumed these error messages were caused by
> the browser closing the connection -- generally because the
> user has clicked on something else or pressed STOP.
> (Of course, a double-click can exhibit the same way.)
> 
> The servlet doesn't know that the user is no longer listening,
> so when it tries to write the response to a closed connection,
> it get's an error.  

thanks for the answer... so nothing serious (no bugs in mod_jk) :) . 
What about buggy browsers needing a workaround in httpd.conf or similar? 
Are the following directives sufficient?

httpd.conf (SSL virtual host):
   SetEnvIf User-Agent ".*MSIE.*" \
   nokeepalive ssl-unclean-shutdown \
   downgrade-1.0 force-response-1.0

Greetings,

Carsten


--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

magic mod_jk error

[Billingham, Walter 475]

Hey,  I get this error when trying to start apache 2 on my box I have Tomcat
4.0.2 and Apache 2.0.39 installed on a AIX 5.1L box.  Apache is in
/webserver and Tomcat /Jakarta is in /webserver/jakarta-tomcat-4.0.2, I did
not compile this copy of mod_jk.so, so does anyone know what this means?
Thanks. Trask.



--
CONFIDENTIALITY NOTICE: If you have received this e-mail in error, please immediately 
notify the sender by e-mail at the address shown.  This e-mail transmission may 
contain confidential information.  This information is intended only for the use of 
the individual(s) or entity to whom it is intended even if addressed incorrectly.  
Please delete it from your files if you are not the intended recipient.  Thank you for 
your compliance. Copyright (c) 2002 CIGNA




--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

RE: Mod_jk error

[BENARD Christophe, DDE 34/SG]

Have a look at this line in your workers.properties file

# workers.tomcat_home should point to the location where you
# installed tomcat. This is where you have your conf, webapps and lib
# directories.
#
workers.tomcat_home=/usr/local/tomcat-3.2.1

# example for win* :
#workers.tomcat_home=D:\Tomcat-3.2.1

-Message d'origine-
De: Simmons, Donald [mailto:[EMAIL PROTECTED]]
Date: mercredi 7 mars 2001 15:14
À: [EMAIL PROTECTED]
Objet: Mod_jk error


I am getting an error message when starting apache - No such file or
directory: Error while opening the workers
The message is being issued from mod_jk.so. Has anyone seen this problem and
if so what is the resolution. I am running Apache and Tomcat on Red Hat 6.2
LINUX. Thanks much.

dj

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

RE: Mod_jk error

[Simmons, Donald]

The workers.properties files appears to be correct. I may have to modify the source of 
the mod_jk file and recompile to find out what file it is looking for. A more 
descriptive message would help. Any other suggestions. thanks!!

dj



-Original Message-
From: BENARD Christophe, DDE 34/SG
[mailto:[EMAIL PROTECTED]]
Sent: Wednesday, March 07, 2001 8:19 AM
To: '[EMAIL PROTECTED]'
Subject: RE: Mod_jk error


Have a look at this line in your workers.properties file

# workers.tomcat_home should point to the location where you
# installed tomcat. This is where you have your conf, webapps and lib
# directories.
#
workers.tomcat_home=/usr/local/tomcat-3.2.1

# example for win* :
#workers.tomcat_home=D:\Tomcat-3.2.1

-Message d'origine-
De: Simmons, Donald [mailto:[EMAIL PROTECTED]]
Date: mercredi 7 mars 2001 15:14
À: [EMAIL PROTECTED]
Objet: Mod_jk error


I am getting an error message when starting apache - No such file or
directory: Error while opening the workers
The message is being issued from mod_jk.so. Has anyone seen this problem and
if so what is the resolution. I am running Apache and Tomcat on Red Hat 6.2
LINUX. Thanks much.

dj

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

RE: Mod_jk error

[greyson . smith]

When I had this problem it was caused by how my localhost was defined, so
this line:

worker.ajp12.host=localhost

was apparently causing me problems.  I fixed my localhost, and the error
has gone away.



   
  
"Simmons,  
  
Donald"  To: [EMAIL PROTECTED]
  
  Subject: RE: Mod_jk error 
  
   
  
07-03-01   
  
07:33 AM   
  
Please 
  
respond to 
  
tomcat-user
  
   
  
   
  





The workers.properties files appears to be correct. I may have to modify
the source of the mod_jk file and recompile to find out what file it is
looking for. A more descriptive message would help. Any other suggestions.
thanks!!

dj




--

NOTICE:  The information contained in this electronic mail transmission is
intended by Convergys Corporation for the use of the named individual or
entity to which it is directed and may contain information that is
privileged or otherwise confidential.  If you have received this electronic
mail transmission in error, please delete it from your system without
copying or forwarding it, and notify the sender of the error by reply email
or by telephone (collect), so that the sender's address records can be
corrected.



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

RE: Mod_jk error

[Simmons, Donald]

Greyson,

I went in and modified the mod_jk.c code to spit out some values when this error is 
generated. It appears that it is looking for some log file. I thought it might be 
mod_jk.log, but that exists and in the correct location. There are 3 possible errors 
that generate this error condition, conf->log file not existing (is there another log 
file somewhere), conf->workersproperties file which exists, and an error allocating 
memory for the initialization map. When I print out the error messages the conf->log 
file is null which generates the error. Is there a configuration log file that I might 
be missing?

dj



-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, March 07, 2001 11:42 AM
To: [EMAIL PROTECTED]
Subject: RE: Mod_jk error



When I had this problem it was caused by how my localhost was defined, so
this line:

worker.ajp12.host=localhost

was apparently causing me problems.  I fixed my localhost, and the error
has gone away.



   
  
"Simmons,  
  
Donald"  To: [EMAIL PROTECTED]
  
  Subject:     RE: Mod_jk error 
  
   
  
07-03-01   
  
07:33 AM   
  
Please 
  
respond to 
  
tomcat-user
  
   
  
   
  





The workers.properties files appears to be correct. I may have to modify
the source of the mod_jk file and recompile to find out what file it is
looking for. A more descriptive message would help. Any other suggestions.
thanks!!

dj




--

NOTICE:  The information contained in this electronic mail transmission is
intended by Convergys Corporation for the use of the named individual or
entity to which it is directed and may contain information that is
privileged or otherwise confidential.  If you have received this electronic
mail transmission in error, please delete it from your system without
copying or forwarding it, and notify the sender of the error by reply email
or by telephone (collect), so that the sender's address records can be
corrected.



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

RE: mod_jk error

[Turner, John]

Try deleting the "lbfactor" line from your workers.properties file.  It's
not necessary when you only have one worker defined, and it may be causing
confusion to mod_jk.so.

John


> -Original Message-
> From: Adam Denenberg [mailto:[EMAIL PROTECTED]
> Sent: Saturday, March 01, 2003 8:36 PM
> To: [EMAIL PROTECTED]
> Subject: mod_jk error
> 
> 
> I have been digging everywhere and can not find the answer to 
> this error
> that I am getting.
> 
>  Has anyone seen this error, and resolved it, or found the root of its
> cause?
> 
>  [Fri Feb 28 21:13:27 2003]  [jk_worker.c (136)]: 
> wc_get_worker_for_name,
> done did not found a worker
> 
> Thanks
> Adam
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: mod_jk error

[Adam Denenberg]

Hmm, tried that but still no luck.

 I still get the following

 [Mon Mar 03 08:16:00 2003]  [jk_uri_worker_map.c (477)]: Attempting to map
URI '/examples/jsp/dates/date.jsp'

 [Mon Mar 03 08:16:00 2003]  [jk_uri_worker_map.c (558)]:
jk_uri_worker_map_t::map_uri_to_worker, Found a suffix match ajp13 -> *.jsp

[Mon Mar 03 08:16:00 2003]  [jk_worker.c (132)]: Into wc_get_worker_for_name
ajp13

[Mon Mar 03 08:16:00 2003]  [jk_worker.c (136)]: wc_get_worker_for_name,
done did not found a worker

Using a very simple workers.properties file.

worker.list=ajp13
worker.ajp13.port=8009
worker.ajp13.host=localhost
worker.ajp13.type=ajp13

  any other suggestions?  I am totally out of ideas as to what is causing
this error..
 
 thanks
Adam


On 3/3/03 8:06 AM, "Turner, John" <[EMAIL PROTECTED]> wrote:

> 
> Try deleting the "lbfactor" line from your workers.properties file.  It's
> not necessary when you only have one worker defined, and it may be causing
> confusion to mod_jk.so.
> 
> John
> 
> 
>> -Original Message-
>> From: Adam Denenberg [mailto:[EMAIL PROTECTED]
>> Sent: Saturday, March 01, 2003 8:36 PM
>> To: [EMAIL PROTECTED]
>> Subject: mod_jk error
>> 
>> 
>> I have been digging everywhere and can not find the answer to
>> this error
>> that I am getting.
>> 
>>  Has anyone seen this error, and resolved it, or found the root of its
>> cause?
>> 
>>  [Fri Feb 28 21:13:27 2003]  [jk_worker.c (136)]:
>> wc_get_worker_for_name,
>> done did not found a worker
>> 
>> Thanks
>> Adam
>> 
>> 
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: mod_jk error

[Turner, John]

No other ideas, really.  In the past, problems like this have come down to
something really simple, such as using an el ("l") instead of a one ("1") in
"ajp13" and other typo-related problems (or permission problems).  My
eyesight isn't as good as it used to be, but it looks like you have "ajp13"
typed out correctly in all the places where it needs to be.

John

> -Original Message-
> From: Adam Denenberg [mailto:[EMAIL PROTECTED]
> Sent: Monday, March 03, 2003 8:24 AM
> To: Tomcat Users List
> Subject: Re: mod_jk error
> 
> 
> Hmm, tried that but still no luck.
> 
>  I still get the following
> 
>  [Mon Mar 03 08:16:00 2003]  [jk_uri_worker_map.c (477)]: 
> Attempting to map
> URI '/examples/jsp/dates/date.jsp'
> 
>  [Mon Mar 03 08:16:00 2003]  [jk_uri_worker_map.c (558)]:
> jk_uri_worker_map_t::map_uri_to_worker, Found a suffix match 
> ajp13 -> *.jsp
> 
> [Mon Mar 03 08:16:00 2003]  [jk_worker.c (132)]: Into 
> wc_get_worker_for_name
> ajp13
> 
> [Mon Mar 03 08:16:00 2003]  [jk_worker.c (136)]: 
> wc_get_worker_for_name,
> done did not found a worker
> 
> Using a very simple workers.properties file.
> 
> worker.list=ajp13
> worker.ajp13.port=8009
> worker.ajp13.host=localhost
> worker.ajp13.type=ajp13
> 
>   any other suggestions?  I am totally out of ideas as to 
> what is causing
> this error..
>  
>  thanks
> Adam
> 
> 
> On 3/3/03 8:06 AM, "Turner, John" <[EMAIL PROTECTED]> wrote:
> 
> > 
> > Try deleting the "lbfactor" line from your 
> workers.properties file.  It's
> > not necessary when you only have one worker defined, and it 
> may be causing
> > confusion to mod_jk.so.
> > 
> > John
> > 
> > 
> >> -Original Message-
> >> From: Adam Denenberg [mailto:[EMAIL PROTECTED]
> >> Sent: Saturday, March 01, 2003 8:36 PM
> >> To: [EMAIL PROTECTED]
> >> Subject: mod_jk error
> >> 
> >> 
> >> I have been digging everywhere and can not find the answer to
> >> this error
> >> that I am getting.
> >> 
> >>  Has anyone seen this error, and resolved it, or found the 
> root of its
> >> cause?
> >> 
> >>  [Fri Feb 28 21:13:27 2003]  [jk_worker.c (136)]:
> >> wc_get_worker_for_name,
> >> done did not found a worker
> >> 
> >> Thanks
> >> Adam
> >> 
> >> 
> >> 
> -
> >> To unsubscribe, e-mail: [EMAIL PROTECTED]
> >> For additional commands, e-mail: 
> [EMAIL PROTECTED]
> >> 
> > 
> > 
> -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> > 
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: mod_jk error

[Adam Denenberg]

Thanks john.  Does this error come from a problem in the workers.properties
file, or an entry in the httpd.conf do you know?

 It seems that mod_jk finds the match fine in the httpd.conf file, but then
when tries to use a worker it for some reason can not.  I have debug on but
am missing the piece that it is specifically dying on.

 thanks again for the help.

Adam

On 3/3/03 8:50 AM, "Turner, John" <[EMAIL PROTECTED]> wrote:

> 
> No other ideas, really.  In the past, problems like this have come down to
> something really simple, such as using an el ("l") instead of a one ("1") in
> "ajp13" and other typo-related problems (or permission problems).  My
> eyesight isn't as good as it used to be, but it looks like you have "ajp13"
> typed out correctly in all the places where it needs to be.
> 
> John
> 
>> -Original Message-
>> From: Adam Denenberg [mailto:[EMAIL PROTECTED]
>> Sent: Monday, March 03, 2003 8:24 AM
>> To: Tomcat Users List
>> Subject: Re: mod_jk error
>> 
>> 
>> Hmm, tried that but still no luck.
>> 
>>  I still get the following
>> 
>>  [Mon Mar 03 08:16:00 2003]  [jk_uri_worker_map.c (477)]:
>> Attempting to map
>> URI '/examples/jsp/dates/date.jsp'
>> 
>>  [Mon Mar 03 08:16:00 2003]  [jk_uri_worker_map.c (558)]:
>> jk_uri_worker_map_t::map_uri_to_worker, Found a suffix match
>> ajp13 -> *.jsp
>> 
>> [Mon Mar 03 08:16:00 2003]  [jk_worker.c (132)]: Into
>> wc_get_worker_for_name
>> ajp13
>> 
>> [Mon Mar 03 08:16:00 2003]  [jk_worker.c (136)]:
>> wc_get_worker_for_name,
>> done did not found a worker
>> 
>> Using a very simple workers.properties file.
>> 
>> worker.list=ajp13
>> worker.ajp13.port=8009
>> worker.ajp13.host=localhost
>> worker.ajp13.type=ajp13
>> 
>>   any other suggestions?  I am totally out of ideas as to
>> what is causing
>> this error..
>>  
>>  thanks
>> Adam
>> 
>> 
>> On 3/3/03 8:06 AM, "Turner, John" <[EMAIL PROTECTED]> wrote:
>> 
>>> 
>>> Try deleting the "lbfactor" line from your
>> workers.properties file.  It's
>>> not necessary when you only have one worker defined, and it
>> may be causing
>>> confusion to mod_jk.so.
>>> 
>>> John
>>> 
>>> 
>>>> -Original Message-
>>>> From: Adam Denenberg [mailto:[EMAIL PROTECTED]
>>>> Sent: Saturday, March 01, 2003 8:36 PM
>>>> To: [EMAIL PROTECTED]
>>>> Subject: mod_jk error
>>>> 
>>>> 
>>>> I have been digging everywhere and can not find the answer to
>>>> this error
>>>> that I am getting.
>>>> 
>>>>  Has anyone seen this error, and resolved it, or found the
>> root of its
>>>> cause?
>>>> 
>>>>  [Fri Feb 28 21:13:27 2003]  [jk_worker.c (136)]:
>>>> wc_get_worker_for_name,
>>>> done did not found a worker
>>>> 
>>>> Thanks
>>>> Adam
>>>> 
>>>> 
>>>> 
>> -
>>>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>>>> For additional commands, e-mail:
>> [EMAIL PROTECTED]
>>>> 
>>> 
>>> 
>> -
>>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>>> For additional commands, e-mail: [EMAIL PROTECTED]
>>> 
>> 
>> 
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Strange mod_jk error

[Denise Mangano]

Hi all.  

I have not posted in some time as thanks to some great help from this list
my application was running smoothly.  However, I needed to make some
configuration changes, and now my apps stopped working.  Apache (1.3.23)
runs fine, and Tomcat (4.1.17) runs fine but the problem is with mod_jk.

I tried searching the archives for this one but had no luck.  The error I am
getting in my mod_jk.log is:

In jk_endpoint_t::service, Error sd = -1

And of course the error I am getting in my apache error log shows that it is
looking for the file in the apache web directory.  So it appears that mod_jk
is not working and the request is never being interpreted by the JkMount
statements.

Does anyone have any idea what this means?  I even tried restoring the
original server.xml file, but I still received the error.  I can post
server.xml, httpd.conf, etc if you need to see it, but I thought first I
would send out the error message.

Thanks for your help!

Denise Mangano
Help Desk Analyst
Complus Data Innovations, Inc.
 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

mod_jk: Error flushing

[Javier Ayllon]

Hi friends:

A few days ago I upgraded to Tomcat 4.1.24 with mod_jk 1.2.3 and apache
2.0.46. Averything seems to work right (in fact really fast). Just a
little detail disturbs my internal peace ;-)
In error_log I see every now and then the message "mod_jk: Error
flushing" but nothing else (apparently) happens. Any ideas?

Thanks in advance.

-- 
Javier Ayllon <[EMAIL PROTECTED]>
Universidad de Castilla La Mancha



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

building mod_jk error

[george]

when i building the mod_jk,there have some error msg

www# apxs -o
mod_jk.so -I../jk -I/usr/local/jdk1.2.2/include -I/usr/local/jdk1.2
.2/include/linux -c *.c ../jk/*.c
apxs:Error: Sorry, no DSO support for Apache available
apxs:Error: under your platform. Make sure the Apache
apxs:Error: module mod_so is compiled into your server
apxs:Error: binary `/usr/local/apache/bin/httpd'.

so,what's the problem


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

mod_jk error flushing ...

[Clara Ines Pena de Carrillo]

Hi everybody, 

I have installed tomcat 4.1.24, apache 2.0.47, jdk 1.4.2 and 
mod_jk2-2.0.43 in a Sun Solaris 8 machine. Everything have worked more or 
less ok since today that the system crashed !!!. I got the 
following 
error messages in the apache error_log file:


[Thu Nov 04 08:32:56 2004] [error] mod_jk child init 1 -2
[Thu Nov 04 08:34:00 2004] [error] jk2_init() Can't find child 1407 in 
scoreboard
[Thu Nov 04 08:34:00 2004] [error] mod_jk child init 1 -2
[Thu Nov 04 08:34:39 2004] [error] jk2_init() Can't find child 1414 in 
scoreboard
[Thu Nov 04 08:34:39 2004] [error] mod_jk child init 1 -2
[Thu Nov 04 08:34:39 2004] [error] jk2_init() Can't find child 1416 in 
scoreboard
[Thu Nov 04 08:34:39 2004] [error] mod_jk child init 1 -2
mod_jk: Error flushing

[Thu Nov 04 08:35:51 2004] [error] Error ajp_process_callback - write 
failed
[Thu Nov 04 08:35:51 2004] [error] ajp13.service() ajpGetReply recoverable 
error 3
[Thu Nov 04 08:35:51 2004] [error] Error ajp_process_callback - write 
failed
[Thu Nov 04 08:35:51 2004] [error] ajp13.service() ajpGetReply recoverable 
error 3
[Thu Nov 04 08:35:51 2004] [error] ajp13.service() Error  forwarding 
ajp13:localhost:8009 1 0

[Thu Nov 04 08:47:31 2004] [error] mod_jk.handler() Error connecting to 
tomcat 3


do you have any idea about why these errors are appearing ?


I would appreciate your help,


Clara



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

mod_jk Error Flushing

[Paolo Lai]

Hi,
I've this problem.
I've installed, in a win2000 server, Apache 2.0.53,
tomcat 4.1.31 and
mod_jk 1.2.10.
When Apache service stars it display :

Apache/2.0.53 (Win32) mod_ssl/2.0.53 OpenSSL/0.9.7e
mod_jk/1.2.10
configured -- resuming normal operations.

My servlet is functionally properly but, sometimes, in
the error.log of
apache2 directory i've a lot of "mod_jk: Error
flushing" error.
What does thios error means?
Thank's for your attention
Best regard




__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Mod_JK error

[BATCHELOR, SCOTT \(CONTRACTOR\)]

My apologies...

I should have added that I only get this error when the server comes under load 
and even then the errors are intermittent.

-SB

-Original Message-
From: BATCHELOR, SCOTT (CONTRACTOR) [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 07, 2005 2:12 PM
To: Tomcat User List (E-mail)
Subject: Mod_JK error


Can anyone give me an idea of what might be causing this?  I have searched the 
web to no avail.

[jk_ajp_common.c (1250)]: Tomcat is down or network problems. No response has 
been sent to the client (yet)
[Tue Jun 07 13:46:09 2005]  [jk_ajp_common.c (1449)]: ERROR: Receiving from 
tomcat failed, recoverable operation. err=0
[Tue Jun 07 13:46:09 2005]  [jk_ajp_common.c (783)]: ERROR: can't receive the 
response message from tomcat, network problems or tomcat is down (some 
IP:8012), err=-131

Thanks,

SB

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

mod_jk error under load

[David Ward]

In running an automated load test against our app, we get the following 
errors in or jk.log file:

[jk_connect.c (143)]: jk_open_socket, connect() failed errno = 146
[jk_ajp12_worker.c (152)]: In jk_endpoint_t::service, Error sd = -1
[jk_connect.c (143)]: jk_open_socket, connect() failed errno = 146
[jk_ajp12_worker.c (152)]: In jk_endpoint_t::service, Error sd = -1
[jk_connect.c (143)]: jk_open_socket, connect() failed errno = 146
[jk_ajp12_worker.c (152)]: In jk_endpoint_t::service, Error sd = -1
[jk_connect.c (143)]: jk_open_socket, connect() failed errno = 146
[jk_ajp12_worker.c (152)]: In jk_endpoint_t::service, Error sd = -1
[jk_connect.c (143)]: jk_open_socket, connect() failed errno = 146
[jk_ajp12_worker.c (152)]: In jk_endpoint_t::service, Error sd = -1
[jk_connect.c (143)]: jk_open_socket, connect() failed errno = 146

Anyone know what these errors are? I can't find anything conclusive 
about them searching various lists/forums.

We are running Apache 1.3.12 on a Solaris 7 Ultra 10 using mod_jk/ajp12 
to talk to JBoss-2.4.7_Tomcat-3.2.3 on a Solaris 7 E250, JDK 1.3.1_02.

The symptoms we see are that the number of httpd processes maxes out on 
the web server box, though the CPU is almost completely idle. The weird 
thing is that the app server is mostly idle too, and doing a thread dump 
on the java (jboss+tomcat in same vm) process shows that there are lots 
of threads waiting for work to do. Once we stop the load test, things 
are still messed up until I restart apache, then we can access the app 
again. Note that I didn't have to touch the app server at all. Accessing 
URLs that aren't configured to go through mod_jk have no problem, until 
the max http children process gets reached, of course...

I haven't gotten a response from the Tomcat forum at JGuru.

Thanks all,
David


--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

RE: magic mod_jk error

[Billingham, Walter 475]

> -Original Message-
> From: Billingham, Walter  475 [SMTP:[EMAIL PROTECTED]]
> Sent: Tuesday, July 23, 2002 3:36 PM
> To:   '[EMAIL PROTECTED]'
> Subject:  magic mod_jk error
> 
> Hey,  I get this error when trying to start apache 2 on my box I have
> Tomcat
> 4.0.2 and Apache 2.0.39 installed on a AIX 5.1L box.  Apache is in
> /webserver and Tomcat /Jakarta is in /webserver/jakarta-tomcat-4.0.2, I
> did
> not compile this copy of mod_jk.so, so does anyone know what this means?
> Thanks. Trask.
> 
> 
  Dohh, here is the error:  # apachectl stop
Syntax error on line 7 of
/webserver/jakarta-tomcat-4.0.2/conf/mod_jk.conf:
Cannot load /webserver/modules/mod_jk.so into server:   0509-022
Cannot load module /webserver/modules/mod_jk.so.
0509-103   The module has an invalid magic number.
[wdc4002a(root): /webserver/bin] 
>  

--
CONFIDENTIALITY NOTICE: If you have received this e-mail in error, please immediately 
notify the sender by e-mail at the address shown.  This e-mail transmission may 
contain confidential information.  This information is intended only for the use of 
the individual(s) or entity to whom it is intended even if addressed incorrectly.  
Please delete it from your files if you are not the intended recipient.  Thank you for 
your compliance. Copyright (c) 2002 CIGNA




--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

RE: magic mod_jk error

[Billingham, Walter 475]

]  Someone tell me what is a magic number anyway? 

> > -Original Message-
> > From:   Billingham, Walter  475
> [SMTP:[EMAIL PROTECTED]]
> > Sent:   Tuesday, July 23, 2002 3:36 PM
> > To: '[EMAIL PROTECTED]'
> > Subject:magic mod_jk error
> > 
> > Hey,  I get this error when trying to start apache 2 on my box I have
> > Tomcat
> > 4.0.2 and Apache 2.0.39 installed on a AIX 5.1L box.  Apache is in
> > /webserver and Tomcat /Jakarta is in /webserver/jakarta-tomcat-4.0.2, I
> > did
> > not compile this copy of mod_jk.so, so does anyone know what this means?
> > Thanks. Trask.
> > 
> > 
> Dohh, here is the error:  # apachectl stop
>   Syntax error on line 7 of
> /webserver/jakarta-tomcat-4.0.2/conf/mod_jk.conf:
>   Cannot load /webserver/modules/mod_jk.so into server:   0509-022
> Cannot load module /webserver/modules/mod_jk.so.
>   0509-103   The module has an invalid magic number.
>   [wdc4002a(root): /webserver/bin] 
> >  
> 

--
CONFIDENTIALITY NOTICE: If you have received this e-mail in error, please immediately 
notify the sender by e-mail at the address shown.  This e-mail transmission may 
contain confidential information.  This information is intended only for the use of 
the individual(s) or entity to whom it is intended even if addressed incorrectly.  
Please delete it from your files if you are not the intended recipient.  Thank you for 
your compliance. Copyright (c) 2002 CIGNA




--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Re: magic mod_jk error

[Chris McCabe]

The magic number is the way the operating system identifies the type of 
file.  It takes a look into the file to find something that identifies 
it as the right type of file before it blinding tries to load it and run it.
Since it is a compiled executable library, your system is telling you 
that it is not a valid library file for your OS.  You are probably using 
a mod_jk.so that was compiled for  some other operating system.

Chris

Billingham, Walter 475 wrote:

>   ]  Someone tell me what is a magic number anyway? 
>
>  
>
>>>-Original Message-
>>>From:Billingham, Walter  475
>>>  
>>>
>>[SMTP:[EMAIL PROTECTED]]
>>
>>
>>>Sent:Tuesday, July 23, 2002 3:36 PM
>>>To:  '[EMAIL PROTECTED]'
>>>Subject: magic mod_jk error
>>>
>>>Hey,  I get this error when trying to start apache 2 on my box I have
>>>Tomcat
>>>4.0.2 and Apache 2.0.39 installed on a AIX 5.1L box.  Apache is in
>>>/webserver and Tomcat /Jakarta is in /webserver/jakarta-tomcat-4.0.2, I
>>>did
>>>not compile this copy of mod_jk.so, so does anyone know what this means?
>>>Thanks. Trask.
>>>
>>>
>>>  
>>>
>>Dohh, here is the error:  # apachectl stop
>>  Syntax error on line 7 of
>>/webserver/jakarta-tomcat-4.0.2/conf/mod_jk.conf:
>>  Cannot load /webserver/modules/mod_jk.so into server:   0509-022
>>Cannot load module /webserver/modules/mod_jk.so.
>>  0509-103   The module has an invalid magic number.
>>  [wdc4002a(root): /webserver/bin] 
>>
>>
>>> 
>>>  
>>>
>
>--
>CONFIDENTIALITY NOTICE: If you have received this e-mail in error, please immediately 
>notify the sender by e-mail at the address shown.  This e-mail transmission may 
>contain confidential information.  This information is intended only for the use of 
>the individual(s) or entity to whom it is intended even if addressed incorrectly.  
>Please delete it from your files if you are not the intended recipient.  Thank you 
>for your compliance. Copyright (c) 2002 CIGNA
>
>
>
>
>--
>To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
>For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
>
>
>  
>


-- 
Chris P. McCabe  - Senior Software Systems Architect
Choice Hotels International - Information Technology
[EMAIL PROTECTED]602-953-4416




--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Re: Strange mod_jk error

[John Turner]

As far as I know, that error message is socket related, as in the socket is 
closed, or Apache thinks the socket is closed when it isn't.  Its pretty 
old, from what I know, and should be fixed in recent incarnations of 
mod_jk.  Then again, you are using Apache 1.3.23, so maybe that error still 
crops up.

Verify that your workers.properties has the right port number, verify that 
it has the right host, and verify that you don't have any workers 
configured (like ajp12 or ajp14) that you don't need.

Other than that, you'll have to explain further what you mean by "some 
configuration changes".  ;)

John

On Mon, 2 Jun 2003 16:09:26 -0400, Denise Mangano <[EMAIL PROTECTED]> 
wrote:

Hi all.

I have not posted in some time as thanks to some great help from this 
list
my application was running smoothly.  However, I needed to make some
configuration changes, and now my apps stopped working.  Apache (1.3.23)
runs fine, and Tomcat (4.1.17) runs fine but the problem is with mod_jk.

I tried searching the archives for this one but had no luck.  The error I 
am
getting in my mod_jk.log is:

In jk_endpoint_t::service, Error sd = -1

And of course the error I am getting in my apache error log shows that it 
is
looking for the file in the apache web directory.  So it appears that 
mod_jk
is not working and the request is never being interpreted by the JkMount
statements.

Does anyone have any idea what this means?  I even tried restoring the
original server.xml file, but I still received the error.  I can post
server.xml, httpd.conf, etc if you need to see it, but I thought first I
would send out the error message.
Thanks for your help!

Denise Mangano
Help Desk Analyst
Complus Data Innovations, Inc.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



--
Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Strange mod_jk error

[Denise Mangano]

By "some configuration changes" I added in virtual hosting.  That error
message is gone.  I'm not exactly sure what I did to get it to 'go away' but
it did.  The problem I am having is that my worker is not being found.

I have two properties files defined.  One is workers.properties for use with
the default virtual host, and one is test.workers.properties to use with my
testing virtual host.  I tried combining each into one workers.properties
file but still get the same error message.  The suffix is matched, but when
it looks for the worker named testWorker it doesn't fin it:

[Mon Jun 02 16:16:57 2003]  [jk_worker.c (132)]: Into wc_get_worker_for_name
testWorker [Mon Jun 02 16:16:57 2003]  [jk_worker.c (136)]:
wc_get_worker_for_name, done did not found a worker

My test.workers.properties file looks like:
worker.list = testWorker
worker.testWorker.type = ajp13
worker.testWorker.host = test.mysite.com
worker.testWorker.port = 8080

My test.workers.properties file looks like:
worker.list = worker
worker.worker.type = ajp13
worker.worker.host = www.mysite.com
worker.worker.port = 8080

My server.xml, mod_jk.conf and httpd.conf both point to the appropriate
worker properties file within each virtual host.  I am in the process of
going over all my config files to see if I missed anything, but it appears
that everything is configured right.  Mod_jk is doing its job - but for some
reason it is not finding the definition of the named worker.

Any suggestion?  I can post my files if necessary.

Thanks for taking a look!
Denise

-Original Message-
From: John Turner [mailto:[EMAIL PROTECTED] 
Sent: Monday, June 02, 2003 4:10 PM
To: Tomcat Users List
Subject: Re: Strange mod_jk error



As far as I know, that error message is socket related, as in the socket is 
closed, or Apache thinks the socket is closed when it isn't.  Its pretty 
old, from what I know, and should be fixed in recent incarnations of 
mod_jk.  Then again, you are using Apache 1.3.23, so maybe that error still 
crops up.

Verify that your workers.properties has the right port number, verify that 
it has the right host, and verify that you don't have any workers 
configured (like ajp12 or ajp14) that you don't need.

Other than that, you'll have to explain further what you mean by "some 
configuration changes".  ;)

John

On Mon, 2 Jun 2003 16:09:26 -0400, Denise Mangano <[EMAIL PROTECTED]> 
wrote:

> Hi all.
>
> I have not posted in some time as thanks to some great help from this 
> list my application was running smoothly.  However, I needed to make 
> some configuration changes, and now my apps stopped working.  Apache 
> (1.3.23) runs fine, and Tomcat (4.1.17) runs fine but the problem is 
> with mod_jk.
>
> I tried searching the archives for this one but had no luck.  The
> error I
> am
> getting in my mod_jk.log is:
>
> In jk_endpoint_t::service, Error sd = -1
>
> And of course the error I am getting in my apache error log shows that
> it
> is
> looking for the file in the apache web directory.  So it appears that 
> mod_jk
> is not working and the request is never being interpreted by the JkMount
> statements.
>
> Does anyone have any idea what this means?  I even tried restoring the
> original server.xml file, but I still received the error.  I can post 
> server.xml, httpd.conf, etc if you need to see it, but I thought first 
> I would send out the error message.
>
> Thanks for your help!
>
> Denise Mangano
> Help Desk Analyst
> Complus Data Innovations, Inc.
>
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>



-- 
Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Strange mod_jk error

[Denise Mangano]

I decided to scratch having the second worker since my problems seemed to
start with that approach.  I restored everything to the original worker file
and have both default and test virtual hosts pointing to the same
workers.properties.

For some reason, mod_jk is still not working.  Its not a problem with Tomcat
itself because I can access everything on port 8080.  Apache throws an
internal server error every time I try to access a jsp without the port in
the URL.

The error in the apache error log is:
[Mon Jun  2 23:04:59 2003] [error] Error while opening the workers, jk will
not work
[Mon Jun  2 23:05:01 2003] [error] (2)No such file or directory: Error while
opening the workers, jk will not work

The error in mod_jk.log is:
[Mon Jun 02 23:01:47 2003]  [jk_uri_worker_map.c (558)]:
jk_uri_worker_map_t::map_uri_to_worker, Found a suffix match worker -> *.jsp
[Mon Jun 02 23:01:47 2003]  [jk_worker.c (132)]: Into wc_get_worker_for_name
worker
[Mon Jun 02 23:01:47 2003]  [jk_worker.c (136)]: wc_get_worker_for_name,
done did not found a worker

Content of my worker file is:
worker.list = worker
worker.worker.type = ajp13
worker.worker.host = localhost
worker.worker.port = 8009

My JkMount statements are like this: JkMount /*.jsp worker

I'd appreciate any help on this.  It has put me in a pretty serious bind,
and I can't for the life of me figure out why it won't work.

Thanks,
Denise

-Original Message-
From: Denise Mangano [mailto:[EMAIL PROTECTED] 
Sent: Monday, June 02, 2003 4:56 PM
To: 'Tomcat Users List'
Subject: RE: Strange mod_jk error


By "some configuration changes" I added in virtual hosting.  That error
message is gone.  I'm not exactly sure what I did to get it to 'go away' but
it did.  The problem I am having is that my worker is not being found.

I have two properties files defined.  One is workers.properties for use with
the default virtual host, and one is test.workers.properties to use with my
testing virtual host.  I tried combining each into one workers.properties
file but still get the same error message.  The suffix is matched, but when
it looks for the worker named testWorker it doesn't fin it:

[Mon Jun 02 16:16:57 2003]  [jk_worker.c (132)]: Into wc_get_worker_for_name
testWorker [Mon Jun 02 16:16:57 2003]  [jk_worker.c (136)]:
wc_get_worker_for_name, done did not found a worker

My test.workers.properties file looks like:
worker.list = testWorker
worker.testWorker.type = ajp13
worker.testWorker.host = test.mysite.com
worker.testWorker.port = 8080

My test.workers.properties file looks like:
worker.list = worker
worker.worker.type = ajp13
worker.worker.host = www.mysite.com
worker.worker.port = 8080

My server.xml, mod_jk.conf and httpd.conf both point to the appropriate
worker properties file within each virtual host.  I am in the process of
going over all my config files to see if I missed anything, but it appears
that everything is configured right.  Mod_jk is doing its job - but for some
reason it is not finding the definition of the named worker.

Any suggestion?  I can post my files if necessary.

Thanks for taking a look!
Denise

-Original Message-
From: John Turner [mailto:[EMAIL PROTECTED] 
Sent: Monday, June 02, 2003 4:10 PM
To: Tomcat Users List
Subject: Re: Strange mod_jk error



As far as I know, that error message is socket related, as in the socket is 
closed, or Apache thinks the socket is closed when it isn't.  Its pretty 
old, from what I know, and should be fixed in recent incarnations of 
mod_jk.  Then again, you are using Apache 1.3.23, so maybe that error still 
crops up.

Verify that your workers.properties has the right port number, verify that 
it has the right host, and verify that you don't have any workers 
configured (like ajp12 or ajp14) that you don't need.

Other than that, you'll have to explain further what you mean by "some 
configuration changes".  ;)

John

On Mon, 2 Jun 2003 16:09:26 -0400, Denise Mangano <[EMAIL PROTECTED]> 
wrote:

> Hi all.
>
> I have not posted in some time as thanks to some great help from this
> list my application was running smoothly.  However, I needed to make 
> some configuration changes, and now my apps stopped working.  Apache 
> (1.3.23) runs fine, and Tomcat (4.1.17) runs fine but the problem is 
> with mod_jk.
>
> I tried searching the archives for this one but had no luck.  The 
> error I am
> getting in my mod_jk.log is:
>
> In jk_endpoint_t::service, Error sd = -1
>
> And of course the error I am getting in my apache error log shows that 
> it is
> looking for the file in the apache web directory.  So it appears that 
> mod_jk
> is not working and the request is never being interpreted by the JkMount
> statements.
>
> Does anyone have any idea what this means?  I even tried restoring the 
> original server.xml file, but I still r

Re: Strange mod_jk error

[John Turner]

I think the problem is that, in the .properties files you posted, you have 
the port as 8080.  That's the HTTP port...the JK port is 8009.

John

On Mon, 2 Jun 2003 23:37:04 -0400, Denise Mangano <[EMAIL PROTECTED]> 
wrote:

I decided to scratch having the second worker since my problems seemed to
start with that approach.  I restored everything to the original worker 
file
and have both default and test virtual hosts pointing to the same
workers.properties.

For some reason, mod_jk is still not working.  Its not a problem with 
Tomcat
itself because I can access everything on port 8080.  Apache throws an
internal server error every time I try to access a jsp without the port 
in
the URL.

The error in the apache error log is:
[Mon Jun  2 23:04:59 2003] [error] Error while opening the workers, jk 
will
not work
[Mon Jun  2 23:05:01 2003] [error] (2)No such file or directory: Error 
while
opening the workers, jk will not work

The error in mod_jk.log is:
[Mon Jun 02 23:01:47 2003]  [jk_uri_worker_map.c (558)]:
jk_uri_worker_map_t::map_uri_to_worker, Found a suffix match worker -> 
*.jsp
[Mon Jun 02 23:01:47 2003]  [jk_worker.c (132)]: Into 
wc_get_worker_for_name
worker
[Mon Jun 02 23:01:47 2003]  [jk_worker.c (136)]: wc_get_worker_for_name,
done did not found a worker

Content of my worker file is:
worker.list = worker
worker.worker.type = ajp13
worker.worker.host = localhost
worker.worker.port = 8009
My JkMount statements are like this: JkMount /*.jsp worker

I'd appreciate any help on this.  It has put me in a pretty serious bind,
and I can't for the life of me figure out why it won't work.
Thanks,
Denise
-Original Message-
From: Denise Mangano [mailto:[EMAIL PROTECTED] Sent: Monday, June 
02, 2003 4:56 PM
To: 'Tomcat Users List'
Subject: RE: Strange mod_jk error

By "some configuration changes" I added in virtual hosting.  That error
message is gone.  I'm not exactly sure what I did to get it to 'go away' 
but
it did.  The problem I am having is that my worker is not being found.

I have two properties files defined.  One is workers.properties for use 
with
the default virtual host, and one is test.workers.properties to use with 
my
testing virtual host.  I tried combining each into one workers.properties
file but still get the same error message.  The suffix is matched, but 
when
it looks for the worker named testWorker it doesn't fin it:

[Mon Jun 02 16:16:57 2003]  [jk_worker.c (132)]: Into 
wc_get_worker_for_name
testWorker [Mon Jun 02 16:16:57 2003]  [jk_worker.c (136)]:
wc_get_worker_for_name, done did not found a worker

My test.workers.properties file looks like:
worker.list = testWorker
worker.testWorker.type = ajp13
worker.testWorker.host = test.mysite.com
worker.testWorker.port = 8080
My test.workers.properties file looks like:
worker.list = worker
worker.worker.type = ajp13
worker.worker.host = www.mysite.com
worker.worker.port = 8080
My server.xml, mod_jk.conf and httpd.conf both point to the appropriate
worker properties file within each virtual host.  I am in the process of
going over all my config files to see if I missed anything, but it 
appears
that everything is configured right.  Mod_jk is doing its job - but for 
some
reason it is not finding the definition of the named worker.

Any suggestion?  I can post my files if necessary.

Thanks for taking a look!
Denise
-Original Message-
From: John Turner [mailto:[EMAIL PROTECTED] Sent: Monday, June 
02, 2003 4:10 PM
To: Tomcat Users List
Subject: Re: Strange mod_jk error



As far as I know, that error message is socket related, as in the socket 
is closed, or Apache thinks the socket is closed when it isn't.  Its 
pretty old, from what I know, and should be fixed in recent incarnations 
of mod_jk.  Then again, you are using Apache 1.3.23, so maybe that error 
still crops up.

Verify that your workers.properties has the right port number, verify 
that it has the right host, and verify that you don't have any workers 
configured (like ajp12 or ajp14) that you don't need.

Other than that, you'll have to explain further what you mean by "some 
configuration changes".  ;)

John

On Mon, 2 Jun 2003 16:09:26 -0400, Denise Mangano 
<[EMAIL PROTECTED]> wrote:

Hi all.

I have not posted in some time as thanks to some great help from this
list my application was running smoothly.  However, I needed to make 
some configuration changes, and now my apps stopped working.  Apache 
(1.3.23) runs fine, and Tomcat (4.1.17) runs fine but the problem is 
with mod_jk.

I tried searching the archives for this one but had no luck.  The error 
I am
getting in my mod_jk.log is:

In jk_endpoint_t::service, Error sd = -1

And of course the error I am getting in my apache error log shows that 
it is
looking for the file in the apache web directory.  So it appears that 
mod_jk
is not working and the request is never being interpreted by 

RE: Strange mod_jk error

[Denise Mangano]

John,

Actually I changed it all to port 8009 after posting while I was trying to
fix the problem but I still have no luck.  As I mentioned all the paths to
the worker file are correct.  The mod_jk.log shows that the rules for
worker1 are being set.  I even restored the original server.xml, and
restarted both Tomcat and Apache, and the apache error log still shows the
error while opening the workers, jk will not work. I have all logging set to
debug, but can't seem to get more specific information.

I am at an absolute loss.  I can only think of a few possibilities:

1) It is possible that I am still using the auto generated mod_jk.conf file
- which would have worked previously when I had one default host set up, but
will not work now that I have added in the virtual hosts?  How can I check
this to make sure that I am using my version of mod_jk.conf found in
/tomcat/conf and not the auto generated one in /tomcat/conf/auto?  The
problem with this possibility is that I get this error message when trying
either Virtual Host (even the one that is in the generated mod_jk.conf).

2) The permissions are wrong on the workers.properties file: permissions are
read everyone, write owner

3) The workers.properties specifies the host as localhost: will this work
with virtual hosts?

4) I do not have the connectors configured right: The connectors configured
are the original defaults so I don't think this is the problem.

Do any of these sound like valid possibilities?  Or is there something I am
missing.  I appreciate all your help.

Denise


-Original Message-
From: John Turner [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, June 03, 2003 8:16 AM
To: Tomcat Users List
Subject: Re: Strange mod_jk error



I think the problem is that, in the .properties files you posted, you have 
the port as 8080.  That's the HTTP port...the JK port is 8009.

John

On Mon, 2 Jun 2003 23:37:04 -0400, Denise Mangano <[EMAIL PROTECTED]> 
wrote:

> I decided to scratch having the second worker since my problems seemed 
> to start with that approach.  I restored everything to the original 
> worker file and have both default and test virtual hosts pointing to 
> the same workers.properties.
>
> For some reason, mod_jk is still not working.  Its not a problem with
> Tomcat
> itself because I can access everything on port 8080.  Apache throws an
> internal server error every time I try to access a jsp without the port 
> in
> the URL.
>
> The error in the apache error log is:
> [Mon Jun  2 23:04:59 2003] [error] Error while opening the workers, jk
> will
> not work
> [Mon Jun  2 23:05:01 2003] [error] (2)No such file or directory: Error 
> while
> opening the workers, jk will not work
>
> The error in mod_jk.log is:
> [Mon Jun 02 23:01:47 2003]  [jk_uri_worker_map.c (558)]: 
> jk_uri_worker_map_t::map_uri_to_worker, Found a suffix match worker -> 
> *.jsp [Mon Jun 02 23:01:47 2003]  [jk_worker.c (132)]: Into
> wc_get_worker_for_name
> worker
> [Mon Jun 02 23:01:47 2003]  [jk_worker.c (136)]: wc_get_worker_for_name,
> done did not found a worker
>
> Content of my worker file is:
> worker.list = worker
> worker.worker.type = ajp13
> worker.worker.host = localhost
> worker.worker.port = 8009
>
> My JkMount statements are like this: JkMount /*.jsp worker
>
> I'd appreciate any help on this.  It has put me in a pretty serious 
> bind, and I can't for the life of me figure out why it won't work.
>
> Thanks,
> Denise
>
> -----Original Message-
> From: Denise Mangano [mailto:[EMAIL PROTECTED] Sent: Monday, 
> June
> 02, 2003 4:56 PM
> To: 'Tomcat Users List'
> Subject: RE: Strange mod_jk error
>
>
> By "some configuration changes" I added in virtual hosting.  That 
> error message is gone.  I'm not exactly sure what I did to get it to 
> 'go away' but it did.  The problem I am having is that my worker is 
> not being found.
>
> I have two properties files defined.  One is workers.properties for 
> use
> with
> the default virtual host, and one is test.workers.properties to use with 
> my
> testing virtual host.  I tried combining each into one workers.properties
> file but still get the same error message.  The suffix is matched, but 
> when
> it looks for the worker named testWorker it doesn't fin it:
>
> [Mon Jun 02 16:16:57 2003]  [jk_worker.c (132)]: Into
> wc_get_worker_for_name
> testWorker [Mon Jun 02 16:16:57 2003]  [jk_worker.c (136)]:
> wc_get_worker_for_name, done did not found a worker
>
> My test.workers.properties file looks like:
> worker.list = testWorker
> worker.testWorker.type = ajp13
> worker.testWorker.host = test.mysite.com worker.testWorker.port = 8080
>
> My test.workers.properties file looks like:
> worker.

Re: Strange mod_jk error

[John Turner]

On Tue, 3 Jun 2003 09:51:14 -0400, Denise Mangano <[EMAIL PROTECTED]> 
wrote:

1) It is possible that I am still using the auto generated mod_jk.conf 
file
- which would have worked previously when I had one default host set up, 
but
will not work now that I have added in the virtual hosts?  How can I 
check
this to make sure that I am using my version of mod_jk.conf found in
/tomcat/conf and not the auto generated one in /tomcat/conf/auto?  The
problem with this possibility is that I get this error message when 
trying
either Virtual Host (even the one that is in the generated mod_jk.conf).
There's no way to check, as far as I know.  It would be based on the 
Include statement in httpd.conf.  Is it possible that your Apache restart 
didn't actually happen?  Sometimes the "restart" option doesn't behave...I 
have more luck actually shutting Apache down, then starting it back up.

2) The permissions are wrong on the workers.properties file: permissions 
are
read everyone, write owner
I doubt this is a problem, 644 should be fine.

3) The workers.properties specifies the host as localhost: will this work
with virtual hosts?
Yes...the .host parameter is the location of the machine hosting the Tomcat 
instance, not any sort of virtual host or other server name/address.

4) I do not have the connectors configured right: The connectors 
configured
are the original defaults so I don't think this is the problem.
I agree.

Do any of these sound like valid possibilities?  Or is there something I 
am
missing.  I appreciate all your help.
#1 sounds pretty good.  The other thing I noticed, on reviewing your 
earlier posts, is that your worker is named "worker".  My gut feeling tells 
me that's bad.  Try changing it to "ajp13" for the sake of debugging.

John

-Original Message-
From: John Turner [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 
03, 2003 8:16 AM
To: Tomcat Users List
Subject: Re: Strange mod_jk error



I think the problem is that, in the .properties files you posted, you 
have the port as 8080.  That's the HTTP port...the JK port is 8009.

John

On Mon, 2 Jun 2003 23:37:04 -0400, Denise Mangano 
<[EMAIL PROTECTED]> wrote:

I decided to scratch having the second worker since my problems seemed 
to start with that approach.  I restored everything to the original 
worker file and have both default and test virtual hosts pointing to the 
same workers.properties.

For some reason, mod_jk is still not working.  Its not a problem with
Tomcat
itself because I can access everything on port 8080.  Apache throws an
internal server error every time I try to access a jsp without the port 
in
the URL.

The error in the apache error log is:
[Mon Jun  2 23:04:59 2003] [error] Error while opening the workers, jk
will
not work
[Mon Jun  2 23:05:01 2003] [error] (2)No such file or directory: Error 
while
opening the workers, jk will not work

The error in mod_jk.log is:
[Mon Jun 02 23:01:47 2003]  [jk_uri_worker_map.c (558)]: 
jk_uri_worker_map_t::map_uri_to_worker, Found a suffix match worker -> 
*.jsp [Mon Jun 02 23:01:47 2003]  [jk_worker.c (132)]: Into
wc_get_worker_for_name
worker
[Mon Jun 02 23:01:47 2003]  [jk_worker.c (136)]: wc_get_worker_for_name,
done did not found a worker

Content of my worker file is:
worker.list = worker
worker.worker.type = ajp13
worker.worker.host = localhost
worker.worker.port = 8009
My JkMount statements are like this: JkMount /*.jsp worker

I'd appreciate any help on this.  It has put me in a pretty serious 
bind, and I can't for the life of me figure out why it won't work.

Thanks,
Denise
-Original Message-
From: Denise Mangano [mailto:[EMAIL PROTECTED] Sent: Monday, June
02, 2003 4:56 PM
To: 'Tomcat Users List'
Subject: RE: Strange mod_jk error
By "some configuration changes" I added in virtual hosting.  That error 
message is gone.  I'm not exactly sure what I did to get it to 'go away' 
but it did.  The problem I am having is that my worker is not being 
found.

I have two properties files defined.  One is workers.properties for use
with
the default virtual host, and one is test.workers.properties to use with 
my
testing virtual host.  I tried combining each into one 
workers.properties
file but still get the same error message.  The suffix is matched, but 
when
it looks for the worker named testWorker it doesn't fin it:

[Mon Jun 02 16:16:57 2003]  [jk_worker.c (132)]: Into
wc_get_worker_for_name
testWorker [Mon Jun 02 16:16:57 2003]  [jk_worker.c (136)]:
wc_get_worker_for_name, done did not found a worker
My test.workers.properties file looks like:
worker.list = testWorker
worker.testWorker.type = ajp13
worker.testWorker.host = test.mysite.com worker.testWorker.port = 8080
My test.workers.properties file looks like:
worker.list = worker
worker.worker.type = ajp13
worker.worker.host = www.mysite.com
worker.worker.port = 8080
My server.xm

RE: Strange mod_jk error

[Denise Mangano]

I noticed that having the worker named worker wasn't the smartest thing, so
I changed it to worker1 and still got the same problem.  

Now the strange thing is, I did not have an include statement in my
httpd.conf.  I had originally set this up a while ago, so to be honest I am
not sure why I didn't have it there, because I remember putting it in when I
followed your how-to.  So this means that I have been using the auto
generated mod_jk.conf (is that right?).

I tried to 1) change the worker name to ajp13 and 2) include the edited
mod_jk.conf.  I am still getting the error message when I start up apache
stating that there was an error opening the workers and jk will not work.
When I try to access a jsp page I still get the same error message in my
mod_jk.log stating that it is looking for worker ajp13, but the worker is
not found.  It appears that the actual problem is opening the
workers.properties... The system finds it, sets the rules, attempts the
matches the URI request, and eventually finds a context match for the
worker.  The problem is when looking for the worker it does not see it.  It
would make sense that this would happen since Apache is having trouble
opening the workers.properties file.  The strange thing is that Apache is
also stating there is "No such file or directory" but the file is in fact
there, and all the paths pointing to it are correct.

Any other suggestions?  Should I maybe post my files?

Thanks,
Denise


-Original Message-
From: John Turner [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, June 03, 2003 9:59 AM
To: Tomcat Users List
Subject: Re: Strange mod_jk error


On Tue, 3 Jun 2003 09:51:14 -0400, Denise Mangano <[EMAIL PROTECTED]> 
wrote:

> 1) It is possible that I am still using the auto generated mod_jk.conf
> file
> - which would have worked previously when I had one default host set up, 
> but
> will not work now that I have added in the virtual hosts?  How can I 
> check
> this to make sure that I am using my version of mod_jk.conf found in
> /tomcat/conf and not the auto generated one in /tomcat/conf/auto?  The
> problem with this possibility is that I get this error message when 
> trying
> either Virtual Host (even the one that is in the generated mod_jk.conf).

There's no way to check, as far as I know.  It would be based on the 
Include statement in httpd.conf.  Is it possible that your Apache restart 
didn't actually happen?  Sometimes the "restart" option doesn't behave...I 
have more luck actually shutting Apache down, then starting it back up.

>
> 2) The permissions are wrong on the workers.properties file: 
> permissions
> are
> read everyone, write owner

I doubt this is a problem, 644 should be fine.

> 3) The workers.properties specifies the host as localhost: will this 
> work with virtual hosts?

Yes...the .host parameter is the location of the machine hosting the Tomcat 
instance, not any sort of virtual host or other server name/address.

> 4) I do not have the connectors configured right: The connectors
> configured
> are the original defaults so I don't think this is the problem.

I agree.

> Do any of these sound like valid possibilities?  Or is there something 
> I
> am
> missing.  I appreciate all your help.

#1 sounds pretty good.  The other thing I noticed, on reviewing your 
earlier posts, is that your worker is named "worker".  My gut feeling tells 
me that's bad.  Try changing it to "ajp13" for the sake of debugging.

John

> -----Original Message-
> From: John Turner [mailto:[EMAIL PROTECTED] Sent: Tuesday, 
> June
> 03, 2003 8:16 AM
> To: Tomcat Users List
> Subject: Re: Strange mod_jk error
>
>
>
> I think the problem is that, in the .properties files you posted, you
> have the port as 8080.  That's the HTTP port...the JK port is 8009.
>
> John
>
> On Mon, 2 Jun 2003 23:37:04 -0400, Denise Mangano
> <[EMAIL PROTECTED]> wrote:
>
>> I decided to scratch having the second worker since my problems 
>> seemed
>> to start with that approach.  I restored everything to the original 
>> worker file and have both default and test virtual hosts pointing to the 
>> same workers.properties.
>>
>> For some reason, mod_jk is still not working.  Its not a problem with 
>> Tomcat itself because I can access everything on port 8080.  Apache 
>> throws an internal server error every time I try to access a jsp 
>> without the port in
>> the URL.
>>
>> The error in the apache error log is:
>> [Mon Jun  2 23:04:59 2003] [error] Error while opening the workers, 
>> jk will not work
>> [Mon Jun  2 23:05:01 2003] [error] (2)No such file or directory: Error 
>> while
>> opening the workers, jk will not work
>>
>> The err

Re: Strange mod_jk error

[John Turner]

The mod_jk.conf file isn't getting used unless there is an Include 
directive in httpd.conf to include it.

Make sure you have these lines somewhere, either hard-coded in httpd.conf, 
or at the top of your mod_jk.conf file:

JkWorkersFile "/path/to/workers.properties"
JkLogFile "/path/to/mod_jk.log"
JkLogLevel emerg
John

On Tue, 3 Jun 2003 12:05:09 -0400, Denise Mangano <[EMAIL PROTECTED]> 
wrote:

I noticed that having the worker named worker wasn't the smartest thing, 
so
I changed it to worker1 and still got the same problem.

Now the strange thing is, I did not have an include statement in my
httpd.conf.  I had originally set this up a while ago, so to be honest I 
am
not sure why I didn't have it there, because I remember putting it in 
when I
followed your how-to.  So this means that I have been using the auto
generated mod_jk.conf (is that right?).

I tried to 1) change the worker name to ajp13 and 2) include the edited
mod_jk.conf.  I am still getting the error message when I start up apache
stating that there was an error opening the workers and jk will not work.
When I try to access a jsp page I still get the same error message in my
mod_jk.log stating that it is looking for worker ajp13, but the worker is
not found.  It appears that the actual problem is opening the
workers.properties... The system finds it, sets the rules, attempts the
matches the URI request, and eventually finds a context match for the
worker.  The problem is when looking for the worker it does not see it.  
It
would make sense that this would happen since Apache is having trouble
opening the workers.properties file.  The strange thing is that Apache is
also stating there is "No such file or directory" but the file is in fact
there, and all the paths pointing to it are correct.

Any other suggestions?  Should I maybe post my files?

Thanks,
Denise
-Original Message-
From: John Turner [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 
03, 2003 9:59 AM
To: Tomcat Users List
Subject: Re: Strange mod_jk error

On Tue, 3 Jun 2003 09:51:14 -0400, Denise Mangano 
<[EMAIL PROTECTED]> wrote:

1) It is possible that I am still using the auto generated mod_jk.conf
file
- which would have worked previously when I had one default host set up, 
but
will not work now that I have added in the virtual hosts?  How can I 
check
this to make sure that I am using my version of mod_jk.conf found in
/tomcat/conf and not the auto generated one in /tomcat/conf/auto?  The
problem with this possibility is that I get this error message when 
trying
either Virtual Host (even the one that is in the generated mod_jk.conf).
There's no way to check, as far as I know.  It would be based on the 
Include statement in httpd.conf.  Is it possible that your Apache restart 
didn't actually happen?  Sometimes the "restart" option doesn't 
behave...I have more luck actually shutting Apache down, then starting it 
back up.

2) The permissions are wrong on the workers.properties file: permissions
are
read everyone, write owner
I doubt this is a problem, 644 should be fine.

3) The workers.properties specifies the host as localhost: will this 
work with virtual hosts?
Yes...the .host parameter is the location of the machine hosting the 
Tomcat instance, not any sort of virtual host or other server 
name/address.

4) I do not have the connectors configured right: The connectors
configured
are the original defaults so I don't think this is the problem.
I agree.

Do any of these sound like valid possibilities?  Or is there something I
am
missing.  I appreciate all your help.
#1 sounds pretty good.  The other thing I noticed, on reviewing your 
earlier posts, is that your worker is named "worker".  My gut feeling 
tells me that's bad.  Try changing it to "ajp13" for the sake of 
debugging.

John

-Original Message-
From: John Turner [mailto:[EMAIL PROTECTED] Sent: Tuesday, 
June
03, 2003 8:16 AM
To: Tomcat Users List
Subject: Re: Strange mod_jk error



I think the problem is that, in the .properties files you posted, you
have the port as 8080.  That's the HTTP port...the JK port is 8009.
John

On Mon, 2 Jun 2003 23:37:04 -0400, Denise Mangano
<[EMAIL PROTECTED]> wrote:
I decided to scratch having the second worker since my problems seemed
to start with that approach.  I restored everything to the original 
worker file and have both default and test virtual hosts pointing to 
the same workers.properties.

For some reason, mod_jk is still not working.  Its not a problem with 
Tomcat itself because I can access everything on port 8080.  Apache 
throws an internal server error every time I try to access a jsp 
without the port in
the URL.

The error in the apache error log is:
[Mon Jun  2 23:04:59 2003] [error] Error while opening the workers, jk 
will not work
[Mon Jun  2 23:05:01 2003] [error] (2)No such file or directory: Error 
whi

RE: Strange mod_jk error

[Denise Mangano]

Those lines are at the top of my mod_jk.conf (the one I edited) and my
Include statement points to my version of the mod_jk.conf.

This is a strange problem, I've searched the archives but can't seem to find
a fix.  Whats worse is that it doesn't give more detail on the error, for
example what file and line the error occurs on...

Denise

-Original Message-
From: John Turner [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, June 03, 2003 12:18 PM
To: Tomcat Users List
Subject: Re: Strange mod_jk error



The mod_jk.conf file isn't getting used unless there is an Include 
directive in httpd.conf to include it.

Make sure you have these lines somewhere, either hard-coded in httpd.conf, 
or at the top of your mod_jk.conf file:

JkWorkersFile "/path/to/workers.properties"
JkLogFile "/path/to/mod_jk.log"
JkLogLevel emerg

John

On Tue, 3 Jun 2003 12:05:09 -0400, Denise Mangano <[EMAIL PROTECTED]> 
wrote:

> I noticed that having the worker named worker wasn't the smartest 
> thing,
> so
> I changed it to worker1 and still got the same problem.
>
> Now the strange thing is, I did not have an include statement in my 
> httpd.conf.  I had originally set this up a while ago, so to be honest 
> I am not sure why I didn't have it there, because I remember putting 
> it in when I
> followed your how-to.  So this means that I have been using the auto
> generated mod_jk.conf (is that right?).
>
> I tried to 1) change the worker name to ajp13 and 2) include the 
> edited mod_jk.conf.  I am still getting the error message when I start 
> up apache stating that there was an error opening the workers and jk 
> will not work. When I try to access a jsp page I still get the same 
> error message in my mod_jk.log stating that it is looking for worker 
> ajp13, but the worker is not found.  It appears that the actual 
> problem is opening the workers.properties... The system finds it, sets 
> the rules, attempts the matches the URI request, and eventually finds 
> a context match for the worker.  The problem is when looking for the
worker it does not see it.
> It
> would make sense that this would happen since Apache is having trouble
> opening the workers.properties file.  The strange thing is that Apache is
> also stating there is "No such file or directory" but the file is in fact
> there, and all the paths pointing to it are correct.
>
> Any other suggestions?  Should I maybe post my files?
>
> Thanks,
> Denise
>
>
> -Original Message-
> From: John Turner [mailto:[EMAIL PROTECTED] Sent: Tuesday, 
> June
> 03, 2003 9:59 AM
> To: Tomcat Users List
> Subject: Re: Strange mod_jk error
>
>
> On Tue, 3 Jun 2003 09:51:14 -0400, Denise Mangano
> <[EMAIL PROTECTED]> wrote:
>
>> 1) It is possible that I am still using the auto generated 
>> mod_jk.conf file
>> - which would have worked previously when I had one default host set 
>> up,
>> but
>> will not work now that I have added in the virtual hosts?  How can I 
>> check
>> this to make sure that I am using my version of mod_jk.conf found in
>> /tomcat/conf and not the auto generated one in /tomcat/conf/auto?  The
>> problem with this possibility is that I get this error message when 
>> trying
>> either Virtual Host (even the one that is in the generated mod_jk.conf).
>
> There's no way to check, as far as I know.  It would be based on the
> Include statement in httpd.conf.  Is it possible that your Apache restart 
> didn't actually happen?  Sometimes the "restart" option doesn't 
> behave...I have more luck actually shutting Apache down, then starting it 
> back up.
>
>>
>> 2) The permissions are wrong on the workers.properties file: 
>> permissions are read everyone, write owner
>
> I doubt this is a problem, 644 should be fine.
>
>> 3) The workers.properties specifies the host as localhost: will this
>> work with virtual hosts?
>
> Yes...the .host parameter is the location of the machine hosting the
> Tomcat instance, not any sort of virtual host or other server 
> name/address.
>
>> 4) I do not have the connectors configured right: The connectors 
>> configured are the original defaults so I don't think this is the 
>> problem.
>
> I agree.
>
>> Do any of these sound like valid possibilities?  Or is there 
>> something I am missing.  I appreciate all your help.
>
> #1 sounds pretty good.  The other thing I noticed, on reviewing your
> earlier posts, is that your worker is named "worker".  My gut feeling 
> tells me that's bad.  Try changing it to "ajp13" for the sake of 
> debugging.
>
> John
>
>> -

Re: Strange mod_jk error

[John Turner]

A "configtest" of Apache returns "Syntax OK"?

John

On Tue, 3 Jun 2003 12:50:25 -0400, Denise Mangano <[EMAIL PROTECTED]> 
wrote:

Those lines are at the top of my mod_jk.conf (the one I edited) and my
Include statement points to my version of the mod_jk.conf.
This is a strange problem, I've searched the archives but can't seem to 
find
a fix.  Whats worse is that it doesn't give more detail on the error, for
example what file and line the error occurs on...

Denise

-Original Message-
From: John Turner [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 
03, 2003 12:18 PM
To: Tomcat Users List
Subject: Re: Strange mod_jk error



The mod_jk.conf file isn't getting used unless there is an Include 
directive in httpd.conf to include it.

Make sure you have these lines somewhere, either hard-coded in 
httpd.conf, or at the top of your mod_jk.conf file:

JkWorkersFile "/path/to/workers.properties"
JkLogFile "/path/to/mod_jk.log"
JkLogLevel emerg
John

On Tue, 3 Jun 2003 12:05:09 -0400, Denise Mangano 
<[EMAIL PROTECTED]> wrote:

I noticed that having the worker named worker wasn't the smartest thing,
so
I changed it to worker1 and still got the same problem.
Now the strange thing is, I did not have an include statement in my 
httpd.conf.  I had originally set this up a while ago, so to be honest I 
am not sure why I didn't have it there, because I remember putting it in 
when I
followed your how-to.  So this means that I have been using the auto
generated mod_jk.conf (is that right?).

I tried to 1) change the worker name to ajp13 and 2) include the edited 
mod_jk.conf.  I am still getting the error message when I start up 
apache stating that there was an error opening the workers and jk will 
not work. When I try to access a jsp page I still get the same error 
message in my mod_jk.log stating that it is looking for worker ajp13, 
but the worker is not found.  It appears that the actual problem is 
opening the workers.properties... The system finds it, sets the rules, 
attempts the matches the URI request, and eventually finds a context 
match for the worker.  The problem is when looking for the
worker it does not see it.
It
would make sense that this would happen since Apache is having trouble
opening the workers.properties file.  The strange thing is that Apache 
is
also stating there is "No such file or directory" but the file is in 
fact
there, and all the paths pointing to it are correct.

Any other suggestions?  Should I maybe post my files?

Thanks,
Denise
-Original Message-
From: John Turner [mailto:[EMAIL PROTECTED] Sent: Tuesday, 
June
03, 2003 9:59 AM
To: Tomcat Users List
Subject: Re: Strange mod_jk error

On Tue, 3 Jun 2003 09:51:14 -0400, Denise Mangano
<[EMAIL PROTECTED]> wrote:
1) It is possible that I am still using the auto generated mod_jk.conf 
file
- which would have worked previously when I had one default host set 
up,
but
will not work now that I have added in the virtual hosts?  How can I 
check
this to make sure that I am using my version of mod_jk.conf found in
/tomcat/conf and not the auto generated one in /tomcat/conf/auto?  The
problem with this possibility is that I get this error message when 
trying
either Virtual Host (even the one that is in the generated mod_jk.conf) 
.
There's no way to check, as far as I know.  It would be based on the
Include statement in httpd.conf.  Is it possible that your Apache 
restart didn't actually happen?  Sometimes the "restart" option doesn't 
behave...I have more luck actually shutting Apache down, then starting 
it back up.

2) The permissions are wrong on the workers.properties file: 
permissions are read everyone, write owner
I doubt this is a problem, 644 should be fine.

3) The workers.properties specifies the host as localhost: will this
work with virtual hosts?
Yes...the .host parameter is the location of the machine hosting the
Tomcat instance, not any sort of virtual host or other server 
name/address.

4) I do not have the connectors configured right: The connectors 
configured are the original defaults so I don't think this is the 
problem.
I agree.

Do any of these sound like valid possibilities?  Or is there something 
I am missing.  I appreciate all your help.
#1 sounds pretty good.  The other thing I noticed, on reviewing your
earlier posts, is that your worker is named "worker".  My gut feeling 
tells me that's bad.  Try changing it to "ajp13" for the sake of 
debugging.

John

-Original Message-
From: John Turner [mailto:[EMAIL PROTECTED] Sent: Tuesday,
June
03, 2003 8:16 AM
To: Tomcat Users List
Subject: Re: Strange mod_jk error


I think the problem is that, in the .properties files you posted, you 
have the port as 8080.  That's the HTTP port...the JK port is 8009.

John

On Mon, 2 Jun 2003 23:37:04 -0400, Denise Mangano 
<[EMAIL PROTECTED]&

RE: Strange mod_jk error

[Denise Mangano]

Well it throws me two warnings:

[Tue Jun  3 11:16:23 2003] [warn] VirtualHost www.ptp.com:80 overlaps with
VirtualHost test.ptp.com:80, the first has precedence, perhaps you need a
NameVirtualHost directive 
[Tue Jun  3 11:16:23 2003] [warn] VirtualHost www.ptp.com:443 overlaps with
VirtualHost test.ptp.com:443, the first has precedence, perhaps you need a
NameVirtualHost directive

I'm in the process of trying to get this problem worked out.  Other than
this, the syntax is OK.

Denise

-Original Message-
From: John Turner [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, June 03, 2003 12:45 PM
To: Tomcat Users List
Subject: Re: Strange mod_jk error



A "configtest" of Apache returns "Syntax OK"?

John

On Tue, 3 Jun 2003 12:50:25 -0400, Denise Mangano <[EMAIL PROTECTED]> 
wrote:

> Those lines are at the top of my mod_jk.conf (the one I edited) and my 
> Include statement points to my version of the mod_jk.conf.
>
> This is a strange problem, I've searched the archives but can't seem 
> to
> find
> a fix.  Whats worse is that it doesn't give more detail on the error, for
> example what file and line the error occurs on...
>
> Denise
>
> -Original Message-
> From: John Turner [mailto:[EMAIL PROTECTED] Sent: Tuesday, 
> June
> 03, 2003 12:18 PM
> To: Tomcat Users List
> Subject: Re: Strange mod_jk error
>
>
>
> The mod_jk.conf file isn't getting used unless there is an Include
> directive in httpd.conf to include it.
>
> Make sure you have these lines somewhere, either hard-coded in
> httpd.conf, or at the top of your mod_jk.conf file:
>
> JkWorkersFile "/path/to/workers.properties"
> JkLogFile "/path/to/mod_jk.log"
> JkLogLevel emerg
>
> John
>
> On Tue, 3 Jun 2003 12:05:09 -0400, Denise Mangano
> <[EMAIL PROTECTED]> wrote:
>
>> I noticed that having the worker named worker wasn't the smartest 
>> thing, so I changed it to worker1 and still got the same problem.
>>
>> Now the strange thing is, I did not have an include statement in my
>> httpd.conf.  I had originally set this up a while ago, so to be honest I 
>> am not sure why I didn't have it there, because I remember putting it in 
>> when I
>> followed your how-to.  So this means that I have been using the auto
>> generated mod_jk.conf (is that right?).
>>
>> I tried to 1) change the worker name to ajp13 and 2) include the 
>> edited
>> mod_jk.conf.  I am still getting the error message when I start up 
>> apache stating that there was an error opening the workers and jk will 
>> not work. When I try to access a jsp page I still get the same error 
>> message in my mod_jk.log stating that it is looking for worker ajp13, 
>> but the worker is not found.  It appears that the actual problem is 
>> opening the workers.properties... The system finds it, sets the rules, 
>> attempts the matches the URI request, and eventually finds a context 
>> match for the worker.  The problem is when looking for the
> worker it does not see it.
>> It
>> would make sense that this would happen since Apache is having 
>> trouble opening the workers.properties file.  The strange thing is 
>> that Apache is also stating there is "No such file or directory" but 
>> the file is in fact
>> there, and all the paths pointing to it are correct.
>>
>> Any other suggestions?  Should I maybe post my files?
>>
>> Thanks,
>> Denise
>>
>>
>> -Original Message-
>> From: John Turner [mailto:[EMAIL PROTECTED] Sent: Tuesday,
>> June
>> 03, 2003 9:59 AM
>> To: Tomcat Users List
>> Subject: Re: Strange mod_jk error
>>
>>
>> On Tue, 3 Jun 2003 09:51:14 -0400, Denise Mangano 
>> <[EMAIL PROTECTED]> wrote:
>>
>>> 1) It is possible that I am still using the auto generated 
>>> mod_jk.conf
>>> file
>>> - which would have worked previously when I had one default host set 
>>> up,
>>> but
>>> will not work now that I have added in the virtual hosts?  How can I 
>>> check
>>> this to make sure that I am using my version of mod_jk.conf found in
>>> /tomcat/conf and not the auto generated one in /tomcat/conf/auto?  The
>>> problem with this possibility is that I get this error message when 
>>> trying
>>> either Virtual Host (even the one that is in the generated mod_jk.conf) 
>>> .
>>
>> There's no way to check, as far as I know.  It would be based on the 
>> Include statement in httpd.conf.  Is it possible that your Apache 
>> restart didn't actually h

RE: Strange mod_jk error

[PELOQUIN,JEFFREY (HP-Boise,ex1)]

Denise,

I could not see in the email trail if it ever was determined that you truly
have a listener on the ajp13 port for the problem domain

if you do
telnet test.mysite.com 8009 

or whatever the correct domain/port for your current configuration do you
get a valid telnet response?

also if you are on linux, you can do a netstat -a | grep LISTEN to see what
is addresses and port have listeners

Jeff

-Original Message-
From: Denise Mangano [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 03, 2003 10:58 AM
To: 'Tomcat Users List'
Subject: RE: Strange mod_jk error


Well it throws me two warnings:

[Tue Jun  3 11:16:23 2003] [warn] VirtualHost www.ptp.com:80 overlaps with
VirtualHost test.ptp.com:80, the first has precedence, perhaps you need a
NameVirtualHost directive 
[Tue Jun  3 11:16:23 2003] [warn] VirtualHost www.ptp.com:443 overlaps with
VirtualHost test.ptp.com:443, the first has precedence, perhaps you need a
NameVirtualHost directive

I'm in the process of trying to get this problem worked out.  Other than
this, the syntax is OK.

Denise

-Original Message-
From: John Turner [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, June 03, 2003 12:45 PM
To: Tomcat Users List
Subject: Re: Strange mod_jk error



A "configtest" of Apache returns "Syntax OK"?

John

On Tue, 3 Jun 2003 12:50:25 -0400, Denise Mangano <[EMAIL PROTECTED]> 
wrote:

> Those lines are at the top of my mod_jk.conf (the one I edited) and my 
> Include statement points to my version of the mod_jk.conf.
>
> This is a strange problem, I've searched the archives but can't seem 
> to
> find
> a fix.  Whats worse is that it doesn't give more detail on the error, for
> example what file and line the error occurs on...
>
> Denise
>
> -Original Message-
> From: John Turner [mailto:[EMAIL PROTECTED] Sent: Tuesday, 
> June
> 03, 2003 12:18 PM
> To: Tomcat Users List
> Subject: Re: Strange mod_jk error
>
>
>
> The mod_jk.conf file isn't getting used unless there is an Include
> directive in httpd.conf to include it.
>
> Make sure you have these lines somewhere, either hard-coded in
> httpd.conf, or at the top of your mod_jk.conf file:
>
> JkWorkersFile "/path/to/workers.properties"
> JkLogFile "/path/to/mod_jk.log"
> JkLogLevel emerg
>
> John
>
> On Tue, 3 Jun 2003 12:05:09 -0400, Denise Mangano
> <[EMAIL PROTECTED]> wrote:
>
>> I noticed that having the worker named worker wasn't the smartest 
>> thing, so I changed it to worker1 and still got the same problem.
>>
>> Now the strange thing is, I did not have an include statement in my
>> httpd.conf.  I had originally set this up a while ago, so to be honest I 
>> am not sure why I didn't have it there, because I remember putting it in 
>> when I
>> followed your how-to.  So this means that I have been using the auto
>> generated mod_jk.conf (is that right?).
>>
>> I tried to 1) change the worker name to ajp13 and 2) include the 
>> edited
>> mod_jk.conf.  I am still getting the error message when I start up 
>> apache stating that there was an error opening the workers and jk will 
>> not work. When I try to access a jsp page I still get the same error 
>> message in my mod_jk.log stating that it is looking for worker ajp13, 
>> but the worker is not found.  It appears that the actual problem is 
>> opening the workers.properties... The system finds it, sets the rules, 
>> attempts the matches the URI request, and eventually finds a context 
>> match for the worker.  The problem is when looking for the
> worker it does not see it.
>> It
>> would make sense that this would happen since Apache is having 
>> trouble opening the workers.properties file.  The strange thing is 
>> that Apache is also stating there is "No such file or directory" but 
>> the file is in fact
>> there, and all the paths pointing to it are correct.
>>
>> Any other suggestions?  Should I maybe post my files?
>>
>> Thanks,
>> Denise
>>
>>
>> -Original Message-
>> From: John Turner [mailto:[EMAIL PROTECTED] Sent: Tuesday,
>> June
>> 03, 2003 9:59 AM
>> To: Tomcat Users List
>> Subject: Re: Strange mod_jk error
>>
>>
>> On Tue, 3 Jun 2003 09:51:14 -0400, Denise Mangano 
>> <[EMAIL PROTECTED]> wrote:
>>
>>> 1) It is possible that I am still using the auto generated 
>>> mod_jk.conf
>>> file
>>> - which would have worked previously when I had one default host set 
>>> up,
>>> but
>>> will not work now that I have added in the virtual hosts?  How can I 
>>>

RE: Strange mod_jk error

[Denise Mangano]

Ok, dumb question.  Does port 8009 have to be open on my firewall then?  If
so then how was it possibly working before?  I can only telnet on port 80
and port 443 (These are the only ports open on my firewall).

The results of the netstat are:
tcp0  0 *:32768 *:* LISTEN

tcp0  0 *:login *:* LISTEN

tcp0  0 *:vboxd *:* LISTEN

tcp0  0 *:sunrpc*:* LISTEN

tcp0  0 *:ssh   *:* LISTEN

tcp0  0 cdiserv:smtp*:* LISTEN

unix  2  [ ACC ] STREAM LISTENING 1257   /dev/gpmctl
unix  2  [ ACC ] STREAM LISTENING 1324
/tmp/.font-unix/fs7100


I am getting the feeling something is not right... But it did work at one
point with the single virtual host...

In httpd.conf
Port 80
BindAddress *
NameVirtualHost *

  Listen 80
  Listen 443

ServerName www (overwritten within Vhosts)

Thanks,
Denise


-Original Message-
From: PELOQUIN,JEFFREY (HP-Boise,ex1) [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, June 03, 2003 1:06 PM
To: 'Tomcat Users List'
Subject: RE: Strange mod_jk error


Denise,

I could not see in the email trail if it ever was determined that you truly
have a listener on the ajp13 port for the problem domain

if you do
telnet test.mysite.com 8009 

or whatever the correct domain/port for your current configuration do you
get a valid telnet response?

also if you are on linux, you can do a netstat -a | grep LISTEN to see what
is addresses and port have listeners

Jeff

-Original Message-
From: Denise Mangano [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 03, 2003 10:58 AM
To: 'Tomcat Users List'
Subject: RE: Strange mod_jk error


Well it throws me two warnings:

[Tue Jun  3 11:16:23 2003] [warn] VirtualHost www.ptp.com:80 overlaps with
VirtualHost test.ptp.com:80, the first has precedence, perhaps you need a
NameVirtualHost directive 
[Tue Jun  3 11:16:23 2003] [warn] VirtualHost www.ptp.com:443 overlaps with
VirtualHost test.ptp.com:443, the first has precedence, perhaps you need a
NameVirtualHost directive

I'm in the process of trying to get this problem worked out.  Other than
this, the syntax is OK.

Denise

-Original Message-
From: John Turner [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, June 03, 2003 12:45 PM
To: Tomcat Users List
Subject: Re: Strange mod_jk error



A "configtest" of Apache returns "Syntax OK"?

John

On Tue, 3 Jun 2003 12:50:25 -0400, Denise Mangano <[EMAIL PROTECTED]> 
wrote:

> Those lines are at the top of my mod_jk.conf (the one I edited) and my
> Include statement points to my version of the mod_jk.conf.
>
> This is a strange problem, I've searched the archives but can't seem
> to
> find
> a fix.  Whats worse is that it doesn't give more detail on the error, for
> example what file and line the error occurs on...
>
> Denise
>
> -Original Message-
> From: John Turner [mailto:[EMAIL PROTECTED] Sent: Tuesday,
> June
> 03, 2003 12:18 PM
> To: Tomcat Users List
> Subject: Re: Strange mod_jk error
>
>
>
> The mod_jk.conf file isn't getting used unless there is an Include 
> directive in httpd.conf to include it.
>
> Make sure you have these lines somewhere, either hard-coded in 
> httpd.conf, or at the top of your mod_jk.conf file:
>
> JkWorkersFile "/path/to/workers.properties"
> JkLogFile "/path/to/mod_jk.log"
> JkLogLevel emerg
>
> John
>
> On Tue, 3 Jun 2003 12:05:09 -0400, Denise Mangano 
> <[EMAIL PROTECTED]> wrote:
>
>> I noticed that having the worker named worker wasn't the smartest
>> thing, so I changed it to worker1 and still got the same problem.
>>
>> Now the strange thing is, I did not have an include statement in my 
>> httpd.conf.  I had originally set this up a while ago, so to be 
>> honest I am not sure why I didn't have it there, because I remember 
>> putting it in when I followed your how-to.  So this means that I have 
>> been using the auto generated mod_jk.conf (is that right?).
>>
>> I tried to 1) change the worker name to ajp13 and 2) include the
>> edited
>> mod_jk.conf.  I am still getting the error message when I start up 
>> apache stating that there was an error opening the workers and jk will 
>> not work. When I try to access a jsp page I still get the same error 
>> message in my mod_jk.log stating that it is looking for worker ajp13, 
>> but the worker is not found.  It appears that the actual problem is 
>> opening the workers.properties... The system finds it, sets the rules, 
>> attempts the matches th

RE: Strange mod_jk error

[Denise Mangano]

I tried to open port 8009 on the firewall but that did not solve the
problem...

-Original Message-
From: Denise Mangano [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, June 03, 2003 1:51 PM
To: 'Tomcat Users List'
Subject: RE: Strange mod_jk error


Ok, dumb question.  Does port 8009 have to be open on my firewall then?  If
so then how was it possibly working before?  I can only telnet on port 80
and port 443 (These are the only ports open on my firewall).

The results of the netstat are:
tcp0  0 *:32768 *:* LISTEN
tcp0  0 *:login *:* LISTEN
tcp0  0 *:vboxd *:* LISTEN
tcp0  0 *:sunrpc*:* LISTEN
tcp0  0 *:ssh   *:* LISTEN
tcp0  0 cdiserv:smtp*:* LISTEN
unix  2  [ ACC ] STREAM LISTENING 1257   /dev/gpmctl
unix  2  [ ACC ] STREAM LISTENING 1324
/tmp/.font-unix/fs7100


I am getting the feeling something is not right... But it did work at one
point with the single virtual host...

In httpd.conf
Port 80
BindAddress *
NameVirtualHost *

  Listen 80
  Listen 443

ServerName www (overwritten within Vhosts)

Thanks,
Denise


-Original Message-
From: PELOQUIN,JEFFREY (HP-Boise,ex1) [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, June 03, 2003 1:06 PM
To: 'Tomcat Users List'
Subject: RE: Strange mod_jk error


Denise,

I could not see in the email trail if it ever was determined that you truly
have a listener on the ajp13 port for the problem domain

if you do
telnet test.mysite.com 8009 

or whatever the correct domain/port for your current configuration do you
get a valid telnet response?

also if you are on linux, you can do a netstat -a | grep LISTEN to see what
is addresses and port have listeners

Jeff

-Original Message-
From: Denise Mangano [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 03, 2003 10:58 AM
To: 'Tomcat Users List'
Subject: RE: Strange mod_jk error


Well it throws me two warnings:

[Tue Jun  3 11:16:23 2003] [warn] VirtualHost www.ptp.com:80 overlaps with
VirtualHost test.ptp.com:80, the first has precedence, perhaps you need a
NameVirtualHost directive 
[Tue Jun  3 11:16:23 2003] [warn] VirtualHost www.ptp.com:443 overlaps with
VirtualHost test.ptp.com:443, the first has precedence, perhaps you need a
NameVirtualHost directive

I'm in the process of trying to get this problem worked out.  Other than
this, the syntax is OK.

Denise

-Original Message-
From: John Turner [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, June 03, 2003 12:45 PM
To: Tomcat Users List
Subject: Re: Strange mod_jk error



A "configtest" of Apache returns "Syntax OK"?

John

On Tue, 3 Jun 2003 12:50:25 -0400, Denise Mangano <[EMAIL PROTECTED]> 
wrote:

> Those lines are at the top of my mod_jk.conf (the one I edited) and my 
> Include statement points to my version of the mod_jk.conf.
>
> This is a strange problem, I've searched the archives but can't seem 
> to find
> a fix.  Whats worse is that it doesn't give more detail on the error, for
> example what file and line the error occurs on...
>
> Denise
>
> -Original Message-
> From: John Turner [mailto:[EMAIL PROTECTED] Sent: Tuesday, 
> June 03, 2003 12:18 PM
> To: Tomcat Users List
> Subject: Re: Strange mod_jk error
>
>
>
> The mod_jk.conf file isn't getting used unless there is an Include
> directive in httpd.conf to include it.
>
> Make sure you have these lines somewhere, either hard-coded in
> httpd.conf, or at the top of your mod_jk.conf file:
>
> JkWorkersFile "/path/to/workers.properties"
> JkLogFile "/path/to/mod_jk.log"
> JkLogLevel emerg
>
> John
>
> On Tue, 3 Jun 2003 12:05:09 -0400, Denise Mangano
> <[EMAIL PROTECTED]> wrote:
>
>> I noticed that having the worker named worker wasn't the smartest 
>> thing, so I changed it to worker1 and still got the same problem.
>>
>> Now the strange thing is, I did not have an include statement in my
>> httpd.conf.  I had originally set this up a while ago, so to be 
>> honest I am not sure why I didn't have it there, because I remember 
>> putting it in when I followed your how-to.  So this means that I have 
>> been using the auto generated mod_jk.conf (is that right?).
>>
>> I tried to 1) change the worker name to ajp13 and 2) include the 
>> edited mod_jk.conf.  I am still getting the error message when I 
>> start up apache stating that there was an error opening the workers 
>> and jk will not work. When I try to access a jsp page I still get the 
>> same error message in my mod_jk

Re: Strange mod_jk error

[John Turner]

OK, that tells me that you have multiple VirtualHosts going on, which means 
that you probably have multiple/conflicting JkMount and workers.

Probably, there is a hard-coded VirtualHost in httpd.conf, in addition to 
the definitions being included from mod_jk.conf.  That would explain 
(possibly) some of the problems you are experiencing...for example, the 
configuration you want is the second one, but only the first is being used 
by Apache, or vice versa.

"configtest" should return "Syntax OK".

John

On Tue, 3 Jun 2003 12:58:26 -0400, Denise Mangano <[EMAIL PROTECTED]> 
wrote:

Well it throws me two warnings:

[Tue Jun  3 11:16:23 2003] [warn] VirtualHost www.ptp.com:80 overlaps 
with
VirtualHost test.ptp.com:80, the first has precedence, perhaps you need a
NameVirtualHost directive [Tue Jun  3 11:16:23 2003] [warn] VirtualHost 
www.ptp.com:443 overlaps with
VirtualHost test.ptp.com:443, the first has precedence, perhaps you need 
a
NameVirtualHost directive

I'm in the process of trying to get this problem worked out.  Other than
this, the syntax is OK.
Denise

-Original Message-
From: John Turner [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 
03, 2003 12:45 PM
To: Tomcat Users List
Subject: Re: Strange mod_jk error



A "configtest" of Apache returns "Syntax OK"?

John

On Tue, 3 Jun 2003 12:50:25 -0400, Denise Mangano 
<[EMAIL PROTECTED]> wrote:

Those lines are at the top of my mod_jk.conf (the one I edited) and my 
Include statement points to my version of the mod_jk.conf.

This is a strange problem, I've searched the archives but can't seem to
find
a fix.  Whats worse is that it doesn't give more detail on the error, 
for
example what file and line the error occurs on...

Denise

-Original Message-
From: John Turner [mailto:[EMAIL PROTECTED] Sent: Tuesday, 
June
03, 2003 12:18 PM
To: Tomcat Users List
Subject: Re: Strange mod_jk error



The mod_jk.conf file isn't getting used unless there is an Include
directive in httpd.conf to include it.
Make sure you have these lines somewhere, either hard-coded in
httpd.conf, or at the top of your mod_jk.conf file:
JkWorkersFile "/path/to/workers.properties"
JkLogFile "/path/to/mod_jk.log"
JkLogLevel emerg
John

On Tue, 3 Jun 2003 12:05:09 -0400, Denise Mangano
<[EMAIL PROTECTED]> wrote:
I noticed that having the worker named worker wasn't the smartest 
thing, so I changed it to worker1 and still got the same problem.

Now the strange thing is, I did not have an include statement in my
httpd.conf.  I had originally set this up a while ago, so to be honest 
I am not sure why I didn't have it there, because I remember putting it 
in when I
followed your how-to.  So this means that I have been using the auto
generated mod_jk.conf (is that right?).

I tried to 1) change the worker name to ajp13 and 2) include the edited
mod_jk.conf.  I am still getting the error message when I start up 
apache stating that there was an error opening the workers and jk will 
not work. When I try to access a jsp page I still get the same error 
message in my mod_jk.log stating that it is looking for worker ajp13, 
but the worker is not found.  It appears that the actual problem is 
opening the workers.properties... The system finds it, sets the rules, 
attempts the matches the URI request, and eventually finds a context 
match for the worker.  The problem is when looking for the
worker it does not see it.
It
would make sense that this would happen since Apache is having trouble 
opening the workers.properties file.  The strange thing is that Apache 
is also stating there is "No such file or directory" but the file is in 
fact
there, and all the paths pointing to it are correct.

Any other suggestions?  Should I maybe post my files?

Thanks,
Denise
-Original Message-
From: John Turner [mailto:[EMAIL PROTECTED] Sent: Tuesday,
June
03, 2003 9:59 AM
To: Tomcat Users List
Subject: Re: Strange mod_jk error
On Tue, 3 Jun 2003 09:51:14 -0400, Denise Mangano 
<[EMAIL PROTECTED]> wrote:

1) It is possible that I am still using the auto generated mod_jk.conf
file
- which would have worked previously when I had one default host set 
up,
but
will not work now that I have added in the virtual hosts?  How can I 
check
this to make sure that I am using my version of mod_jk.conf found in
/tomcat/conf and not the auto generated one in /tomcat/conf/auto?  The
problem with this possibility is that I get this error message when 
trying
either Virtual Host (even the one that is in the generated 
mod_jk.conf) .
There's no way to check, as far as I know.  It would be based on the 
Include statement in httpd.conf.  Is it possible that your Apache 
restart didn't actually happen?  Sometimes the "restart" option doesn't 
behave...I have more luck actually shutting Apache down, then starting 
it back up.

2) The permissions are 

Re: Strange mod_jk error

[John Turner]

Yes, 8009 needs to be "open" on your firewall, but only if the Tomcat 
server has its own internal firewall.  If by "firewall" you mean an 
external firewall, on a machine physically distinct from the Tomcat server, 
then no, all you need is 80 and 443.  Some operating systems, like Red Hat, 
come with a software firewall (iptables or ipchains) that is installed by 
default and is sometimes configured to be very restrictive.

John

On Tue, 3 Jun 2003 13:51:27 -0400, Denise Mangano <[EMAIL PROTECTED]> 
wrote:

Ok, dumb question.  Does port 8009 have to be open on my firewall then?  
If
so then how was it possibly working before?  I can only telnet on port 80
and port 443 (These are the only ports open on my firewall).

The results of the netstat are:
tcp0  0 *:32768 *:* 
LISTEN

tcp0  0 *:login *:* 
LISTEN

tcp0  0 *:vboxd *:* 
LISTEN

tcp0  0 *:sunrpc*:* 
LISTEN

tcp0  0 *:ssh   *:* 
LISTEN

tcp0  0 cdiserv:smtp*:* 
LISTEN

unix  2  [ ACC ] STREAM LISTENING 1257   /dev/gpmctl
unix  2  [ ACC ] STREAM LISTENING 1324
/tmp/.font-unix/fs7100
I am getting the feeling something is not right... But it did work at one
point with the single virtual host...
In httpd.conf
Port 80
BindAddress *
NameVirtualHost *

Listen 80
Listen 443

ServerName www (overwritten within Vhosts)
Thanks,
Denise
-Original Message-
From: PELOQUIN,JEFFREY (HP-Boise,ex1) [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, June 03, 2003 1:06 PM
To: 'Tomcat Users List'
Subject: RE: Strange mod_jk error

Denise,

I could not see in the email trail if it ever was determined that you 
truly
have a listener on the ajp13 port for the problem domain

if you do
telnet test.mysite.com 8009
or whatever the correct domain/port for your current configuration do you
get a valid telnet response?
also if you are on linux, you can do a netstat -a | grep LISTEN to see 
what
is addresses and port have listeners

Jeff

-Original Message-
From: Denise Mangano [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 03, 2003 10:58 AM
To: 'Tomcat Users List'
Subject: RE: Strange mod_jk error
Well it throws me two warnings:

[Tue Jun  3 11:16:23 2003] [warn] VirtualHost www.ptp.com:80 overlaps 
with
VirtualHost test.ptp.com:80, the first has precedence, perhaps you need a
NameVirtualHost directive [Tue Jun  3 11:16:23 2003] [warn] VirtualHost 
www.ptp.com:443 overlaps with
VirtualHost test.ptp.com:443, the first has precedence, perhaps you need 
a
NameVirtualHost directive

I'm in the process of trying to get this problem worked out.  Other than
this, the syntax is OK.
Denise

-Original Message-
From: John Turner [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 
03, 2003 12:45 PM
To: Tomcat Users List
Subject: Re: Strange mod_jk error



A "configtest" of Apache returns "Syntax OK"?

John

On Tue, 3 Jun 2003 12:50:25 -0400, Denise Mangano 
<[EMAIL PROTECTED]> wrote:

Those lines are at the top of my mod_jk.conf (the one I edited) and my
Include statement points to my version of the mod_jk.conf.
This is a strange problem, I've searched the archives but can't seem
to
find
a fix.  Whats worse is that it doesn't give more detail on the error, 
for
example what file and line the error occurs on...

Denise

-Original Message-
From: John Turner [mailto:[EMAIL PROTECTED] Sent: Tuesday,
June
03, 2003 12:18 PM
To: Tomcat Users List
Subject: Re: Strange mod_jk error


The mod_jk.conf file isn't getting used unless there is an Include 
directive in httpd.conf to include it.

Make sure you have these lines somewhere, either hard-coded in 
httpd.conf, or at the top of your mod_jk.conf file:

JkWorkersFile "/path/to/workers.properties"
JkLogFile "/path/to/mod_jk.log"
JkLogLevel emerg
John

On Tue, 3 Jun 2003 12:05:09 -0400, Denise Mangano 
<[EMAIL PROTECTED]> wrote:

I noticed that having the worker named worker wasn't the smartest
thing, so I changed it to worker1 and still got the same problem.
Now the strange thing is, I did not have an include statement in my 
httpd.conf.  I had originally set this up a while ago, so to be honest 
I am not sure why I didn't have it there, because I remember putting it 
in when I followed your how-to.  So this means that I have been using 
the auto generated mod_jk.conf (is that right?).

I tried to 1) change the worker name to ajp13 and 2) include the
edited
mod_jk.conf.  I am still getting the error message when I start up 
apache stating that there was an error opening the workers and jk will 
not work. When I try to access a jsp page I still get the same error 
message in my mod_

RE: Strange mod_jk error

[PELOQUIN,JEFFREY (HP-Boise,ex1)]

You might check in your /etc/services file to see if 8009 corresponds to one
of the names listed in your net stat

you might try the netstat and change the grep to 8009 and see if there is
any mention of it at all.


Given the fact that your original error report was

In jk_endpoint_t::service, Error sd = -1

I would hazard a guess that everything was working originally except that
you had the ajp13 port worngly specified in your workers.properties or in
your server.xml.  From my own tests I can only get anjk_endpoint_t::service
error if apache is able to find the worker but the i/port are wrong in
worker.properties.  You current problem of not being able to find a worker
is most likely an artifact of trying changing things in your configuration
files one too many times.

Suggestion:


1) Stop all instances of apache
2) Stop all instances of tomcat
use kill -9 if need be to ensure no JVMs are left (Unless of course this is
a production server and you cannot be that indiscrimate)

3)Start tomcat

4) telnet tomcat-ajp13-domain tomcat-ajp13-port  (as specified in server.xml
for the ajp13 connector tag)
5) netstat -a | grep LISTEN

one of these tests should demonstrate the existence of your listener.  If
not check catalina.out for ajp13 error messages


6) once you are confident that your listener is correct recreate your
workers.property to have the correct tomcat-ajp13-domain tomcat-ajp13-port
information entered.

7) check that your virtual host is loading this file or place the
JkWorkersFile command outside all virtual host to make sure everyone uses
it.

8) restart apache and watch the mod_jk logs and see that it load your
workers file correctly

9) hit webpage and hopefully it will work.

-Original Message-
From: Denise Mangano [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 03, 2003 11:51 AM
To: 'Tomcat Users List'
Subject: RE: Strange mod_jk error


Ok, dumb question.  Does port 8009 have to be open on my firewall then?  If
so then how was it possibly working before?  I can only telnet on port 80
and port 443 (These are the only ports open on my firewall).

The results of the netstat are:
tcp0  0 *:32768 *:* LISTEN

tcp0  0 *:login *:* LISTEN

tcp0  0 *:vboxd *:* LISTEN

tcp0  0 *:sunrpc*:* LISTEN

tcp0  0 *:ssh   *:* LISTEN

tcp0  0 cdiserv:smtp*:* LISTEN

unix  2  [ ACC ] STREAM LISTENING 1257   /dev/gpmctl
unix  2  [ ACC ] STREAM LISTENING 1324
/tmp/.font-unix/fs7100


I am getting the feeling something is not right... But it did work at one
point with the single virtual host...

In httpd.conf
Port 80
BindAddress *
NameVirtualHost *

  Listen 80
  Listen 443

ServerName www (overwritten within Vhosts)

Thanks,
Denise


-Original Message-
From: PELOQUIN,JEFFREY (HP-Boise,ex1) [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, June 03, 2003 1:06 PM
To: 'Tomcat Users List'
Subject: RE: Strange mod_jk error


Denise,

I could not see in the email trail if it ever was determined that you truly
have a listener on the ajp13 port for the problem domain

if you do
telnet test.mysite.com 8009 

or whatever the correct domain/port for your current configuration do you
get a valid telnet response?

also if you are on linux, you can do a netstat -a | grep LISTEN to see what
is addresses and port have listeners

Jeff

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Strange mod_jk error

[Denise Mangano]

John,

Actually, the virtual hosts were hard coded in my mod_jk.conf file.  I
changed that to be:

NameVirtualHost *

   ServerName www.ptp.com
   ...


   ServerName test.ptp.com
   ...


This seemed to get rid of the conflict on port 80.  I changed the SSL
virtual host to be for *:443 for the live site and just * for the test site,
and this seemed to get rid of the conflict.

However, I am still getting the error opening workers.

Thanks,
Denise


-Original Message-
From: John Turner [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, June 03, 2003 2:13 PM
To: Tomcat Users List
Subject: Re: Strange mod_jk error



OK, that tells me that you have multiple VirtualHosts going on, which means 
that you probably have multiple/conflicting JkMount and workers.

Probably, there is a hard-coded VirtualHost in httpd.conf, in addition to 
the definitions being included from mod_jk.conf.  That would explain 
(possibly) some of the problems you are experiencing...for example, the 
configuration you want is the second one, but only the first is being used 
by Apache, or vice versa.

"configtest" should return "Syntax OK".

John

On Tue, 3 Jun 2003 12:58:26 -0400, Denise Mangano <[EMAIL PROTECTED]> 
wrote:

> Well it throws me two warnings:
>
> [Tue Jun  3 11:16:23 2003] [warn] VirtualHost www.ptp.com:80 overlaps
> with
> VirtualHost test.ptp.com:80, the first has precedence, perhaps you need a
> NameVirtualHost directive [Tue Jun  3 11:16:23 2003] [warn] VirtualHost 
> www.ptp.com:443 overlaps with
> VirtualHost test.ptp.com:443, the first has precedence, perhaps you need 
> a
> NameVirtualHost directive
>
> I'm in the process of trying to get this problem worked out.  Other 
> than this, the syntax is OK.
>
> Denise
>
> -Original Message-
> From: John Turner [mailto:[EMAIL PROTECTED] Sent: Tuesday, 
> June
> 03, 2003 12:45 PM
> To: Tomcat Users List
> Subject: Re: Strange mod_jk error
>
>
>
> A "configtest" of Apache returns "Syntax OK"?
>
> John
>
> On Tue, 3 Jun 2003 12:50:25 -0400, Denise Mangano
> <[EMAIL PROTECTED]> wrote:
>
>> Those lines are at the top of my mod_jk.conf (the one I edited) and 
>> my
>> Include statement points to my version of the mod_jk.conf.
>>
>> This is a strange problem, I've searched the archives but can't seem 
>> to find a fix.  Whats worse is that it doesn't give more detail on 
>> the error, for
>> example what file and line the error occurs on...
>>
>> Denise
>>
>> -Original Message-
>> From: John Turner [mailto:[EMAIL PROTECTED] Sent: Tuesday,
>> June
>> 03, 2003 12:18 PM
>> To: Tomcat Users List
>> Subject: Re: Strange mod_jk error
>>
>>
>>
>> The mod_jk.conf file isn't getting used unless there is an Include 
>> directive in httpd.conf to include it.
>>
>> Make sure you have these lines somewhere, either hard-coded in 
>> httpd.conf, or at the top of your mod_jk.conf file:
>>
>> JkWorkersFile "/path/to/workers.properties"
>> JkLogFile "/path/to/mod_jk.log"
>> JkLogLevel emerg
>>
>> John
>>
>> On Tue, 3 Jun 2003 12:05:09 -0400, Denise Mangano 
>> <[EMAIL PROTECTED]> wrote:
>>
>>> I noticed that having the worker named worker wasn't the smartest
>>> thing, so I changed it to worker1 and still got the same problem.
>>>
>>> Now the strange thing is, I did not have an include statement in my 
>>> httpd.conf.  I had originally set this up a while ago, so to be 
>>> honest I am not sure why I didn't have it there, because I remember 
>>> putting it in when I followed your how-to.  So this means that I 
>>> have been using the auto generated mod_jk.conf (is that right?).
>>>
>>> I tried to 1) change the worker name to ajp13 and 2) include the 
>>> edited mod_jk.conf.  I am still getting the error message when I 
>>> start up apache stating that there was an error opening the workers 
>>> and jk will not work. When I try to access a jsp page I still get 
>>> the same error message in my mod_jk.log stating that it is looking 
>>> for worker ajp13, but the worker is not found.  It appears that the 
>>> actual problem is opening the workers.properties... The system finds 
>>> it, sets the rules, attempts the matches the URI request, and 
>>> eventually finds a context match for the worker.  The problem is 
>>> when looking for the
>> worker it does not see it.
>>> It
>>> would make sense that this would happen since Apache is having 
>>> trouble
>>> openin

RE: building mod_jk error

[Michal Biernacki]

> www# apxs -o
> mod_jk.so -I../jk -I/usr/local/jdk1.2.2/include -I/usr/local/jdk1.2
> .2/include/linux -c *.c ../jk/*.c
> apxs:Error: Sorry, no DSO support for Apache available

Here is the answet. You didn't install apxs. If you are working with
redhat distribution you will find it in apache-devel package.

rpm -hiv apache-devel-1.3.14.i386.rpm

Regards

Michal Biernacki

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Re: building mod_jk error

[george]

O~~
Thank you very much!!!
but i'm using FreeBSD + Apache 1.3.12
how to install apxs??
Thank

- Original Message - 
From: "Michal Biernacki" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, January 09, 2001 4:42 PM
Subject: RE: building mod_jk error


> > www# apxs -o
> > mod_jk.so -I../jk -I/usr/local/jdk1.2.2/include -I/usr/local/jdk1.2
> > .2/include/linux -c *.c ../jk/*.c
> > apxs:Error: Sorry, no DSO support for Apache available
> 
> Here is the answet. You didn't install apxs. If you are working with
> redhat distribution you will find it in apache-devel package.
> 
> rpm -hiv apache-devel-1.3.14.i386.rpm
> 
> Regards
> 
> Michal Biernacki
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]
> 
> 
> 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Re: building mod_jk error

[Bill Kocik]

> > www# apxs -o
> > mod_jk.so -I../jk -I/usr/local/jdk1.2.2/include -I/usr/local/jdk1.2
> > .2/include/linux -c *.c ../jk/*.c
> > apxs:Error: Sorry, no DSO support for Apache available
> 
> Here is the answet. You didn't install apxs. If you are working with
> redhat distribution you will find it in apache-devel package.

Actually, yes he did, as it's apxs that throws out the error.
What he didn't do, was compile DSO support into Apache. 

Re-run the Apache configure script specifying
"--enable-module=so", and recompile/install it.

-- 
Bill Kocik
Taos - Santa Clara, CA
http://www.taos.com
[EMAIL PROTECTED]

Quantum Mechanics: The dreams stuff is made of.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

RE: building mod_jk error

[Michal Biernacki]

> > Here is the answer. You didn't install apxs. If you are working with
> > redhat distribution you will find it in apache-devel package.
> 
> Actually, yes he did, as it's apxs that throws out the error.
> What he didn't do, was compile DSO support into Apache. 
> 
> Re-run the Apache configure script specifying
> "--enable-module=so", and recompile/install it.

Right! Made a mistake.

./configure --enable-module=so
make
make install

and that we can build mod_jk.so;)

-- 
Michal Biernacki

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

RE: mod_jk error flushing ...

[Phillip Qin]

I kept these messages too although I only installed Tomcat 5. It happened in
Tomcat 4.1 as well.

-Original Message-
From: Clara Ines Pena de Carrillo [mailto:[EMAIL PROTECTED] 
Sent: November 4, 2004 9:21 AM
To: Tomcat Users List
Subject: mod_jk error flushing ...



Hi everybody, 

I have installed tomcat 4.1.24, apache 2.0.47, jdk 1.4.2 and 
mod_jk2-2.0.43 in a Sun Solaris 8 machine. Everything have worked more or 
less ok since today that the system crashed !!!. I got the 
following 
error messages in the apache error_log file:


[Thu Nov 04 08:32:56 2004] [error] mod_jk child init 1 -2
[Thu Nov 04 08:34:00 2004] [error] jk2_init() Can't find child 1407 in 
scoreboard
[Thu Nov 04 08:34:00 2004] [error] mod_jk child init 1 -2
[Thu Nov 04 08:34:39 2004] [error] jk2_init() Can't find child 1414 in 
scoreboard
[Thu Nov 04 08:34:39 2004] [error] mod_jk child init 1 -2
[Thu Nov 04 08:34:39 2004] [error] jk2_init() Can't find child 1416 in 
scoreboard
[Thu Nov 04 08:34:39 2004] [error] mod_jk child init 1 -2
mod_jk: Error flushing

[Thu Nov 04 08:35:51 2004] [error] Error ajp_process_callback - write 
failed
[Thu Nov 04 08:35:51 2004] [error] ajp13.service() ajpGetReply recoverable 
error 3
[Thu Nov 04 08:35:51 2004] [error] Error ajp_process_callback - write 
failed
[Thu Nov 04 08:35:51 2004] [error] ajp13.service() ajpGetReply recoverable 
error 3
[Thu Nov 04 08:35:51 2004] [error] ajp13.service() Error  forwarding 
ajp13:localhost:8009 1 0

[Thu Nov 04 08:47:31 2004] [error] mod_jk.handler() Error connecting to 
tomcat 3


do you have any idea about why these errors are appearing ?


I would appreciate your help,


Clara



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


!DSPAM:418a3b7147583305085000!

RE: mod_jk error flushing ...

[Clara Ines Pena de Carrillo]

On Thu, 4 Nov 2004, Phillip Qin wrote:

> I kept these messages too although I only installed Tomcat 5. It happened in
> Tomcat 4.1 as well.
> 

ok, thank you. I will try to change my tomcat version.

Clara

> -Original Message-
> From: Clara Ines Pena de Carrillo [mailto:[EMAIL PROTECTED] 
> Sent: November 4, 2004 9:21 AM
> To: Tomcat Users List
> Subject: mod_jk error flushing ...
> 
> 
> 
> Hi everybody, 
> 
> I have installed tomcat 4.1.24, apache 2.0.47, jdk 1.4.2 and 
> mod_jk2-2.0.43 in a Sun Solaris 8 machine. Everything have worked more or 
> less ok since today that the system crashed !!!. I got the 
> following 
> error messages in the apache error_log file:
> 
> 
> [Thu Nov 04 08:32:56 2004] [error] mod_jk child init 1 -2
> [Thu Nov 04 08:34:00 2004] [error] jk2_init() Can't find child 1407 in 
> scoreboard
> [Thu Nov 04 08:34:00 2004] [error] mod_jk child init 1 -2
> [Thu Nov 04 08:34:39 2004] [error] jk2_init() Can't find child 1414 in 
> scoreboard
> [Thu Nov 04 08:34:39 2004] [error] mod_jk child init 1 -2
> [Thu Nov 04 08:34:39 2004] [error] jk2_init() Can't find child 1416 in 
> scoreboard
> [Thu Nov 04 08:34:39 2004] [error] mod_jk child init 1 -2
> mod_jk: Error flushing
> 
> [Thu Nov 04 08:35:51 2004] [error] Error ajp_process_callback - write 
> failed
> [Thu Nov 04 08:35:51 2004] [error] ajp13.service() ajpGetReply recoverable 
> error 3
> [Thu Nov 04 08:35:51 2004] [error] Error ajp_process_callback - write 
> failed
> [Thu Nov 04 08:35:51 2004] [error] ajp13.service() ajpGetReply recoverable 
> error 3
> [Thu Nov 04 08:35:51 2004] [error] ajp13.service() Error  forwarding 
> ajp13:localhost:8009 1 0
> 
> [Thu Nov 04 08:47:31 2004] [error] mod_jk.handler() Error connecting to 
> tomcat 3
> 
> 
> do you have any idea about why these errors are appearing ?
> 
> 
> I would appreciate your help,
> 
> 
> Clara
> 
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> !DSPAM:418a3b7147583305085000!
> 

-- 
Clara Ines Pe¤a de Carrillo
Divisi¢n de Servicios de Informaci¢n
Universidad Industrial de Santander
Bucaramanga, Colombia




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: mod_jk error flushing ...

[Phillip Qin]

Sorry, typo. I mean I got these messages too since I started using Tomcat
4.1 and now Tomcat 5. 

-Original Message-
From: Clara Ines Pena de Carrillo [mailto:[EMAIL PROTECTED] 
Sent: November 4, 2004 9:59 AM
To: Tomcat Users List
Subject: RE: mod_jk error flushing ...


On Thu, 4 Nov 2004, Phillip Qin wrote:

> I kept these messages too although I only installed Tomcat 5. It 
> happened in Tomcat 4.1 as well.
> 

ok, thank you. I will try to change my tomcat version.

Clara

> -Original Message-
> From: Clara Ines Pena de Carrillo [mailto:[EMAIL PROTECTED]
> Sent: November 4, 2004 9:21 AM
> To: Tomcat Users List
> Subject: mod_jk error flushing ...
> 
> 
> 
> Hi everybody,
> 
> I have installed tomcat 4.1.24, apache 2.0.47, jdk 1.4.2 and
> mod_jk2-2.0.43 in a Sun Solaris 8 machine. Everything have worked more or 
> less ok since today that the system crashed !!!. I got the 
> following 
> error messages in the apache error_log file:
> 
> 
> [Thu Nov 04 08:32:56 2004] [error] mod_jk child init 1 -2 [Thu Nov 04 
> 08:34:00 2004] [error] jk2_init() Can't find child 1407 in scoreboard
> [Thu Nov 04 08:34:00 2004] [error] mod_jk child init 1 -2
> [Thu Nov 04 08:34:39 2004] [error] jk2_init() Can't find child 1414 in 
> scoreboard
> [Thu Nov 04 08:34:39 2004] [error] mod_jk child init 1 -2
> [Thu Nov 04 08:34:39 2004] [error] jk2_init() Can't find child 1416 in 
> scoreboard
> [Thu Nov 04 08:34:39 2004] [error] mod_jk child init 1 -2
> mod_jk: Error flushing
> 
> [Thu Nov 04 08:35:51 2004] [error] Error ajp_process_callback - write
> failed
> [Thu Nov 04 08:35:51 2004] [error] ajp13.service() ajpGetReply recoverable

> error 3
> [Thu Nov 04 08:35:51 2004] [error] Error ajp_process_callback - write 
> failed
> [Thu Nov 04 08:35:51 2004] [error] ajp13.service() ajpGetReply recoverable

> error 3
> [Thu Nov 04 08:35:51 2004] [error] ajp13.service() Error  forwarding 
> ajp13:localhost:8009 1 0
> 
> [Thu Nov 04 08:47:31 2004] [error] mod_jk.handler() Error connecting 
> to
> tomcat 3
> 
> 
> do you have any idea about why these errors are appearing ?
> 
> 
> I would appreciate your help,
> 
> 
> Clara
> 
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> 
> 

-- 
Clara Ines Pe¤a de Carrillo
Divisi¢n de Servicios de Informaci¢n
Universidad Industrial de Santander
Bucaramanga, Colombia




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


!DSPAM:418a443a49555369657494!

mod_jk error handling question

[Paulsen, Jay M]

Environment:
Apache 2.0.52
mod_jk 1.2.7-beta-2
Tomcat 5.5.4

I've set up Tomcat with and AJP1.3 Connector to handle requests for web
apps from Apache.  I'd like to be able to set up an ErrorDocument
directive for apache to forward the user to a custom error page when
tomcat is unavailable.  This page would inform the user that maintenance
is being performed on the web app and so on.

When I test this, the http status code that gets returned by mod_jk is
500 (internal server error).  This seems too generic to me as it
encompasses all kinds of other errors that mod_jk could experience.  I
was thinking that mod_jk should return 503 (service unavailable) instead
when tomcat cannot be contacted.

I modified apache-2.0/mod_jk.c (line 1858) to return
HTTP_SERVICE_UNAVAILABLE instead of HTTP_INTERNAL_SERVICE_ERROR.  With
this change mod_jk now returns 503 when tomcat cannot be contacted, but
I have no idea if this is the right place to make this change.  

Is there a better way to handle this or is this an acceptable change?
I'd like to fix it with an Apache source code change as a last resort if
possible.

Any insight is appreciated.


Regards,
Jay 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: mod_jk error under load

[Anthony Milbourne]

Hi

146 is a socket connection error.
Try checking your workers.properties file (or the JBoss file that generates
it ?) and making sure that the only connectors mentioned in workers.list
also have connectors defined in server.xml.  Specifically - check there
isn't an ajp12 in workers.properties and not in server.xml.

Hope that helps.

Anthony.

> -Original Message-
> From: David Ward [SMTP:[EMAIL PROTECTED]]
> Sent: 27 September 2002 17:57
> To:   [EMAIL PROTECTED]
> Subject:  mod_jk error under load
> 
> In running an automated load test against our app, we get the following 
> errors in or jk.log file:
> 
> [jk_connect.c (143)]: jk_open_socket, connect() failed errno = 146
> [jk_ajp12_worker.c (152)]: In jk_endpoint_t::service, Error sd = -1
> [jk_connect.c (143)]: jk_open_socket, connect() failed errno = 146
> [jk_ajp12_worker.c (152)]: In jk_endpoint_t::service, Error sd = -1
> [jk_connect.c (143)]: jk_open_socket, connect() failed errno = 146
> [jk_ajp12_worker.c (152)]: In jk_endpoint_t::service, Error sd = -1
> [jk_connect.c (143)]: jk_open_socket, connect() failed errno = 146
> [jk_ajp12_worker.c (152)]: In jk_endpoint_t::service, Error sd = -1
> [jk_connect.c (143)]: jk_open_socket, connect() failed errno = 146
> [jk_ajp12_worker.c (152)]: In jk_endpoint_t::service, Error sd = -1
> [jk_connect.c (143)]: jk_open_socket, connect() failed errno = 146
> 
> Anyone know what these errors are? I can't find anything conclusive 
> about them searching various lists/forums.
> 
> We are running Apache 1.3.12 on a Solaris 7 Ultra 10 using mod_jk/ajp12 
> to talk to JBoss-2.4.7_Tomcat-3.2.3 on a Solaris 7 E250, JDK 1.3.1_02.
> 
> The symptoms we see are that the number of httpd processes maxes out on 
> the web server box, though the CPU is almost completely idle. The weird 
> thing is that the app server is mostly idle too, and doing a thread dump 
> on the java (jboss+tomcat in same vm) process shows that there are lots 
> of threads waiting for work to do. Once we stop the load test, things 
> are still messed up until I restart apache, then we can access the app 
> again. Note that I didn't have to touch the app server at all. Accessing 
> URLs that aren't configured to go through mod_jk have no problem, until 
> the max http children process gets reached, of course...
> 
> I haven't gotten a response from the Tomcat forum at JGuru.
> 
> Thanks all,
> David
> 
> 
> --
> To unsubscribe, e-mail:
> <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail:
> <mailto:[EMAIL PROTECTED]>


**
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.
This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.
www.mimesweeper.com
**


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Re: mod_jk error under load

[Marc]

Hi, where can I find a description for each 'errno'?
I receive errno = 110 when I try to access tomcat connecting to a *.jsp page
through apache.

Thank you!!!

Marc

Anthony Milbourne wrote:

> Hi
>
> 146 is a socket connection error.
> Try checking your workers.properties file (or the JBoss file that generates
> it ?) and making sure that the only connectors mentioned in workers.list
> also have connectors defined in server.xml.  Specifically - check there
> isn't an ajp12 in workers.properties and not in server.xml.
>
> Hope that helps.
>
> Anthony.
>
> > -Original Message-
> > From: David Ward [SMTP:[EMAIL PROTECTED]]
> > Sent: 27 September 2002 17:57
> > To:   [EMAIL PROTECTED]
> > Subject:  mod_jk error under load
> >
> > In running an automated load test against our app, we get the following
> > errors in or jk.log file:
> >
> > [jk_connect.c (143)]: jk_open_socket, connect() failed errno = 146
> > [jk_ajp12_worker.c (152)]: In jk_endpoint_t::service, Error sd = -1
> > [jk_connect.c (143)]: jk_open_socket, connect() failed errno = 146
> > [jk_ajp12_worker.c (152)]: In jk_endpoint_t::service, Error sd = -1
> > [jk_connect.c (143)]: jk_open_socket, connect() failed errno = 146
> > [jk_ajp12_worker.c (152)]: In jk_endpoint_t::service, Error sd = -1
> > [jk_connect.c (143)]: jk_open_socket, connect() failed errno = 146
> > [jk_ajp12_worker.c (152)]: In jk_endpoint_t::service, Error sd = -1
> > [jk_connect.c (143)]: jk_open_socket, connect() failed errno = 146
> > [jk_ajp12_worker.c (152)]: In jk_endpoint_t::service, Error sd = -1
> > [jk_connect.c (143)]: jk_open_socket, connect() failed errno = 146
> >
> > Anyone know what these errors are? I can't find anything conclusive
> > about them searching various lists/forums.
> >
> > We are running Apache 1.3.12 on a Solaris 7 Ultra 10 using mod_jk/ajp12
> > to talk to JBoss-2.4.7_Tomcat-3.2.3 on a Solaris 7 E250, JDK 1.3.1_02.
> >
> > The symptoms we see are that the number of httpd processes maxes out on
> > the web server box, though the CPU is almost completely idle. The weird
> > thing is that the app server is mostly idle too, and doing a thread dump
> > on the java (jboss+tomcat in same vm) process shows that there are lots
> > of threads waiting for work to do. Once we stop the load test, things
> > are still messed up until I restart apache, then we can access the app
> > again. Note that I didn't have to touch the app server at all. Accessing
> > URLs that aren't configured to go through mod_jk have no problem, until
> > the max http children process gets reached, of course...
> >
> > I haven't gotten a response from the Tomcat forum at JGuru.
> >
> > Thanks all,
> > David
> >
> >
> > --
> > To unsubscribe, e-mail:
> > <mailto:[EMAIL PROTECTED]>
> > For additional commands, e-mail:
> > <mailto:[EMAIL PROTECTED]>
>
> **
> This email and any files transmitted with it are confidential and
> intended solely for the use of the individual or entity to whom they
> are addressed. If you have received this email in error please notify
> the system manager.
> This footnote also confirms that this email message has been swept by
> MIMEsweeper for the presence of computer viruses.
> www.mimesweeper.com
> **
>
> --
> To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

mod_jk error and Header dumping

[Ben Ricker]

I am running using Apache 1.2.6 talking to two Tomcat 4.0.5 (I think
that is the version number; how do you verify it? The Tomcat default
page comes up with just '4.0') listening on two separate ports. 

I am seeing a strange problem. We have a customized web application
which we run through Tomcat. In one particular module, we have an issue:
on several pages sent from Apache, there is HTTP protocol header
information displayed at the top of the page. Here is some text from it:

"HTTP/1.1 200 OK Date: Yue, 19 Nov 2002 22:31:05 GMT Server:
Apache/1.3.26 (Unix) mod_jk/1.2 Keep-Alive:..."

At roughly the same time we get that text on the client's screen, we see
the following logged to mod_jk.log:

[Wed Nov 20 09:06:38 2002]  [jk_ajp_common.c (679)]: ajp_connection_tcp_get_message: 
Error - jk_tcp_socket_recvfull failed
[Wed Nov 20 09:06:38 2002]  [jk_ajp_common.c (1041)]: Error reading reply
[Wed Nov 20 09:06:38 2002]  [jk_ajp_common.c (1178)]: In jk_endpoint_t::service, 
ajp_get_reply failed in send loop 0

I cannot verify that the error thrown in mod_jk is exactly correlated
with the dumping of the strange text on the screen, but it does look
like it happens at the roughly the same time (within 3 minutes or so).

Any guidance would be appreciated.

Ben Ricker
Wellinx.com


--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

hp unix mod_jk error -help

[Paula_J_Bosch]

Apache 2 Tomcat 4

Does anyone know why I am getting this error?  I compiled mod_jk using
hp-unix.sh.  I received no errors.  When I try to test httpd.conf I get the
following...

$ apachectl configtest
Syntax error on line 251 of /opt/apache2/etc/httpd.conf:
Cannot load /opt/apache2/modules/mod_jk.so into server: Unresolved symbol:
ap_ps
trdup (code)  from /opt/apache2/modules/mod_jk.so
$


--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

mod_jk Error by stress test.

[Jacob FanChiang]

Hi,
I use a software called LoadRunner to stress my apache1.2.30 + tomcat-3.3-b1
on Redhat Linux-7.1 simulate 200 users.
There are all these kind of message in my logs/mod_jk.log
Could somebody tell me what should I do to avoid this problem??
Thanks

[Thu Oct 18 09:01:07 2001]  [jk_ajp13_worker.c (226)]:
connection_tcp_get_message: Error - jk_tcp_so
cket_recvfull failed
[Thu Oct 18 09:01:07 2001]  [jk_ajp13_worker.c (681)]: Error reading reply
[Thu Oct 18 09:01:07 2001]  [jk_ajp13_worker.c (805)]: In
jk_endpoint_t::service, get_reply failed i
n send loop 0
[Thu Oct 18 09:01:07 2001]  [jk_connect.c (143)]: jk_open_socket, connect()
failed errno = 111
[Thu Oct 18 09:01:07 2001]  [jk_ajp13_worker.c (194)]: In
jk_endpoint_t::connect_to_tomcat, failed e
rrno = 111
[Thu Oct 18 09:01:07 2001]  [jk_ajp13_worker.c (604)]: Error connecting to
the Tomcat process.
[Thu Oct 18 09:01:07 2001]  [jk_ajp13_worker.c (808)]: In
jk_endpoint_t::service, send_request faile
d in send loop 1
[Thu Oct 18 09:01:07 2001]  [jk_connect.c (143)]: jk_open_socket, connect()
failed errno = 111
[Thu Oct 18 09:01:07 2001]  [jk_ajp13_worker.c (194)]: In
jk_endpoint_t::connect_to_tomcat, failed e
rrno = 111
[Thu Oct 18 09:01:07 2001]  [jk_ajp13_worker.c (604)]: Error connecting to
the Tomcat process.
[Thu Oct 18 09:01:07 2001]  [jk_ajp13_worker.c (808)]: In
jk_endpoint_t::service, send_request faile
d in send loop 2
[Thu Oct 18 09:45:54 2001]  [jk_ajp13_worker.c (350)]: Error
ajp13_process_callback - write failed
[Thu Oct 18 09:45:54 2001]  [jk_ajp13_worker.c (801)]: In
jk_endpoint_t::service, get_reply failed w
ithout recovery in send loop 0


Jacob FanChiang

Re: mod_jk error (jk_map.c ERROR)

[Adam Denenberg]

I have identified the problem to be in the jk_map.c file.  For some reason
when jk_worker.c calls "map_get()" in jk_map.c, it does not get a value back
and thus produces this error.

 Anyone good in C or who works on mod_jk source know why this would happen ?

 thanks
Adam

On 3/3/03 9:12 AM, "Adam Denenberg" <[EMAIL PROTECTED]> wrote:

> Thanks john.  Does this error come from a problem in the workers.properties
> file, or an entry in the httpd.conf do you know?
> 
> It seems that mod_jk finds the match fine in the httpd.conf file, but then
> when tries to use a worker it for some reason can not.  I have debug on but
> am missing the piece that it is specifically dying on.
> 
> thanks again for the help.
> 
> Adam
> 
> On 3/3/03 8:50 AM, "Turner, John" <[EMAIL PROTECTED]> wrote:
> 
>> 
>> No other ideas, really.  In the past, problems like this have come down to
>> something really simple, such as using an el ("l") instead of a one ("1") in
>> "ajp13" and other typo-related problems (or permission problems).  My
>> eyesight isn't as good as it used to be, but it looks like you have "ajp13"
>> typed out correctly in all the places where it needs to be.
>> 
>> John
>> 
>>> -Original Message-
>>> From: Adam Denenberg [mailto:[EMAIL PROTECTED]
>>> Sent: Monday, March 03, 2003 8:24 AM
>>> To: Tomcat Users List
>>> Subject: Re: mod_jk error
>>> 
>>> 
>>> Hmm, tried that but still no luck.
>>> 
>>>  I still get the following
>>> 
>>>  [Mon Mar 03 08:16:00 2003]  [jk_uri_worker_map.c (477)]:
>>> Attempting to map
>>> URI '/examples/jsp/dates/date.jsp'
>>> 
>>>  [Mon Mar 03 08:16:00 2003]  [jk_uri_worker_map.c (558)]:
>>> jk_uri_worker_map_t::map_uri_to_worker, Found a suffix match
>>> ajp13 -> *.jsp
>>> 
>>> [Mon Mar 03 08:16:00 2003]  [jk_worker.c (132)]: Into
>>> wc_get_worker_for_name
>>> ajp13
>>> 
>>> [Mon Mar 03 08:16:00 2003]  [jk_worker.c (136)]:
>>> wc_get_worker_for_name,
>>> done did not found a worker
>>> 
>>> Using a very simple workers.properties file.
>>> 
>>> worker.list=ajp13
>>> worker.ajp13.port=8009
>>> worker.ajp13.host=localhost
>>> worker.ajp13.type=ajp13
>>> 
>>>   any other suggestions?  I am totally out of ideas as to
>>> what is causing
>>> this error..
>>>  
>>>  thanks
>>> Adam
>>> 
>>> 
>>> On 3/3/03 8:06 AM, "Turner, John" <[EMAIL PROTECTED]> wrote:
>>> 
>>>> 
>>>> Try deleting the "lbfactor" line from your
>>> workers.properties file.  It's
>>>> not necessary when you only have one worker defined, and it
>>> may be causing
>>>> confusion to mod_jk.so.
>>>> 
>>>> John
>>>> 
>>>> 
>>>>> -Original Message-
>>>>> From: Adam Denenberg [mailto:[EMAIL PROTECTED]
>>>>> Sent: Saturday, March 01, 2003 8:36 PM
>>>>> To: [EMAIL PROTECTED]
>>>>> Subject: mod_jk error
>>>>> 
>>>>> 
>>>>> I have been digging everywhere and can not find the answer to
>>>>> this error
>>>>> that I am getting.
>>>>> 
>>>>>  Has anyone seen this error, and resolved it, or found the
>>> root of its
>>>>> cause?
>>>>> 
>>>>>  [Fri Feb 28 21:13:27 2003]  [jk_worker.c (136)]:
>>>>> wc_get_worker_for_name,
>>>>> done did not found a worker
>>>>> 
>>>>> Thanks
>>>>> Adam
>>>>> 
>>>>> 
>>>>> 
>>> -
>>>>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>>>>> For additional commands, e-mail:
>>> [EMAIL PROTECTED]
>>>>> 
>>>> 
>>>> 
>>> -
>>>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>>>> For additional commands, e-mail: [EMAIL PROTECTED]
>>>> 
>>> 
>>> 
>>> -
>>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>>> For additional commands, e-mail: [EMAIL PROTECTED]
>>> 
>> 
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>> 
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Strange mod_jk error - SOLVED

[Denise Mangano]

I was having some Vhost conflicts which I just cleared up (thanks John).  I
ran netstat again, with both Tomcat and Apache running, and these are the
results:
tcp0  0 *:8009  *:* LISTEN


I was still having the "error opening workers" in apache error log, so I
also removed the path to the workers file from inside the VirtualHost
container to be outside all virtual hosts.  The errors are now gone, and ...
the problem is SOLVED!!!  Phew...

Thank you, Thank you, Thank you :)  That's what a newbie gets for messing
with the configuration.  But thankfully it works now, and it is working the
way I want it to (have a new "small" issue - will post separately).

The last note on this, is that in my mod_jk.log, after starting apache, it
has the following code:
[Tue Jun 03 15:45:14 2003]  [jk_worker.c (118)]: Into wc_close
[Tue Jun 03 15:45:14 2003]  [jk_worker.c (199)]: close_workers got -1
workers to destroy
[Tue Jun 03 15:45:14 2003]  [jk_worker.c (120)]: wc_close, done
[Tue Jun 03 15:45:14 2003]  [jk_uri_worker_map.c (190)]: Into
jk_uri_worker_map_t::uri_worker_map_free
[Tue Jun 03 15:45:14 2003]  [jk_uri_worker_map.c (441)]: Into
jk_uri_worker_map_t::uri_worker_map_close

The weird thing is that it has this code repeatedly, every time ... 12 times
to be exact.  Is that normal?

Thanks again to both of you for all your help :)
Denise

-Original Message-
From: PELOQUIN,JEFFREY (HP-Boise,ex1) [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, June 03, 2003 2:24 PM
To: 'Tomcat Users List'
Subject: RE: Strange mod_jk error


You might check in your /etc/services file to see if 8009 corresponds to one
of the names listed in your net stat

you might try the netstat and change the grep to 8009 and see if there is
any mention of it at all.


Given the fact that your original error report was

In jk_endpoint_t::service, Error sd = -1

I would hazard a guess that everything was working originally except that
you had the ajp13 port worngly specified in your workers.properties or in
your server.xml.  From my own tests I can only get anjk_endpoint_t::service
error if apache is able to find the worker but the i/port are wrong in
worker.properties.  You current problem of not being able to find a worker
is most likely an artifact of trying changing things in your configuration
files one too many times.

Suggestion:


1) Stop all instances of apache
2) Stop all instances of tomcat
use kill -9 if need be to ensure no JVMs are left (Unless of course this is
a production server and you cannot be that indiscrimate)

3)Start tomcat

4) telnet tomcat-ajp13-domain tomcat-ajp13-port  (as specified in server.xml
for the ajp13 connector tag)
5) netstat -a | grep LISTEN

one of these tests should demonstrate the existence of your listener.  If
not check catalina.out for ajp13 error messages


6) once you are confident that your listener is correct recreate your
workers.property to have the correct tomcat-ajp13-domain tomcat-ajp13-port
information entered.

7) check that your virtual host is loading this file or place the
JkWorkersFile command outside all virtual host to make sure everyone uses
it.

8) restart apache and watch the mod_jk logs and see that it load your
workers file correctly

9) hit webpage and hopefully it will work.

-Original Message-
From: Denise Mangano [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 03, 2003 11:51 AM
To: 'Tomcat Users List'
Subject: RE: Strange mod_jk error


Ok, dumb question.  Does port 8009 have to be open on my firewall then?  If
so then how was it possibly working before?  I can only telnet on port 80
and port 443 (These are the only ports open on my firewall).

The results of the netstat are:
tcp0  0 *:32768 *:* LISTEN

tcp0  0 *:login *:* LISTEN

tcp0  0 *:vboxd *:* LISTEN

tcp0  0 *:sunrpc*:* LISTEN

tcp0  0 *:ssh   *:* LISTEN

tcp0  0 cdiserv:smtp*:* LISTEN

unix  2  [ ACC ] STREAM LISTENING 1257   /dev/gpmctl
unix  2  [ ACC ] STREAM LISTENING 1324
/tmp/.font-unix/fs7100


I am getting the feeling something is not right... But it did work at one
point with the single virtual host...

In httpd.conf
Port 80
BindAddress *
NameVirtualHost *

  Listen 80
  Listen 443

ServerName www (overwritten within Vhosts)

Thanks,
Denise


-Original Message-
From: PELOQUIN,JEFFREY (HP-Boise,ex1) [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, June 03, 2003 1:06 PM
To: 'Tomcat Users List'
Subject: RE: Strange mod_jk error


Denise,

I could not see in the email trail if it ever was determined that you truly
have a listener on the ajp13 port for the problem domain

if you do
telnet test.my

Re: Strange mod_jk error - SOLVED

[John Turner]

Glad you got it working.  Lesson learned on both sides...next time I'll ask 
for config files right away...we would have spotted multiple JkWorkersFile 
statements in a heartbeat, and saved you a lot of time and frustration.

John

On Tue, 3 Jun 2003 16:09:54 -0400, Denise Mangano <[EMAIL PROTECTED]> 
wrote:

I was having some Vhost conflicts which I just cleared up (thanks John).  
I
ran netstat again, with both Tomcat and Apache running, and these are the
results:
tcp0  0 *:8009  *:* 
LISTEN

I was still having the "error opening workers" in apache error log, so I
also removed the path to the workers file from inside the VirtualHost
container to be outside all virtual hosts.  The errors are now gone, and 
...
the problem is SOLVED!!!  Phew...

Thank you, Thank you, Thank you :)  That's what a newbie gets for messing
with the configuration.  But thankfully it works now, and it is working 
the
way I want it to (have a new "small" issue - will post separately).

The last note on this, is that in my mod_jk.log, after starting apache, 
it
has the following code:
[Tue Jun 03 15:45:14 2003]  [jk_worker.c (118)]: Into wc_close
[Tue Jun 03 15:45:14 2003]  [jk_worker.c (199)]: close_workers got -1
workers to destroy
[Tue Jun 03 15:45:14 2003]  [jk_worker.c (120)]: wc_close, done
[Tue Jun 03 15:45:14 2003]  [jk_uri_worker_map.c (190)]: Into
jk_uri_worker_map_t::uri_worker_map_free
[Tue Jun 03 15:45:14 2003]  [jk_uri_worker_map.c (441)]: Into
jk_uri_worker_map_t::uri_worker_map_close

The weird thing is that it has this code repeatedly, every time ... 12 
times
to be exact.  Is that normal?

Thanks again to both of you for all your help :)
Denise
--
Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Strange mod_jk error - SOLVED

[Denise Mangano]

Sometimes time and frustration are a good thing... Especially when learning
something.

Thanks again :)
Denise

-Original Message-
From: John Turner [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, June 03, 2003 4:07 PM
To: Tomcat Users List
Subject: Re: Strange mod_jk error - SOLVED



Glad you got it working.  Lesson learned on both sides...next time I'll ask 
for config files right away...we would have spotted multiple JkWorkersFile 
statements in a heartbeat, and saved you a lot of time and frustration.

John

On Tue, 3 Jun 2003 16:09:54 -0400, Denise Mangano <[EMAIL PROTECTED]> 
wrote:

> I was having some Vhost conflicts which I just cleared up (thanks 
> John).
> I
> ran netstat again, with both Tomcat and Apache running, and these are the
> results:
> tcp0  0 *:8009  *:* 
> LISTEN
>
>
> I was still having the "error opening workers" in apache error log, so 
> I also removed the path to the workers file from inside the 
> VirtualHost container to be outside all virtual hosts.  The errors are 
> now gone, and ... the problem is SOLVED!!!  Phew...
>
> Thank you, Thank you, Thank you :)  That's what a newbie gets for 
> messing with the configuration.  But thankfully it works now, and it 
> is working the way I want it to (have a new "small" issue - will post 
> separately).
>
> The last note on this, is that in my mod_jk.log, after starting 
> apache,
> it
> has the following code:
> [Tue Jun 03 15:45:14 2003]  [jk_worker.c (118)]: Into wc_close
> [Tue Jun 03 15:45:14 2003]  [jk_worker.c (199)]: close_workers got -1
> workers to destroy
> [Tue Jun 03 15:45:14 2003]  [jk_worker.c (120)]: wc_close, done
> [Tue Jun 03 15:45:14 2003]  [jk_uri_worker_map.c (190)]: Into
> jk_uri_worker_map_t::uri_worker_map_free
> [Tue Jun 03 15:45:14 2003]  [jk_uri_worker_map.c (441)]: Into
> jk_uri_worker_map_t::uri_worker_map_close
>
> The weird thing is that it has this code repeatedly, every time ... 12
> times
> to be exact.  Is that normal?
>
> Thanks again to both of you for all your help :)
> Denise
>

-- 
Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

mod_jk error in browser window

[Armenio Pinto]

Hi there,

 I'm using Tomcat 3.2.4 and Apache as frontend, with mod_jk. Sometimes,
when I open the main page, the following error apears in the browser window:

HTTP/1.0 200 OK Date: Tue, 23 Sep 2003 18:42:28 GMT Server: Apache/1.3.27
(Unix) (Red-Hat/Linux) mod_jk/1.2.4 mod_python/2.7.8 Python/1.5.2
mod_ssl/2.8.12 OpenSSL/0.9.6b DAV/1.0.3 PHP/4.1.2 mod_perl/1.26
mod_throttle/3.1.2 Cache-Control: no-cache Pragma: no-cache Expires: Thu, 01
Jan 1970 00:00:00 GMT Servlet-Engine: Tomcat Web Server/3.2.4 (JSP 1.1;
Servlet 2.2; Java 1.4.2; Linux 2.4.18-27.7.x i386; java.vendor=Sun
Microsystems Inc.) Content-Type: text/html;charset=ISO-8859-1 X-Cache: MISS
from xx.xxx.xxx..pt Connection: close


Can anyone, please, explain me what's going on? Thanks in advance,

Arménio Pinto

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

mod_jk error with Apache 2.0.49

[Barry Roberts]

I'm trying to get mod_jk working with apache 2.0.49 built from source on
RedHat ES 3.0.  I've got the module built and in the modules directory,
and my httpd.conf contains:

LoadModule jk_module modules/mod_jk.so

JkWorkersFile /usr/local/apache2/conf/workers.properties
JkLogFile /var/log/mod_jk.log
JkLogLevel debug
JkMount /apps/* xsappa
JkMount /admin xsappa

This is towards the top of the file outside of any  or
 elements (I have also tried putting this at the bottom of
the file).

My workers.properties is:


worker.list=xsappa

worker.xsappa.port=139
worker.xsappa.host=192.168.2.42
worker.xsappa.type=ajp13
worker.xsappa.lbfactor=1

Every time I try to hit a servlet or jsp I get the following in my
mod_jk.log:
[Tue May 25 12:45:38 2004]  [jk_worker.c (136)]: wc_get_worker_for_name,
done did not found a worker

And of course a 500 in the browser.

The tomcat server works fine.  I can put jk2 into the web server and it
mostly works (I get "Broken Pipe" exceptions when I KNOW it's not a user
pressing cancel in the browser, but that's another issue).  I can hit
the tomcat server on port 8080 and it's just fine.

I can't use jk2 because of the spurious broken pipes, and now I can't
get jk1 working at all.  I have this suspicion that I'm missing
something obvious, but I can't find it.

Any help would be greatly appreciated.

Thanks,
Barry Roberts


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Mod_jk error... help me please

[Kommuru, Bhaskar]

I have compiled Mod_jk2-2.0.4 with apache2.0.49. But when i configtest/start
apache i get the following error.

# /usr/local/apache2/bin/apachectl configtest
Syntax error on line 269 of /usr/local/apache2/conf/httpd.conf:
Can't locate API module structure `jk2_module' in file
/usr/local/apache2/modules/mod_jk2.so: ld.so.1:
/usr/local/apache2/bin/httpd: fatal: jk2_module: can't find symbol

1. Is there problem with mod_jk.so object i.e. created by compiler?? 
2. Should the compiler version of Apache2.0.49 and Mod_jk2.0.4 be the same? 
3. If so, How can i find version of compiler that compiled apache?

Please help me if any one knows!!

Regards
Bhaskar


__

For information about the Standard Bank group visit our web site 

__

Disclaimer and confidentiality note 
Everything in this e-mail and any attachments relating to the official business of 
Standard Bank Group Limited  is proprietary to the group. 
It is confidential, legally privileged and protected by law. 
Standard Bank does not own and endorse any other content. Views and opinions are those 
of the sender unless clearly stated as being that of the group. 
The person addressed in the e-mail is the sole authorised recipient. Please notify the 
sender immediately if it has unintentionally reached you and do not read, 
disclose or use the content in any way.
Standard Bank can not assure that the integrity of this communication has been 
maintained nor that it is free of errors, virus, interception or interference.
___

Re: HP-UX 11 mod_jk error

[John Whitley]

Ganesh,

The shared library calls dl* are only available on 64-bit HP-UX 11.00. I 
seem to remember that they are not available on 32-bit HP-UX until 11.11 
(11i). We had to rebuild ours for 32-bit use by providing stubs for the 
calls. This worked in our case because we do not use the functionality 
of mod_jk which requires shared libraries. We are using mod_jk  purely 
as an interface between Apache and tomcat. If you download the 
connectors part of tomcat, you will find a script for compiling mod_jk 
on hp-ux, for either ANSI cc or gcc.

Regards

John Whitley


Sankaranarayanan (Ganesh) Ganapathy wrote:

>I am trying to setup the tomcat4.0.4 against apache 1.3.26 on HP-UX 11..
>
>I built the redirector and it went thru fine. But when I try to load it in apache I 
>see the following errors:
>
>Am I missing some patch?
>
>Can somebody help.
>
>Thanx in advance!
>Ganesh
>
>/usr/lib/dld.sl: Unresolved symbol: dlclose (code)  from 
>/export/home/ganesh/apache_1.3.26/bindist/libexec/mod_jk.so
>/usr/lib/dld.sl: Unresolved symbol: dlopen (code)  from 
>/export/home/ganesh/apache_1.3.26/bindist/libexec/mod_jk.so
>/usr/lib/dld.sl: Unresolved symbol: dlerror (code)  from 
>/export/home/ganesh/apache_1.3.26/bindist/libexec/mod_jk.so
>/usr/lib/dld.sl: Unresolved symbol: dlsym (code)  from 
>/export/home/ganesh/apache_1.3.26/bindist/libexec/mod_jk.so
>Syntax error on line 236 of /export/home/ganesh/apache_1.3.26/bindist/conf/httpd.conf:
>Cannot load /export/home/ganesh/apache_1.3.26/bindist/libexec/mod_jk.so into server: 
>Unresolved external
>
>--
>To unsubscribe, e-mail:   
>For additional commands, e-mail: 
>



--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

mod_jk error shortly after starting tomcat

[Fritz Thielemann]

Hi friends,

shortly after starting tomcat some requests are going wrong (error 500
visible in the browser). mod_jk.log says:
jk_ajp13_worker.c (203): connection_tcp_get_message: Error -
jk_tcp_socket_recvfull failed
jk_ajp13_worker.c (619): Error reading request

after a while this error doesn't appear again

versions: tomcat 3.2.1, jdk1.3 (IBM), apache 1.3.14

is this known by someone? if yes, what does it mean? should I take care
of what?

thanks in advance

regards Fritz

RE: Mod_jk error (worker.ajp12.host=localhost)

[Nathan Potter]

I'm having a similar problem. What was wrong with you localhost?

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, March 07, 2001 12:42 PM
To: [EMAIL PROTECTED]
Subject: RE: Mod_jk error



When I had this problem it was caused by how my localhost was defined, so
this line:

worker.ajp12.host=localhost

was apparently causing me problems.  I fixed my localhost, and the error
has gone away.




"Simmons,
Donald"  To:
[EMAIL PROTECTED]
  Subject: RE: Mod_jk error

07-03-01
07:33 AM
Please
respond to
tomcat-user







The workers.properties files appears to be correct. I may have to modify
the source of the mod_jk file and recompile to find out what file it is
looking for. A more descriptive message would help. Any other suggestions.
thanks!!

dj




--

NOTICE:  The information contained in this electronic mail transmission is
intended by Convergys Corporation for the use of the named individual or
entity to which it is directed and may contain information that is
privileged or otherwise confidential.  If you have received this electronic
mail transmission in error, please delete it from your system without
copying or forwarding it, and notify the sender of the error by reply email
or by telephone (collect), so that the sender's address records can be
corrected.



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

RE: Mod_jk error (worker.ajp12.host=localhost)

[greyson . smith]

My localhost was ill-defined in the hosts file.  When I pinged localhost, I
didn't get the correct address, so I fixed it, and the problem stopped.

I found the solution in the archives, and the person who lead me to the
problem used the ip of the machine rather than localhost, and that fixed
their problem.

good luck.



   
 
"Nathan Potter"
 
  cc: (bcc: Greyson Smith/CCMG/CVG)  
 
Subject: RE: Mod_jk error 
(worker.ajp12.host=localhost) 
09-03-01 11:15 
 
PM 
 
Please respond 
 
to tomcat-user 
 
   
 
   
 





I'm having a similar problem. What was wrong with you localhost?


--

NOTICE:  The information contained in this electronic mail transmission is
intended by Convergys Corporation for the use of the named individual or
entity to which it is directed and may contain information that is
privileged or otherwise confidential.  If you have received this electronic
mail transmission in error, please delete it from your system without
copying or forwarding it, and notify the sender of the error by reply email
or by telephone (collect), so that the sender's address records can be
corrected.



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Réf. : mod_jk error with Apache 2.0.49

[meissa . Sakho]

Barry,

make sure you have built the right jk module.

I've exactly the same config than you.
Redhat ES 3.0, apache 2.0.49 jk2 and jboss 3.2.3 that
comes with tomcat 3.2.3

my httpd.conf file  contains :
LoadModule jk2_module modules/mod_jk2.so

JKSet config.file /opt/apachessl-2.0.49/inet/conf/workers2.properties


the workers2 file may contains
[shm]
file=/var/log/apache/inet/jk2.shm
[channel.socket:localhost:8009]
port=8009
host=127.0.0.1

[ajp13:localhost:8009]
channel=channel.socket:localhost:8009

# Uri mapping

[uri:/apps/*]
worker=ajp13:localhost:8009

and it works fine.
___
NATEXIS ASSET MANAGEMENT
Meissa SAKHO
01 58 19 45 71. . . . . . . . . . . . (84571)
[EMAIL PROTECTED]




Barry Roberts <[EMAIL PROTECTED]>
25/05/2004 21:14
Veuillez répondre à "Tomcat Users List"


Pour :  [EMAIL PROTECTED]
cc :
    Objet : mod_jk error with Apache 2.0.49


I'm trying to get mod_jk working with apache 2.0.49 built from source on
RedHat ES 3.0.  I've got the module built and in the modules directory,
and my httpd.conf contains:

LoadModule jk_module modules/mod_jk.so

JkWorkersFile /usr/local/apache2/conf/workers.properties
JkLogFile /var/log/mod_jk.log
JkLogLevel debug
JkMount /apps/* xsappa
JkMount /admin xsappa

This is towards the top of the file outside of any  or
 elements (I have also tried putting this at the bottom of
the file).

My workers.properties is:


worker.list=xsappa

worker.xsappa.port=139
worker.xsappa.host=192.168.2.42
worker.xsappa.type=ajp13
worker.xsappa.lbfactor=1

Every time I try to hit a servlet or jsp I get the following in my
mod_jk.log:
[Tue May 25 12:45:38 2004]  [jk_worker.c (136)]: wc_get_worker_for_name,
done did not found a worker

And of course a 500 in the browser.

The tomcat server works fine.  I can put jk2 into the web server and it
mostly works (I get "Broken Pipe" exceptions when I KNOW it's not a user
pressing cancel in the browser, but that's another issue).  I can hit
the tomcat server on port 8080 and it's just fine.

I can't use jk2 because of the spurious broken pipes, and now I can't
get jk1 working at all.  I have this suspicion that I'm missing
something obvious, but I can't find it.

Any help would be greatly appreciated.

Thanks,
Barry Roberts


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





L'integrite de ce message n'etant pas assuree sur internet, Natexis
Banques Populaires ne peut etre tenu responsable de
son contenu. Toute utilisation ou diffusion non autorisee est
interdite. Si vous n'etes pas destinataire de ce message, merci de le
detruire et d'avertir l'expediteur.

The integrity of this message cannot be guaranteed
on the Internet. Natexis Banques Populaires can not therefore be
considered responsible for the contents.Any unauthorized use or dissemination is 
prohibited.
If you are not the intended recipient of this message, then please delete it and
notify the sender.

Re: Mod_jk error... help me please

[Emerson Cargnin]

I'm confused... are you trying to use mod_jk or mod_jk2? mod_jk2 is on 
mod_jk.so, not mod_jk.so, this is the mod_jk library.

Kommuru, Bhaskar wrote:
I have compiled Mod_jk2-2.0.4 with apache2.0.49. But when i configtest/start
apache i get the following error.
# /usr/local/apache2/bin/apachectl configtest
Syntax error on line 269 of /usr/local/apache2/conf/httpd.conf:
Can't locate API module structure `jk2_module' in file
/usr/local/apache2/modules/mod_jk2.so: ld.so.1:
/usr/local/apache2/bin/httpd: fatal: jk2_module: can't find symbol
1. Is there problem with mod_jk.so object i.e. created by compiler?? 
mod_jk??? you mean mod_jk2?
2. Should the compiler version of Apache2.0.49 and Mod_jk2.0.4 be the same? 
3. If so, How can i find version of compiler that compiled apache?

Please help me if any one knows!!
Regards
Bhaskar
__
For information about the Standard Bank group visit our web site 
__
	
Disclaimer and confidentiality note 
Everything in this e-mail and any attachments relating to the official business of Standard Bank Group Limited  is proprietary to the group. 
It is confidential, legally privileged and protected by law. 
Standard Bank does not own and endorse any other content. Views and opinions are those of the sender unless clearly stated as being that of the group. 
The person addressed in the e-mail is the sole authorised recipient. Please notify the sender immediately if it has unintentionally reached you and do not read, 
disclose or use the content in any way.
Standard Bank can not assure that the integrity of this communication has been maintained nor that it is free of errors, virus, interception or interference.
___


--
Emerson Cargnin
Analista de Sistemas
Setor de Desenvolvimento de Sistemas - TRE-SC
tel : (048) - 251-3700 - Ramal 3181
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Mod_jk error... help me please

[Kommuru, Bhaskar]

Hi Emerson,

I am using Mod_jk2-2.0.4 (downloaded latest source). Any clues on this? 

Thanks
bhaskar

-Original Message-
From: Emerson Cargnin [mailto:[EMAIL PROTECTED]
Sent: Friday, May 28, 2004 7:02 PM
To: Tomcat Users List
Subject: Re: Mod_jk error... help me please


I'm confused... are you trying to use mod_jk or mod_jk2? mod_jk2 is on 
mod_jk.so, not mod_jk.so, this is the mod_jk library.

Kommuru, Bhaskar wrote:
> I have compiled Mod_jk2-2.0.4 with apache2.0.49. But when i
configtest/start
> apache i get the following error.
> 
> # /usr/local/apache2/bin/apachectl configtest
> Syntax error on line 269 of /usr/local/apache2/conf/httpd.conf:
> Can't locate API module structure `jk2_module' in file
> /usr/local/apache2/modules/mod_jk2.so: ld.so.1:
> /usr/local/apache2/bin/httpd: fatal: jk2_module: can't find symbol
> 
> 1. Is there problem with mod_jk.so object i.e. created by compiler?? 

mod_jk??? you mean mod_jk2?

> 2. Should the compiler version of Apache2.0.49 and Mod_jk2.0.4 be the
same? 
> 3. If so, How can i find version of compiler that compiled apache?
> 
> Please help me if any one knows!!
> 
> Regards
> Bhaskar
> 
> 
>

__
> 
> For information about the Standard Bank group visit our web site

>

__
>   
> Disclaimer and confidentiality note 
> Everything in this e-mail and any attachments relating to the official
business of Standard Bank Group Limited  is proprietary to the group. 
> It is confidential, legally privileged and protected by law. 
> Standard Bank does not own and endorse any other content. Views and
opinions are those of the sender unless clearly stated as being that of the
group. 
> The person addressed in the e-mail is the sole authorised recipient.
Please notify the sender immediately if it has unintentionally reached you
and do not read, 
> disclose or use the content in any way.
> Standard Bank can not assure that the integrity of this communication has
been maintained nor that it is free of errors, virus, interception or
interference.
>

___
> 


-- 
Emerson Cargnin
Analista de Sistemas
Setor de Desenvolvimento de Sistemas - TRE-SC
tel : (048) - 251-3700 - Ramal 3181

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

__

For information about the Standard Bank group visit our web site 

__

Disclaimer and confidentiality note 
Everything in this e-mail and any attachments relating to the official business of 
Standard Bank Group Limited  is proprietary to the group. 
It is confidential, legally privileged and protected by law. 
Standard Bank does not own and endorse any other content. Views and opinions are those 
of the sender unless clearly stated as being that of the group. 
The person addressed in the e-mail is the sole authorised recipient. Please notify the 
sender immediately if it has unintentionally reached you and do not read, 
disclose or use the content in any way.
Standard Bank can not assure that the integrity of this communication has been 
maintained nor that it is free of errors, virus, interception or interference.
___

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

how to customize mod_jk error messages

[Michal Kwiatek]

Hello all,

I'm trying to find a way to customize the following mod_jk error message: 

OK
The server encountered an internal error or misconfiguration and was unable to 
complete your request.

Please contact the server administrator, [EMAIL PROTECTED] and inform them of 
the time the error occurred, and anything you might have done that may have 
caused the error.

More information about this error may be available in the server error log.

This message is shown when the underlying tomcat server is down. I tried 
redefining message for error 500 or 502 in httpd.conf, but it doesn't help. I 
guess it comes from mod_jk internals...

Any idea how to solve this problem?

Thank you in advance,
Michal.


> -Original Message-
> From: Weseloh, Markus [mailto:[EMAIL PROTECTED] 
> Sent: Thursday, June 30, 2005 2:08 PM
> To: 'Tomcat Users List'
> Subject: AW: WebSphere SOAP under tomcat
> 
> Hi,
> 
> I have to confess that I'm an Axis beginner. I've managed to 
> write my own WebService in Axis and generate the 
> corresponding client stub. But the specific service I want to 
> use diverges from the standard. The people who generated the 
> WebSphere client implementation said, that they have to 
> manipulate the generated stub so that it works correctly. Now 
> I have to identitfy this manipulation and try to implement it 
> for Axis. That's an option, but I would prefer to use the 
> existing version...if there is a way to do it.
> 
> Regards
> Markus
> 
> -Ursprüngliche Nachricht-
> Von: Bruno Georges [mailto:[EMAIL PROTECTED]
> Gesendet: Donnerstag, 30. Juni 2005 13:48
> An: Tomcat Users List
> Cc: 'tomcat-user@jakarta.apache.org'
> Betreff: Re: WebSphere SOAP under tomcat
> 
> If you have the WSDL you can generate clients very easily.
> For AXIS as wella s PHP, Perl, etc...
> For Java use tools suchas wsdl2java, then SOAP implementation 
> such as axis will do.
> 
> 
> Hope this helps.
> Bruno Georges
> 
> Glencore International AG
> Tel. +41 41 709 3204
> Fax +41 41 709 3000
> 
> 
>  
> 
>   "Weseloh,
> 
>   Markus"  To:
> "'tomcat-user@jakarta.apache.org'" 
> 
>
>   gedas.de>Subject: 
> WebSphere SOAP under
> tomcat
>
>  
> 
>   30.06.05 13:43   Distribute:
> 
>   Please respond   Personal?  
>  |---|
> 
>   to "Tomcat Users
>  | [ ] x |
> 
>   List"   
>  |---|
> 
>  
> 
>  
> 
> 
> 
> 
> 
> Hi,
> 
> currently I'm developing an application for Tomcat 5.0.28. 
> Now I want to call a SOAP service but for this service exists 
> only a client implementation for the WebSphere libs. Is there 
> a way to use this client implementation under an standalone 
> Tomcat? The first missing dependency is the file 
> webservices.jar from WebSphere, but when I look in the 
> MANIFEST.MF of webservices.jar I can find a lot of JARs that 
> are required by webservices.jar...and don't want to know how 
> many libs are required by these JARs. Does anybody know how I 
> can use the WebSphere Client implementation of the SOAP 
> service (or ist the only way for me to generate an Axis 
> implementation manually)? One more info: the client 
> implementation works under WAS 5.1.1.4.
> 
> Regards
> Markus Weseloh
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: mod_jk error under load (errno codes)

[Anthony Milbourne]

Hi

I just searched through google.  I didn't find any lists of error codes -
which is something that I would find quite useful as well.  All I found was
someone elses post to another forum.

Question for developers & people in the know:

I realise that I could read the source to find this out but I would rather
not have to (I use Tomcat at work and my boss would not appreciate me
spending the time to do this)...
Is there any way of obtaining a list of what these errno's mean?
It might be a handy appendix to future documentation - it would certainly
give competent sys-admins/users more of a clue where to look for the
problem.

Thanks,

Anthony.

> -Original Message-
> From: Marc [SMTP:[EMAIL PROTECTED]]
> Sent: 30 September 2002 14:23
> To:   Tomcat Users List
> Subject:  Re: mod_jk error under load
> 
> Hi, where can I find a description for each 'errno'?
> I receive errno = 110 when I try to access tomcat connecting to a *.jsp
> page
> through apache.
> 
> Thank you!!!
> 
> Marc
> 
> Anthony Milbourne wrote:
> 
> > Hi
> >
> > 146 is a socket connection error.
> > Try checking your workers.properties file (or the JBoss file that
> generates
> > it ?) and making sure that the only connectors mentioned in workers.list
> > also have connectors defined in server.xml.  Specifically - check there
> > isn't an ajp12 in workers.properties and not in server.xml.
> >
> > Hope that helps.
> >
> > Anthony.
> >
> > > -----Original Message-
> > > From: David Ward [SMTP:[EMAIL PROTECTED]]
> > > Sent: 27 September 2002 17:57
> > > To:   [EMAIL PROTECTED]
> > > Subject:  mod_jk error under load
> > >
> > > In running an automated load test against our app, we get the
> following
> > > errors in or jk.log file:
> > >
> > > [jk_connect.c (143)]: jk_open_socket, connect() failed errno = 146
> > > [jk_ajp12_worker.c (152)]: In jk_endpoint_t::service, Error sd = -1
> > > [jk_connect.c (143)]: jk_open_socket, connect() failed errno = 146
> > > [jk_ajp12_worker.c (152)]: In jk_endpoint_t::service, Error sd = -1
> > > [jk_connect.c (143)]: jk_open_socket, connect() failed errno = 146
> > > [jk_ajp12_worker.c (152)]: In jk_endpoint_t::service, Error sd = -1
> > > [jk_connect.c (143)]: jk_open_socket, connect() failed errno = 146
> > > [jk_ajp12_worker.c (152)]: In jk_endpoint_t::service, Error sd = -1
> > > [jk_connect.c (143)]: jk_open_socket, connect() failed errno = 146
> > > [jk_ajp12_worker.c (152)]: In jk_endpoint_t::service, Error sd = -1
> > > [jk_connect.c (143)]: jk_open_socket, connect() failed errno = 146
> > >
> > > Anyone know what these errors are? I can't find anything conclusive
> > > about them searching various lists/forums.
> > >
> > > We are running Apache 1.3.12 on a Solaris 7 Ultra 10 using
> mod_jk/ajp12
> > > to talk to JBoss-2.4.7_Tomcat-3.2.3 on a Solaris 7 E250, JDK 1.3.1_02.
> > >
> > > The symptoms we see are that the number of httpd processes maxes out
> on
> > > the web server box, though the CPU is almost completely idle. The
> weird
> > > thing is that the app server is mostly idle too, and doing a thread
> dump
> > > on the java (jboss+tomcat in same vm) process shows that there are
> lots
> > > of threads waiting for work to do. Once we stop the load test, things
> > > are still messed up until I restart apache, then we can access the app
> > > again. Note that I didn't have to touch the app server at all.
> Accessing
> > > URLs that aren't configured to go through mod_jk have no problem,
> until
> > > the max http children process gets reached, of course...
> > >
> > > I haven't gotten a response from the Tomcat forum at JGuru.
> > >
> > > Thanks all,
> > > David
> > >
> > >
> > > --
> > > To unsubscribe, e-mail:
> > > <mailto:[EMAIL PROTECTED]>
> > > For additional commands, e-mail:
> > > <mailto:[EMAIL PROTECTED]>
> >
> > **
> > This email and any files transmitted with it are confidential and
> > intended solely for the use of the individual or entity to whom they
> > are addressed. If you have received this email in error please notify
> > the system manager.
> > This footnote also confirms that this email message has been swept by
> > MIMEsweeper for the presence of computer viruses.
> > www

Re: Réf. : mod_jk error with Apache 2.0.49

[Barry Roberts]

What do you mean the "right" one?  I built jk2 from the
jakarta-tomcat-connectors-jk2-src-current.tar.gz tarball.  Is that
"right"?

The problem I'm having with jk2 is a known issue
(http://nagoya.apache.org/bugzilla/show_bug.cgi?id=28790).  I would love
to see that one figured out, but right now I would settle for just
getting jk1 to work.

I compiled a modified mod_jk.so and inside get_map (jk_map.c) the
jk_map_t* passed in is null.  That's why there's no worker found.  I
haven't had time to try and figure out what could cause it to be null.

Thanks,
Barry


On Wed, 2004-05-26 at 01:34, [EMAIL PROTECTED]
wrote:
> Barry,
> 
> make sure you have built the right jk module.
> 
> I've exactly the same config than you.
> Redhat ES 3.0, apache 2.0.49 jk2 and jboss 3.2.3 that
> comes with tomcat 3.2.3
> 
> my httpd.conf file  contains :
> LoadModule jk2_module modules/mod_jk2.so
> 
> JKSet config.file /opt/apachessl-2.0.49/inet/conf/workers2.properties
> 
> 
> the workers2 file may contains
> [shm]
> file=/var/log/apache/inet/jk2.shm
> [channel.socket:localhost:8009]
> port=8009
> host=127.0.0.1
> 
> [ajp13:localhost:8009]
> channel=channel.socket:localhost:8009
> 
> # Uri mapping
> 
> [uri:/apps/*]
> worker=ajp13:localhost:8009
> 
> and it works fine.
> ___
> NATEXIS ASSET MANAGEMENT
> Meissa SAKHO
> 01 58 19 45 71. . . . . . . . . . . . (84571)
> [EMAIL PROTECTED]
> 
> 
> 
> 
> Barry Roberts <[EMAIL PROTECTED]>
> 25/05/2004 21:14
> Veuillez rÃpondre à "Tomcat Users List"
> 
> 
> Pour :  [EMAIL PROTECTED]
> cc :
> Objet : mod_jk error with Apache 2.0.49
> 
> 
> I'm trying to get mod_jk working with apache 2.0.49 built from source on
> RedHat ES 3.0.  I've got the module built and in the modules directory,
> and my httpd.conf contains:
> 
> LoadModule jk_module modules/mod_jk.so
> 
> JkWorkersFile /usr/local/apache2/conf/workers.properties
> JkLogFile /var/log/mod_jk.log
> JkLogLevel debug
> JkMount /apps/* xsappa
> JkMount /admin xsappa
> 
> This is towards the top of the file outside of any  or
>  elements (I have also tried putting this at the bottom of
> the file).
> 
> My workers.properties is:
> 
> 
> worker.list=xsappa
> 
> worker.xsappa.port=139
> worker.xsappa.host=192.168.2.42
> worker.xsappa.type=ajp13
> worker.xsappa.lbfactor=1
> 
> Every time I try to hit a servlet or jsp I get the following in my
> mod_jk.log:
> [Tue May 25 12:45:38 2004]  [jk_worker.c (136)]: wc_get_worker_for_name,
> done did not found a worker
> 
> And of course a 500 in the browser.
> 
> The tomcat server works fine.  I can put jk2 into the web server and it
> mostly works (I get "Broken Pipe" exceptions when I KNOW it's not a user
> pressing cancel in the browser, but that's another issue).  I can hit
> the tomcat server on port 8080 and it's just fine.
> 
> I can't use jk2 because of the spurious broken pipes, and now I can't
> get jk1 working at all.  I have this suspicion that I'm missing
> something obvious, but I can't find it.
> 
> Any help would be greatly appreciated.
> 
> Thanks,
> Barry Roberts
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> 
> 
> 
> L'integrite de ce message n'etant pas assuree sur internet, Natexis
> Banques Populaires ne peut etre tenu responsable de
> son contenu. Toute utilisation ou diffusion non autorisee est
> interdite. Si vous n'etes pas destinataire de ce message, merci de le
> detruire et d'avertir l'expediteur.
> 
> The integrity of this message cannot be guaranteed
> on the Internet. Natexis Banques Populaires can not therefore be
> considered responsible for the contents.Any unauthorized use or dissemination is 
> prohibited.
> If you are not the intended recipient of this message, then please delete it and
> notify the sender.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

mod_jk error 404 with Apache 1.3.27, Tomcat 4.1.18

[Randall Perry]

Successfully installed tomcat 4.1.18 and can access it on port 8080. Jsp &
servlets run ok.

Installed mod_jk.so v1.2.2, configured apache and get no errors on startup.

But, though I can access the directory pointed to by JKMount, and can load
static .html, no .jsp or servlet examples will run.

My machine is a Mac Xserve running OS 10.2.3 server.

Relevant configs appear below.

Any help is appreciated.


workers.properties

# Setup for Mac OS X
workers.tomcat_home=/usr/local/jakarta-tomcat-4.1.18
workers.java_home=/System/Library/Frameworks/JavaVM.framework/Home
worker.list=ajp13

#Definition for Ajp13 worker
worker.ajp13.port=8009
worker.ajp13.host=127.0.0.1
worker.ajp13.type=ajp13


httpd.conf

LoadModule jk_module/usr/libexec/httpd/mod_jk.so
AddModule mod_jk.c


DocumentRoot /usr/local/jakarta-tomcat-4.1.18
JKMount /*.jsp ajp13
JKMount /webapps/examples/servlet/* ajp13


JkWorkersFile /usr/local/jakarta-tomcat-4.1.18/conf/jk/workers.properties
JkLogFile /usr/local/jakarta-tomcat-4.1.18/logs/mod_jk.log
JkLogLevel debug


mod_jk.log

[Sun Jan 12 13:36:49 2003]  [jk_ajp13_worker.c (108)]: Into
ajp13_worker_factory
[Sun Jan 12 13:36:49 2003]  [jk_worker.c (171)]: wc_create_worker, about to
validate and init ajp13
[Sun Jan 12 13:36:49 2003]  [jk_ajp_common.c (1219)]: Into
jk_worker_t::validate
[Sun Jan 12 13:36:49 2003]  [jk_ajp_common.c (1239)]: In
jk_worker_t::validate for worker ajp13 contact is 127.0.0.1:8009
[Sun Jan 12 13:36:49 2003]  [jk_ajp_common.c (1267)]: Into jk_worker_t::init
[Sun Jan 12 13:36:49 2003]  [jk_ajp_common.c (1287)]: In jk_worker_t::init,
setting socket timeout to 0
[Sun Jan 12 13:36:49 2003]  [jk_worker.c (187)]: wc_create_worker, done
[Sun Jan 12 13:36:49 2003]  [jk_worker.c (238)]: build_worker_map, removing
old ajp13 worker 
[Sun Jan 12 13:36:49 2003]  [jk_worker.c (250)]: build_worker_map, done
[Sun Jan 12 13:36:49 2003]  [jk_worker.c (111)]: wc_open, done 1
[Sun Jan 12 13:36:59 2003]  [jk_uri_worker_map.c (460)]: Into
jk_uri_worker_map_t::map_uri_to_worker
[Sun Jan 12 13:36:59 2003]  [jk_uri_worker_map.c (477)]: Attempting to map
URI '/webapps/examples/jsp'
[Sun Jan 12 13:36:59 2003]  [jk_uri_worker_map.c (599)]:
jk_uri_worker_map_t::map_uri_to_worker, done without a match
[Sun Jan 12 13:37:00 2003]  [jk_uri_worker_map.c (460)]: Into
jk_uri_worker_map_t::map_uri_to_worker
[Sun Jan 12 13:37:00 2003]  [jk_uri_worker_map.c (477)]: Attempting to map
URI '/webapps/examples/jsp/'
[Sun Jan 12 13:37:00 2003]  [jk_uri_worker_map.c (599)]:
jk_uri_worker_map_t::map_uri_to_worker, done without a match
[Sun Jan 12 13:37:00 2003]  [jk_uri_worker_map.c (460)]: Into
jk_uri_worker_map_t::map_uri_to_worker
[Sun Jan 12 13:37:00 2003]  [jk_uri_worker_map.c (477)]: Attempting to map
URI '/webapps/examples/jsp/index.html'
[Sun Jan 12 13:37:00 2003]  [jk_uri_worker_map.c (599)]:
jk_uri_worker_map_t::map_uri_to_worker, done without a match
[Sun Jan 12 13:37:00 2003]  [jk_uri_worker_map.c (460)]: Into
jk_uri_worker_map_t::map_uri_to_worker
[Sun Jan 12 13:37:00 2003]  [jk_uri_worker_map.c (477)]: Attempting to map
URI '/webapps/examples/jsp/index.html'
[Sun Jan 12 13:37:00 2003]  [jk_uri_worker_map.c (599)]:
jk_uri_worker_map_t::map_uri_to_worker, done without a match
[Sun Jan 12 13:37:07 2003]  [jk_uri_worker_map.c (460)]: Into
jk_uri_worker_map_t::map_uri_to_worker
[Sun Jan 12 13:37:07 2003]  [jk_uri_worker_map.c (477)]: Attempting to map
URI '/webapps/examples/jsp/num/numguess.jsp'
[Sun Jan 12 13:37:07 2003]  [jk_uri_worker_map.c (558)]:
jk_uri_worker_map_t::map_uri_to_worker, Found a suffix match ajp13 -> *.jsp
[Sun Jan 12 13:37:07 2003]  [jk_worker.c (132)]: Into wc_get_worker_for_name
ajp13
[Sun Jan 12 13:37:07 2003]  [jk_worker.c (136)]: wc_get_worker_for_name,
done  found a worker
[Sun Jan 12 13:37:07 2003]  [jk_ajp_common.c (1404)]: Into
jk_worker_t::get_endpoint
[Sun Jan 12 13:37:07 2003]  [jk_ajp_common.c (1116)]: Into
jk_endpoint_t::service
[Sun Jan 12 13:37:07 2003]  [jk_ajp_common.c (295)]: Into
ajp_marshal_into_msgb
[Sun Jan 12 13:37:07 2003]  [jk_ajp_common.c (432)]: ajp_marshal_into_msgb -
Done
[Sun Jan 12 13:37:07 2003]  [jk_connect.c (158)]: Into jk_open_socket
[Sun Jan 12 13:37:07 2003]  [jk_connect.c (165)]: jk_open_socket, try to
connect socket = 6
[Sun Jan 12 13:37:07 2003]  [jk_connect.c (174)]: jk_open_socket, after
connect ret = 0
[Sun Jan 12 13:37:07 2003]  [jk_connect.c (183)]: jk_open_socket, set
TCP_NODELAY to on
[Sun Jan 12 13:37:07 2003]  [jk_connect.c (200)]: jk_open_socket, return, sd
= 6
[Sun Jan 12 13:37:07 2003]  [jk_ajp_common.c (614)]: In
jk_endpoint_t::ajp_connect_to_endpoint, connected sd = 6
[Sun Jan 12 13:37:07 2003]  [jk_ajp_common.c (642)]: sending to ajp13 #263
[Sun Jan 12 13:37:07 2003]  [jk_ajp_common.c (884)]: ajp_send_request 2:
request body to send 0 - request body to resend 0
[Sun Jan 12 

Réf. : Re: Réf. : mod_jk error with Apache 2.0.49

[meissa . Sakho]

You've built jk2. that's ok. Your load instruction is not correct.
your httpc.conf contains LoadModule jk_module modules/mod_jk.so
instead ofLoadModule jk2_module modules/mod_jk2.so
The set of instructions I send to you must work.
You are using apache 2 and jk2. And the instructions you set
are for jk (not jk2)

___
NATEXIS ASSET MANAGEMENT
Meissa SAKHO
01 58 19 45 71. . . . . . . . . . . . (84571)
[EMAIL PROTECTED]




Barry Roberts <[EMAIL PROTECTED]>
26/05/2004 17:54
Veuillez répondre à "Tomcat Users List"


Pour :  Tomcat Users List <[EMAIL PROTECTED]>
cc :
    Objet : Re: Réf. : mod_jk error with Apache 2.0.49


What do you mean the "right" one?  I built jk2 from the
jakarta-tomcat-connectors-jk2-src-current.tar.gz tarball.  Is that
"right"?

The problem I'm having with jk2 is a known issue
(http://nagoya.apache.org/bugzilla/show_bug.cgi?id=28790).  I would love
to see that one figured out, but right now I would settle for just
getting jk1 to work.

I compiled a modified mod_jk.so and inside get_map (jk_map.c) the
jk_map_t* passed in is null.  That's why there's no worker found.  I
haven't had time to try and figure out what could cause it to be null.

Thanks,
Barry


On Wed, 2004-05-26 at 01:34, [EMAIL PROTECTED]
wrote:
> Barry,
>
> make sure you have built the right jk module.
>
> I've exactly the same config than you.
> Redhat ES 3.0, apache 2.0.49 jk2 and jboss 3.2.3 that
> comes with tomcat 3.2.3
>
> my httpd.conf file  contains :
> LoadModule jk2_module modules/mod_jk2.so
> 
> JKSet config.file /opt/apachessl-2.0.49/inet/conf/workers2.properties
> 
>
> the workers2 file may contains
> [shm]
> file=/var/log/apache/inet/jk2.shm
> [channel.socket:localhost:8009]
> port=8009
> host=127.0.0.1
>
> [ajp13:localhost:8009]
> channel=channel.socket:localhost:8009
>
> # Uri mapping
>
> [uri:/apps/*]
> worker=ajp13:localhost:8009
>
> and it works fine.
> ___
> NATEXIS ASSET MANAGEMENT
> Meissa SAKHO
> 01 58 19 45 71. . . . . . . . . . . . (84571)
> [EMAIL PROTECTED]
>
>
>
>
> Barry Roberts <[EMAIL PROTECTED]>
> 25/05/2004 21:14
> Veuillez répondre à "Tomcat Users List"
>
>
> Pour :  [EMAIL PROTECTED]
> cc :
> Objet : mod_jk error with Apache 2.0.49
>
>
> I'm trying to get mod_jk working with apache 2.0.49 built from source on
> RedHat ES 3.0.  I've got the module built and in the modules directory,
> and my httpd.conf contains:
>
> LoadModule jk_module modules/mod_jk.so
>
> JkWorkersFile /usr/local/apache2/conf/workers.properties
> JkLogFile /var/log/mod_jk.log
> JkLogLevel debug
> JkMount /apps/* xsappa
> JkMount /admin xsappa
>
> This is towards the top of the file outside of any  or
>  elements (I have also tried putting this at the bottom of
> the file).
>
> My workers.properties is:
>
>
> worker.list=xsappa
>
> worker.xsappa.port=139
> worker.xsappa.host=192.168.2.42
> worker.xsappa.type=ajp13
> worker.xsappa.lbfactor=1
>
> Every time I try to hit a servlet or jsp I get the following in my
> mod_jk.log:
> [Tue May 25 12:45:38 2004]  [jk_worker.c (136)]: wc_get_worker_for_name,
> done did not found a worker
>
> And of course a 500 in the browser.
>
> The tomcat server works fine.  I can put jk2 into the web server and it
> mostly works (I get "Broken Pipe" exceptions when I KNOW it's not a user
> pressing cancel in the browser, but that's another issue).  I can hit
> the tomcat server on port 8080 and it's just fine.
>
> I can't use jk2 because of the spurious broken pipes, and now I can't
> get jk1 working at all.  I have this suspicion that I'm missing
> something obvious, but I can't find it.
>
> Any help would be greatly appreciated.
>
> Thanks,
> Barry Roberts
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
>
>
> L'integrite de ce message n'etant pas assuree sur internet, Natexis
> Banques Populaires ne peut etre tenu responsable de
> son contenu. Toute utilisation ou diffusion non autorisee est
> interdite. Si vous n'etes pas destinataire de ce message, merci de le
> detruire et d'avertir l'expediteur.
>
> The integrity of this message cannot be guaranteed
> on the Internet. Natexis Banques Populaires can not therefore be
> considered responsible for the contents.Any unauthorized use or
dissemination is prohibited.
> If y

RE: mod_jk error 404 with Apache 1.3.27, Tomcat 4.1.18

[mech]

Use:

JkMount *.jsp ajp13
JkMount /examples/* ajp13

> -Original Message-
> From: Randall Perry [mailto:[EMAIL PROTECTED]] 
> Sent: Sonntag, 12. Januar 2003 19:52
> To: [EMAIL PROTECTED]
> Subject: mod_jk error 404 with Apache 1.3.27, Tomcat 4.1.18
> 
> 
> Successfully installed tomcat 4.1.18 and can access it on 
> port 8080. Jsp & servlets run ok.
> 
> Installed mod_jk.so v1.2.2, configured apache and get no 
> errors on startup.
> 
> But, though I can access the directory pointed to by JKMount, 
> and can load static .html, no .jsp or servlet examples will run.
> 
> My machine is a Mac Xserve running OS 10.2.3 server.
> 
> Relevant configs appear below.
> 
> Any help is appreciated.
> 
> 
> workers.properties
> 
> # Setup for Mac OS X 
> workers.tomcat_home=/usr/local/jakarta-tomcat-4.1.18
> workers.java_home=/System/Library/Frameworks/JavaVM.framework/Home
> worker.list=ajp13
> 
> #Definition for Ajp13 worker
> worker.ajp13.port=8009
> worker.ajp13.host=127.0.0.1
> worker.ajp13.type=ajp13
> 
> 
> httpd.conf
> 
> LoadModule jk_module/usr/libexec/httpd/mod_jk.so
> AddModule mod_jk.c
> 
> 
> DocumentRoot /usr/local/jakarta-tomcat-4.1.18
> JKMount /*.jsp ajp13
> JKMount /webapps/examples/servlet/* ajp13
> 
> 
> JkWorkersFile 
> /usr/local/jakarta-tomcat-4.1.18/conf/jk/workers.properties
> JkLogFile /usr/local/jakarta-tomcat-4.1.18/logs/mod_jk.log
> JkLogLevel debug
> 
> 
> mod_jk.log
> 
> [Sun Jan 12 13:36:49 2003]  [jk_ajp13_worker.c (108)]: Into 
> ajp13_worker_factory [Sun Jan 12 13:36:49 2003]  [jk_worker.c 
> (171)]: wc_create_worker, about to validate and init ajp13 
> [Sun Jan 12 13:36:49 2003]  [jk_ajp_common.c (1219)]: Into 
> jk_worker_t::validate [Sun Jan 12 13:36:49 2003]  
> [jk_ajp_common.c (1239)]: In jk_worker_t::validate for worker 
> ajp13 contact is 127.0.0.1:8009 [Sun Jan 12 13:36:49 2003]  
> [jk_ajp_common.c (1267)]: Into jk_worker_t::init [Sun Jan 12 
> 13:36:49 2003]  [jk_ajp_common.c (1287)]: In 
> jk_worker_t::init, setting socket timeout to 0 [Sun Jan 12 
> 13:36:49 2003]  [jk_worker.c (187)]: wc_create_worker, done 
> [Sun Jan 12 13:36:49 2003]  [jk_worker.c (238)]: 
> build_worker_map, removing old ajp13 worker 
> [Sun Jan 12 13:36:49 2003]  [jk_worker.c (250)]: 
> build_worker_map, done [Sun Jan 12 13:36:49 2003]  
> [jk_worker.c (111)]: wc_open, done 1 [Sun Jan 12 13:36:59 
> 2003]  [jk_uri_worker_map.c (460)]: Into 
> jk_uri_worker_map_t::map_uri_to_worker
> [Sun Jan 12 13:36:59 2003]  [jk_uri_worker_map.c (477)]: 
> Attempting to map URI '/webapps/examples/jsp' [Sun Jan 12 
> 13:36:59 2003]  [jk_uri_worker_map.c (599)]: 
> jk_uri_worker_map_t::map_uri_to_worker, done without a match 
> [Sun Jan 12 13:37:00 2003]  [jk_uri_worker_map.c (460)]: Into 
> jk_uri_worker_map_t::map_uri_to_worker
> [Sun Jan 12 13:37:00 2003]  [jk_uri_worker_map.c (477)]: 
> Attempting to map URI '/webapps/examples/jsp/' [Sun Jan 12 
> 13:37:00 2003]  [jk_uri_worker_map.c (599)]: 
> jk_uri_worker_map_t::map_uri_to_worker, done without a match 
> [Sun Jan 12 13:37:00 2003]  [jk_uri_worker_map.c (460)]: Into 
> jk_uri_worker_map_t::map_uri_to_worker
> [Sun Jan 12 13:37:00 2003]  [jk_uri_worker_map.c (477)]: 
> Attempting to map URI '/webapps/examples/jsp/index.html'
> [Sun Jan 12 13:37:00 2003]  [jk_uri_worker_map.c (599)]: 
> jk_uri_worker_map_t::map_uri_to_worker, done without a match 
> [Sun Jan 12 13:37:00 2003]  [jk_uri_worker_map.c (460)]: Into 
> jk_uri_worker_map_t::map_uri_to_worker
> [Sun Jan 12 13:37:00 2003]  [jk_uri_worker_map.c (477)]: 
> Attempting to map URI '/webapps/examples/jsp/index.html'
> [Sun Jan 12 13:37:00 2003]  [jk_uri_worker_map.c (599)]: 
> jk_uri_worker_map_t::map_uri_to_worker, done without a match 
> [Sun Jan 12 13:37:07 2003]  [jk_uri_worker_map.c (460)]: Into 
> jk_uri_worker_map_t::map_uri_to_worker
> [Sun Jan 12 13:37:07 2003]  [jk_uri_worker_map.c (477)]: 
> Attempting to map URI '/webapps/examples/jsp/num/numguess.jsp'
> [Sun Jan 12 13:37:07 2003]  [jk_uri_worker_map.c (558)]: 
> jk_uri_worker_map_t::map_uri_to_worker, Found a suffix match 
> ajp13 -> *.jsp [Sun Jan 12 13:37:07 2003]  [jk_worker.c 
> (132)]: Into wc_get_worker_for_name ajp13 [Sun Jan 12 
> 13:37:07 2003]  [jk_worker.c (136)]: wc_get_worker_for_name, 
> done  found a worker [Sun Jan 12 13:37:07 2003]  
> [jk_ajp_common.c (1404)]: Into jk_worker_t::get_endpoint [Sun 
> Jan 12 13:37:07 2003]  [jk_ajp_common.c (1116)]: Into 
> jk_endpoint_t::service [S

Re: mod_jk error 404 with Apache 1.3.27, Tomcat 4.1.18

[Randall Perry]

That's not it. I get the following error from 'apachectl configtest' :
Context should start with /

> Use:
> JkMount *.jsp ajp13
> JkMount /examples/* ajp13

-- 
Randall Perry
sysTame

Xserve Web Hosting/Co-location
Website Development/Promotion
Mac Consulting/Sales

http://www.systame.com/



--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Re: mod_jk error 404 with Apache 1.3.27, Tomcat 4.1.18

[Randall Perry]

I discovered that the URL I was using to access the pages was wrong.

Never mind. It's working fine. :)


> That's not it. I get the following error from 'apachectl configtest' :
>   Context should start with /
> 
>> Use:
>> JkMount *.jsp ajp13
>> JkMount /examples/* ajp13

-- 
Randall Perry
sysTame

Xserve Web Hosting/Co-location
Website Development/Promotion
Mac Consulting/Sales

http://www.systame.com/



--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

RE: mod_jk error 404 with Apache 1.3.27, Tomcat 4.1.18

[Turner, John]

The error message in this case is correct, as was the previous post.

The correct lines would be:

JkMount /*.jsp ajp13
JkMount /examples/* ajp13 

Note the leading "/" in the first line that was missing previously.

Also, in the original post, the error message specifically said "done
without a match" on "/webapps/examples/jsp" which was also true based on
your original config files.  There was no JkMount that matched that URL.

John


> -Original Message-
> From: Randall Perry [mailto:[EMAIL PROTECTED]]
> Sent: Sunday, January 12, 2003 8:08 PM
> To: [EMAIL PROTECTED]
> Subject: Re: mod_jk error 404 with Apache 1.3.27, Tomcat 4.1.18
> 
> 
> I discovered that the URL I was using to access the pages was wrong.
> 
> Never mind. It's working fine. :)
> 
> 
> > That's not it. I get the following error from 'apachectl 
> configtest' :
> >   Context should start with /
> > 
> >> Use:
> >> JkMount *.jsp ajp13
> >> JkMount /examples/* ajp13
> 
> -- 
> Randall Perry
> sysTame
> 
> Xserve Web Hosting/Co-location
> Website Development/Promotion
> Mac Consulting/Sales
> 
> http://www.systame.com/
> 
> 
> 
> --
> To unsubscribe, e-mail:   
> <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail: 
> <mailto:[EMAIL PROTECTED]>
> 

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

RE: mod_jk error 404 with Apache 1.3.27, Tomcat 4.1.18

[mech]

Well actually *.jsp without leading "/" works for me, too. And I've seen
it also in some tutorials ;-)

By the way, it might by useful to add 

JkMount /examples ajp13

I experienced that http://localhost/examples was not transfered (only
http://localhost/examples/ )to the corresponding examples/index.jsp
until I added above JkMount. But IMHO this small issue might depend also
on Apache's config with respect to trailing slashes. Could be worth a
try in case, but might not be necessary...

mech

> -Original Message-
> From: Turner, John [mailto:[EMAIL PROTECTED]] 
> Sent: Montag, 13. Januar 2003 13:57
> To: 'Tomcat Users List'
> Subject: RE: mod_jk error 404 with Apache 1.3.27, Tomcat 4.1.18
> 
> 
> 
> The error message in this case is correct, as was the previous post.
> 
> The correct lines would be:
> 
> JkMount /*.jsp ajp13
> JkMount /examples/* ajp13 
> 
> Note the leading "/" in the first line that was missing previously.
> 
> Also, in the original post, the error message specifically 
> said "done without a match" on "/webapps/examples/jsp" which 
> was also true based on your original config files.  There was 
> no JkMount that matched that URL.
> 
> John
> 
> 
> > -Original Message-----
> > From: Randall Perry [mailto:[EMAIL PROTECTED]]
> > Sent: Sunday, January 12, 2003 8:08 PM
> > To: [EMAIL PROTECTED]
> > Subject: Re: mod_jk error 404 with Apache 1.3.27, Tomcat 4.1.18
> > 
> > 
> > I discovered that the URL I was using to access the pages was wrong.
> > 
> > Never mind. It's working fine. :)
> > 
> > 
> > > That's not it. I get the following error from 'apachectl
> > configtest' :
> > >   Context should start with /
> > > 
> > >> Use:
> > >> JkMount *.jsp ajp13
> > >> JkMount /examples/* ajp13
> > 
> > --
> > Randall Perry
> > sysTame
> > 
> > Xserve Web Hosting/Co-location
> > Website Development/Promotion
> > Mac Consulting/Sales
> > 
> > http://www.systame.com/
> > 
> > 
> > 
> > --
> > To unsubscribe, e-mail:   
> > <mailto:[EMAIL PROTECTED]>
> > For additional commands, e-mail:
> > <mailto:[EMAIL PROTECTED]>
> > 
> 
> --
> To unsubscribe, e-mail:   
> <mailto:tomcat-user-> [EMAIL PROTECTED]>
> For 
> additional commands, 
> e-mail: <mailto:[EMAIL PROTECTED]>
> 


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Re: Réf. : Re: Réf. : mod_jk error with Apache 2.0.49

[Barry Roberts]

As I've stated in both my previous messages I've tried both and jk1 is
the one I really want to get to work.

On Thu, 2004-05-27 at 01:25, [EMAIL PROTECTED]
wrote:
> You've built jk2. that's ok. Your load instruction is not correct.
> your httpc.conf contains LoadModule jk_module modules/mod_jk.so
> instead ofLoadModule jk2_module modules/mod_jk2.so
> The set of instructions I send to you must work.

It does under VERY low load.  With any reasonable load I get "Broken
Pipe" messages in the tomcat log and pages that just never load.  Again,
this is a known issue that doesn't appear to have a resolution yet.

> You are using apache 2 and jk2. And the instructions you set
> are for jk (not jk2)

No, I'm using jk1.  I'm well aware of the difference. I've used both and
I've never gotten jk2 to work reliably under Linux or Solaris.  That's
why I would prefer jk1.  I only replied to you about jk2 because you
said that's what you're using.  My original message clearly states that
I've tried both.  I have a workers.properties and a workers2.properties,
and I have verified that I'm loading jk2/jk1 when I think I am (by the
log files) and that deleting the applicable .properties prevents apache
from starting.

> 
> 
> 
> Barry Roberts <[EMAIL PROTECTED]>
> 26/05/2004 17:54
> Veuillez rÃpondre à "Tomcat Users List"
> 
> 
> Pour :  Tomcat Users List <[EMAIL PROTECTED]>
> cc :
> Objet : Re: RÃf. : mod_jk error with Apache 2.0.49
> 
> 
> What do you mean the "right" one?  I built jk2 from the
> jakarta-tomcat-connectors-jk2-src-current.tar.gz tarball.  Is that
> "right"?
> 
> The problem I'm having with jk2 is a known issue
> (http://nagoya.apache.org/bugzilla/show_bug.cgi?id=28790).  I would love
> to see that one figured out, but right now I would settle for just
> getting jk1 to work.
> 
> I compiled a modified mod_jk.so and inside get_map (jk_map.c) the
> jk_map_t* passed in is null.  That's why there's no worker found.  I
> haven't had time to try and figure out what could cause it to be null.
> 
> Thanks,
> Barry
> 
> 
> On Wed, 2004-05-26 at 01:34, [EMAIL PROTECTED]
> wrote:
> > Barry,
> >
> > make sure you have built the right jk module.
> >
> > I've exactly the same config than you.
> > Redhat ES 3.0, apache 2.0.49 jk2 and jboss 3.2.3 that
> > comes with tomcat 3.2.3
> >
> > my httpd.conf file  contains :
> > LoadModule jk2_module modules/mod_jk2.so
> > 
> > JKSet config.file /opt/apachessl-2.0.49/inet/conf/workers2.properties
> > 
> >
> > the workers2 file may contains
> > [shm]
> > file=/var/log/apache/inet/jk2.shm
> > [channel.socket:localhost:8009]
> > port=8009
> > host=127.0.0.1
> >
> > [ajp13:localhost:8009]
> > channel=channel.socket:localhost:8009
> >
> > # Uri mapping
> >
> > [uri:/apps/*]
> > worker=ajp13:localhost:8009
> >
> > and it works fine.
> > ___
> > NATEXIS ASSET MANAGEMENT
> > Meissa SAKHO
> > 01 58 19 45 71. . . . . . . . . . . . (84571)
> > [EMAIL PROTECTED]
> >
> >
> >
> >
> > Barry Roberts <[EMAIL PROTECTED]>
> > 25/05/2004 21:14
> > Veuillez rÃpondre à "Tomcat Users List"
> >
> >
> > Pour :  [EMAIL PROTECTED]
> > cc :
> > Objet : mod_jk error with Apache 2.0.49
> >
> >
> > I'm trying to get mod_jk working with apache 2.0.49 built from source on
> > RedHat ES 3.0.  I've got the module built and in the modules directory,
> > and my httpd.conf contains:
> >
> > LoadModule jk_module modules/mod_jk.so
> >
> > JkWorkersFile /usr/local/apache2/conf/workers.properties
> > JkLogFile /var/log/mod_jk.log
> > JkLogLevel debug
> > JkMount /apps/* xsappa
> > JkMount /admin xsappa
> >
> > This is towards the top of the file outside of any  or
> >  elements (I have also tried putting this at the bottom of
> > the file).
> >
> > My workers.properties is:
> >
> >
> > worker.list=xsappa
> >
> > worker.xsappa.port=139
> > worker.xsappa.host=192.168.2.42
> > worker.xsappa.type=ajp13
> > worker.xsappa.lbfactor=1
> >
> > Every time I try to hit a servlet or jsp I get the following in my
> > mod_jk.log:
> > [Tue May 25 12:45:38 2004]  [jk_worker.c (136)]: wc_get_worker_for_name,
> > done did not found a worker
> >
> > And of course a 500 in the browser.
&g

mod_jk error: ERROR: can't receive the response message from tomcat

[Galam]

 
What are all these mod_jk errors?  There are also many "CLOSE_WAIT" messages when I do 
"netstat -n -o". It seems that whenever one of those connections closes, an error 
message is generated in mod_jk.log.
 
Any solutions to this problem?  
 
Thanks!
 
mod_jk.log
---
 
[Sat Mar 13 16:28:54 2004]  [jk_ajp_common.c (738)]: ERROR: can't receive the response 
message from tomcat, network problems or tom$
[Sat Mar 13 16:28:54 2004]  [jk_ajp_common.c (1137)]: Error reading reply from tomcat. 
Tomcat is down or network problems.
[Sat Mar 13 16:28:54 2004]  [jk_ajp_common.c (1290)]: ERROR: Receiving from tomcat 
failed, recoverable operation. err=0
[Sat Mar 13 16:44:23 2004]  [jk_ajp_common.c (738)]: ERROR: can't receive the response 
message from tomcat, network problems or tom$
[Sat Mar 13 16:44:23 2004]  [jk_ajp_common.c (1137)]: Error reading reply from tomcat. 
Tomcat is down or network problems.
[Sat Mar 13 16:44:23 2004]  [jk_ajp_common.c (1290)]: ERROR: Receiving from tomcat 
failed, recoverable operation. err=0
[Sat Mar 13 16:44:26 2004]  [jk_ajp_common.c (738)]: ERROR: can't receive the response 
message from tomcat, network problems or tom$
[Sat Mar 13 16:44:26 2004]  [jk_ajp_common.c (1137)]: Error reading reply from tomcat. 
Tomcat is down or network problems.
[Sat Mar 13 16:44:26 2004]  [jk_ajp_common.c (1290)]: ERROR: Receiving from tomcat 
failed, recoverable operation. err=0

 
output form "netstat -n -o"

tcp1  0 127.0.0.1:35366 127.0.0.1:8009  CLOSE_WAIT  off 
(0.00/0/0)
tcp1  0 127.0.0.1:35367 127.0.0.1:8009  CLOSE_WAIT  off 
(0.00/0/0)
tcp0  0 127.0.0.1:3306  127.0.0.1:32776 ESTABLISHED 
keepalive (5104.92/0/0)
tcp0  0 127.0.0.1:3306  127.0.0.1:32777 ESTABLISHED 
keepalive (5104.93/0/0)
tcp0  0 127.0.0.1:3306  127.0.0.1:32778 ESTABLISHED 
keepalive (5104.94/0/0)
tcp0  0 127.0.0.1:3306  127.0.0.1:32774 ESTABLISHED 
keepalive (5104.74/0/0)
tcp0  0 127.0.0.1:3306  127.0.0.1:32775 ESTABLISHED 
keepalive (5104.92/0/0)
tcp1  0 127.0.0.1:33808 127.0.0.1:8009  CLOSE_WAIT  off 
(0.00/0/0)
tcp1  0 127.0.0.1:33803 127.0.0.1:8009  CLOSE_WAIT  off 
(0.00/0/0)
tcp1  0 127.0.0.1:33800 127.0.0.1:8009  CLOSE_WAIT  off 
(0.00/0/0)
tcp1  0 127.0.0.1:33806 127.0.0.1:8009  CLOSE_WAIT  off 
(0.00/0/0)
tcp1  0 127.0.0.1:33807 127.0.0.1:8009  CLOSE_WAIT  off 
(0.00/0/0)
tcp1  0 127.0.0.1:33805 127.0.0.1:8009  CLOSE_WAIT  off 
(0.00/0/0)
tcp0  0 127.0.0.1:32774 127.0.0.1:3306  ESTABLISHED off 
(0.00/0/0)
tcp0  0 127.0.0.1:32775 127.0.0.1:3306  ESTABLISHED off 
(0.00/0/0)
tcp0  0 127.0.0.1:32778 127.0.0.1:3306  ESTABLISHED off 
(0.00/0/0)
tcp0  0 127.0.0.1:32776 127.0.0.1:3306  ESTABLISHED off 
(0.00/0/0)
tcp0  0 127.0.0.1:32777 127.0.0.1:3306  ESTABLISHED off 
(0.00/0/0)

Do you Yahoo!?
Yahoo! Mail - More reliable, more storage, less spam

Does anyone know why I am getting these mod_jk error messages or what they mean????

[Francom, Kodie]

We are using Tomcat 4.1, Sun JDK 1.4, Linux 7.2 and Apache 1.3.


[Thu Sep 26 18:13:26 2002]  [jk_ajp13_worker.c (845)]: In
jk_endpoint_t::service, get_reply failed in send loop 1
[Thu Sep 26 18:13:26 2002]  [jk_ajp13_worker.c (845)]: In
jk_endpoint_t::service, get_reply failed in send loop 1
[Thu Sep 26 18:13:46 2002]  [jk_ajp13_worker.c (228)]:
connection_tcp_get_message: Error - jk_tcp_socket_recvfull failed
[Thu Sep 26 18:13:46 2002]  [jk_ajp13_worker.c (712)]: Error reading reply
[Thu Sep 26 18:13:46 2002]  [jk_ajp13_worker.c (845)]: In
jk_endpoint_t::service, get_reply failed in send loop 0
[Thu Sep 26 18:13:48 2002]  [jk_ajp13_worker.c (228)]:
connection_tcp_get_message: Error - jk_tcp_socket_recvfull failed
[Thu Sep 26 18:13:48 2002]  [jk_ajp13_worker.c (712)]: Error reading reply
[Thu Sep 26 18:13:48 2002]  [jk_ajp13_worker.c (845)]: In
jk_endpoint_t::service, get_reply failed in send loop 2
[Thu Sep 26 18:13:51 2002]  [jk_ajp13_worker.c (228)]:
connection_tcp_get_message: Error - jk_tcp_socket_recvfull failed
[Thu Sep 26 18:13:51 2002]  [jk_ajp13_worker.c (712)]: Error reading reply
[Thu Sep 26 18:13:51 2002]  [jk_ajp13_worker.c (845)]: In
jk_endpoint_t::service, get_reply failed in send loop 0
[Thu Sep 26 18:13:53 2002]  [jk_ajp13_worker.c (228)]:
connection_tcp_get_message: Error - jk_tcp_socket_recvfull failed
[Thu Sep 26 18:13:53 2002]  [jk_ajp13_worker.c (712)]: Error reading reply
[Thu Sep 26 18:13:53 2002]  [jk_ajp13_worker.c (845)]: In
jk_endpoint_t::service, get_reply failed in send loop 2
[Thu Sep 26 18:13:57 2002]  [jk_ajp13_worker.c (228)]:
connection_tcp_get_message: Error - jk_tcp_socket_recvfull failed


--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

RE: Does anyone know why I am getting these mod_jk error messagesor what they mean????

[Tom Sherrod]

I just fought through these errors this morning.
I found that tomcat didn't have the processes.  I tripled the
maxProcessor settings for the connector and
the mod_jk errors stopped.

After lots of lucky guessing, I finally looked in the catalina_log file
for the tomcat server and found it full of:

2002-10-08 09:57:27 Ajp13Connector[1209] No processor available, rejecting
this connection

Check all logs for clues...

Tom

On Tue, 8 Oct 2002, Ricky Leung wrote:

> I have found that I could generate this error when the site is slow and I go
> view a page and then clicked stop on the browser.  What happens is that the
> user gave up looking at the page and ajp could no longer send it out.  This
> usually happens when jsps are compiling...
>
>
> > -Original Message-
> > From: Francom, Kodie [mailto:[EMAIL PROTECTED]]
> > Sent: Tuesday, October 08, 2002 10:26 AM
> > To: 'Tomcat Users List'
> > Subject: Does anyone know why I am getting these mod_jk error messages
> > or what they mean
> >
> >
> > We are using Tomcat 4.1, Sun JDK 1.4, Linux 7.2 and Apache 1.3.
> >
> >
> > [Thu Sep 26 18:13:26 2002]  [jk_ajp13_worker.c (845)]: In
> > jk_endpoint_t::service, get_reply failed in send loop 1
> > [Thu Sep 26 18:13:26 2002]  [jk_ajp13_worker.c (845)]: In
> > jk_endpoint_t::service, get_reply failed in send loop 1
> > [Thu Sep 26 18:13:46 2002]  [jk_ajp13_worker.c (228)]:
> > connection_tcp_get_message: Error - jk_tcp_socket_recvfull failed
> > [Thu Sep 26 18:13:46 2002]  [jk_ajp13_worker.c (712)]: Error reading reply
> > [Thu Sep 26 18:13:46 2002]  [jk_ajp13_worker.c (845)]: In
> > jk_endpoint_t::service, get_reply failed in send loop 0
> > [Thu Sep 26 18:13:48 2002]  [jk_ajp13_worker.c (228)]:
> > connection_tcp_get_message: Error - jk_tcp_socket_recvfull failed
> > [Thu Sep 26 18:13:48 2002]  [jk_ajp13_worker.c (712)]: Error reading reply
> > [Thu Sep 26 18:13:48 2002]  [jk_ajp13_worker.c (845)]: In
> > jk_endpoint_t::service, get_reply failed in send loop 2
> > [Thu Sep 26 18:13:51 2002]  [jk_ajp13_worker.c (228)]:
> > connection_tcp_get_message: Error - jk_tcp_socket_recvfull failed
> > [Thu Sep 26 18:13:51 2002]  [jk_ajp13_worker.c (712)]: Error reading reply
> > [Thu Sep 26 18:13:51 2002]  [jk_ajp13_worker.c (845)]: In
> > jk_endpoint_t::service, get_reply failed in send loop 0
> > [Thu Sep 26 18:13:53 2002]  [jk_ajp13_worker.c (228)]:
> > connection_tcp_get_message: Error - jk_tcp_socket_recvfull failed
> > [Thu Sep 26 18:13:53 2002]  [jk_ajp13_worker.c (712)]: Error reading reply
> > [Thu Sep 26 18:13:53 2002]  [jk_ajp13_worker.c (845)]: In
> > jk_endpoint_t::service, get_reply failed in send loop 2
> > [Thu Sep 26 18:13:57 2002]  [jk_ajp13_worker.c (228)]:
> > connection_tcp_get_message: Error - jk_tcp_socket_recvfull failed
> >
> >
> > --
> > To unsubscribe, e-mail:
> <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail:
> <mailto:[EMAIL PROTECTED]>
>
>
>
> --
> To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
>



--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

RE: Does anyone know why I am getting these mod_jk error messages or what they mean????

[Ricky Leung]

I have found that I could generate this error when the site is slow and I go
view a page and then clicked stop on the browser.  What happens is that the
user gave up looking at the page and ajp could no longer send it out.  This
usually happens when jsps are compiling...


> -Original Message-
> From: Francom, Kodie [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, October 08, 2002 10:26 AM
> To: 'Tomcat Users List'
> Subject: Does anyone know why I am getting these mod_jk error messages
> or what they mean
>
>
> We are using Tomcat 4.1, Sun JDK 1.4, Linux 7.2 and Apache 1.3.
>
>
> [Thu Sep 26 18:13:26 2002]  [jk_ajp13_worker.c (845)]: In
> jk_endpoint_t::service, get_reply failed in send loop 1
> [Thu Sep 26 18:13:26 2002]  [jk_ajp13_worker.c (845)]: In
> jk_endpoint_t::service, get_reply failed in send loop 1
> [Thu Sep 26 18:13:46 2002]  [jk_ajp13_worker.c (228)]:
> connection_tcp_get_message: Error - jk_tcp_socket_recvfull failed
> [Thu Sep 26 18:13:46 2002]  [jk_ajp13_worker.c (712)]: Error reading reply
> [Thu Sep 26 18:13:46 2002]  [jk_ajp13_worker.c (845)]: In
> jk_endpoint_t::service, get_reply failed in send loop 0
> [Thu Sep 26 18:13:48 2002]  [jk_ajp13_worker.c (228)]:
> connection_tcp_get_message: Error - jk_tcp_socket_recvfull failed
> [Thu Sep 26 18:13:48 2002]  [jk_ajp13_worker.c (712)]: Error reading reply
> [Thu Sep 26 18:13:48 2002]  [jk_ajp13_worker.c (845)]: In
> jk_endpoint_t::service, get_reply failed in send loop 2
> [Thu Sep 26 18:13:51 2002]  [jk_ajp13_worker.c (228)]:
> connection_tcp_get_message: Error - jk_tcp_socket_recvfull failed
> [Thu Sep 26 18:13:51 2002]  [jk_ajp13_worker.c (712)]: Error reading reply
> [Thu Sep 26 18:13:51 2002]  [jk_ajp13_worker.c (845)]: In
> jk_endpoint_t::service, get_reply failed in send loop 0
> [Thu Sep 26 18:13:53 2002]  [jk_ajp13_worker.c (228)]:
> connection_tcp_get_message: Error - jk_tcp_socket_recvfull failed
> [Thu Sep 26 18:13:53 2002]  [jk_ajp13_worker.c (712)]: Error reading reply
> [Thu Sep 26 18:13:53 2002]  [jk_ajp13_worker.c (845)]: In
> jk_endpoint_t::service, get_reply failed in send loop 2
> [Thu Sep 26 18:13:57 2002]  [jk_ajp13_worker.c (228)]:
> connection_tcp_get_message: Error - jk_tcp_socket_recvfull failed
>
>
> --
> To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>



--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>