For this part of the error you have to look at at the application.
appweb.NativeCall looks like a class that is an interfaces to a
native (C) library. The error is thrown in that native library.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Wednesday,
Btw. appweb.NativeCall doesn't look like a part of tomcat
so it most likely the application or an additional library
that is used by the application.
-Original Message-
From: Ralph Einfeldt
Sent: Wednesday, June 23, 2004 11:15 AM
To: Tomcat Users List
Subject: RE: tomcat crash
To: Tomcat Users List
Subject: RE: tomcat crash ... unexpected exception
For this part of the error you have to look at at the application.
appweb.NativeCall looks like a class that is an interfaces to a
native (C) library. The error is thrown in that native library
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 23, 2004 11:39 AM
To: Tomcat Users List
Subject: Re: tomcat crash ... unexpected exception
Jun 23, 2004 11:17:12 AM org.apache.jk.server.JkCoyoteHandler action
SEVERE: Error in action code
that created the request died
- the user closed the browser before the response was sent
- there may be further reasons
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 23, 2004 11:39 AM
To: Tomcat Users List
Subject: Re: tomcat crash ... unexpected
that created the request died
- the user closed the browser before the response was sent
- there may be further reasons
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 23, 2004 11:39 AM
To: Tomcat Users List
Subject: Re: tomcat crash
the by their name.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 23, 2004 2:25 PM
To: Tomcat Users List
Subject: Re: tomcat crash ... unexpected exception
Again about my general problem, below is an output of the
'top' command on the webserver.
We
- there may be further reasons
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 23, 2004 11:39 AM
To: Tomcat Users List
Subject: Re: tomcat crash ... unexpected exception
Jun 23, 2004 11:17:12 AM org.apache.jk.server.JkCoyoteHandler action
SEVERE: Error
files. You should be
able to identify the by their name.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 23, 2004 2:25 PM
To: Tomcat Users List
Subject: Re: tomcat crash ... unexpected exception
Again about my general problem
by the way, I have maybe a problem in my configuration
If you have two minutes ... what do you think about it ?
and also, I have no jk2.properties file, is it absolutely necessary ?
- httpd.conf ---
...
LoadModule jk2_module modules/mod_jk2-2.0.4.so
...
-
if you're using tomcat in standalone mode, I would recommend
commenting out the jk stuff all together. I noticed your minProcessors
is 100 and max is 500. You must get some serious load, or the usage
pattern is such that an unique user session has lots of requets.
good luck.
peter
On Wed, 23
Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 23, 2004 3:24 PM
To: Tomcat Users List
Subject: Re: tomcat crash ... unexpected exception
# real workers (Tomcat instances)
[ajp13:localhost:8009]
info=Worker1
channel=channel.socket:localhost:8009
group=lb
if you're using tomcat in standalone mode, I would recommend
commenting out the jk stuff all together.
Tomcat serves all .jsp files and Apache manages the rest. The idea is to increase
performance by letting Tomcat only with its .jsp while leaving the rest to Apache.
Do you think it's a good
13 matches
Mail list logo
