Hi Greg
Thank you very much for your update. I put latest version of jetty at my
production server, and so far (running about 4h) I don't see any unclosed
FIN state connections.
I will update you after the weekend when we will have more then 6-8M visits.
Thank you again for good work. Other mem
] Jetty 8.0.0 - 8.0.4 not closing connections using
SelectChannelConnector
Sorry for my last e-mail. I meant to click 'Forward' and clicked
'Reply' instead. :-). My apologies.
2011/11/28 Bartek K. :
> ROTFL. Gosc odpisal na liste userow Jetty'iego w cyrylicy. Wszyscy
>
з ngnix.
>>
>> Вдалого дня,
>> Володя
>>
>> -Original Message-
>> From: jetty-users-boun...@eclipse.org
>> [mailto:jetty-users-boun...@eclipse.org] On Behalf Of Greg Wilkins
>> Sent: Monday, November 28, 2011 2:59 AM
>> To: JETTY user mailing
> Sent: Monday, November 28, 2011 2:59 AM
> To: JETTY user mailing list
> Subject: Re: [jetty-users] Jetty 8.0.0 - 8.0.4 not closing connections using
> SelectChannelConnector
>
> I believe I've fixed this now in jetty-7.6 (RC0 will be out in days
> and fix will also be me
Message-
From: jetty-users-boun...@eclipse.org [mailto:jetty-users-boun...@eclipse.org]
On Behalf Of Greg Wilkins
Sent: Monday, November 28, 2011 2:59 AM
To: JETTY user mailing list
Subject: Re: [jetty-users] Jetty 8.0.0 - 8.0.4 not closing connections using
SelectChannelConnector
I believe
I believe I've fixed this now in jetty-7.6 (RC0 will be out in days
and fix will also be merged to 8).
Jetty now resets the idle timeout when it expires (and does a
shutdownOutput), and if it expires again, the connection is closed
without waiting for a FIN.
I have a test harness that check this h
Since this has been reproduced against latest branch, I've opened an
issue to track this bug:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=364921
I'm wondering if the issue is that Jetty has sent a FIN to close the
connection but never receives a FIN in response. The idle timeout
should catc
Hi Volodia,
Thank you for your update.
In regard for restarting, is the worst solution even, but because we are
quite busy in the moment, that was my first quick solution. As I mention I
have several heavy web sites (mips.tv - php/apache/java/simpleframework,
liveflash.tv -java/jetty...), and fo
Hello pecko,
Restarting the java is not the best solution. Did you try other web
container? We used jetty since the activemq servlet does not work reliably
under Tomcat with NIO connector. All other our projects are hosted under
Tomcat.
1) We did not try jetty 6.5 and I am not sure if there is
Se
Hi Jan and Volodia,
I was very interested in this post, because I have the same on one of my
production server online (embedded jetty ver 8).
Jan, thanks for your update, but as Volodia already explain, there are still
dead sockets with FIN_WAIT2 state with new version.
Volodia, currently we are
Posting the update.
We had dead FIN_WAIT_2 connections on jetty 7.5.4 and 8.1 snapshot.
Looks like we resolved the problem by installing nginx and configuring it to
forward requests to jetty.
FYI: We are streaming ActiveMQ messages through HTTP using long pooling.
The machine is virtual VMWare s
Volodia and Mathijs,
We've been working a lot on the half-close handling
for jetty, and these improvements may solve your issues.
I've pushed a snapshot of jetty-8.1.0 to the snapshot
repo here:
http://oss.sonatype.org/content/groups/jetty/org/eclipse/jetty/jetty-distribution/
Please download a
Hi Mathijs,
Thank you for the feedback.
We are going to try:
- downgrading to jetty 7.x
- if jetty 7.x has the same problem kill the connections in cron task
Will update with results.
Volodia
--
View this message in context:
http://jetty.1047016.n5.nabble.com/jetty-users-Jetty-8-0-0-8-0-4
Hi Volodia & Jan,
I have not really found a good solution. Even with "Connection: Close"
set on every request, connections are still built up at a very slow
rate, and I need to restart the server every few days.
It looks to me like the server is really dependent on the client
closing the connectio
Jan & Mathijs,
I am facing the same problem running jetty 8.02 or 8.04 with
SelectChannelConnector on CentOS Linux release 6.0.
Any ideas how to push the jetty to release connections?
Volodia
--
View this message in context:
http://jetty.1047016.n5.nabble.com/jetty-users-Jetty-8-0-0-8-0-4-not-
Hi Jan,
This is on Ubuntu server 11.04 (Linux 2.6.35.4). I have explicitly
checked (and try to set lower) parameters that should influence this,
such as
/proc/sys/net/ipv4/tcp_fin_timeout, but this didn't help. As soon as I
stop the jetty server, the connections stay around for about 15
seconds,
a
Mathijs,
What OS is this running on? Seems like it might be one that does not
have a timeout for FIN_WAIT_2 in the tcp stack, so the sockets might be
building up and up until you reach the limit.
Is this problem seen with persistent connections? If so, have you
tried closing the connection on eac
Hi,
I'm running an embedded jetty server which has fairly high numbers
ofconnections from mobile phones, which oftensuddenly lose connections
without properly shutting them down.I noticed that on my server, over
time it's building up lots ofconnections that are in FIN_WAIT2 state.
This was the case
18 matches
Mail list logo
