You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@isis.apache.org by "Dan Haywood (JIRA)" <ji...@apache.org> on 2013/05/28 16:40:23 UTC
[jira] [Updated] (ISIS-414) When a stack overflow kills thread,
then HSQLDB in-memory session locks up on subsequent request.
[ https://issues.apache.org/jira/browse/ISIS-414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dan Haywood updated ISIS-414:
-----------------------------
Component/s: Viewer: Wicket
Objectstore: JDO
> When a stack overflow kills thread, then HSQLDB in-memory session locks up on subsequent request.
> -------------------------------------------------------------------------------------------------
>
> Key: ISIS-414
> URL: https://issues.apache.org/jira/browse/ISIS-414
> Project: Isis
> Issue Type: Bug
> Components: Objectstore: JDO, Viewer: Wicket
> Reporter: Dan Haywood
> Assignee: Dan Haywood
> Priority: Minor
>
> The stack overflowing on a previous request means that the session is not closed properly. This missing housekeeping breaks any subsequent request that uses the same connection.
> Not sure if this is a problem with HSQLDB (2.2.9), or whether Isis should deal with the issue. As things stand, a localized problem (stack overflow) becomes a global issue - need to recycle web server.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira