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.
>
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
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.
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 assume
Pid pid at 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
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 guess - I've got no idea how many
Caldarale, Charles R Chuck.Caldarale at 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
On 10/05/2012 21:40, Jon Drukman wrote:
Caldarale, Charles R Chuck.Caldarale at 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?
Pid pid at 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.
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 threads, heap memory
Caldarale, Charles R Chuck.Caldarale at 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
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 j...@cluttered.com wrote:
Caldarale, Charles R Chuck.Caldarale at unisys.com
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
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 these socket
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 we see
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 site
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
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
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 archive at Nabble.com
commands, e-mail: users-h...@tomcat.apache.org
--
View this message in context:
http://old.nabble.com/Trouble-with-connection-timeout-settings-tp30826944p30827517.html
Sent from the Tomcat - User mailing list archive at Nabble.com
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? - Dave
-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
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
ch...@christopherschultz.net wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris,
On 2/19/2010 11:08 AM, Chris Mannion wrote:
Thank,
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=value in milliseconds
-
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) Chris is using a library
The OP already posted the code of interest
-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
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 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
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 peter.crowt...@melandra.com wrote:
A swift Google for:
java url openStream timeout
reveals:
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()
-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()
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 appropriate timeout value
-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) Chris is using a library
The OP
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 a...@ice-sa.com wrote:
vichi wrote:
i want to close a connection
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-tp26315070p26315070
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
://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, e-mail: users-h
--
View this message in 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
back..is there any setting or facility provided by tomcat if not how
can i do it.
i am 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
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 COMMUNICATION MAY CONTAIN
Sent: Monday, 29 December, 2008 20:50:05
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:
jta-data-sourcejava
...@gmail.com
To: Tomcat Users List users@tomcat.apache.org
Sent: Monday, 29 December, 2008 20:50:05
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
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 kbo...@als.com 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)
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 kbo...@als.com
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:
jta-data-sourcejava:/DefaultDS/jta-data-source
Cheers,
Kees de Kooter
http://www.boplicity.net
On Mon, Dec 29, 2008 at
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):
Resource
[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 network device that performs NAT
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:
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
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
(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 there any
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
filter doesn't know
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
): 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-tf3522364.html#a9826278
Sent from the Tomcat - User
::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 attempt=1
::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] ajp_service
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
You're also only allowing 1 sec to connect it appears. Might ratchet it 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
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 which
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 in the Connector element of server.xml. You need
?
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 (Tomcat to database). The idle
connection timeout in the case of tomcat is the value of
conncetiontimeout
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 attempt=1
-
To start a new topic, e-mail: users
Hello
In the server.xml
!-- A AJP 1.3 Connector on port 8009 --
Connector port=8009 address=${jboss.bind.address} maxThreads=250
emptySessionPath=true enableLookups=false redirectPort=8443
protocol=AJP/1.3/
There is no connection timeout value set
What is the default
66 matches
Mail list logo
