mod_jk Ajp13 and Tomcat 3.2.X

[Chad Cannell]

I am working on Tuning our Apache 2.0, mod_jk-2.0.42, Tomcat 3.2.3 on
Win2K config

In all I have read, I never have seen that you can set minProcessors,
maxProcessors, and acceptCount in the Tomcat 3.2.3 server.xml like:









I did that and the system degraded conciderably. If I remove them I do
better, like this:






What do the minProcessors, maxProcessors, and acceptCount default to in
this config?
Can I use explictly set minProcessors, maxProcessors, and acceptCount in
Tomcat 3.2.3? Guidelines?

Chad

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

RE: Standalone Machine

[Chad Cannell]

-Original Message-
From: Craig R. McClanahan [mailto:craigmcc@;apache.org]
Sent: Thursday, November 14, 2002 4:03 PM
To: Tomcat Users List
Subject: Re: Standalone Machine




On Thu, 14 Nov 2002, Conyers, Dwayne wrote:

> Date: Thu, 14 Nov 2002 14:47:52 -0500
> From: "Conyers, Dwayne" <[EMAIL PROTECTED]>
> Reply-To: Tomcat Users List <[EMAIL PROTECTED]>
> To: 'Tomcat Users List' <[EMAIL PROTECTED]>
> Subject: Standalone Machine
>
> We are prototyping on a machine that unfortunately does not have a
network
> card and no internet connectivity.
>
> Our attempts at viewing resources are failing and looking at Tomcat
> Administration it appears that the Session ID initializer needs an
external
> URL to function.
>

Works fine for me on a disconnected Win2K laptop (4.0, 4.1, 5.0).  What
version are you running?  What gave you the impression that the session
id
initializer needs anything external?

"Without a network card" might be a problem if your OS doesn't properly
initialize the TCP/IP network layer without it.  But there's no way to
help you without more detailed info about what failures (such as
exceptions and stack traces) you are seeing.

> Any ideas on how to fix?
>
> Thanks!

Craig


--
To unsubscribe, e-mail:

For additional commands, e-mail:



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

RE: Apache Index page jsp and sessionid with JKMount *.jsp

[Chad Cannell]

Yea, I'm more comfortable at this point just adding the meta redirect.
Thanks for all the suggestions though!

C

-Original Message-
From: Turner, John [mailto:JTurner@;AAS.com]
Sent: Thursday, November 14, 2002 8:22 AM
To: 'Tomcat Users List'
Subject: RE: Apache Index page jsp and sessionid with JKMount *.jsp



All I know is the behavior I see on my servers.

I have DirectoryIndex set to index.jsp.  My Apache has mod_dir.

Calling a directory mapped to Tomcat (such as /myApp) with
http://localhost/myApp doesn't return anything, definitely not
index.jsp.
This is on 4.0.4 and 4.1.12.  

If your DirectoryIndex does work with index.jsp, I'd be interested in
seeing
your configuration.  About the only way I can think of to approach this
problem is to play with the load order for the Apache modules...perhaps
loading mod_jk at a different time or loading mod_dir after mod_jk might
change the behavior.  For me, at this time, it's just easier to stick an
index.html file in there with a refresh of 0.  

John


