On 24 December 2013 07:58, Daniel Mikusa wrote:
> On Dec 19, 2013, at 8:08 PM, David Bullock
> wrote:
>
>> On 20 December 2013 04:10, Daniel Mikusa wrote:
> Unfortunately, once this problem starts to occur onWritePossible doesn't get
> called back.
> When I take a thread dump of the code, it
> Date: Fri, 20 Dec 2013 14:43:30 -0500
> From: ch...@christopherschultz.net
> To: users@tomcat.apache.org
> Subject: Re: ssl_error_internal_error_alert in tomcat 7
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
> Thanks for the suggestions!!
> Jaya,
>
> On 12/20/13, 2:13 PM, jaya ra
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Barry,
On 12/23/13, 4:14 PM, Propes, Barry L wrote:
>
> -Original Message- From: Tomcat Random
> [mailto:tomcat.ran...@gmail.com] Sent: Monday, December 23, 2013
> 2:56 PM To: Tomcat Users List Subject: Re: What if my database is
> unavaila
Sorry if resurrecting the dead is frowned upon here but I thought I would
just add my resolve to this. Honestly, after writing a lot of code
otherwise, logging was probably the most frustrating.
Tomcat 7.0.42, RHEL 6
1. SL4FJ with Logback works beautifully.
2. I have custom error pages in web.xm
-Original Message-
From: Tomcat Random [mailto:tomcat.ran...@gmail.com]
Sent: Monday, December 23, 2013 2:56 PM
To: Tomcat Users List
Subject: Re: What if my database is unavailable at startup?
Barry,
You have testOnBorrow="true" without a validation query. That means the line is
usele
On Dec 19, 2013, at 8:08 PM, David Bullock
wrote:
> On 20 December 2013 04:10, Daniel Mikusa wrote:
>> When run, you'll see that it processes some of the requests but fails due to
>> a timeout. I've not been able to replicate the other exceptions with the
>> unit test though, so those may be
Barry,
You have testOnBorrow="true" without a validation query. That means the
line is useless. Or as the docs say:* NOTE - for a true value to have any
effect, the validationQuery parameter must be set to a non-null string*
Best,
Alec
On Mon, Dec 16, 2013 at 10:07 AM, Propes, Barry L
wrote:
>
On 12/23/2013 9:40 AM, Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Dan,
On 12/23/13, 7:01 AM, Daniel Mikusa wrote:
On Dec 23, 2013, at 5:17 AM, CRMG Sysadmin
wrote:
We are facing the below fatal error in tomcat log file
frequently. While the error occurs our to
Hi André,
> -Original Message-
> From: André Warnier [mailto:a...@ice-sa.com]
> Sent: Monday, December 23, 2013 6:09 PM
> To: Tomcat Users List
> Subject: Re: EOFException in AjpNioProcessor
>
> Jesse Barnum wrote:
> > On Dec 22, 2013, at 8:54 AM, Konstantin Preißer
> wrote:
> >
> >> I s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
André,
On 12/23/13, 7:05 AM, André Warnier wrote:
> May I point out that the log below already provides a link to
> report the error, which seems to belong to Java itself, not to
> Tomcat ?
I think you get that link no matter why the JVM crashed. F
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Dan,
On 12/23/13, 7:01 AM, Daniel Mikusa wrote:
> On Dec 23, 2013, at 5:17 AM, CRMG Sysadmin
> wrote:
>> We are facing the below fatal error in tomcat log file
>> frequently. While the error occurs our tomcat is stopped. Kindly
>> help us on this A
Hi Jesse,
> -Original Message-
> From: Jesse Barnum [mailto:jsb_tom...@360works.com]
> Sent: Monday, December 23, 2013 5:46 PM
> To: Tomcat Users List
> Subject: Re: EOFException in AjpNioProcessor
>
> On Dec 22, 2013, at 8:54 AM, Konstantin Preißer
> wrote:
>
> > I suspect the AJP clie
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
André,
On 12/23/13, 12:09 PM, André Warnier wrote:
> Jesse Barnum wrote:
>> On Dec 22, 2013, at 8:54 AM, Konstantin Preißer
>> wrote:
>>
>>> I suspect the AJP client intentionally closes the connection if
>>> e.g. the HTTP client which connected t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jessie,
On 12/23/13, 11:45 AM, Jesse Barnum wrote:
> On Dec 22, 2013, at 8:54 AM, Konstantin Preißer
> wrote:
>
>> I suspect the AJP client intentionally closes the connection if
>> e.g. the HTTP client which connected to the outer Webserver
>> (H
Jesse Barnum wrote:
On Dec 22, 2013, at 8:54 AM, Konstantin Preißer wrote:
I suspect the AJP client intentionally closes the connection if e.g. the HTTP
client which connected to the outer Webserver (HTTPD, IIS) aborted the HTTP
connection (or there was some other error) so this error is ref
On Dec 22, 2013, at 8:54 AM, Konstantin Preißer wrote:
> I suspect the AJP client intentionally closes the connection if e.g. the HTTP
> client which connected to the outer Webserver (HTTPD, IIS) aborted the HTTP
> connection (or there was some other error) so this error is reflected at
> Tomc
Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Konstantin,
On 12/22/13, 8:54 AM, Konstantin Preißer wrote:
Note that the reason for a EOFException is slightly different than
just reading from a stream when there is no more data present.
In Java (and .Net), when yo
CRMG Sysadmin wrote:
Hi,
We are facing the below fatal error in tomcat log file frequently. While
the error occurs our tomcat is stopped. Kindly help us on this ASAP.
May I point out that the log below already provides a link to report the error, which
seems to belong to Java itself, not to T
On Dec 23, 2013, at 5:17 AM, CRMG Sysadmin wrote:
> Hi,
>
> We are facing the below fatal error in tomcat log file frequently. While
> the error occurs our tomcat is stopped. Kindly help us on this ASAP.
This is not a Tomcat issue. Your JVM is crashing. See further down for more
info...
>
Hi,
We are facing the below fatal error in tomcat log file frequently. While
the error occurs our tomcat is stopped. Kindly help us on this ASAP.
Also paste the /root/hs_err_pid1112.log with this mail.
A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x
20 matches
Mail list logo
