required by the
> spec). It it doesn't, that will trigger another error and Tomcat will
> call on onComplete()
>
> This should be fixed in the next set of releases.
>
> Mark
>
>
> >
> > Mark
> >
> >
> > On 18/10/2016 09:55, Thomas Bonifa
orrect
-> 0xe005), seq 1:128, ack 122, win 342, options [nop,nop,TS val 273198492
ecr 273198377], length 127
> E...rC@.@...*..i..ZV...
> .H...H.)HTTP/1.1 200 OK
> Server: Apache-Coyote/1.1
> Transfer-Encoding: chunked
> Date: Tue, 18 Oct 2016 07:47:44 GMT
>
&g
[R], cksum 0xd571 (correct),
seq 3052296895, win 0, length 0
E..(..@.@.o;..Z.Pq..
This shows the python "client", sends a FIN to tomcat, tomcat PUSH anyway
and then the "client" RESETs.
Thomas
2016-10-10 19:10 GMT+02:00 Mark Thomas :
> On 10/10/2016
the end, the situation seems pretty similar. The container appears to
recycle the request without completing the async context and I can't
complete on application side as the request I have is now recycled.
Thanks,
Thomas
2016-10-03 17:06 GMT+02:00 Thomas Boniface :
> Hi,
>
> Tha
an input on
what are the consequences of the behaviour I described ?
Thanks,
Thomas
2016-09-29 9:41 GMT+02:00 Violeta Georgieva :
> Hi,
>
> 2016-09-29 10:14 GMT+03:00 Thomas Boniface :
> >
> > The tomcat version is 7.0.64.
>
> I would recommend you to verify the behaviou
The tomcat version is 7.0.64.
Thomas
2016-09-28 22:43 GMT+02:00 Christopher Schultz :
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Thomas,
>
> On 9/28/16 11:55 AM, Thomas Boniface wrote:
> > Hi,
> >
> > When a client calls an asynchronous ser
Hi,
When a client calls an asynchronous servlet and closes the connection a
java.io.IOException: Broken pipe is catched by Tomcat level when the webapp
tries to write to the socket.
This exception is not transmited to the webapp level but it seems the
request has been recycled (all content is rei
Hi,
I can observer RecycleRequiredException (example below) in the catalina.out
of my application. This application relies on async servlets with some
async libraries, this exception can lead to strange behavior I guess like
mixing user cookies.
Is there some specific logs I could activate to iso
2016-02-11 12:31 GMT+01:00 André Warnier (tomcat) :
> On 11.02.2016 12:07, Thomas Boniface wrote:
>
>> Hi,
>>
>> I'm using async servlet with a timeout configured to 300ms
>>
>
> naive question : is that not awfully short, if this relates to some
>
2016-02-11 12:16 GMT+01:00 Mark Thomas :
> On 11/02/2016 11:07, Thomas Boniface wrote:
> > Hi,
> >
> > I'm using async servlet with a timeout configured to 300ms but I can
> > observe in live environnement some big differences with the actual
> applied
>
Hi,
I'm using async servlet with a timeout configured to 300ms but I can
observe in live environnement some big differences with the actual applied
timeout 700ms or more for instance.
I was wondering how are triggered onTimeout events to AsyncListeners, is
there a limited number of thread handli
Thanks for your reply, we'll give a try to your suggestions.
2015-04-29 23:15 GMT+02:00 Christopher Schultz :
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Thomas,
>
> On 4/25/15 4:25 AM, Thomas Boniface wrote:
> > When talking about the strategy for ou
de we have a connector like follows:
Thomas
2015-04-23 14:50 GMT+02:00 Thomas Boniface :
> I just want to keep you updated and tell you that all your replies are
> very helpful. It give me clues on what to look for and sometimes confirm
> some of our suspicion.
>
> I have tra
I just want to keep you updated and tell you that all your replies are very
helpful. It give me clues on what to look for and sometimes confirm some of
our suspicion.
I have transmitted some of the element collected in this thread to our
platform team but we were not able to setup new test so far
What concerns me the most is the CLOSE_WAIT on tomcat side because when an
fd peak appears the web application appears to be stuck. It feels like all
its connections are consumed and none can be established from nginx
anymore. Shouldn't the CLOSE_WAIT connection be recycled to received new
connecti
n the last release of tomcat but only
occassionally in the previous one we used.
Thomas
2015-04-21 16:56 GMT+02:00 André Warnier :
> Thomas Boniface wrote:
>
>> The file descriptor peak show up in our monitoring application. We have
>> some charts showing the number of file descript
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Thomas,
>
> On 4/20/15 8:11 AM, Thomas Boniface wrote:
> > I have tried to find help regarding an issue we experience with
> > our platform leading to random file descriptor peaks. This happens
> > more of
etsat
Thomas
2015-04-20 17:13 GMT+02:00 André Warnier :
> Thomas Boniface wrote:
>
>> I did some captures during a peak this morning, I have some lsof and
>> netstat data.
>>
>> It seems to me that most file descriptors used by tomcat are some http
>> conn
low). Also,
it feels unexpected that this version of tomcat makes the application
getting slower more often than a server with the other version of tomcat.
Thomas
2015-04-20 16:32 GMT+02:00 Rainer Jung :
> Am 20.04.2015 um 15:41 schrieb Rainer Jung:
>
>> Am 20.04.2015 um 14:11 schrieb Thoma
ng :
> Am 20.04.2015 um 14:11 schrieb Thomas Boniface:
>
>> Hi,
>>
>> I have tried to find help regarding an issue we experience with our
>> platform leading to random file descriptor peaks. This happens more often
>> on heavy load but can also happen on low tr
Hi,
I have tried to find help regarding an issue we experience with our
platform leading to random file descriptor peaks. This happens more often
on heavy load but can also happen on low traffic periods.
Our application is using servlet 3.0 async features and an async connector.
We noticed that a
could
represent for the test we made.
Thanks,
Thomas
2015-03-27 14:08 GMT+01:00 Christopher Schultz :
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Thomas,
>
> On 3/26/15 12:16 PM, Thomas Boniface wrote:
> > Following the update of the tomcat 7 version
Following the update of the tomcat 7 version from 7.0.28-4 to 7.0.56-1
hoping to improve our application performances we experienced a quick
freeze of the application under a standard load (that was handle by
previous tomcat version without particular issue).
Our application is behind a nginx serv
Hi,
We have a setup where tomcat is behind nginx and in some case the maximum
number of connection is reached between these two. These connections are
in close wait state and a tomcat thread dump shows no blocking on its side.
I tried to check the connections status using jmxproxy. I was able se
24 matches
Mail list logo