tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Paul Roubekas <p...@orthogroup.holdings>
Subject Re: No binary distribution for mod_jk?
Date Sat, 23 Jul 2016 00:37:10 GMT
On 7/22/2016 8:14 PM, Paul Roubekas wrote:
> On 7/22/2016 4:24 PM, Paul Roubekas wrote:
>> On 7/22/2016 4:14 PM, Christopher Schultz wrote:
>>> Paul,
>>>
>>> On 7/21/16 5:08 PM, Paul Roubekas wrote:
>>> > On 7/21/2016 2:21 PM, Coty Sutherland wrote:
>>> >>> Actually my requirement is not that complex.  All I need to do
>>> >>> is host TomEE (a Tomcat 7 superset), Bugzilla and phpBB (forum
>>> >>> software) on the same server.  It is my understanding the I
>>> >>> need httpd to do this.
>>> >> TomEE can run outside of a web server (its it's on web
>>> >> container), but Bugzilla and phpBB seem to require a webserver to
>>> >> run, so you're correct there. If you install Bugzilla and phpBB
>>> >> in httpd, then it should be accessible via http://host/bugzilla
>>> >> (or whatever the path is). Tomcat would be accessible via
>>> >> http://host:8080/. If you wanted tomcat to be accessible via
>>> >> http://host/tomcat, then you'd have to proxy to it.
>>> > understood.
>>> >>
>>> >>> It is also my understanding that I needed mod_jk to have the
>>> >>> httpd route to TomEE (Tomcat 7).  I have TomEE running on the
>>> >>> server now.
>>> >> Unless you only have an AJP connector on TomEE (which isn't
>>> >> likely) it's probably easier/less work for you to use mod_proxy
>>> >> (or mod_proxy_ajp even if you want AJP traffic) instead of
>>> >> mod_jk. It's provided by the httpd package that's likely already
>>> >> installed. You just need to setup ProxyPass[Reverse] rules as
>>> >> documented here:
>>> >> https://httpd.apache.org/docs/current/mod/mod_proxy.html#proxypass.
>>> >>
>>> >>
>>> I'd also suggest setting proxyName and proxyPort on your connector so
>>> >> that any links generated by your application don't try and bypass
>>> >> the proxy (see:
>>> >> https://tomcat.apache.org/tomcat-7.0-doc/config/http.html#Common_Attr
>>> ibutes).
>>>
>>> >>
>>> Don't know what AJP is.  Therefore I assume it is not in use.  If my
>>> > understand of AJP is correct, based on a 5 minute read on
>>> > Wikipedia, I only have one server so there is no value in AJP for
>>> > me.
>>>
>>> If you are starting from scratch, I would recommend using mod_proxy
>>> for your proxying with httpd. It comes pre-built with whatever binary
>>> httpd distribution you got, and is arguably easier to configure.
>>>
>>> You can even use either HTTP or AJP as the protocol to connect httpd
>>> -> Tomcat. I would recommend mod_proxy_http just because it's
>>> basically the simplest to configure. If you want to use TLS and get
>>> the certificate information over to Tomcat/TomEE, it's a bit easier to
>>> do with AJP, but not impossible with HTTP.
>>>
>> I have pages that require HTTPS.
>>> I was just assuming you knew you wanted mod_jk and were looking for a
>>> binary.
>>>
>>> Apologies for the confusion.
>> No problem.
>>>
>>> httpd + Tomcat/TomEE is quite easy to get set up with mod_proxy_http.
>>> Simply:
>>>
>>> 1. Configure Tomcat/TomEE as usual, with an HTTP connector listening
>>> on some port (probably 8080 is already being used if you have the
>>> default configuration).
>>>
>>> 2. Enable mod_proxy and mod_proxy_ajp in httpd. You may also want
>>> mod_proxy_balancer if you have multiple Tomcat/TomEE nodes you want to
>>> use for load-balancing.
>> Only one server.  No load balancing at this time.
>>>
>>> 3. Configure a <Proxy> directive in your httpd configuration that
>>> looks something like this:
>>>
>>> ProxyPass /webappname/ http://tomcathost:8080/webappname/
>>> ProxyPassReverse /webappname/ http://tomcathost:8080/webappname/
>> I have a requirement that when a user enters /http://www.myhost.com
>> they get the TomEE website. That is why my configuration is as below.
>>
>> ProxyPass         /  ...
>> ProxyPassReverse  /  ...
>>
>>>
>>> Bounce httpd and hit http://httpdhost/webappname/index.jsp and your
>>> request should go through the reverse-proxy (that's httpd) through to
>>> the Tomcat/TomEE node. The "ProxyPassReverse" will re-write certain
>>> response HTTP header fields as they are passed-back to the client, so
>>> that the client will see the "outside" view of the back-end server,
>>> instead of the "inside view" -- that is, the client will see
>>> http://httpdhost/ as the base URL instead of http://tomcathost:8080/
>>> as the base URL.
>>>
>>> Write back with any questions or problems.
>>>
>>> Welcome to the community!
>>>
>>> -chris
>> > >
>> ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org > For
>> additional commands, e-mail: users-help@tomcat.apache.org >
>>
>> -- 
>> The people that bring you Usque <http://Usque.software/>.
>>
> I tried going with ajp with the following configuration after reading
> the ajp documentation.
> Adding a Load module for ajp was not needed as per this message.
> =========================================================================================================
> apachectl configtest
> [Fri Jul 22 19:42:00.022959 2016] [so:warn] [pid 12080] AH01574:
> module proxy_ajp_module is already loaded, skipping
> =========================================================================================================
> With only the following changes to the default httpd.conf
>
> ServerName 70.63.204.226:80
>
> ProxyPass         /  ajp://myDomain.com:8080/MyApp
> =========================================================================================================
> I get the following error trying to access my servlet based web site.
>
>
>   Proxy Error
>
> The proxy server received an invalid response from an upstream server.
> The proxy server could not handle the request /GET /
> <http://www.usque.software/>/.
>
> Reason: *DNS lookup failure for: myDomain.com*
>
> =========================================================================================================
> There is no router or upstream server.  The Fedora 23 server is
> connected to a cable modem with the routing feature turned off.  All
> internet traffic does a straight pass-through to the Fedora server.
>
After changing the ProxyPass config to the IP address of my Fedora
Server I now get Service Unavailable

With only the following changes to the default httpd.conf

ServerName 70.63.204.226:80

ProxyPass         /  ajp://70.63.[redacted].[redacted]:8080/


  503


  Service Unavailable

The server is temporarily unable to service your request due to
maintenance downtime or capacity problems. Please try again later.


-- 
The people that bring you Usque <http://Usque.software/>.

Mime
View raw message