-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Syam,
On 10/8/17 2:27 PM, Syam Pillai wrote:
> Thanks Chris, yes you are right they messed it up. I will also file
> a complaint with them.
https://forums.aws.amazon.com/thread.jspa?messageID=809159
https://forums.aws.amazon.com/thread.jspa?message
Thanks Chris, yes you are right they messed it up.
I will also file a complaint with them.
On Sun, Oct 8, 2017 at 9:44 PM, Christopher Schultz <
ch...@christopherschultz.net> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Syam,
>
> On 10/5/17 5:10 PM, Syam Pillai wrote:
> > On my
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Syam,
On 10/5/17 5:10 PM, Syam Pillai wrote:
> On my AMI (Amazon Linux) server, tomcat 8 was running happily but
> today, after an upgrade (Version is now 8.5.16.0), the server is
> failing to start with the following message:
>
> INFO [main] org.a
Dear Mark,
Thanks for the response.
I already have the following installed:
Tomcat Native: 1.2.10-1.18.amzn1
OpenSSL 1.0.2k-fips 26 Jan 2017
Also, please see this:
ld /usr/lib64/libtcnative-1.so.0.2.10
ld: warning: cannot find entry symbol _start; not setting start address
/usr/lib64/libtcnativ
On 05/10/17 22:10, Syam Pillai wrote:
> On my AMI (Amazon Linux) server, tomcat 8 was running happily but today,
> after an upgrade (Version is now 8.5.16.0), the server is failing to start
> with the following message:
>
> INFO [main] org.apache.coyote.AbstractProtocol.init Initializing
> Protoco
On my AMI (Amazon Linux) server, tomcat 8 was running happily but today,
after an upgrade (Version is now 8.5.16.0), the server is failing to start
with the following message:
INFO [main] org.apache.coyote.AbstractProtocol.init Initializing
ProtocolHandler ["https-openssl-nio-8443"]
/usr/share/soe
