On 05/08/2019 21:49, Chen Levy wrote:
> Hello Experts
>
> Several of my production servers were recently upgraded from Tomcat 9.0.14 to
> 9.0.21; immediately after the upgrade the servers started accumulating memory
> and open-files (on Linux) in a steady trend that was not observed before.
> Af
Hello Experts
Several of my production servers were recently upgraded from Tomcat 9.0.14 to
9.0.21; immediately after the upgrade the servers started accumulating memory
and open-files (on Linux) in a steady trend that was not observed before.
After a couple of days (without reaching the memory
uot;important"
> publicly-known vulnerabilities. You should upgrade ASAP.
>
Yes, I agree. There are some "technical debt" and upgrade Tomcat and
Apache are one of them. We have plans to do it on next release. :)
> The connection timeout you are seeing is on the client end:
omcat: 7.0.55 JRE: 1.8_92 -Dhttps.protocols=TLSv1,TLSv1.1,TLSv1.2
Your version is Tomcat is quite old and contains numerous "important"
publicly-known vulnerabilities. You should upgrade ASAP.
The connection timeout you are seeing is on the client end: your
client is connecting to another
One of our legacy applications is using Apache Commons HttpClient 3.1.
POST call to one REST service is failing with
"java.net.ConnectException: Connection timed out: connect"
exception[1]. Timeout is occurring after one minute. To figure out
where thread is spending all the time, I took multiple t
Typing this from my phone so sorry for top posting no other option.
You might also check your garbage collection which can introduce some
pauses in some cases. Just a thought ...
On May 11, 2012 7:26 AM, "Jon Drukman" wrote:
> Caldarale, Charles R unisys.com> writes:
>
> > Using JConsole or Vis
Caldarale, Charles R unisys.com> writes:
> Using JConsole or VisualVM would be a good start.
OK, I'll take a look at those.
> > There's only one app running on this tomcat, if that makes
> > any difference.
>
> Does it connect to a database (or any other external resource)?
> If so, are you
> From: Jon Drukman [mailto:j...@cluttered.com]
> Subject: Re: Connection timeout
> Is there any way to find out how many threads are being used
> at a given moment?
Using JConsole or VisualVM would be a good start. Either of those will let you
see what's going on with thr
Pid pidster.com> writes:
> The basic point we're making is that you are twiddling the wrong knobs.
OK, good to know.
> If you want to handle more connections, increase the size of the thread
> pool that handles requests, don't increase the size of the queue of
> requests waiting to be handled.
On 10/05/2012 21:40, Jon Drukman wrote:
> Caldarale, Charles R unisys.com> writes:
>
>> You keep contradicting yourself: is it a massive box, or can it
>> only support a miniscule number of threads?
>> Pick one.
>
> Where did I say it could only support a miniscule number of threads?
> I'm sor
Caldarale, Charles R unisys.com> writes:
> You keep contradicting yourself: is it a massive box, or can it
> only support a miniscule number of threads?
> Pick one.
Where did I say it could only support a miniscule number of threads?
I'm sorry if I accidentally gave that impression.
It's a ma
> From: Jon Drukman [mailto:j...@cluttered.com]
> Subject: Re: Connection timeout
> > Do you really want to queue up requests, rather than just accepting them
> > and assigning them to threads?
> Well, I assume at some point I may run out of threads.
> > * 400 is a g
Pid pidster.com> writes:
> Not really. Did you change the connectionTimeout downwards from the
> default 60 secs to 3 secs?
Yes. Although the original version of the file was 20 seconds.
The clients (which I wrote) all have a 3 second connect timeout, so it seemed
to make sense to make the se
On 10/05/2012 20:06, Jon Drukman wrote:
> I have a commercial app running Tomcat 6. I don't really know anything
> about Tomcat, so I need some help with performance tuning.
>
> What happens is that a small percentage of connections from our client
> machines just timeout on the connect. I assum
I have a commercial app running Tomcat 6. I don't really know anything
about Tomcat, so I need some help with performance tuning.
What happens is that a small percentage of connections from our client
machines just timeout on the connect. I assume I'm running into some
limitation in Tomcat.
Her
some questions regarding connection timeout settings. Occasionally, when
the site is busier we see jumps in the number of connections to 8009 and then
that number stays high for about 30 minutes before settling back down into our
average range. A thread dump shows that these connections correspond to
.
>> I have some questions regarding connection timeout settings. Occasionally,
>> when the site is busier we see jumps in the number of connections to 8009
>> and then that number stays high for about 30 minutes before settling back
>> down into our average range. A thread d
Kari Scott wrote:
We are running Tomcat 6. 0.32 with jdk1.6.0_26 on Solaris 10, mod_ajp 1.3 and
Apache 2.2.21 on all but one production server which is the same except for
it's running Tomcat 7.0.21.
I have some questions regarding connection timeout settings. Occasionally, when
the
We are running Tomcat 6. 0.32 with jdk1.6.0_26 on Solaris 10, mod_ajp 1.3 and
Apache 2.2.21 on all but one production server which is the same except for
it's running Tomcat 7.0.21.
I have some questions regarding connection timeout settings. Occasionally, when
the site is busier w
Patrick Flaherty wrote:
Hi,
I see that the default connection timeout for the Tomcat connector by
default is set to 2 (20 sec).
This has been the shipping default for 5.x, 6.x and 7.x (in the
server.xml) The documentation describes
the default timeout to be 6 (60 sec). Is the default
Hi,
I see that the default connection timeout for the Tomcat connector by
default is set to 2 (20 sec).
This has been the shipping default for 5.x, 6.x and 7.x (in the
server.xml) The documentation describes
the default timeout to be 6 (60 sec). Is the default value of
2 in the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
laredotornado,
On 2/2/2011 11:23 AM, laredotornado wrote:
> You mean set timeouts at the database level?
I would do it at the query level. The JDBC API has overloaded methods
for Statement.executeQuery and friends that all take timeouts.
It's possib
On 02/02/2011 16:23, laredotornado wrote:
>
> You mean set timeouts at the database level?
Yes.
> What if the Tomcat thread is
> hung for some other reason?
Then you have an application bug to fix.
> Is there any setting that will cause Tomcat to
> kill a thread if that thread is "stuck"? - D
gt; -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>
>
--
View this message in context:
http://old.nabble.com
On 02/02/2011 15:22, laredotornado wrote:
>
> Hi,
>
> We're using Tomcat 6.0.24. We would like Tomcat to kill stuck threads after
> a certain period of time, but Tomcat doesn't appear to be doing this.
> Specifically, when the database doesn't return results, the connections just
> build up. H
ything we might
need to add to get Tomcat to kill stuck connections? - Dave
--
View this message in context:
http://old.nabble.com/Trouble-with-connection-timeout-settings-tp30826944p30826944.html
Sent from the Tomcat - User mailing list archiv
On 25-02-10 18:37, Chris Mannion wrote:
Very helpful advice. I can't help but feel a little out of my depth
with this one :-\
Hi Chris,
You may want to check if your JVM is started with one of the following
options:
-Dsun.net.client.defaultConnectTimeout=
-Dsun.net.client.defaultReadTim
Thanks Chris,
Very helpful advice. I can't help but feel a little out of my depth
with this one :-\
On 19 February 2010 16:46, Christopher Schultz
wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Chris,
>
> On 2/19/2010 11:08 AM, Chris Mannion wrote:
>> Thank, genuinely, for the res
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris,
On 2/19/2010 11:08 AM, Chris Mannion wrote:
> Thank, genuinely, for the responses, I've learned how I *could* set a
> timeout, which I didn't know before. However, what I'm actually
> trying to get to the bottom of is what timeout could be in
-BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Chuck,
>
> On 2/12/2010 10:46 AM, Caldarale, Charles R wrote:
>>> From: Christopher Schultz [mailto:ch...@christopherschultz.net]
>>> Subject: Re: What governs a URL connection timeout?
>>>
>>> It'
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chuck,
On 2/12/2010 10:46 AM, Caldarale, Charles R wrote:
>> From: Christopher Schultz [mailto:ch...@christopherschultz.net]
>> Subject: Re: What governs a URL connection timeout?
>>
>> It's possible that (the other) Chri
> From: Christopher Schultz [mailto:ch...@christopherschultz.net]
> Subject: Re: What governs a URL connection timeout?
>
> It's possible that (the other) Chris is using a library
The OP already posted the code of interest, and it would be simple to modify it
to set an appropri
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Peter,
On 2/12/2010 7:34 AM, Peter Crowther wrote:
> Chris, did you actually read the link or was that a knee-jerk
> response? Notably the following, taken from between the first and
> second boxed pieces of code on that page:
>
> "The openStream()
Chris, did you actually read the link or was that a knee-jerk
response? Notably the following, taken from between the first and
second boxed pieces of code on that page:
"The openStream() method is actually just a shortcut for
openConnection().getInputStream()."
... plus the source of openStream(
Thanks Peter but we're not using a URLConnection, nor are we
explicitly setting any timeouts, as you can see from the code.
On 12 February 2010 12:06, Peter Crowther wrote:
> A swift Google for:
> java url openStream timeout
> reveals:
> http://stuffthathappens.com/blog/2007/09/10/urlopenstream
A swift Google for:
java url openStream timeout
reveals:
http://stuffthathappens.com/blog/2007/09/10/urlopenstream-might-leave-you-hanging/
as its first hit.
In essence: the timeout is controlled by setTimeout on UrlConnection.
On 12 February 2010 11:59, Chris Mannion wrote:
> Hi all
>
> Ho
Hi all
Hoping someone can shed some light on a little puzzle I have. This
may be more a Java programming problem than a Tomcat problem so
apologies if that is the case but it's specific to a system running on
Tomcat so I'm asking here too. One of our servlets is opening a URL
connection to hit a
Have you tried *removeAbandonedTimeout* in connection pool settings ? this
will help to get the connectionb closed if your DB connection waiting more
than a specific amount of time.
On Thu, Nov 12, 2009 at 4:02 AM, André Warnier wrote:
> vichi wrote:
>
>> i want to close a connection if i don't
> From: vichi [mailto:vichi...@gmail.com]
> Subject: Re: Connection Timeout
>
> does closing a connection will free http thread?
No; the thread does not return to the pool until the webapp logic is completed.
You'll need to have the webapp monitor itself.
- Chuck
THIS
m using tomcat:-5.5.23 , OS:- Windos XP, Connector:- non-SSL HTTP/1.1
>> Connector
>>
>> please need an urgent help
>> --
>> View this message in context:
>> http://old.nabble.com/Connection-Timeout-tp26315289p26315289.html
>> Sent from the Tomcat - User mailing list ar
non-SSL HTTP/1.1
> Connector
>
> please need an urgent help
> --
> View this message in context:
> http://old.nabble.com/Connection-Timeout-tp26315289p26315289.html
> Sent from the Tomcat - User mailing list archive at Nabble.com.
>
>
>
context:
http://old.nabble.com/Connection-Timeout-tp26315289p26315289.html
Sent from the Tomcat - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands,
vichi wrote:
i want to close a connection if i don't get response back in specific time
(let say in 30 sec) . is there any setting in tomcat for this purpose.
please need an urgent help
It might help if you explained what connection, to what.
And as long as you are doing that, some information
i want to close a connection if i don't get response back in specific time
(let say in 30 sec) . is there any setting in tomcat for this purpose.
please need an urgent help
Thanks in advance.
-Vichi
--
View this message in context:
http://old.nabble.com/connection-Timeout-tp26315070p263
n the query and hibernate.cfg.xml properties, you have given
> so that we can know little more better the error.
> wishes,
>Prasad DTR
>
>
> - Original Message
> From: Kees de Kooter
> To: Tomcat Users List
> Sent: Monday, 29 December, 2008 20:50:05
> Subject: Re: J
Subject: Re: JPA/Hibernate persistence and MySQL connection timeout
Hi Ken,
Take a look at this page:
http://www.hibernate.org/hib_docs/entitymanager/reference/en/html/configuration.html
As you can see the datasource is obtained using JNDI:
java:/DefaultDS
Cheers,
Kees de Kooter
http
Hi Ken,
Take a look at this page:
http://www.hibernate.org/hib_docs/entitymanager/reference/en/html/configuration.html
As you can see the datasource is obtained using JNDI:
java:/DefaultDS
Cheers,
Kees de Kooter
http://www.boplicity.net
On Mon, Dec 29, 2008 at 14:41, Ken Bowen wrote:
> Kees,
Kees,
Can you point me to a discussion of how to do that?
Thanks,
Ken
On Dec 29, 2008, at 3:42 AM, Kees de Kooter wrote:
Why don't u use the existing datasources for JPA (instead of setting
the hibernate.connection properties)?
Kees
On Mon, Dec 29, 2008 at 00:50, Ken Bowen wrote:
Hi All,
Why don't u use the existing datasources for JPA (instead of setting
the hibernate.connection properties)?
Kees
On Mon, Dec 29, 2008 at 00:50, Ken Bowen wrote:
> Hi All,
>
> I'm using: Tomcat 6.0.18; Mysql 5.0.51a; Java 1.5; Hibernate 3.2; (no
> spring)
>
> MyApp utilizes five (5) distinct mys
Hi All,
I'm using: Tomcat 6.0.18; Mysql 5.0.51a; Java 1.5; Hibernate 3.2; (no
spring)
MyApp utilizes five (5) distinct mysql catalogs (databases).
Originally all 5 were accessed using JDBC/JNDI with Resources that all
look like this
(in webapps/MyApp/META-INF):
type="javax.sql.DataSource
Plana, Richard schrieb:
I've upgraded to httpd-2.2.9 and added ping=120 to my BalancerMember
line and the connection still times out and becomes hung. The only thing
I'm getting on the logs is the following:
[Thu Jul 03 14:02:12 2008] [error] (70007)The timeout specified
has expired: ajp
om: Rainer Jung [mailto:[EMAIL PROTECTED]
Sent: Friday, June 27, 2008 5:05 PM
To: Tomcat Users List
Subject: Re: Problem with mod_proxy_ajp Connection Timeout
Plana, Richard schrieb:
> Hi,
>
> Our Apache httpd proxy connects to the two tomcat servers
> (load-balanced) through a netwo
Plana, Richard schrieb:
Hi,
Our Apache httpd proxy connects to the two tomcat servers
(load-balanced) through a network device that performs NAT.
Unfortunately, when the connections go idle (and it happens quite often
since it's a currently low-volume application), the NAT box seems to
lose th
Hi,
Our Apache httpd proxy connects to the two tomcat servers
(load-balanced) through a network device that performs NAT.
Unfortunately, when the connections go idle (and it happens quite often
since it's a currently low-volume application), the NAT box seems to
lose the TCP session. The Apache h
est, ServletResponse response,
FilterChain filterChain) throws IOException, ServletException {
startTiming(request, response);
filterChain.doFilter(request, response);
stopTimingAndLogTime(request, response);
}
The problem is that if the delegated servlet gets a connection timeout, my
(request, response);
stopTimingAndLogTime(request, response);
}
The problem is that if the delegated servlet gets a connection timeout, my
filter doesn't know about it, and prints a value like 2 ms in the logs
(whatever the HTTP Connector's connectionTimeout attribute is set to).
Is
Hi
I am seeing this error in my stderror.log, I am running IIS 6.0, tomcat
4.1 and jk 1.2.23
Jul 8, 2007 7:38:37 PM org.apache.jk.common.ChannelSocket
processConnection
INFO: connection timeout reached
Does anyone know what this means, and what the cure is?
Thanks,
Rasmus
tion_tcp_send_message::jk_ajp_common.c (896): 12 34 00 E6
02 02 00 08 48 54
54 50 2F 31 2E 31 - .4..HTTP/1.1
With regards,
Babu Satasiya
--
View this message in context:
http://www.nabble.com/increase-the-backend-idle-connection-timeout-or-the-connection_pool_minsize-tf352236
omcat-publicweb-01.socket_timeout=30
> worker.tomcat-publicweb-01.connect_timeout=2000
> worker.tomcat-publicweb-01.prepost_timeout=5000
> worker.tomcat-publicweb-01.reply_timeout=300000
>
> mod_jk errors:
> ajp_send_request::jk_ajp_common.c (1201): (tomcat-publicweb-01) error
>
p_send_request::jk_ajp_common.c (1241): (app103) all endpoints are
disconnected
[Tue Mar 20 08:27:46 2007][24590:14016] [info]
ajp_send_request::jk_ajp_common.c (1244): (app103) increase the backend idle
connection timeout or the connection_pool_minsize
[Tue Mar 20 08:27:46 2007][24590:14016] [info
endpoints
are disconnected
ajp_send_request::jk_ajp_common.c (1230): (tomcat-publicweb-01) increase the
backend idle connection timeout or the connection_pool_minsize
ajp_service::jk_ajp_common.c (1916): (tomcat-publicweb-01) sending request to
tomcat failed, recoverable operation att
erence in error rate.
> Maybe I need to modify them with bigger deltas to see a difference?
> Is there a way to tell which parameter would have the most impact?
If those are for a DataSource, they have no relation to your mod_jk
messages.
>> This looks like a DataSource definition (
need to modify them with bigger deltas to see a difference?
Is there a way to tell which parameter would have the most impact?
> This looks like a DataSource definition (Tomcat to database). The "idle
> connection timeout" in the case of tomcat is the value of
> conncetiontimeout
Fletcher Cocquyt wrote:
Hi,
This is a followup to my Feb14 post: Re: socket is not connected any more
(errno=11)
I've just upgraded from 1.2.19 to 1.2.20 and the new log messages are:
increase the backend idle connection timeout or the connection_pool_minsize
I could not find much on
up a
little more.
-Original Message-
From: news [mailto:[EMAIL PROTECTED] Behalf Of Fletcher Cocquyt
Sent: Monday, February 26, 2007 12:32 PM
To: users@tomcat.apache.org
Subject: increase the backend idle connection timeout or the
connection_pool_minsize
Hi,
This is a followup to my Feb14 pos
Hi,
This is a followup to my Feb14 post: Re: socket is not connected any more
(errno=11)
I've just upgraded from 1.2.19 to 1.2.20 and the new log messages are:
increase the backend idle connection timeout or the connection_pool_minsize
I could not find much on which parameters th
Hello
In the server.xml
There is no connection timeout value set
What is the default value ?
Should the value that is set here be equal to the value set in
workers.properties file ?
socket_timeout
And what is the value set here..also in server.xml
(connectionTimeout
67 matches
Mail list logo
