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,
Thanks. Answers below
On Tuesday, 2 February 2016, Christopher Schultz <
ch...@christopherschultz.net
> wrote:
> -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...@christophers
-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
:27 AM, Christoph Nenning <
> christoph.nenn...@lex-com.net> wrote:
>
>> > Hello,
>> >
>> > tomcat version: 8.0.22
>> > java: jdk1.8.0_05
>> > server: Amazon Linux AMI
>> >
>> > When deploying my web application to my produc
stoph Nenning <
christoph.nenn...@lex-com.net> wrote:
> > 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
> 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
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 environments was not found on
ERE [main]
> org.apache.catalina.core.AprLifecycleListener.init An incompatible
> version 1.1.31 of the APR based Apache Tomcat Native library is
> installed, while Tomcat requires version 1.1.32
>
> SEVERE [main]
> org.apache.tomcat.util.net.jsse.JSSESocketFactory.getStore Failed
> to load keystor
I tried upgrading from Tomcat 8.0.14 to 8.0.24 over the weekend and could not
get it working (using Tomcat Native)… Here is what I see in catalina.out:
———
SEVERE [main] org.apache.catalina.core.AprLifecycleListener.init An
incompatible version 1.1.31 of the APR based Apache Tomcat Native
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Andrew,
On 1/24/13 12:59 PM, Andrew Winter wrote:
> We have a COBOL back end that handles the core functions of our
> product. The only way we have for the servlet based front end to
> get at that data is via a type 1 odbc driver. It is a real pain
We have a COBOL back end that handles the core functions of our product.
The only way we have for the servlet based front end to get at that data is
via a type 1 odbc driver. It is a real pain because it is not thread safe
so we have to funnel all the traffic through a single thread.
Anyway, I go
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Andrew,
On 1/23/13 9:54 PM, Andrew Winter wrote:
> Sorry I forgot the versions of things I am using.
>
> Tomcat 6.0.36 Red Hat Enterprise Linux Server release 6.2
> (Santiago) Java 7u11 (32 bit)
>
> I think I found the problem, though. I have to r
Sorry I forgot the versions of things I am using.
Tomcat 6.0.36
Red Hat Enterprise Linux Server release 6.2 (Santiago)
Java 7u11 (32 bit)
I think I found the problem, though. I have to run a 32 bit jvm because a
COBOL odbc driver we have to use only comes in a 32 bit version. But the
Red Hat box
t java.library.path (a JVM
system property) to it.
APR should be installed in /usr/lib and not in /usr/local. Where did
APR end up when you installed the RPM?
> In the tomcat6.conf I set the
> JAVA_OPTS="-Djava.library.path=/usr/local/apr/lib"
That should be enough to load apr, but
folder. In the tomcat6.conf I set
the JAVA_OPTS="-Djava.library.path=/usr/local/apr/lib"
But I still get the message at start: INFO: The APR based Apache Tomcat
Native library which allows optimal performance in production environments
was not found on the java.library.path: /usr/local/apr
> From: Charl Gerber [mailto:[EMAIL PROTECTED]
> Subject: APR based Apache Tomcat Native library
>
> INFO: The APR based Apache Tomcat Native library which
> allows optimal performance in production environments
> was not found on the java.library.path:
>
> What's t
entos 5.0
> with
> Java 1.6_05. I made no customizations to the setups
> and deployed a .war file to the webapps directory of
> Tomcat.
>
> The first thing I see in the log files is:
>
> INFO: The APR based Apache Tomcat Native library
> which
> allows optimal perform
I have just installed Tomcat 6.0.16 on Centos 5.0 with
Java 1.6_05. I made no customizations to the setups
and deployed a .war file to the webapps directory of
Tomcat.
The first thing I see in the log files is:
INFO: The APR based Apache Tomcat Native library which
allows optimal performance in
26 matches
Mail list logo
