tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christopher Schultz <ch...@christopherschultz.net>
Subject Re: Unable to sendViaPost to url...... .... java.net.SocketTimeoutException: Read timed out
Date Wed, 18 Jan 2012 16:02:14 GMT
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Bert,

On 1/16/12 11:15 AM, Bert Verhees wrote:
> I am not sure if it is an Axis2 problem or a Tomcat-problem.
> 
> I have an client-application for test-purposes which runs inside
> the Eclipse-IDE. The problem only occurs when running Axis2 inside
> Tomcat6, when running in Axis2 as stand-alone server, it runs
> better.

SO, running Axis2 using it's built-in HTTP server (I didn't know it
had one) has acceptable performance, but running Axis2 within Tomcat
does not have acceptable performance?

> I have some console-output to see how long it takes.

How about real profiling data?

> When running in Axis2 standalone, it stays about 4 seconds until
> 8000 persons stored (which is the complete group to store) This is
> slow, I must investigate the library directly without webservice if
> that is a problem of my coding. So we forget that for the moment.

So, Axis2 performance is also unaccaptable.

> The problem which bothers me is when I am using Tomcat.
> 
> The problem start to occur after posting 1200 patients, it takes 8 
> seconds.

So your observation is that, when running within Tomcat, your code
appears to perform more slowly. Is that consistent? I wonder if your
code / database slows down considerably as data is added and you are
running your in-Tomcat tests after the out-of-Tomcat tests.

> I try a lot of things to solve the problem.

Like what?

> I put a Thread.sleep(1000); in my client-code between to postings,
> I thought, maybe the webservice needs some rest to do garbage-clean
> up.

Obviously, pausing for a second per record will limit performance. GC
will run when it has to -- you don't have to "give it time" to do its job.

> Because it looks very much like a memory blowing up. But it didn't
> help.

What makes you think that memory is "blowing up"?

It probably didn't help because you have mis-identified the problem.

- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEUEARECAAYFAk8W7QUACgkQ9CaO5/Lv0PDBEQCfTaLMZE7TPBdwAVaFe56MRBDC
OccAmNgqaj57ji+z11Z/hVourbydlS0=
=H9YI
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


Mime
View raw message