>> When I am trying to start my server I got following error as:
>> A fatal error has been detected by the Java Runtime Environment:
>> #
>> # SIGSEGV (0xb) at pc=0x7fd4f206e28a, pid=2412, tid=2412
>> #
>> # JRE version: (11.0+18) (build )
>> # Java VM: Java HotSpot(TM) 64-Bit Server VM (11-e
On 6/25/2018 9:20 PM, Prateek wrote:
> My configuration:
> OS:REDHAT 7.5 (64 bit)
> Tomcat: 8.5.31
> Jdk- jdk-11(Early-Access)
+1 to everything else you've been told on this thread.
More stuff inline below.
> When I am trying to start my server I got following error as:
> A fatal error has been
On 6/27/2018 10:53 AM, Coty Sutherland wrote:
On Wed, Jun 27, 2018 at 1:08 PM, Prateek wrote:
Hi Chris,
By hardened, I meant that support for some FIPS non-complaint algos were
removed/disabled.
Thanks for confirming again that this is a clear problem with the JVM.
From what you've given us
; Prateek.
>
> From: Christopher Schultz
> Sent: Wednesday, June 27, 2018 10:04 PM
> To: users@tomcat.apache.org
> Subject: Re: problem in starting tomcat
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Prateek,
>
> On 6/27/18 12:04 PM, Prateek wrote
11.super-alpha that you were referring to. Can you please point me in
that direction.
Thanks and Regards,
Prateek.
From: Christopher Schultz
Sent: Wednesday, June 27, 2018 10:04 PM
To: users@tomcat.apache.org
Subject: Re: problem in starting tomcat
-BEGIN PGP SIGNED MESSAGE-
Hash
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Prateek,
On 6/27/18 12:04 PM, Prateek wrote:
> Hi Chris,
>
> We are running, libtcnative version 1.2.16 with apr version 1.6.3,
> compiled from the source, configured to use a hardened version of
> OpenSSL version 1.0.2.
(LOL hardened OpenSSL)
with any Java early access
builds and hence the attempt to run using JDK11 EA build. Please suggest on
the course of action that I should be taking.
Regards,
Prateek.
From: Igal Sapir
Sent: Tuesday, June 26, 2018 10:21 PM
To: users@tomcat.apache.org
Subject: Re: problem in starting tomcat
Hi Coty,
I have tried after removing OnError from the JAVA_OPTS. The results are the
same.
Please suggest.
Regards,
Prateek.
From: Coty Sutherland
Sent: Tuesday, June 26, 2018 10:22 PM
To: Tomcat Users List
Subject: Re: problem in starting tomcat
On Tue, Jun 26, 2018 at 12:27 PM, Prateek
: Re: problem in starting tomcat
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Prateek,
On 6/25/18 11:20 PM, Prateek wrote:
> Hi, My configuration: OS:REDHAT 7.5 (64 bit) Tomcat: 8.5.31 Jdk-
> jdk-11(Early-Access)
>
> When I am trying to start my server I got following error as: A
&
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Prateek,
On 6/27/18 1:41 AM, Prateek wrote:
> Here I am hs_err_pid file
> Native frames: (J=compiled Java code, A=aot compiled Java code,
> j=interpreted, Vv=VM code, C=native code) C [libc.so.6+0x8128a]
> strlen+0x2a V [libjvm.so+0x6030f1]
> Cla
Here I am hs_err_pid file
Sent from Mail for Windows 10
From: Coty Sutherland
Sent: Tuesday, June 26, 2018 10:22 PM
To: Tomcat Users List
Subject: Re: problem in starting tomcat
On Tue, Jun 26, 2018 at 12:27 PM, Prateek Yadav
wrote:
> Thanks for reply
> I already tested it for more th
On Tue, Jun 26, 2018 at 12:27 PM, Prateek Yadav
wrote:
> Thanks for reply
> I already tested it for more than one machine so hardware problem can not
> be a case.
>
What happens if you don't specify that OnError call? Can you attach a
fuller stack trace if not the entire hs_err_pid log (make su
Prateek,
On 6/26/2018 9:27 AM, Prateek Yadav wrote:
Thanks for reply
I already tested it for more than one machine so hardware problem can not
be a case.
On 6/25/2018 8:20 PM, Prateek wrote:
My configuration:
OS:REDHAT 7.5 (64 bit)
Tomcat: 8.5.31
Jdk- jdk-11(Early-Access)
When I am trying t
Thanks for reply
I already tested it for more than one machine so hardware problem can not
be a case.
On Tue, Jun 26, 2018, 9:40 PM Christopher Schultz <
ch...@christopherschultz.net> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Prateek,
>
> On 6/25/18 11:20 PM, Prateek wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Prateek,
On 6/25/18 11:20 PM, Prateek wrote:
> Hi, My configuration: OS:REDHAT 7.5 (64 bit) Tomcat: 8.5.31 Jdk-
> jdk-11(Early-Access)
>
> When I am trying to start my server I got following error as: A
> fatal error has been detected by the Java R
Date sent: Wed, 11 Jun 2008 09:51:03 -0400
From: Christopher Schultz <[EMAIL PROTECTED]>
Subject:Re: OT: Fedora Core 8 viability (was Re: Problem in
starting tomcat)
To: Tomcat Users List
Send reply to: Tomcat User
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Steve,
Steve Ochani wrote:
| On 10 Jun 2008 at 17:20, Christopher Schultz wrote:
|> What leads you to that conclusion [that Fedora Core is inappropriate
for production use]?
|
| 1. When Fedora project was started I remember reading that it was
almost
On 10 Jun 2008 at 17:20, Christopher Schultz wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Steve,
>
> Steve Ochani wrote:
> | Off topic remark. I hope you don't use [Fedora Core 8] on
> production
> machines. Fedora is not
> | designed for that.
>
> What leads you to that conclus
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Steve,
Steve Ochani wrote:
| Off topic remark. I hope you don't use [Fedora Core 8] on production
machines. Fedora is not
| designed for that.
What leads you to that conclusion?
- -chris
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (MingW32
Date sent: Mon, 09 Jun 2008 06:23:08 -0700 (PDT)
From: Raghavan_sat <[EMAIL PROTECTED]>
Subject:Problem in starting tomcat
To: users@tomcat.apache.org
Send reply to: Tomcat Users List
>
> Hi,
>I downloaded apache-tom
Do you have Native POSIX Thread Library installed?
Identification of this subsystem features as well as which package you
should download are available at
http://linux-sxs.org/internet_serving/c140.html
also be aware of the environmental parameters that tomcat uses
an example is located at
# y
21 matches
Mail list logo