> -Original Message-
> From: Veniamin Fichin [mailto:3ca28f66@;mail.ru]
> Sent: Thursday, November 14, 2002 3:31 AM
> To: Tomcat Users List
> Subject: Re: Apache Index page jsp and sessionid with JKMount *.jsp
> 
> 
> Turner, John wrote:
> 
> > That's pretty much the solution...this has come up before.  
> > 
> > By the time JK gets involved, Apache is just about done 
> with the URL...it
> > doesn't perform any rewriting, etc. it's just looking for a match.
> 
> But in my understanding first of all when Apache is requested 
> to process 
> some directory (for example, http://www.somehost.com/test/), 
> it tries to 
> invoke any file listed in its DirectoryIndex directive, then he finds 
> index.jsp and invokes it, causing to jk to wake up. So Apache 
> is first 
> in action, and jk is following it. Am I right?
> 
> > The elegant solution is probably using mod_rewrite to 
> rewrite requests
> > ending in "/" to "/index.jsp".
> > 
> > John
> > 
> >>-Original Message-
> >>From: Chad Cannell [mailto:ccannell@;elogex.com]
> >>Sent: Wednesday, November 13, 2002 3:45 PM
> >>To: Tomcat Users List
> >>Subject: Apache Index page jsp and sessionid with JKMount *.jsp
> >>
> >>
> >>I am trying to set Apache's index file to index.jsp. It is 
> >>not working.
> --= [ cut ] =--
> >>
> >>Using Apache 2.0, ajp13. Tomcat 3.2x
> >>
> >>Chad
> 
> 
> 
> --
> To unsubscribe, e-mail:   
<mailto:tomcat-user-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail:
<mailto:tomcat-user-help@;jakarta.apache.org>

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


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

Apache Index page jsp and sessionid with JKMount *.jsp

[Chad Cannell]

I am trying to set Apache's index file to index.jsp. It is not working.

I am using JKmount *.jsp for the dynamic stuff, so for what ever reason,
Apache won't server this as the point of entry to our site.

We currently use an index.html page to redirect to index.jsp, but want
to get rid of that.

Any ideas?

Using Apache 2.0, ajp13. Tomcat 3.2x

Chad

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

RE: mod_jk.log entries

[Chad Cannell]

Is there an error reference guide or chart. I need to look into the
folowing errors:

I am seeing a lot of chatter in my mod_jk.log:

[jk_ajp13_worker.c (326)]: Error ajp13_process_callback - write failed
[jk_uri_worker_map.c (335)]:
jk_uri_worker_map_t::uri_worker_map_close,NULL parameter
[jk_uri_worker_map.c (185)]: In
jk_uri_worker_map_t::uri_worker_map_free, NULL parameters
[jk_ajp13_worker.c (326)]: Error ajp13_process_callback - write failed
[jk_ajp13_worker.c (204)]: connection_tcp_get_message: Error -
jk_tcp_socket_recvfull failed
[jk_ajp13_worker.c (622)]: Error reading request
[jk_connect.c (143)]: jk_open_socket, connect() failed errno = 61
[jk_ajp13_worker.c (174)]: In jk_endpoint_t::connect_to_tomcat, failed
errno = 61
[jk_ajp13_worker.c (587)]: Error connecting to the Tomcat process.


Can anyone help me dicepher these and are they critical? 

Chad


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

mod_jk.log entries

[Chad Cannell]

I am seeing a lot of chatter in my mod_jk.log:

[jk_ajp13_worker.c (326)]: Error ajp13_process_callback - write failed
[jk_uri_worker_map.c (335)]: jk_uri_worker_map_t::uri_worker_map_close,
NULL parameter
[jk_uri_worker_map.c (185)]: In
jk_uri_worker_map_t::uri_worker_map_free, NULL parameters
[jk_ajp13_worker.c (326)]: Error ajp13_process_callback - write failed
[jk_ajp13_worker.c (204)]: connection_tcp_get_message: Error -
jk_tcp_socket_recvfull failed
[jk_ajp13_worker.c (622)]: Error reading request
[jk_connect.c (143)]: jk_open_socket, connect() failed errno = 61
[jk_ajp13_worker.c (174)]: In jk_endpoint_t::connect_to_tomcat, failed
errno = 61
[jk_ajp13_worker.c (587)]: Error connecting to the Tomcat process.


Can anyone help me dicepher these and are they critical? 

Chad

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

RE: Friendly error messages when Tomcat is down

[Chad Cannell]

You say you have tried the: ErrorDocument 500 ./systemUnavail.html 
directive? We are using this and it works well when Tomacat is down.

c

-Original Message-
From: Andrew Ormsby [mailto:andrew.ormsby@;lexicle.com]
Sent: Monday, November 11, 2002 11:29 AM
To: [EMAIL PROTECTED]
Subject: Friendly error messages when Tomcat is down


Hi,

Like Robert Tansley in another message on the list earlier today, we're 
trying to get friendly error pages produced when Tomcat is down.

Specifically, we're using Tomcat 4.1.12 front-ended with Apache 2.0.43 
via mod_jk2.

We've tried various combinations of ErrorDocuments in httpd.conf but 
these don't seem to have the desired effect.  When Tomcat is 
unavailable, references to a JSP served by Tomcat produce the following 
page:


The servlet container is temporary unavailable or being upgraded
Internal Server Error

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.

Additionally, a 500 Internal Server Error error was encountered while
trying to use an ErrorDocument to handle the request.


I've seen a reference to a "noWorkerMsg" and "noWorkerCode" in the 
documentation for jk2 which look somewhat promising but there's no 
explanation of what these do or how to use them.

Right now, we're stuck.  Any suggestions?

Regards,

Andy Ormsby


--
To unsubscribe, e-mail:

For additional commands, e-mail:



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

mod_jk2/ajp13 and Tomcat 3.x

[Chad Cannell]

Can Tomcat 3.x and Apache 1.3.X use the mod_jk2 ajp13 connector? We
aren't able to move up to 4.X yet but would like to use mod_jk2 as it
seems to provide more worker configurabilit and performance than mod_jk
and ajp13 for Tomcat 3.x. For example the minProcessors, MaxProcessors,
acceptCount do not appear to be available for an mod_jk, ajb13 Tomcat
3.x setup.

Chad

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

RE: Suppress Servlet-Engine Info in HTTP Header

[Chad Cannell]

Would it be possible to see your module and add mod section of your
httpd.conf file? Not the whole thing just the 2 mod sections. I must be
missing a module.

c

-Original Message-
From: Tim Funk [mailto:funkman@;joedog.org]
Sent: Wednesday, November 06, 2002 1:09 PM
To: Tomcat Users List
Subject: Re: Suppress Servlet-Engine Info in HTTP Header


I'm out of ideas at this point. In any case I would try the following:
- Add another header of the same name and see what happens
- Add another header of a diff name and see what happens. If this 
doesn't work - then I would go to the apache user lists for help.

My admin installed (compiled) mod_headers for me and I use it with no 
problem w/respect to P3P. (http://www.w3.org/P3P/ for those curious) So 
I can't be of anymore help except for the debugging advice above.

-Tim

Chad Cannell wrote:
> Still not doing the trick, tried adding to the server level directive
> and the Root directory directive. Have the modules added and loaded. 
> 
> LoadModule headers_module modules/mod_headers.so
> AddModule mod_headers.c
> 
> Any other modules needed? Any other thoughts
> 
> -Original Message-
> From: Tim Funk [mailto:funkman@;joedog.org]
> Sent: Wednesday, November 06, 2002 11:18 AM
> To: Tomcat Users List
> Subject: Re: Suppress Servlet-Engine Info in HTTP Header
> 
> 
> See mod_headers: http://httpd.apache.org/docs/mod/mod_headers.html
> 
> In particular, you probably want this:
> ##
> Header unset Servlet-Engine
> ##
> 
> -Tim
> 
> 
> Chad Cannell wrote:
> 
>>I am trying to tighten up our Apache and Tomcat implementation. I want
>>to suppress server type and version to make fingerprinting harder. We
>>have Apache httpd in front of Tomacat on Win32. I can suppress the
>>Apache info passed in "Server:" parameter, but do not know how to
>>suppress the "Servlet-Engine:" that Tomcat passes.  Anyone?
>>
>>HTTP response header
>>
>>HTTP/1.1 200 OK
>>Date: Tue, 05 Nov 2002 17:49:51 GMT
>>Server: 
>>Set-Cookie2: JSESSIONID=naa2in3fj1;Version=1;Discard;Path="/"
>>Set-Cookie: JSESSIONID=naa2in3fj1;Path=/
>>Servlet-Engine: Tomcat Web Server/3.2.3 (JSP 1.1; Servlet 2.2; Java
>>1.3.1_04; Windows 2000 5.0 x86; java.vendor=Sun Microsystems Inc.)
>><---Want to null this  
>>Connection: close
>>
> 
> 
> 
> --
> To unsubscribe, e-mail:
> <mailto:tomcat-user-unsubscribe@;jakarta.apache.org>
> For additional commands, e-mail:
> <mailto:tomcat-user-help@;jakarta.apache.org>
> 
> 
> --
> To unsubscribe, e-mail:
<mailto:tomcat-user-unsubscribe@;jakarta.apache.org>
> For additional commands, e-mail:
<mailto:tomcat-user-help@;jakarta.apache.org>
> 
> 
> 


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


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

RE: Suppress Servlet-Engine Info in HTTP Header

[Chad Cannell]

Still not doing the trick, tried adding to the server level directive
and the Root directory directive. Have the modules added and loaded. 

LoadModule headers_module modules/mod_headers.so
AddModule mod_headers.c

Any other modules needed? Any other thoughts

-Original Message-
From: Tim Funk [mailto:funkman@;joedog.org]
Sent: Wednesday, November 06, 2002 11:18 AM
To: Tomcat Users List
Subject: Re: Suppress Servlet-Engine Info in HTTP Header


See mod_headers: http://httpd.apache.org/docs/mod/mod_headers.html

In particular, you probably want this:
##
Header unset Servlet-Engine
##

-Tim


Chad Cannell wrote:
> I am trying to tighten up our Apache and Tomcat implementation. I want
> to suppress server type and version to make fingerprinting harder. We
> have Apache httpd in front of Tomacat on Win32. I can suppress the
> Apache info passed in "Server:" parameter, but do not know how to
> suppress the "Servlet-Engine:" that Tomcat passes.  Anyone?
> 
> HTTP response header
> 
> HTTP/1.1 200 OK
> Date: Tue, 05 Nov 2002 17:49:51 GMT
> Server: 
> Set-Cookie2: JSESSIONID=naa2in3fj1;Version=1;Discard;Path="/"
> Set-Cookie: JSESSIONID=naa2in3fj1;Path=/
> Servlet-Engine: Tomcat Web Server/3.2.3 (JSP 1.1; Servlet 2.2; Java
> 1.3.1_04; Windows 2000 5.0 x86; java.vendor=Sun Microsystems Inc.)
> <---Want to null this  
> Connection: close
> 


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


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

Suppress Servlet-Engine Info in HTTP Header

[Chad Cannell]

I am trying to tighten up our Apache and Tomcat implementation. I want
to suppress server type and version to make fingerprinting harder. We
have Apache httpd in front of Tomacat on Win32. I can suppress the
Apache info passed in "Server:" parameter, but do not know how to
suppress the "Servlet-Engine:" that Tomcat passes.  Anyone?

HTTP response header

HTTP/1.1 200 OK
Date: Tue, 05 Nov 2002 17:49:51 GMT
Server: 
Set-Cookie2: JSESSIONID=naa2in3fj1;Version=1;Discard;Path="/"
Set-Cookie: JSESSIONID=naa2in3fj1;Path=/
Servlet-Engine: Tomcat Web Server/3.2.3 (JSP 1.1; Servlet 2.2; Java
1.3.1_04; Windows 2000 5.0 x86; java.vendor=Sun Microsystems Inc.)
<---Want to null this  
Connection: close

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