Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Date: Thu, 31 Jan 2013 14:51:13 +0000 (UTC)
From: "Thomas Mueller (JIRA)" <jira@apache.org>
To: dev@jackrabbit.apache.org
Message-ID: <JIRA.12630128.1359638628069.222580.1359643873010@arcas>
In-Reply-To: <JIRA.12630128.1359638628069@arcas>
References: <JIRA.12630128.1359638628069@arcas>
Subject: [jira] [Commented] (JCR-3509) Workspace maxIdleTime parameter not
 working
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/JCR-3509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13567687#comment-13567687 ] 

Thomas Mueller commented on JCR-3509:
-------------------------------------

I wonder, do you want to change the maxIdleTime in the workspace.xml after the repository and workspace was created? It seems the workspace.xml file is stored in the database in your case, so I guess you would have to change it in the database as well. But I'm not completely sure.
                
> Workspace maxIdleTime parameter not working
> -------------------------------------------
>
>                 Key: JCR-3509
>                 URL: https://issues.apache.org/jira/browse/JCR-3509
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>          Components: config
>    Affects Versions: 2.4.3
>         Environment: JSF, SPRING
>            Reporter: Sarfaraaz ASLAM
>         Attachments: derby.jackrabbit.repository.xml, JcrConfigurer.java
>
>
> would like to set the maximum number of seconds that a workspace can remain unused before the workspace is automatically closed through maxIdleTime parameter but this seems not to work. 

--
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