Re: [users@httpd] Httpd Tomcat
On 17/04/2015 09:15, Bremser, Kurt (AMOS Austria GmbH) wrote: Tomcat uses several ports. One of these is a standard HTML port that can be usefully accessed with a browser. Since tomcat itself listens on this port, DO NOT USE it in httpd! If you want to serve tomcat content via your apache(httpd), you need to use a connector (ie mod_jk) and specify the correct connector port in workers.properties. You can find the example for this in the mod_jk.conf in the conf/extra subdirectory of your apache tree. The ports of tomcat can be found in conf/server.xml in the tomcat tree. You can also use mod_proxy to do this as well - depending on the frequency of connections you may find that the mod_proxy solution is better - mod_jk isn't good at coping with network issues although this probably isn't a problem in your case... -- The Wellcome Trust Sanger Institute is operated by Genome Research Limited, a charity registered in England with number 1021457 and a company registered in England with number 2742969, whose registered office is 215 Euston Road, London, NW1 2BE.
[users@httpd] Httpd Tomcat
Dear All I am trying to run Httpd and Apache together for the first time ever, however, I have been unsuccessful in my endeavours. I have to sites that point to the same server: subdomain1.domain.com - normal HTML PHP site subdomain2.domain.com - tomcat servlet with an instance of Atlassian Confluence which connects to port 8090 In the HTTPD conf file I the following: Listen: 80 #Listen: 8090 Directory / # AllowOverride none # Require all denied Options FollowSymLinks Options Indexes FollowSymLinks Includes ExecCGI AllowOverride All Order deny,allow Allow from all /Directory ServerName: xxx.xxx.xxx.xxx ServerName: xxx.xxx.xxx.xxx:8090 VirtualHost xxx.xxx.xxx.xxx DocumentRoot /www/html ServerName subdomain1.domain.com /VirtualHost VirtualHost xxx.xxx.xxx.xxx:8090 DocumentRoot /opt/confluence/confluence ServerName subdomain2.domain.com /VirtualHost I am able to get the normal site, but not the tomcat instance. Will it be possible to point me in the right direction, please? Kind Regards Leon
Re: [users@httpd] Httpd Tomcat
Tomcat uses several ports. One of these is a standard HTML port that can be usefully accessed with a browser. Since tomcat itself listens on this port, DO NOT USE it in httpd! If you want to serve tomcat content via your apache(httpd), you need to use a connector (ie mod_jk) and specify the correct connector port in workers.properties. You can find the example for this in the mod_jk.conf in the conf/extra subdirectory of your apache tree. The ports of tomcat can be found in conf/server.xml in the tomcat tree. Kurt Bremser AMOS Austria Newton was wrong. There is no gravity. The Earth sucks. Von: Leon Vergottini [le...@cornerstone.ac.za] Gesendet: Freitag, 17. April 2015 10:03 An: users@httpd.apache.org Betreff: **SPAM?** [users@httpd] Httpd Tomcat [wd-vc] Dear All I am trying to run Httpd and Apache together for the first time ever, however, I have been unsuccessful in my endeavours. I have to sites that point to the same server: subdomain1.domain.com – normal HTML PHP site subdomain2.domain.com – tomcat servlet with an instance of Atlassian Confluence which connects to port 8090 In the HTTPD conf file I the following: Listen: 80 #Listen: 8090 Directory / # AllowOverride none # Require all denied Options FollowSymLinks Options Indexes FollowSymLinks Includes ExecCGI AllowOverride All Order deny,allow Allow from all /Directory ServerName: xxx.xxx.xxx.xxx ServerName: xxx.xxx.xxx.xxx:8090 VirtualHost xxx.xxx.xxx.xxx DocumentRoot /www/html ServerName subdomain1.domain.com /VirtualHost VirtualHost xxx.xxx.xxx.xxx:8090 DocumentRoot /opt/confluence/confluence ServerName subdomain2.domain.com /VirtualHost I am able to get the normal site, but not the tomcat instance. Will it be possible to point me in the right direction, please? Kind Regards Leon AMOS Austria GmbH 1130 Wien, Hietzinger Kai 101-105 FN 365014k, Handelsgericht Wien UID: ATU 66614737 http://www.allianz.at Dieses E-Mail und allfaellig daran angeschlossene Anhaenge enthalten Informationen, die vertraulich und ausschliesslich fuer den (die) bezeichneten Adressaten bestimmt sind. Wenn Sie nicht der genannte Adressat sind, darf dieses E-Mail samt allfaelliger Anhaenge von Ihnen weder anderen Personen zugaenglich gemacht noch in anderer Weise verwertet werden. Wenn Sie nicht der beabsichtigte Empfaenger sind, bitten wir Sie, dieses E-Mail und saemtliche angeschlossene Anhaenge zu loeschen. Please note: This email and any files transmitted with it is intended only for the named recipients and may contain confidential and/or privileged information. If you are not the intended recipient, please do not read, copy, use or disclose the contents of this communication to others and notify the sender immediately. Then please delete the email and any copies of it. Thank you.
RE: [users@httpd] Httpd Tomcat
Hi Thank you for the responses. I will investigate both solutions. Everyone have a great weekend. Kind Regards Leon From: James Smith [mailto:j...@sanger.ac.uk] Sent: 17 April 2015 10:23 AM To: users@httpd.apache.org Subject: Re: [users@httpd] Httpd Tomcat On 17/04/2015 09:15, Bremser, Kurt (AMOS Austria GmbH) wrote: Tomcat uses several ports. One of these is a standard HTML port that can be usefully accessed with a browser. Since tomcat itself listens on this port, DO NOT USE it in httpd! If you want to serve tomcat content via your apache(httpd), you need to use a connector (ie mod_jk) and specify the correct connector port in workers.properties. You can find the example for this in the mod_jk.conf in the conf/extra subdirectory of your apache tree. The ports of tomcat can be found in conf/server.xml in the tomcat tree. You can also use mod_proxy to do this as well - depending on the frequency of connections you may find that the mod_proxy solution is better - mod_jk isn't good at coping with network issues although this probably isn't a problem in your case... -- The Wellcome Trust Sanger Institute is operated by Genome Research Limited, a charity registered in England with number 1021457 and a company registered in England with number 2742969, whose registered office is 215 Euston Road, London, NW1 2BE.
Re: [users@httpd] Weird connection issues with mod_proxy_wstunnel
Hello everyone, I just figured out the configuration issue causing my problem. Original configuration mod_proxy_wstunnel with SwampDragon: ProxyPass /data/ ws://127.0.0.1:9001/data/ ProxyPassReverse /data/ ws://127.0.0.1:9001/data/ ProxyPass /settings.js http://127.0.0.1:9001/settings.js ProxyPassReverse /settings.js http://127.0.0.1:9001/settings.js ProxyPreserveHost On ProxyRequests Off ProxyVia On The following configuration for mod_proxy_wstunnel with SwampDragon works fine: ProxyPassMatch /data/(\d+)/(\w+)/websocket ws://127.0.0.1:9001/data/$1/$2/websocket ProxyPass /data/info http://127.0.0.1:9001/data/info ProxyPassReverse /data/info http://127.0.0.1:9001/data/info ProxyPass /settings.js http://127.0.0.1:9001/settings.js ProxyPassReverse /settings.js http://127.0.0.1:9001/settings.js ProxyPreserveHost On ProxyRequests Off ProxyVia On The issue was caused by the fact that /data/info is requested before a WebSocket-upgrade request to /data/(\d+)/(\w+)/websocket is performed. Because /data/info was redirected to the WebSocket-server using the same rule as /data/(\d+)/(\w+)/websocket before, mod_proxy_wstunnel continued to also forward all HTTP-traffic to the WebSocket-server. Hope this helps in case anyone else runs into the same problem. You have to make sure that ws:// or was:// forwarding is only configured for the actual WebSocket-URL and does not affect any other requests. Thanks for pointing me into the right direction. Best regards, Marc - To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org
