[undertow-dev] Lingering session resources in keepalive

[Tomaž Cerar]

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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/undertow-dev/attachments/20150618/f1f1c73f/attachment.html