[undertow-dev] Lingering session resources in keepalive

[Stuart Douglas]

I have cut 1.1.5.Final with this fix, although you should look at upgrading to 1.2.8.Final if possible. 

Stuart

----- Original Message -----
> From: "Stuart Douglas" <sdouglas at redhat.com>
> To: "Eric Peters" <epeters at epicor.com>
> Cc: undertow-dev at lists.jboss.org
> Sent: Friday, 19 June, 2015 10:00:18 AM
> Subject: Re: [undertow-dev] Lingering session resources in keepalive
> 
> This was fixed in Undertow 1.2:
> https://github.com/undertow-io/undertow/commit/ca788df7f550513324f11ded155e71f5f3219aa0
> 
> Stuart
> 
> ----- Original Message -----
> > From: "Eric Peters" <epeters at epicor.com>
> > To: "Tomaž Cerar" <tomaz.cerar at gmail.com>
> > Cc: undertow-dev at lists.jboss.org
> > Sent: Friday, 19 June, 2015 12:10:12 AM
> > Subject: Re: [undertow-dev] Lingering session resources in keepalive
> > 
> > 
> > 
> > I honestly was expecting the answer to that to be Undertow 1.1.4, but in
> > double-checking I found it’s on Undertow 1.1.0. Time I skim the patches
> > from
> > 1.1.0 on up to see if anything could have addressed this.
> > 
> > 
> > 
> > Honestly, I’ve got two angles here:
> > 
> > 1) I need a reliable solution which has a minimum of caveats. Updating in
> > 1.1.x or configuration changes preferred, but if patches are needed, so be
> > it
> > 
> > 2) Did we stumble on a shortcoming in Undertow? Honestly, I think this can
> > be
> > argued both ways. If this has merit as a flaw, I’d like to get the find to
> > the right people.
> > 
> > 
> > 
> > //EricP
> > 
> > 
> > 
> > From: Tomaž Cerar [mailto:tomaz.cerar at gmail.com]
> > Sent: Thursday, June 18, 2015 2:47 PM
> > To: Eric Peters
> > Cc: undertow-dev at lists.jboss.org
> > Subject: Re: [undertow-dev] Lingering session resources in keepalive
> > 
> > 
> > 
> > 
> > What version of undertow are you using?
> > 
> > 
> > 
> > 
> > 
> > On Thu, Jun 18, 2015 at 4:57 PM, Eric Peters < epeters at epicor.com > wrote:
> > 
> > 
> > We’re still trying to confirm things on our end, so it’s still possible a
> > wrong assumption’s been made somewhere, but it looks like session resources
> > are lingering with the http connection after the session has expired.
> > 
> > 
> > 
> > From one of the heap dumps, following session data that expired the
> > previous
> > day back to a GC root:
> > http://imgur.com/Ov8xFy1
> > 
> > That’s from a dump where the read-timeout was disabled.
> > 
> > 
> > 
> > We can set the read-timeout, but I don’t know if the behavior of keep-alive
> > will limit the impact of the read timeout. After the reply has been created
> > and sent, do the particulars of the request or reply need to be kept beyond
> > the expiry of the session they were for?
> > 
> > 
> > 
> > Is there a way to disable keep-alive? In this particular instance it’s more
> > important that the resources be freed up timely than it is that the server
> > use keep-alive to give a boost on performance..
> > 
> > 
> > 
> > //EricP
> > 
> > 
> > 
> > 
> > This message has been scanned for malware by Websense. www.websense.com
> > 
> > 
> > 
> > _______________________________________________
> > undertow-dev mailing list
> > undertow-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/undertow-dev
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > Click here to report this email as spam.
> > 
> > _______________________________________________
> > undertow-dev mailing list
> > undertow-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/undertow-dev
> 
> _______________________________________________
> undertow-dev mailing list
> undertow-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/undertow-dev