On 7/23/2016 3:15 PM, Paul Roubekas wrote:
> On 7/23/2016 2:57 PM, Christopher Schultz wrote:
>> Paul,
>>
>> On 7/23/16 8:39 AM, Paul Roubekas wrote:
>>> http://www.myDomain.com gets me to Tomcat where my ROOT webapp is
>>> deployed. Thank you very much!!!
>>> A few things that still need correcti
On 7/23/2016 2:57 PM, Christopher Schultz wrote:
> Paul,
>
> On 7/23/16 8:39 AM, Paul Roubekas wrote:
> > http://www.myDomain.com gets me to Tomcat where my ROOT webapp is
> > deployed. Thank you very much!!!
>
> > A few things that still need correction...
>
> > Not all my webpages/servlets are h
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Paul,
On 7/23/16 8:39 AM, Paul Roubekas wrote:
> http://www.myDomain.com gets me to Tomcat where my ROOT webapp is
> deployed. Thank you very much!!!
>
> A few things that still need correction...
>
> Not all my webpages/servlets are https, just on
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Paul,
On 7/22/16 4:24 PM, Paul Roubekas wrote:
> On 7/22/2016 4:14 PM, Christopher Schultz wrote:
>> 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
On 7/23/2016 4:12 AM, André Warnier (tomcat) wrote:
> On 23.07.2016 02:37, Paul Roubekas wrote:
>>> 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.
>>> >==
On 22.07.2016 19:15, Berneburg, Cris J. - US wrote:
> The OutOfMemoryError in Tomcat Manager was caused by a memory leak when Log4J
> did not terminate properly. This was due to my mistake of neglecting to set
> up the necessary Log4J shutdown procedures.
>
> Adding Log4jServletContextListener
On 23.07.2016 02:37, Paul Roubekas wrote:
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.
>==
