Thank you for all of your help, very informative.
Regarding your last answer, I will look at it in greater detail and let you
know if I have questions (I am less familiar with some of the term you
mention there).
On Fri, Feb 5, 2016 at 11:48 PM, Christopher Schultz <
ch...@christopherschultz.net>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Yuval,
On 2/4/16 3:14 AM, Yuval Schwartz wrote:
>> On Wed, Feb 3, 2016 at 11:15 PM, Christopher Schultz <
>> ch...@christopherschultz.net> wrote:
>
> ELB usually uses HTTP keepalive, so that might be part of the
> issue.
>
>> ELB has a feature call
Update below.
On Thu, Feb 4, 2016 at 8:15 AM, Yuval Schwartz
wrote:
> Thanks, answers below.
>
> On Wed, Feb 3, 2016 at 11:15 PM, Christopher Schultz <
> ch...@christopherschultz.net> wrote:
>
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Yuval,
>>
>> On 2/3/16 12:29 PM, Yuval Schwar
Thanks, answers below.
On Wed, Feb 3, 2016 at 11:15 PM, Christopher Schultz <
ch...@christopherschultz.net> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Yuval,
>
> On 2/3/16 12:29 PM, Yuval Schwartz wrote:
> > Thanks a lot. Comments below.
> >
> > On Wed, Feb 3, 2016 at 5:02 PM, C
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Yuval,
On 2/3/16 12:29 PM, Yuval Schwartz wrote:
> Thanks a lot. Comments below.
>
> On Wed, Feb 3, 2016 at 5:02 PM, Christopher Schultz <
> ch...@christopherschultz.net> wrote:
>
> Try this. Before you are ready to shut down, take note of the pid
Thanks a lot. Comments below.
On Wed, Feb 3, 2016 at 5:02 PM, Christopher Schultz <
ch...@christopherschultz.net> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Yuval,
>
> On 2/2/16 6:11 PM, Yuval Schwartz wrote:
> > Thanks. Answers below
> >
> > On Tuesday, 2 February 2016, Christo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Yuval,
On 2/2/16 6:11 PM, Yuval Schwartz wrote:
> Thanks. Answers below
>
> On Tuesday, 2 February 2016, Christopher Schultz <
> ch...@christopherschultz.net
> >
> wrote:
>
> Yuval,
>
> On 2/2/16 9:28 AM, Yuval Schwartz wrote:
On Tue, Feb 2,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Yuval,
On 2/2/16 9:28 AM, Yuval Schwartz wrote:
> On Tue, Feb 2, 2016 at 4:15 PM, Christopher Schultz <
> ch...@christopherschultz.net> wrote:
>
> Yuval,
>
> On 2/2/16 6:21 AM, Yuval Schwartz wrote:
Hello again Christoph,
I think th
On Tue, Feb 2, 2016 at 4:15 PM, Christopher Schultz <
ch...@christopherschultz.net> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Yuval,
>
> On 2/2/16 6:21 AM, Yuval Schwartz wrote:
> > Hello again Christoph,
> >
> > I think there is a problem with the way that I installed the APR
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Yuval,
On 2/2/16 6:21 AM, Yuval Schwartz wrote:
> Hello again Christoph,
>
> I think there is a problem with the way that I installed the APR
> library. If you recall, I installed a compiled version from the
> distros with the commands yum install ap
Hello again Christoph,
I think there is a problem with the way that I installed the APR library.
If you recall, I installed a compiled version from the distros with the
commands
yum install apr-devel openssl-devel tomcat-native
I get the desired "Loaded APR based library" in my logs.
However, eve
Thank you Christoph,
I installed a compiled version from the distros on my production servers
and I installed the binary version from
http://tomcat.apache.org/download-native.cgi
on my development server.
A slight problem is that when I install from the distros I don't have
control of the version
> Hello,
>
> tomcat version: 8.0.22
> java: jdk1.8.0_05
> server: Amazon Linux AMI
>
> When deploying my web application to my production environment (detailed
> above), I get a message:
>
>
>
> *The APR based Apache Tomcat Native library which allows optimal
> performance in production enviro
13 matches
Mail list logo
