You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomee.apache.org by using namespace <fo...@bk.ru> on 2015/07/08 18:58:34 UTC
Connection timeout
I am testing a web service which I have deployed on TomEE plus 1.7.1 Inside
tomee.xml there is following stateless container settings for deployment id:
<Container id="SoaprequestImpl" type="STATELESS">
accessTimeout = -1
callbackThreads = 5
closeTimeout = 5 minutes
garbageCollection = true
idleTimeout = 0 minutes
maxAge = 0 hours
maxAgeOffset = -1
maxSize = 1000
minSize = 100
replaceAged = true
replaceFlushed = false
strictPooling = false
sweepInterval = 5 minutes
</Container>
I have set accessTimeout = -1 so that client could wait endlessly to receive
its bean. However now when I test it with 2000 requests simultaneously my
client sometimes throws timeout exception:
java.net.ConnectException: Connection timed out: connect
That is the problem I am trying to fix.
--
View this message in context: http://tomee-openejb.979440.n4.nabble.com/Connection-timeout-tp4675468.html
Sent from the TomEE Users mailing list archive at Nabble.com.
Re: Connection timeout
Posted by Romain Manni-Bucau <rm...@gmail.com>.
Hi
it is the http timeout then, not the stateless one.
Typically in an app you have 3 layers:
http -> stateless -> database
all have pools to be correctly tuned
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
<http://www.tomitribe.com>
2015-07-08 9:58 GMT-07:00 using namespace <fo...@bk.ru>:
> I am testing a web service which I have deployed on TomEE plus 1.7.1 Inside
> tomee.xml there is following stateless container settings for deployment
> id:
>
> <Container id="SoaprequestImpl" type="STATELESS">
> accessTimeout = -1
> callbackThreads = 5
> closeTimeout = 5 minutes
> garbageCollection = true
> idleTimeout = 0 minutes
> maxAge = 0 hours
> maxAgeOffset = -1
> maxSize = 1000
> minSize = 100
> replaceAged = true
> replaceFlushed = false
> strictPooling = false
> sweepInterval = 5 minutes
> </Container>
> I have set accessTimeout = -1 so that client could wait endlessly to
> receive
> its bean. However now when I test it with 2000 requests simultaneously my
> client sometimes throws timeout exception:
>
> java.net.ConnectException: Connection timed out: connect
> That is the problem I am trying to fix.
>
>
>
> --
> View this message in context:
> http://tomee-openejb.979440.n4.nabble.com/Connection-timeout-tp4675468.html
> Sent from the TomEE Users mailing list archive at Nabble.com.
>