Re: configure HTTP1.1 pipline depth on Tomcat 5.0
OK my knowledge was weak and I am also not an expert on TC internals. But pipelining makes only sense when the requests could be useful parallel processed (e.g. CPU intensive and more CPU's available) and do not depend on each other. The responses must be delivered anyhow in incoming sequence. And the client has the task of matching responses to requests. - Original Message - From: Caldarale, Charles R [EMAIL PROTECTED] To: Tomcat Users List tomcat-user@jakarta.apache.org Sent: Saturday, June 25, 2005 6:06 PM Subject: RE: configure HTTP1.1 pipline depth on Tomcat 5.0 From: Caldarale, Charles R Subject: RE: configure HTTP1.1 pipline depth on Tomcat 5.0 And so TC will also not accept another request before it processed the last Can you tell us where in the Tomcat code such a restriction is implemented? I haven't been able to find it, although I'm certainly not an expert on Tomcat internals. To answer my own question, the serialization of requests occurs in: org.apache.coyote.http11.Http11Processor where there's a loop in the process() method that insures each pipelined request is responded to before starting on the next. Note that this is a serialization of processing, not accepting, so there does not appear to be any limit on the number of requests that can be pipelined together in a single transmission. There is a configurable limit on the number of keep alives that will be tolerated on an otherwise idle connection. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] ___ Gesendet von Yahoo! Mail - Jetzt mit 1GB Speicher kostenlos - Hier anmelden: http://mail.yahoo.de - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: 503 Service Temporarily Unavailable
Have you checked the tomcat/mod_jk logs (catalina,localhost)? And only to be sure... have you checked the modification dates of your apache/mod_jk config files? of course you have tried restarting tomcat and apache? I have done a quick check and it seems ok. The front page of the site is just html and it serves that up just fine, so port 80 should be fine. Is there something I'm not thinking of? John --- [EMAIL PROTECTED] wrote: I'm sure you have already, but check the Windows Firewall settings. Also check what is actually running and listening on what ports. -Original Message- From: John Lindley [mailto:[EMAIL PROTECTED] Sent: Saturday, June 25, 2005 12:41 AM To: tomcat-user@jakarta.apache.org Subject: 503 Service Temporarily Unavailable I am a consultant running Windows server 2003, Apache 2.0.54, Tomcat 5.0.28, mod_jk2 2.0.4 This machine is stored on site of my client. Last night, they applied some server patches which apparently should have had nothing to do with the Apache/Tomcat setup. Before these patches were applied, everything was working completely fine. After the patches were applied and the machine was restarted, we now get a 503 Service Temporarily Unavailable error. Apache is correctly serving html, and when port 8080 is specified Tomcat serves the jsp pages fine. I saw that someone posted almost the exact same problem on another site earlier today. Did anyone else have this problem pop up? Does anyone have any ideas? I essentially need to get this fixed before Monday, so any help would be greatly appreciated. Thanks! John ___ Gesendet von Yahoo! Mail - Jetzt mit 1GB Speicher kostenlos - Hier anmelden: http://mail.yahoo.de - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: configure HTTP1.1 pipline depth on Tomcat 5.0
AFAIK the pipeline length cannot be more than one by design. No client will send another request before it received the response from the last. And so TC will also not accept another request before it processed the last Karl-Heinz - Original Message - From: Feng Xie (fxie) [EMAIL PROTECTED] Hi, Is there any way to configure HTTP1.1's persistent connection's pipeline length on Tomcat 5.0 ? By pipeline length, I mean the number of HTTP request could be sent by the HTTP/1.1 client before it gets back the first response. Thanks in advance, Feng ___ Gesendet von Yahoo! Mail - Jetzt mit 1GB Speicher kostenlos - Hier anmelden: http://mail.yahoo.de - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Re: configuration question : the number of connections could be supported by a connector in Tomcat 5.0
I think the http protocol does not allow the parallel processing of requests using a single connection. At least the response of a following request cannot pass the predecessor on the same connection. (How could the responses be matched to the requests?) So parallel processing is not really useful on a single connection. If a client/browser wants to have parallel processing it uses more than one connection to a server. Karl-Heinz - Original Message - From: Feng Xie (fxie) [EMAIL PROTECTED] To: Tomcat Users List tomcat-user@jakarta.apache.org Sent: Sunday, June 19, 2005 5:25 AM Subject: RE: Re: configuration question : the number of connections could be supported by a connector in Tomcat 5.0 Bill: Thanks for your answer. In my case, the client just directly talks to Tomcat. So, the maxThread means maxConnections. Is it possible for Tomcat ( any version which supports HTTP/1.1 pipelining)'s multiple threads to work on *A same* connection at the same time. I mean, due to pipelining, there might be multiple HTTP requests in this connection waiting for process , therefore, multiple threads in Tomcat are working on processing those pipelined requests simutaneously -- each thread handling a single different request. -Feng -Original Message- From: news [mailto:[EMAIL PROTECTED] On Behalf Of Bill Barker Sent: Friday, June 17, 2005 10:47 PM To: tomcat-user@jakarta.apache.org Subject: Re: configuration question : the number of connections could be supported by a connector in Tomcat 5.0 If you are fronting with Apache, then the mapping between connections and threads is more a function of your MPM. As a result, I'm just going to answer for the stand-alone Connector. In Tomcat 5.0, there is a one-to-one mapping between socket connections and threads. Pipelined HTTP/1.1 keep-alive connections will all use the same thread to process. In 5.5.10+ this will no longer necessarily be the case. It will be possible for Tomcat to handle many (and the value of 'many' is heavily dependent on what your app does :) more socket connections than the configured maxThreads. Feng Xie (fxie) [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] . I like to get some help on how to configure the maximum number of connections could be supported by Tomcat5.0. There is one config attribute called maxThreads, according to Tomcat doc, which isThe maximum number of request processing threads to be created by this Connector, which therefore determines the maximum number of simultaneous requests that can be handled. . My question comes from the fact that there might be multiple HTTP requests pipelined in each HTTP/1.1 connections, so can we still treat the maxThread as the maxConnections. Thanks in advance, Feng - 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] ___ Gesendet von Yahoo! Mail - Jetzt mit 1GB Speicher kostenlos - Hier anmelden: http://mail.yahoo.de - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Managing automatic deployment with multiple virtual hosts
http://jakarta.apache.org/tomcat/tomcat-5.5-doc/config/host.html#Automatic Application Deployment #The context path for this deployed Context will be a slash character (/) followed by the directory name, unless the directory name is ROOT, in which case the context path will be an empty string ().# The directory name is generated from the war filename. - Original Message - From: Ben Rometsch [EMAIL PROTECTED] To: Tomcat Users List tomcat-user@jakarta.apache.org Sent: Sunday, June 12, 2005 12:39 PM Subject: RE: Managing automatic deployment with multiple virtual hosts That seems to have been the solution! Thanks very much. Is this documented anywhere in the official Tomcat documentation? -Original Message- From: charly [mailto:[EMAIL PROTECTED] Sent: 11 June 2005 10:08 To: Tomcat Users List Subject: Re: Managing automatic deployment with multiple virtual hosts Hello, have you tried naming the war files ROOT.war?? Because I think there is a special naming convention for the root context. This means if you have different applications you need to deploy them into different folders. Karl-Heinz - Original Message - From: Ben Rometsch [EMAIL PROTECTED] To: tomcat-user@jakarta.apache.org Sent: Friday, June 10, 2005 10:34 PM Subject: Managing automatic deployment with multiple virtual hosts Hi There, I am running Tomcat 5.5.9 in production, using 1 tomcat instance to service several websites (each with their own hostname) via virtual hosts. I have Apache 2 running in front of Tomcat, connecting via mod_jk. I am having OutOfMemory issues, and have noticed that, due to my webapps structure, I appear to be deploying 2 instances of each site. When I look in the manager application I see the following in the Application List: www.sitea.com/ localhost/sitea www.siteb.com/ localhost/siteb www.sitec.com/ localhost/sitec Etc. etc. My current directory structure is simply placing the war files for each application into the tomcat/webapps folder. I then add a Host declaration in the server.xml file for each virtual host: Host name=www.sitea.com Context path= docBase=/opt/tomcat/webapps/sitea debug=0 reloadable=true/ /Host Host name=www.siteb.com Context path= docBase=/opt/tomcat/webapps/siteb debug=0 reloadable=true/ /Host Host name=www.sitec.com Context path= docBase=/opt/tomcat/webapps/sitec debug=0 reloadable=true/ /Host I still have the localhost set up in the server.xml file: Host name=localhost appBase=webapps unpackWARs=true autoDeploy=true xmlValidation=false xmlNamespaceAware=false I presume this is the culprit. The problem I am having is that I cant figure out how to get Tomcat to auto-deploy war files without then creating a second running instance in memory with a context path of /sitea. I've tried a variety of different directory structures, but am unable to deploy a war file without it correctly deploying to a / path, and thus not consuming more memory within the VM. Is there a best practise way of doing this? Should I be putting context.xml declarations in the META-INF directory of my war files? Thanks in advance, Ben - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] ___ Gesendet von Yahoo! Mail - Jetzt mit 1GB Speicher kostenlos - Hier anmelden: http://mail.yahoo.de - 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] ___ Gesendet von Yahoo! Mail - Jetzt mit 1GB Speicher kostenlos - Hier anmelden: http://mail.yahoo.de - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Managing automatic deployment with multiple virtual hosts
Hello, have you tried naming the war files ROOT.war?? Because I think there is a special naming convention for the root context. This means if you have different applications you need to deploy them into different folders. Karl-Heinz - Original Message - From: Ben Rometsch [EMAIL PROTECTED] To: tomcat-user@jakarta.apache.org Sent: Friday, June 10, 2005 10:34 PM Subject: Managing automatic deployment with multiple virtual hosts Hi There, I am running Tomcat 5.5.9 in production, using 1 tomcat instance to service several websites (each with their own hostname) via virtual hosts. I have Apache 2 running in front of Tomcat, connecting via mod_jk. I am having OutOfMemory issues, and have noticed that, due to my webapps structure, I appear to be deploying 2 instances of each site. When I look in the manager application I see the following in the Application List: www.sitea.com/ localhost/sitea www.siteb.com/ localhost/siteb www.sitec.com/ localhost/sitec Etc. etc. My current directory structure is simply placing the war files for each application into the tomcat/webapps folder. I then add a Host declaration in the server.xml file for each virtual host: Host name=www.sitea.com Context path= docBase=/opt/tomcat/webapps/sitea debug=0 reloadable=true/ /Host Host name=www.siteb.com Context path= docBase=/opt/tomcat/webapps/siteb debug=0 reloadable=true/ /Host Host name=www.sitec.com Context path= docBase=/opt/tomcat/webapps/sitec debug=0 reloadable=true/ /Host I still have the localhost set up in the server.xml file: Host name=localhost appBase=webapps unpackWARs=true autoDeploy=true xmlValidation=false xmlNamespaceAware=false I presume this is the culprit. The problem I am having is that I cant figure out how to get Tomcat to auto-deploy war files without then creating a second running instance in memory with a context path of /sitea. I've tried a variety of different directory structures, but am unable to deploy a war file without it correctly deploying to a / path, and thus not consuming more memory within the VM. Is there a best practise way of doing this? Should I be putting context.xml declarations in the META-INF directory of my war files? Thanks in advance, Ben - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] ___ Gesendet von Yahoo! Mail - Jetzt mit 1GB Speicher kostenlos - Hier anmelden: http://mail.yahoo.de - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: when web.xml changes webapp does not reload if not in webapps (only TC 5.5.9!!)
I do not mean manually reloading using the manager webinterface. I mean automatically reloading when (e.g. class or web.xml) files are changed. The manager webapp is only an example webapp which is not located in the %catalina_base%/webapps folder. I have tried with TC 5.0.30 right now. TC 5.0.30 operates as I expected. The manager webapp reloads when I modify web.xml. It seems to be bug (or feature) with 5.5.9. Can a TC developer say something about this? Regards Karl-Heinz - Original Message - From: Anto Paul [EMAIL PROTECTED] To: Tomcat Users List tomcat-user@jakarta.apache.org Sent: Friday, June 03, 2005 6:33 AM Subject: Re: when web.xml changes webapp does not reload if not in webapps .. On 6/3/05, charly [EMAIL PROTECTED] wrote: For example if I change web.xml of manager the manager webapp will not automatically reload. I think you cannot start,stop or reload the manager application. If you look at the localhost/manager/html you can see that there is no link to do that. -- rgds Anto Paul - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] ___ Gesendet von Yahoo! Mail - Jetzt mit 1GB Speicher kostenlos - Hier anmelden: http://mail.yahoo.de - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
when web.xml changes webapp does not reload if not in webapps
Hello,
How should I configure a webapp which is not located in
${catalina.base}/webapps/ that it will reload when I change its web.xml.
For example if I change web.xml of manager the manager webapp will not
automatically reload.
Adding WatchedResourceWEB-INF/web.xml/WatchedResource to
${catalina.base}/conf/catalina/localhost/manager.xml does not make a visible
difference:
Context docBase=${catalina.home}/server/webapps/manager
privileged=true antiResourceLocking=false antiJARLocking=false
!-- Link to the user database we will get roles from --
ResourceLink name=users global=UserDatabase
type=org.apache.catalina.UserDatabase/
WatchedResourceWEB-INF/web.xml/WatchedResource
/Context
Does anyone know how to configure this?
For what is WatchedResource used for, if not for this?
Any ideas?
Regards Karl-Heinz
___
Gesendet von Yahoo! Mail - Jetzt mit 1GB Speicher kostenlos - Hier anmelden: http://mail.yahoo.de
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
when web.xml changes webapp does not reload if not in webapps ..
Hello,
Sorry I forgot something.
How should I configure a webapp which is not located in
${catalina.base}/webapps/ that it will reload when I change its web.xml.
For example if I change web.xml of manager the manager webapp will not
automatically reload.
Adding WatchedResourceWEB-INF/web.xml/WatchedResource or
reloadable=true to
${catalina.base}/conf/catalina/localhost/manager.xml does not make a visible
difference:
Context docBase=${catalina.home}/server/webapps/manager
privileged=true antiResourceLocking=false antiJARLocking=false
reloadable=true
!-- Link to the user database we will get roles from --
ResourceLink name=users global=UserDatabase
type=org.apache.catalina.UserDatabase/
WatchedResourceWEB-INF/web.xml/WatchedResource
/Context
Does anyone know how to configure this?
For what is WatchedResource used for, if not for this?
Any ideas?
Regards Karl-Heinz
___
Gesendet von Yahoo! Mail - Jetzt mit 1GB Speicher kostenlos - Hier anmelden: http://mail.yahoo.de
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
NTLM authentication using jCIFS over JK1.2.10 IIS fails
I am currently using TC 5.0.28 http1.1-connector and JCIFS for authentication in a webapp. Authentication is done completely within the webapp without using TC methods and only when necessary. This is working quite well except for few users, who are accessing over squid proxy, which suppresses the ntlm auth headers. Only to overcome this and for these users I added access via https/443 using IIS (W2K-Server) and JK2.0.4, furthermore using jCIFS for authentication. This is running ok but unfortunately JK2.0.4 has this file upload bug. Therefore I wanted to upgrade to JK1.2.10 (and thereby TC 5.5.9). But I cannot get the ntlm authentication running over JK1.2.10/IIS. IE shows the login box, though it should silently authenticate. It seems that IIS/JK interferes with the authentication headers/process. I have configured jakarta within IIS to not use basic or integrated windows auth. In the mailing lists I have not found anything (of course except using IIS builtin authentication). I have found a description with also a jCIFS/JK problem, http://lists.samba.org/archive/jcifs/2003-July/002359.html but no solution. Also I did not found any jk configuration parameters, which seem to apply to this. Primarily I do not want to activate authentication within IIS. I want to leave it to the webapp jCIFS in order to avoid two different auth methods. The tomcat version does not seam to matter. Summary: requests running via TC + http1.1 + jCIFS authenticating: OK TC + jk2.0.4/IIS + noauthenticating: OK TC + jk2.0.4/IIS + jCIFS authenticating: OK TC + jk1.2.10/IIS + noauthenticating: OK TC + jk1.2.10/IIS + JCIFS authenticating: NOT OK Anyone an idea whats the difference between jk2.0.4 and jk1.2.10 causing this behaviour ? Have I overlooked something? Is this a bug within JK1.2.10? Regards Karl-Heinz ___ Gesendet von Yahoo! Mail - Jetzt mit 1GB Speicher kostenlos - Hier anmelden: http://mail.yahoo.de - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
