[
https://issues.apache.org/jira/browse/FELIX-2687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13122559#comment-13122559
]
Rob Walker edited comment on FELIX-2687 at 10/7/11 6:12 AM:
------------------------------------------------------------
Looks like others are having this issue so maybe we should make the patch
official if appropriate, or add a full config property.
Email below from [email protected]
====
I am having a problem in my application that too many sessions are remaining
open instead of closing after turning inactive when using the Jetty
HttpService. This eventually leads to the application grounding to a halt after
~2.8 million sessions are made. I have manually set the maxInactiveInterval on
one of the HttpServletRequests REST endpoints to a short period and have
verified that if I create 10,000 requests the sessions are disposed of
properly. Fixing it this manual way seems like a bad solution considering there
is at least 200 places where requests are handled and this number will increase
over time creating a risk of forgetting to set the default timeout value.
Based upon this former email on the mailing list
(http://www.mail-archive.com/[email protected]/msg19839.html) and the lack
of the configuration property in the documentation
(http://felix.apache.org/site/apache-felix-http-service.html) I assume there is
no way to set this value in a configuration file similar to web.xml? Is there a
way that I can from a HttpServletRequest get access to the SessionManager or
some other object that will enable me to set a default timeout value for all
sessions? I also don't see a way to do this by grabbing the HttpService during
a bundle activation through the context.
Thanks!
Adam McKenzie
ITS, University of Saskatchewan
was (Author: walkerr):
Looks like others are having this issue so maybe we should make the patch
official if appropriate, or add a full config property.
Email below from the users@[email protected]
====
I am having a problem in my application that too many sessions are remaining
open instead of closing after turning inactive when using the Jetty
HttpService. This eventually leads to the application grounding to a halt after
~2.8 million sessions are made. I have manually set the maxInactiveInterval on
one of the HttpServletRequests REST endpoints to a short period and have
verified that if I create 10,000 requests the sessions are disposed of
properly. Fixing it this manual way seems like a bad solution considering there
is at least 200 places where requests are handled and this number will increase
over time creating a risk of forgetting to set the default timeout value.
Based upon this former email on the mailing list
(http://www.mail-archive.com/[email protected]/msg19839.html) and the lack
of the configuration property in the documentation
(http://felix.apache.org/site/apache-felix-http-service.html) I assume there is
no way to set this value in a configuration file similar to web.xml? Is there a
way that I can from a HttpServletRequest get access to the SessionManager or
some other object that will enable me to set a default timeout value for all
sessions? I also don't see a way to do this by grabbing the HttpService during
a bundle activation through the context.
Thanks!
Adam McKenzie
ITS, University of Saskatchewan
> Make HTTP session timeout configurable
> --------------------------------------
>
> Key: FELIX-2687
> URL: https://issues.apache.org/jira/browse/FELIX-2687
> Project: Felix
> Issue Type: Improvement
> Components: HTTP Service
> Affects Versions: http-2.0.4
> Environment: apache-karaf-2.1.0 on openjdk-6b18/Linux
> Reporter: Wolfgang Glas
> Attachments: configurable-http-timeout.patch
>
>
> Hi all,
> ThX very much for the really smooth http service packaging ;-)
> According to the docs and to my code review there is no possibility to
> configure the HTTP session timeout in felix' HTTP service bundle.
> It would be very much appreciated, if such a possiblity might be introduced
> in a future version of HTTP service.
> TIA and best regards,
> Wolfgang Glas
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
