AW: tomcat and apache
Tomcat is listening on port 8080 and the standard port for HTTP is port 80. If you only call a page like http://ip-address/examples then the webserver looks for a directory called examples. The http-server has no knowledge that the resource is managed by a servlet engine. Therefore you must complete your URL by the requested port (8080). Port 80 is a so called well knwon port need not be specified extra, but if you want to have a very correct URL you must type in: http://address:80/documentation/servlet.html. You can use other ports than 8080 - but mostly it really makes no sense. Have also a look to the conf-directory of tomcat and tomcat's documentation. franzR __ _ / / (_)__ __ __ / /__/ / _ \/ // /\ \/ / //_/_//_/\_,_/ /_/\_\ TUX for President -Ursprüngliche Nachricht- Von: Andreas Boeyer [mailto:[EMAIL PROTECTED]] Gesendet: Freitag, 31. Mai 2002 23:04 An: [EMAIL PROTECTED] Betreff: tomcat and apache Hello, I have a problem with apache and tomcat. Everything is working fine, as long I stay on the same computer. If I call the servelet examples or jsp from an other computer it only work if I typ the IP-address and the port 8080. If I call the page normal like http://ip-address/examples the browser always say webpage not found I try now since two days and don't know how to solve my problem. when I call the examples with a webbrowser on the local computer the adress line of the browser change to http://linux.local/examples How can external computers find my servlet if the adress change to http://linux.local/examples Thanks a lot Andreas [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]
AW: Tomcat, Webapp, Apache and mod_ssl, Protocol is switching
That sound like https://intra.home.de/examples/servlets/ is redirected to http://intra.home.de:443/examples/servlets/index.html To me this looks like a bug in the part of tomcat that is responsible for the redirection to the 'welcome file'. (The welcome file is implemented in tomcat as a http redirect) Using mod_rewrite on port 80 won't help anything as your browser is already talking to port 443 (just with the wrong protokoll). If you really need the welcome file you can try to let apache serve the welcome file: LoadModule dir_module path-to-apache/lib/mod_dir.so ... IfModule mod_dir.c DirectoryIndex index.html /index.html # First look in the requested directory for index.html, # if this file doesn't exist look in the document root for # index.html /IfModule 'https://intra.home.de/examples/servlets/' It does not matter, if click on the link, or type it in the Browser snip/ I tried also to use apaches mod_rewrite to redirect all acesses from Port 80 to Port 443, but this did not work either snip/ -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
AW: Tomcat, Webapp, Apache and mod_ssl, Protocol is switching
Well, to me it looks also like a bug in tomcat if a file index.html exists in https://intra.home.de/examples/ (an delployed Application) and it contains a line META HTTP-EQUIV=refresh CONTENT=0; URL=servlet/myapp or META HTTP-EQUIV=refresh CONTENT=0; URL=https://intra.home.de/examples/servlet/myapp; tomcat resolves this and you get an error Message in the Browser: http://intra.home.de:443/examples/servlets/index.html does not exist from Apache (that is right) if I rename the File from index.html to something.html the Directory Listing is displayed; clicking on the File something.html serves the right page, as intended in META HTTP-EQUIV=refresh CONTENT=0; ... If somebody knows a little bit more about this issue (or any workaround) please let me know Thanks -Ursprüngliche Nachricht- Von: Ralph Einfeldt [mailto:[EMAIL PROTECTED]] Gesendet: Mittwoch, 27. März 2002 11:05 An: Tomcat Users List Betreff: AW: Tomcat, Webapp, Apache and mod_ssl, Protocol is switching That sound like https://intra.home.de/examples/servlets/ is redirected to http://intra.home.de:443/examples/servlets/index.html To me this looks like a bug in the part of tomcat that is responsible for the redirection to the 'welcome file'. (The welcome file is implemented in tomcat as a http redirect) Using mod_rewrite on port 80 won't help anything as your browser is already talking to port 443 (just with the wrong protokoll). If you really need the welcome file you can try to let apache serve the welcome file: LoadModule dir_module path-to-apache/lib/mod_dir.so ... IfModule mod_dir.c DirectoryIndex index.html /index.html # First look in the requested directory for index.html, # if this file doesn't exist look in the document root for # index.html /IfModule 'https://intra.home.de/examples/servlets/' It does not matter, if click on the link, or type it in the Browser snip/ I tried also to use apaches mod_rewrite to redirect all acesses from Port 80 to Port 443, but this did not work either snip/ -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED] -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
AW: Tomcat, Webapp, Apache and mod_ssl, Protocol is switching
Did you try my apache work around ? -Ursprüngliche Nachricht- Von: Schulze Christian [mailto:[EMAIL PROTECTED]] Gesendet: Mittwoch, 27. März 2002 13:43 An: 'Tomcat Users List' Betreff: AW: Tomcat, Webapp, Apache and mod_ssl, Protocol is switching (or any workaround) please let me know LoadModule dir_module path-to-apache/lib/mod_dir.so ... IfModule mod_dir.c DirectoryIndex index.html /index.html # First look in the requested directory for index.html, # if this file doesn't exist look in the document root for # index.html /IfModule -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
AW: Tomcat, Webapp, Apache and mod_ssl, Protocol is switching
No mod_dir does not work, because mod_webapp first finds a match for /myapp , further processing of all /myapp/... is from now on not been done by apache. I also tried to manipulate with the Alias directive (like it is used for /icons/) but did not work either; probably the same reason as with mod_dir Christian -Ursprüngliche Nachricht- Von: Ralph Einfeldt [mailto:[EMAIL PROTECTED]] Gesendet: Mittwoch, 27. März 2002 15:33 An: Tomcat Users List Betreff: AW: Tomcat, Webapp, Apache and mod_ssl, Protocol is switching Did you try my apache work around ? -Ursprüngliche Nachricht- Von: Schulze Christian [mailto:[EMAIL PROTECTED]] Gesendet: Mittwoch, 27. März 2002 13:43 An: 'Tomcat Users List' Betreff: AW: Tomcat, Webapp, Apache and mod_ssl, Protocol is switching (or any workaround) please let me know LoadModule dir_module path-to-apache/lib/mod_dir.so ... IfModule mod_dir.c DirectoryIndex index.html /index.html # First look in the requested directory for index.html, # if this file doesn't exist look in the document root for # index.html /IfModule -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED] -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
AW: Tomcat, Webapp, Apache and mod_ssl, Protocol is switching
I see only following chances: - switch to mod_jk. - find and fix the bug in tomcat. - enter this problem in bugzilla and hope that a tomcat developer finds a solution. - write your own code to implement the 'welcome file' and disable the tomcat component. -Ursprüngliche Nachricht- Von: Schulze Christian [mailto:[EMAIL PROTECTED]] Gesendet: Mittwoch, 27. März 2002 16:42 An: 'Tomcat Users List' Betreff: AW: Tomcat, Webapp, Apache and mod_ssl, Protocol is switching snip/ No mod_dir does not work, because mod_webapp first finds a match for /myapp , further processing of all /myapp/... is from now on not been done by apache. snip/ -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
AW: Tomcat, Webapp, Apache and mod_ssl, Protocol is switching
http://intra.home.de:443/examples/servlets/index.html Tomcat (or apache) doesn't switch to https you told the browser to do it :) The port 443 is the port for https. But as you tell the browser to use http it's trying to talk http to the https port. (Have a close look at the leading http://) -Ursprüngliche Nachricht- Von: Schulze Christian [mailto:[EMAIL PROTECTED]] Gesendet: Dienstag, 26. März 2002 14:13 An: '[EMAIL PROTECTED]' Betreff: Tomcat, Webapp, Apache and mod_ssl, Protocol is switching The adress shown in my Browser says: 'http://intra.home.de:443/examples/servlets/index.html' snip/ Why is Tomcat switching the protocol from https to http ? As far as I understand the webapp-module everything should work transparently ? ... snip/ -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
AW: Tomcat, Webapp, Apache and mod_ssl, Protocol is switching
I noticed this, but if i view the source of this page (obviously generated by Tomcat) the links just looks this way a href=/examples/servlets/ so the Adress should be right. It seems , that if Tomcat creates an index.html when I access a Directory i maps the URL from https to http ... ??? -Ursprüngliche Nachricht- Von: Ralph Einfeldt [mailto:[EMAIL PROTECTED]] Gesendet: Dienstag, 26. März 2002 15:58 An: Tomcat Users List Betreff: AW: Tomcat, Webapp, Apache and mod_ssl, Protocol is switching http://intra.home.de:443/examples/servlets/index.html Tomcat (or apache) doesn't switch to https you told the browser to do it :) The port 443 is the port for https. But as you tell the browser to use http it's trying to talk http to the https port. (Have a close look at the leading http://) -Ursprüngliche Nachricht- Von: Schulze Christian [mailto:[EMAIL PROTECTED]] Gesendet: Dienstag, 26. März 2002 14:13 An: '[EMAIL PROTECTED]' Betreff: Tomcat, Webapp, Apache and mod_ssl, Protocol is switching The adress shown in my Browser says: 'http://intra.home.de:443/examples/servlets/index.html' snip/ Why is Tomcat switching the protocol from https to http ? As far as I understand the webapp-module everything should work transparently ? ... snip/ -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED] -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
AW: Tomcat, Webapp, Apache and mod_ssl, Protocol is switching
Just to verify that I understood everything: You request: https://intra.home.de/examples/ and get a directory listing that contains the link: a href=/examples/servlets/ that link resolves to http://intra.home.de:443/examples/servlets/index.html That means, that the browser thinks that http://intra.home.de:443 is the base url for all links in the page. This happens through two ways: That was the base for the request that produced the current page or the page contains a base tag. base href=... Can you verify if a redirection happens after you hit https://intra.home.de/examples/ or if the page contains a base tag ? (If a redirect happens you should see a different URL in the location bar of the browser) As I'm not using tomcat, I can't verify this on my own. -Ursprüngliche Nachricht- Von: Schulze Christian [mailto:[EMAIL PROTECTED]] Gesendet: Dienstag, 26. März 2002 16:07 An: 'Tomcat Users List' Betreff: AW: Tomcat, Webapp, Apache and mod_ssl, Protocol is switching I noticed this, but if i view the source of this page (obviously generated by Tomcat) the links just looks this way a href=/examples/servlets/ so the Adress should be right. It seems , that if Tomcat creates an index.html when I access a Directory i maps the URL from https to http ... ??? -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
AW: Tomcat, Webapp, Apache and mod_ssl, Protocol is switching
Hi, thanks for your quick reply -Ursprüngliche Nachricht- Von: Ralph Einfeldt [mailto:[EMAIL PROTECTED]] Gesendet: Dienstag, 26. März 2002 17:42 An: Tomcat Users List Betreff: AW: Tomcat, Webapp, Apache and mod_ssl, Protocol is switching Just to verify that I understood everything: You request: https://intra.home.de/examples/ and get a directory listing that contains the link: a href=/examples/servlets/ Right, this is what I see, when I look at the sourcecode of the page sent to the Browser, when i move the mousepointer over the link, the status-bar of the browser says 'https://intra.home.de/examples/servlets/' It does not matter, if click on the link, or type it in the Browser that link resolves to http://intra.home.de:443/examples/servlets/index.html That means, that the browser thinks that http://intra.home.de:443 is the base url for all links in the page. This happens through two ways: That was the base for the request that produced the current page or the page Even if I type this URL in a new Browser(-instance, not window), where the Browser doesnt know about any base url the same happens ... I tried also to use apaches mod_rewrite to redirect all acesses from Port 80 to Port 443, but this did not work either I'm stuck, no more ideas ... contains a base tag. base href=... No, the Page doesn't contain a base tag Can you verify if a redirection happens after you hit https://intra.home.de/examples/ or if the page contains a base tag ? (If a redirect happens you should see a different URL in the location bar of the browser) As I'm not using tomcat, I can't verify this on my own. -Ursprüngliche Nachricht- Von: Schulze Christian [mailto:[EMAIL PROTECTED]] Gesendet: Dienstag, 26. März 2002 16:07 An: 'Tomcat Users List' Betreff: AW: Tomcat, Webapp, Apache and mod_ssl, Protocol is switching I noticed this, but if i view the source of this page (obviously generated by Tomcat) the links just looks this way a href=/examples/servlets/ so the Adress should be right. It seems , that if Tomcat creates an index.html when I access a Directory i maps the URL from https to http ... ??? -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED] -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
AW: Tomcat 4 + Apache + virtual name-based domains + separate instances
For TC 4 the is an example for virtual hosts with mod_jk: http://jakarta.apache.org/tomcat/tomcat-4.0-doc/config/ajp.html For TC 3.2 there is a how-to for virtual hosts with mod_jk: http://jakarta.apache.org/tomcat/tomcat-3.2-doc/tomcat-apache-howto.html #virtual_hosting http://jakarta.apache.org/tomcat/tomcat-3.2-doc/mod_jk-howto.html#s9 What's missing in all 3 docs, is how to setup the worker.properties for named vitual hosts that share the same IP. I see two way to achive that: - Create two worker.properties files and use the JkWorkersFile inside the virtual host definition to point to the right file VirtualHost www.host1.tld DocumentRoot /web/host1 ServerName www.host1.tld JkMount /*.jsp ajp13 JkMount /servlet/* ajp13 JkWorkersFile /www/host1/conf/workers.properties JkLogFile /www/host1/logs/mod_jk.log JkLogLevel info /VirtualHost VirtualHost www.host2.tld DocumentRoot /web/host2 ServerName www.host2.tld JkMount /*.jsp ajp13 JkMount /servlet/* ajp13 JkWorkersFile /www/host2/conf/workers.properties JkLogFile /www/host2/logs/mod_jk.log JkLogLevel info /VirtualHost - Define two workers in worker.properties like this: VirtualHost www.host1.tld DocumentRoot /web/host1 ServerName www.host1.tld JkMount /*.jsp host1 JkMount /servlet/* host1 /VirtualHost VirtualHost www.host2.tld DocumentRoot /web/host2 ServerName www.host2.tld JkMount /*.jsp host2 JkMount /servlet/* host2 /VirtualHost worker.list=host1, host2 # Definition for Ajp13 worker # worker.host1.port=8009 worker.host1.host=localhost worker.host1.type=ajp13 worker.host2.port=8010 worker.host2.host=localhost worker.host2.type=ajp13 I don't know if any of the both ways work, haven't tried them. -Ursprüngliche Nachricht- Von: Neo Thinker [mailto:[EMAIL PROTECTED]] Gesendet: Donnerstag, 28. Februar 2002 01:53 An: [EMAIL PROTECTED] Betreff: Tomcat 4 + Apache + virtual name-based domains + separate instances snip/ I am convinced that if you use mod_webapp or mod_jk you CANNOT have virtual hosts run their own instances of Tomcat (I am not talking standalone here, I am talking Apache virtual hosts). The closer I read the docs on these modules, the more I thought that they didn't support it, even though they don't come right out and say it. snip/ -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
AW: Tomcat and Apache load-balancing ?
Depends on the architecture of your infrastructure: apache - tomcat Loadbalacer apache - tomcat In this scenario you don't need the loadbalancing feature of mod_jk but the loadbalancer must honor the sessions. apache tomcat Loadbalacer X apache tomcat In this scenario you need the loadbalancing feature of mod_jk and the load balancer doesn't need to know about sessions. Here you have to make shure that both mod_jk's are consistent in their setup. -Ursprüngliche Nachricht- Von: Vjeran Marcinko [mailto:[EMAIL PROTECTED]] Gesendet: Donnerstag, 14. Februar 2002 06:26 An: Tomcat Users List Betreff: Re: Tomcat and Apache load-balancing ? snip/ But I thought I've read somewhere that mod_jk is responsible for determining which Tomcat instance is to be picked based upon request's session ID ? Or, was I wrong ? snip/ -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
AW: Tomcat 3.3a Apache 1.3.22 : Apache not hiding WEB-INF and not using default document (.jsp)
Do you mean with 'my directories' and 'WEB-INF' directories that are in the examples directory ? If not you must define the Directory and the Location tag for your base directory. -Ursprüngliche Nachricht- Von: Elm Gysel [mailto:[EMAIL PROTECTED]] Gesendet: Dienstag, 29. Januar 2002 09:56 An: Tomcat Users List Betreff: Tomcat 3.3a Apache 1.3.22 : Apache not hiding WEB-INF and not using default document (.jsp) snip/ I can browse all my directories through Apache, I can browse WEB-INF without problem? snip/ Directory /usr/local/jakarta-tomcat-3.3a/webapps/examples Options Indexes FollowSymLinks DirectoryIndex index.jsp index.html index.htm /Directory # Deny direct access to WEB-INF and META-INF # Location /examples/WEB-INF/* AllowOverride None deny from all /Location Location /examples/META-INF/* AllowOverride None deny from all /Location JkMount /examples/servlet/* ajp13 JkMount /examples/*.jsp ajp13 Thanks for any suggestions. Elm -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED] -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
AW: Tomcat 3.3a Apache 1.3.22 : Apache not hiding WEB-INF and not using default document (.jsp)
To see the some configuration of apache at runtime include the following in httpd.conf (If not already there): LoadModule info_module /apache dir/lib/mod_info.so IfModule mod_info.c Location /server-info SetHandler server-info /Location /IfModule Hit the Url servername/server-info -Ursprüngliche Nachricht- Von: Elm Gysel [mailto:[EMAIL PROTECTED]] Gesendet: Dienstag, 29. Januar 2002 10:17 An: Tomcat Users List Betreff: Re: Tomcat 3.3a Apache 1.3.22 : Apache not hiding WEB-INF and not using default document (.jsp) Yes, sorry for being not very clear. I do mean the WEB-INF directorie in the examples directory. Also on other mappings its not taking index.jsp as default as defined in the DirectoryIndex for that directory. But let me do say again that all this worked perfectly with 1.3.9 . I have also used other versions of Apache with this Tomcat release and it was also working. Elm Do you mean with 'my directories' and 'WEB-INF' directories that are in the examples directory ? If not you must define the Directory and the Location tag for your base directory. -Ursprüngliche Nachricht- Von: Elm Gysel [mailto:[EMAIL PROTECTED]] Gesendet: Dienstag, 29. Januar 2002 09:56 An: Tomcat Users List Betreff: Tomcat 3.3a Apache 1.3.22 : Apache not hiding WEB-INF and not using default document (.jsp) snip/ I can browse all my directories through Apache, I can browse WEB-INF without problem? snip/ Directory /usr/local/jakarta-tomcat-3.3a/webapps/examples Options Indexes FollowSymLinks DirectoryIndex index.jsp index.html index.htm /Directory # Deny direct access to WEB-INF and META-INF # Location /examples/WEB-INF/* AllowOverride None deny from all /Location Location /examples/META-INF/* AllowOverride None deny from all /Location JkMount /examples/servlet/* ajp13 JkMount /examples/*.jsp ajp13 Thanks for any suggestions. Elm -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED] -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED] -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED] -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
AW: Tomcat 4.0.1, Apache 1.3.22, Warp Connector and Loadbalancing
AFAIK tomcat 4.* currently doesn't support loadbalancing with any connector. Solutions: - Drop back to 3.2/3.3 and mod_jk - use a external loadbalancer that supports sticky sessions with cookies and urls's. -Ursprüngliche Nachricht- Von: Martin Kerstein [mailto:[EMAIL PROTECTED]] Gesendet: Dienstag, 15. Januar 2002 10:40 An: [EMAIL PROTECTED] Betreff: Tomcat 4.0.1, Apache 1.3.22, Warp Connector and Loadbalancing Hy. Iam new to this list, so if this topic has already been covered, please forgive me and point me in the right direction :-) To my problem: We are setting up apache 1.3.22 as web server, integrating tomcat 4.0.1 via the WARP connector. I am looking for a way to configure load balancing, so that requests could be directed to diferrent tomcats? Every hint is appreciated -- Für weitere Fragen stehe ich Ihnen gerne telefonisch oder via E-Mail zur Verfügung. Mit freundlichen Grüßen Martin Kerstein Unix-Administration - Wapme Systems AG Münsterstr. 248 40470 Düsseldorf Tel.: + 49 -211- 74845 - 0 Fax: + 49 -211- 6026 - 2801 E-Mail: [EMAIL PROTECTED] Internet:http://www.wapme-systems.de - - Wapme Systems AG - Der Wert für mobile Internetkommunikation am NEUEN MARKT WKN: 549550 - Reuterskürzel: WPM G.F -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED] -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
AW: Tomcat 4.0.1, Apache 1.3.22, Warp Connector andLoadbalancing
That're really good news !!! We stay tuned and please don't forget the doc :-). When will 4.0.2 be available ? Thanx Oliver AXA eSolutions GmbH AXA Konzern AG Germany Oliver Lauer Web Architect Wörthstraße 34 D-50668 Köln Germany Tel.: +49 221 148 31277 Fax: +49 221 148 43963 Mobil: +49 179 59 064 59 e-Mail: [EMAIL PROTECTED] _ -Ursprüngliche Nachricht- Von: GOMEZ Henri [mailto:[EMAIL PROTECTED]] Gesendet: Dienstag, 15. Januar 2002 12:34 An: Tomcat Users List Betreff: RE: Tomcat 4.0.1, Apache 1.3.22, Warp Connector and Loadbalancing Tomcat 4.0.2 will support load balancing with mod_jk. Stay tuned - Henri Gomez ___[_] EMAIL : [EMAIL PROTECTED](. .) PGP KEY : 697ECEDD...oOOo..(_)..oOOo... PGP Fingerprint : 9DF8 1EA8 ED53 2F39 DC9B 904A 364F 80E6 -Original Message- From: Ralph Einfeldt [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 15, 2002 10:46 AM To: Tomcat Users List Subject: AW: Tomcat 4.0.1, Apache 1.3.22, Warp Connector and Loadbalancing AFAIK tomcat 4.* currently doesn't support loadbalancing with any connector. Solutions: - Drop back to 3.2/3.3 and mod_jk - use a external loadbalancer that supports sticky sessions with cookies and urls's. -Ursprüngliche Nachricht- Von: Martin Kerstein [mailto:[EMAIL PROTECTED]] Gesendet: Dienstag, 15. Januar 2002 10:40 An: [EMAIL PROTECTED] Betreff: Tomcat 4.0.1, Apache 1.3.22, Warp Connector and Loadbalancing Hy. Iam new to this list, so if this topic has already been covered, please forgive me and point me in the right direction :-) To my problem: We are setting up apache 1.3.22 as web server, integrating tomcat 4.0.1 via the WARP connector. I am looking for a way to configure load balancing, so that requests could be directed to diferrent tomcats? Every hint is appreciated -- Für weitere Fragen stehe ich Ihnen gerne telefonisch oder via E-Mail zur Verfügung. Mit freundlichen Grüßen Martin Kerstein Unix-Administration - Wapme Systems AG Münsterstr. 248 40470 Düsseldorf Tel.: + 49 -211- 74845 - 0 Fax: + 49 -211- 6026 - 2801 E-Mail: [EMAIL PROTECTED] Internet:http://www.wapme-systems.de - - Wapme Systems AG - Der Wert für mobile Internetkommunikation am NEUEN MARKT WKN: 549550 - Reuterskürzel: WPM G.F -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED] -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED] -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED] -- Aus Rechts- und Sicherheitsgruenden ist die in dieser E-Mail gegebene Information nicht rechtsverbindlich. Eine rechtsverbindliche Bestaetigung reichen wir Ihnen gerne auf Anforderung in schriftlicher Form nach. Beachten Sie bitte, dass jede Form der unautorisierten Nutzung, Veroeffentlichung, Vervielfaeltigung oder Weitergabe des Inhalts dieser E-Mail nicht gestattet ist.Diese Nachricht ist ausschliesslich fuer den bezeichneten Adressaten oder dessen Vertreter bestimmt. Sollten Sie nicht der vorgesehene Adressat dieser E-Mail oder dessen Vertreter sein, so bitten wir Sie, sich mit dem Absender der E-Mail in Verbindung zu setzen. For legal and security reasons the information provided in this e-mail is not legally binding. Upon request we would be pleased to provide you with a legally binding confirmation in written form. Any form of unauthorised use, publication, reproduction, copying or disclosure of the content of this e-mail is not permitted. This message is exclusively for the person addressed or their representative. If you are not the intended recipient of this message and its contents, please notify the sender immediately. == -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
AW: tomcat and apache jsp execution
I looked on the mod_jk.log file. Here is two lines I am getting quite a lot and I don't really know what it means. [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 Furthemore, I don't have DocumentRoot=tomcatDirectory/webapps/ROOT anywhere. The only documentRoot I found was in httpd.conf file which refer to the directory where are my webpages. I removed all the stuff I added in the httpd.conf file (except for the include command). I found out that the lines I added were already in the mod_jk.conf-local file I was using. Still, I am getting the source of my jsp. mel -Ursprüngliche Nachricht- Von: Dmitri Colebatch [mailto:[EMAIL PROTECTED]] Gesendet am: Montag, 20. August 2001 14:42 An: [EMAIL PROTECTED] Cc: Bernier, Melanie Betreff: Re: tomcat and apache jsp execution Are you getting anything in the mod_jk log when doing a request? Another thing - if you're getting source I might guess that you have DocumentRoot=tomcatDirectory/webapps/ROOT? I'm sure that probably can work, but then you've got two web servers both serving content from one directory, and it might make it harder to debug... hth cheesr dim On Mon, 20 Aug 2001, Bernier, Melanie wrote: Hi! I just installed tomcat 3.2.3 and I am trying to make it work with Apache. I followed the step described on the tomcat web site but I'm still not able to make it work properly. When I request html or jsp from port 8080, everything works fine. When I request html from port 80, again I have no troubles. But when I try to access a .jsp from port 80, Apache sends me back the code of that jsp instead of having it executed by tomcat. Here is what I added in my httpd.conf: Include tomcatDirectory/conf/mod-jk.conf-local LoadModulejk_module modules/mod_jk-eapi.so AddModule mod_jk.c JkWorkersFile tomcatDirectory/conf/workers.properties JkLogFile apacheDirectory/logs/mod_jk.log JkMount /*.jsp ajp13 JkMount /servlet/* apj13 The mod-jk.conf-local is the mod-jk.conf-auto generated by tomcat with the only difference that I changed the reference line to the mod_jk module because I had a different location than /libexec/mod_jk.so I added the following in the server.xml: Connector classname=org.apache.tomcat.service.PoolTcpConnector Parameter name=handler value=org.apache.tomcat.service.connector.Ajp13ConnectionHandler/ Parameter name=port value=8009/ /Connector Any idea? Thanks a lot, Melanie.
Re: AW: tomcat and apache jsp execution
Mel, ok - so its getting to mod_jk ok... (not 100% sure what those lines mean specifically, but I get them too). I suppose the next thing to look at is the tomcat logs. open up server.xml and crank up all the debug levels and see what happens in the logs when the request comes in btw - the reason I was asking about DocumentRoot is that I wondered if somehow apache was serving the jsp source directly... doesn't sound like it. cheesr dim On Tue, 21 Aug 2001, Bernier, Melanie wrote: I looked on the mod_jk.log file. Here is two lines I am getting quite a lot and I don't really know what it means. [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 Furthemore, I don't have DocumentRoot=tomcatDirectory/webapps/ROOT anywhere. The only documentRoot I found was in httpd.conf file which refer to the directory where are my webpages. I removed all the stuff I added in the httpd.conf file (except for the include command). I found out that the lines I added were already in the mod_jk.conf-local file I was using. Still, I am getting the source of my jsp. mel -Ursprüngliche Nachricht- Von: Dmitri Colebatch [mailto:[EMAIL PROTECTED]] Gesendet am: Montag, 20. August 2001 14:42 An: [EMAIL PROTECTED] Cc: Bernier, Melanie Betreff: Re: tomcat and apache jsp execution Are you getting anything in the mod_jk log when doing a request? Another thing - if you're getting source I might guess that you have DocumentRoot=tomcatDirectory/webapps/ROOT? I'm sure that probably can work, but then you've got two web servers both serving content from one directory, and it might make it harder to debug... hth cheesr dim On Mon, 20 Aug 2001, Bernier, Melanie wrote: Hi! I just installed tomcat 3.2.3 and I am trying to make it work with Apache. I followed the step described on the tomcat web site but I'm still not able to make it work properly. When I request html or jsp from port 8080, everything works fine. When I request html from port 80, again I have no troubles. But when I try to access a .jsp from port 80, Apache sends me back the code of that jsp instead of having it executed by tomcat. Here is what I added in my httpd.conf: Include tomcatDirectory/conf/mod-jk.conf-local LoadModule jk_module modules/mod_jk-eapi.so AddModule mod_jk.c JkWorkersFile tomcatDirectory/conf/workers.properties JkLogFile apacheDirectory/logs/mod_jk.log JkMount /*.jsp ajp13 JkMount /servlet/* apj13 The mod-jk.conf-local is the mod-jk.conf-auto generated by tomcat with the only difference that I changed the reference line to the mod_jk module because I had a different location than /libexec/mod_jk.so I added the following in the server.xml: Connector classname=org.apache.tomcat.service.PoolTcpConnector Parameter name=handler value=org.apache.tomcat.service.connector.Ajp13ConnectionHandler/ Parameter name=port value=8009/ /Connector Any idea? Thanks a lot, Melanie.
AW: AW: tomcat and apache jsp execution
Hi Dmitri, I can't find anything useful in the logs:-( As I was reading the documentation from my colleague, I remembered something about RequestInterceptor. I read somewhere on the documentation for ajp13 connection to add in the server.xml : RequestInterceptor className=org.apache.tomcat.modules.server.Ajp13Interceptor port=8009/ When I tried it, I was getting FATAL: configuration error java.lang.ClassNotFoundException: org.apache.tomcat.modules.server.Ajp13Interceptor ...(and blablabla). Could that be related to my problem? mel
Re: AW: AW: tomcat and apache jsp execution
Mel, hmmm... yep - think you might be onto it there (o: ok... just been re-reading the docs, and to be honest I'm not sure what the RequestInterceptor className=org.apache.tomcat.modules.server.Ajp13Interceptor port=8009/ block is about, because I cant find that class either - I would have expected it to be in webserver.jar... anyway, what I think you should do is take that out.. .and put this in: Connector className=org.apache.tomcat.service.PoolTcpConnector Parameter name=handler value=org.apache.tomcat.service.connector.Ajp13ConnectionHandler/ Parameter name=port value=8009/ /Connector pop that under the similar entry to Ajp12. Note thats a Connector not a RequestInterceptor. I'm not a tc developer, so wont be able to go into detail, just making sure we get it right. Anyway, that should (fingers crossed) sort things out (o: On the other hand, you could also try changing your JkMounts from to use the ajp12 worker instead of ajp13. but try putting the above in server.xml first and see how you go. cheers dim On Tue, 21 Aug 2001, Bernier, Melanie wrote: Hi Dmitri, I can't find anything useful in the logs:-( As I was reading the documentation from my colleague, I remembered something about RequestInterceptor. I read somewhere on the documentation for ajp13 connection to add in the server.xml : RequestInterceptor className=org.apache.tomcat.modules.server.Ajp13Interceptor port=8009/ When I tried it, I was getting FATAL: configuration error java.lang.ClassNotFoundException: org.apache.tomcat.modules.server.Ajp13Interceptor ...(and blablabla). Could that be related to my problem? mel
AW: Tomcat with Apache/URLRewritting and mod_rewrite
The mod_rewrite gets loaded in my http.conf. I also added the rewrite rule but it did not work. According to the application name jserv-servlet it seems to me as this rewrite rule is meant to be used with jserv not with mod_jk ?! Nowhere in my http.conf file could I find a definition of the application jserv-servlet, which I guess must be defined in order for this rule to work. Are you running Tomcat with Apache ?? -Ursprngliche Nachricht- Von: Ralph Einfeldt [mailto:[EMAIL PROTECTED]] Gesendet: Mittwoch, 18. April 2001 07:41 An: '[EMAIL PROTECTED]' Betreff: AW: Tomcat with Apache/URLRewritting and mod_rewrite For the remarks see below: -Ursprngliche Nachricht- Von: Tassilo Pilati [mailto:[EMAIL PROTECTED]] Gesendet: Dienstag, 17. April 2001 17:47 An: [EMAIL PROTECTED] Betreff: Tomcat with Apache/URLRewritting and mod_rewrite snip/ IfModule mod_rewrite.c RewriteEngine On RewriteRule ^(/.*;jsessionid=.*)$ $1 [T=jserv-servlet] /IfModule snip/ The mod_rewrite must be loaded to enable the rule. (e.g.: LoadModule rewrite_module /usr/local/apache/lib/mod_rewrite.so) snip/ I also was wondering what the [T=jserv-servlet] means ? snip/ From the mod_rewrite documentation: 'type|T=MIME-type' (force MIME type) Force the MIME-type of the target file to be MIME-type. For instance, this can be used to simulate the mod_alias directive ScriptAlias which internally forces all files inside the mapped directory to have a MIME type of ''application/x-httpd-cgi''.
AW: Tomcat with Apache/URLRewritting and mod_rewrite
Sorry I'm not even using tomcat. Still using jserv 1.1.*. -Ursprngliche Nachricht- Von: Tassilo Pilati [mailto:[EMAIL PROTECTED]] Gesendet: Mittwoch, 18. April 2001 10:49 An: [EMAIL PROTECTED] Betreff: AW: Tomcat with Apache/URLRewritting and mod_rewrite The mod_rewrite gets loaded in my http.conf. I also added the rewrite rule but it did not work. According to the application name jserv-servlet it seems to me as this rewrite rule is meant to be used with jserv not with mod_jk ?! Nowhere in my http.conf file could I find a definition of the application jserv-servlet, which I guess must be defined in order for this rule to work. Are you running Tomcat with Apache ?? -Ursprngliche Nachricht- Von: Ralph Einfeldt [mailto:[EMAIL PROTECTED]] Gesendet: Mittwoch, 18. April 2001 07:41 An: '[EMAIL PROTECTED]' Betreff: AW: Tomcat with Apache/URLRewritting and mod_rewrite For the remarks see below: -Ursprngliche Nachricht- Von: Tassilo Pilati [mailto:[EMAIL PROTECTED]] Gesendet: Dienstag, 17. April 2001 17:47 An: [EMAIL PROTECTED] Betreff: Tomcat with Apache/URLRewritting and mod_rewrite snip/ IfModule mod_rewrite.c RewriteEngine On RewriteRule ^(/.*;jsessionid=.*)$ $1 [T=jserv-servlet] /IfModule snip/ The mod_rewrite must be loaded to enable the rule. (e.g.: LoadModule rewrite_module /usr/local/apache/lib/mod_rewrite.so) snip/ I also was wondering what the [T=jserv-servlet] means ? snip/ From the mod_rewrite documentation: 'type|T=MIME-type' (force MIME type) Force the MIME-type of the target file to be MIME-type. For instance, this can be used to simulate the mod_alias directive ScriptAlias which internally forces all files inside the mapped directory to have a MIME type of ''application/x-httpd-cgi''.
AW: Tomcat with Apache/URLRewritting and mod_rewrite
Do you know if the mod_jserv can be used with tomcat ? -Ursprngliche Nachricht- Von: Ralph Einfeldt [mailto:[EMAIL PROTECTED]] Gesendet: Mittwoch, 18. April 2001 11:47 An: '[EMAIL PROTECTED]' Betreff: AW: Tomcat with Apache/URLRewritting and mod_rewrite Sorry I'm not even using tomcat. Still using jserv 1.1.*. -Ursprngliche Nachricht- Von: Tassilo Pilati [mailto:[EMAIL PROTECTED]] Gesendet: Mittwoch, 18. April 2001 10:49 An: [EMAIL PROTECTED] Betreff: AW: Tomcat with Apache/URLRewritting and mod_rewrite The mod_rewrite gets loaded in my http.conf. I also added the rewrite rule but it did not work. According to the application name jserv-servlet it seems to me as this rewrite rule is meant to be used with jserv not with mod_jk ?! Nowhere in my http.conf file could I find a definition of the application jserv-servlet, which I guess must be defined in order for this rule to work. Are you running Tomcat with Apache ?? -Ursprngliche Nachricht- Von: Ralph Einfeldt [mailto:[EMAIL PROTECTED]] Gesendet: Mittwoch, 18. April 2001 07:41 An: '[EMAIL PROTECTED]' Betreff: AW: Tomcat with Apache/URLRewritting and mod_rewrite For the remarks see below: -Ursprngliche Nachricht- Von: Tassilo Pilati [mailto:[EMAIL PROTECTED]] Gesendet: Dienstag, 17. April 2001 17:47 An: [EMAIL PROTECTED] Betreff: Tomcat with Apache/URLRewritting and mod_rewrite snip/ IfModule mod_rewrite.c RewriteEngine On RewriteRule ^(/.*;jsessionid=.*)$ $1 [T=jserv-servlet] /IfModule snip/ The mod_rewrite must be loaded to enable the rule. (e.g.: LoadModule rewrite_module /usr/local/apache/lib/mod_rewrite.so) snip/ I also was wondering what the [T=jserv-servlet] means ? snip/ From the mod_rewrite documentation: 'type|T=MIME-type' (force MIME type) Force the MIME-type of the target file to be MIME-type. For instance, this can be used to simulate the mod_alias directive ScriptAlias which internally forces all files inside the mapped directory to have a MIME type of ''application/x-httpd-cgi''.
AW: Tomcat with Apache/URLRewritting and mod_rewrite
But SSL has nothing to do with my problem. The problem I have is that when using Tomcat in standalone mode URL rewritting works, however, running Tomcat in combination with Apache does not, because Apache does not hand the request over to Tomcat. I think is is stange that there is nothing mentioned about this in the tomcat user guide - section Setting Tomcat up with Apache. I think so many people are using Tomcat with Apache that it is really a very important issue ?! I mean session tracking is fundamental and it should work using URL rewritting. I guess many people use cookies for session tracking instead of URL rewritting. Probably with cookies it should work, so maybe that`s why this issue hasn`t really come to the attention to the tomcat developers ? What do you think ? -Ursprungliche Nachricht- Von: Wolle [mailto:[EMAIL PROTECTED]] Gesendet: Mittwoch, 18. April 2001 13:56 An: [EMAIL PROTECTED] Betreff: Re: Tomcat with Apache/URLRewritting and mod_rewrite Hello, yes, you're right, the Protocol ajp13 supports the SSL protocol better (relating to the methode request.isSecure() ). But this SSL and URL Rewriting is a Bug , see: http://nagoya.apache.org/bugzilla/show_bug.cgi?id=578 This has been fixed in the last csv release, and will hoply be fixed in the 3.2.2 final release or 3.2.2b4, also. Greetings, Michael Sam Newman wrote: It can (see the Apache-tomcat readme in the tomcat distro), but it is strongly suggested that you use mod_jk tomcat instead of using JServ as it has less bugs, is faster, and I believe is also better maintained. sam - Original Message - From: "Tassilo Pilati" [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, April 18, 2001 11:03 AM Subject: AW: Tomcat with Apache/URLRewritting and mod_rewrite Do you know if the mod_jserv can be used with tomcat ?
AW: Tomcat with Apache/URLRewritting and mod_rewrite
I`m using mod_jk and apj13, however I tried apj12 as well but it should not make a difference. Tomcat version is 3.2.1. You probably set the noCookies parameter to false. Then session tracking is implemented using Cookies and it probably will work. If you set it to false, then session tracking via URL rewritting is used instead and you should run into the problem I have. Do you have the string ";jsessionid=" in you urls, when you are using session tracking ? You probably don`t... -Ursprngliche Nachricht- Von: Sam Newman [mailto:[EMAIL PROTECTED]] Gesendet: Mittwoch, 18. April 2001 15:33 An: [EMAIL PROTECTED] Betreff: Re: Tomcat with Apache/URLRewritting and mod_rewrite - Original Message - From: "Tassilo Pilati" [EMAIL PROTECTED] To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Wednesday, April 18, 2001 1:27 PM Subject: AW: Tomcat with Apache/URLRewritting and mod_rewrite But SSL has nothing to do with my problem. The problem I have is that when using Tomcat in standalone mode URL rewritting works, however, running Tomcat in combination with Apache does not, because Apache does not hand the request over to Tomcat. I think is is stange that there is nothing mentioned about this in the tomcat user guide - section Setting Tomcat up with Apache. I think so many people are using Tomcat with Apache that it is really a very important issue ?! I mean session tracking is fundamental and it should work using URL rewritting. I guess many people use cookies for session tracking instead of URL rewritting. Probably with cookies it should work, so maybe that`s why this issue hasn`t really come to the attention to the tomcat developers ? What do you think ? Just to clarify, are you using jserv or mod_jk? And if you are using mod_jk, are you using the ajpv13 protocl for connection? I'm using mod_jk and ajpv13, and am session tracking using the HttpSesession class and it works fine, as does parameter passing. I don't know too much about URL reqritting though. sam
AW: Tomcat with Apache/URLRewritting and mod_rewrite
For the remarks see below: -Ursprngliche Nachricht- Von: Tassilo Pilati [mailto:[EMAIL PROTECTED]] Gesendet: Dienstag, 17. April 2001 17:47 An: [EMAIL PROTECTED] Betreff: Tomcat with Apache/URLRewritting and mod_rewrite snip/ IfModule mod_rewrite.c RewriteEngine On RewriteRule ^(/.*;jsessionid=.*)$ $1 [T=jserv-servlet] /IfModule snip/ The mod_rewrite must be loaded to enable the rule. (e.g.: LoadModule rewrite_module /usr/local/apache/lib/mod_rewrite.so) snip/ I also was wondering what the [T=jserv-servlet] means ? snip/ From the mod_rewrite documentation: 'type|T=MIME-type' (force MIME type) Force the MIME-type of the target file to be MIME-type. For instance, this can be used to simulate the mod_alias directive ScriptAlias which internally forces all files inside the mapped directory to have a MIME type of ''application/x-httpd-cgi''.
