On 08/09/2010 06:37, Caldarale, Charles R wrote:
From: Anthony J. Biacco [mailto:abia...@formatdynamics.com]
Subject: RE: Tomcat Warning about existing attribute for Host
I think those flags are only valid in the Context blocks now.
There are getters and setters in the 7.0
On 08/09/2010 01:52, Mohammad M. AbuZer wrote:
I'm using tomcat 7.0.2 BETA
-- Forwarded message --
From: Mohammad M. AbuZer m.abuze...@gmail.com
Date: Wed, Sep 8, 2010 at 3:51 AM
Subject: Tomcat Warning about existing attribute for Host
To: Tomcat Users List
Hello
We've just noticed that the maintenance mode operates on all workers, so
having one worker run maintenance for the rest is making tracing the
problem difficult. Reading down the logs, we can see it finds a worker
and iterates through workers perforing maintenance.
Is this correct?
Moving
With 2 workers, the system has been working well for months.
I now wanted to add an extra two workers, i.e. a total of 4 tomcats,
and load balance across all 4. Is this possible?
With respect to the worker names, a number works well. I have set the
jvmRoute to be numbers too, and my app
And here is my JK info
JkWorkersFile E:/products/thirdparty/apache-2.2.15-01/conf/workers.properties
JkShmFile E:/products/thirdparty/apache-2.2.15-01/logs/mod_jk.shm
JkLogFile E:/products/thirdparty/apache-2.2.15-01/logs/mod_jk.log
JkLogLevelerror
JkLogStampFormat [%a %b %d %H:%M:%S
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andrew,
On 9/8/2010 9:10 AM, Andrew Bruno wrote:
And here is my JK info
Thanks.
JkWorkersFile E:/products/thirdparty/apache-2.2.15-01/conf/workers.properties
JkShmFile E:/products/thirdparty/apache-2.2.15-01/logs/mod_jk.shm
JkLogFile
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tom,
On 9/7/2010 11:49 AM, Tom Jones wrote:
I'm trying to figure out which http connector is best suited for my
needs. I was looking around for some info on anything that compares them
all but I really did no find much.
Out of the three
Hello,
I don't thikn the shutdown call is to blame - I think it's the large pile
of code below. i.e. everything below the if (shutdown(..)) below. The
question is, what does it all do and does it actually work? It appears to
be the 'drain' code, but given it often results in this message:
On 09/08/2010 05:08 PM, John Baker wrote:
Hello,
I don't thikn the shutdown call is to blame - I think it's the large pile
of code below. i.e. everything below the if (shutdown(..)) below. The
question is, what does it all do and does it actually work? It appears to
be the 'drain' code, but
please can you remove me off the mailing list
many thanks
On Wed, Sep 8, 2010 at 4:29 PM, Mladen Turk mt...@apache.org wrote:
On 09/08/2010 05:08 PM, John Baker wrote:
Hello,
I don't thikn the shutdown call is to blame - I think it's the large pile
of code below. i.e. everything below
On 09/08/2010 05:08 PM, John Baker wrote:
The code *is* required.
It is used when the client disconnects while the backend
still has some data in the AJP buffer. Drain is needed
to read that excess data.
Why does it always report 0 bytes read?
If you can compile mod_jk and test, try
I think it would be helpful if you could walk us through the code.
The shutdown function provides three error codes - the jk function doesn't
check them, and the most likely is 'socket closed' (ie jboss closed it?), hence
I'm unsure what the drain code is doing.
--Original Message--
Hi,
We are using Apache Tomcat 5.0 which gets stuck sometimes and needs a stop
and restart. We are using Microsoft Windows 2000 Service Pack 4.
Below is the error from the log file,
Kindly provide some solution.
2010-09-07 10:33:38 StandardWrapperValve[IFSCoreServlet]: Servlet.service()
for
Looks like your application took too long to respond and by the time it tried
to write to the output stream, it had been closed. Have you set any
connection/socket timeouts?
-Original Message-
From: Sumeet Chitte chittesum...@gmail.com
Date: Wed, 8 Sep 2010 21:48:31
To:
On 09/08/2010 05:51 PM, John Baker wrote:
I think it would be helpful if you could walk us through the code.
It is very simple actually.
1. shutdown write end of our connection to Tomcat
This should cause the soket.read() in Tomcat
to throw exception which is used to close the socket
I don't know what you mean by We are using Apache Tomcat 5.0 which gets stuck
sometimes and needs a stop and restart but the stack trace you posted is
almost certainly evidence of a bug in your code.
It's an illegal state exception to try and send an error if you have already
sent normal
I thought an illegal state exception would occur if an attempt was made to
write to a socket that's now shut but you are right, it looks more like an
attempt to perform an internal redirect after response has been committed
(although that message should appear in the logs).
-Original
Thank you for your response.
I will tell you some more details.
We are using an Powerbuilder application which calls the documents from
server.
This server uses a third party tool, which uses Apache Tomcat 5.0.
What happens is that this Tomcat service gets stuck sometimes and the
Powerbuilder
Tomcat is *not* getting stuck.
There is a bug in com.infodata.ifs.core.IFSCoreServlet which is attempting to
send an HTTP error *after* content has already been sent.
On the otherwise this powerbuilder or whatever client is waiting for data that
is never going to come because the application
From: Sumeet Chitte [mailto:chittesum...@gmail.com]
Subject: Re: Tomcat 5.0 which gets stuck
This server uses a third party tool, which uses Apache Tomcat 5.0.
Please be aware that Tomcat 5.0 is deprecated. You are much more likely to get
help if you are running on a current level.
What
Thank you some much for your help in such a short time.
Thank you for showing me the right direction to work on.
On Wed, Sep 8, 2010 at 11:39 PM, Maximilian Stocker
m...@talentoyster.comwrote:
Tomcat is *not* getting stuck.
There is a bug in com.infodata.ifs.core.IFSCoreServlet which is
Apache 2:
Is there a way to send custom message instead of just the Error Code
when there is an upload limit set using LimitRequestBody?
Something like You have exceeded the size
-
To unsubscribe, e-mail:
Sorry wrong email group
On Wed, Sep 8, 2010 at 1:37 PM, Mohit Anchlia mohitanch...@gmail.com wrote:
Apache 2:
Is there a way to send custom message instead of just the Error Code
when there is an upload limit set using LimitRequestBody?
Something like You have exceeded the size
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Rainer,
On 9/3/2010 2:53 AM, Rainer Frey wrote:
And if you use cold deployment only, how do you avoid downtime for other
apps?
Do you really use one Tomcat instance per app?
I use one Tomcat instance per webapp, and I use cold deployment only.
I've tried following all of the advice in the previous threads, but I'm up
against a wall here.
I have added Context privileged=true to my context.xml
In the same directory, i have uncommented the SSI Filter as well as the
Filter mapping and the *.shtml mime mapping in web.xml. see below:
I've tried following all of the advice in the previous threads, but I'm up
against a wall here.
I have added Context privileged=true to my context.xml
In the same directory, i have uncommented the SSI Filter as well as the
Filter mapping and the *.shtml mime mapping in web.xml. see below:
I've tried following all of the advice in the previous threads, but I'm up
against a wall here.
I have added Context privileged=true to my context.xml
In the same directory, i have uncommented the SSI Filter as well as the
Filter mapping and the *.shtml mime mapping in web.xml. see below:
jeffo1b wrote:
I've tried following all of the advice in the previous threads, but I'm up
against a wall here.
I have added Context privileged=true to my context.xml
In the same directory, i have uncommented the SSI Filter as well as the
Filter mapping and the *.shtml mime mapping in web.xml.
On Tue, Sep 7, 2010 at 3:40 PM, Pid p...@pidster.com wrote:
On 07/09/2010 06:14, jan gestre wrote:
On Tue, Sep 7, 2010 at 1:02 PM, Wesley Acheson wesley.ache...@gmail.com
wrote:
On Tue, Sep 7, 2010 at 4:34 AM, jan gestre ipcopper...@gmail.com wrote:
I'm using the latest 6.0.29 binary
29 matches
Mail list logo
