You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@marmotta.apache.org by "Sebastian Schaffert (JIRA)" <ji...@apache.org> on 2014/01/07 14:47:52 UTC

[jira] [Commented] (MARMOTTA-257) system-config.properties file is reset on not clean shutdowns

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

Sebastian Schaffert commented on MARMOTTA-257:
----------------------------------------------

Suggestion for a solution: use PropertiesConfiguration.save() to save to a temporary file residing besides the configuration file and then perform an atomic move (using Java 7 NIO) to replace the existing file.

> system-config.properties file is reset on not clean shutdowns
> -------------------------------------------------------------
>
>                 Key: MARMOTTA-257
>                 URL: https://issues.apache.org/jira/browse/MARMOTTA-257
>             Project: Marmotta
>          Issue Type: Bug
>          Components: Platform
>    Affects Versions: 3.0-incubating, 3.1-incubating
>            Reporter: Sergio Fernández
>            Assignee: Sebastian Schaffert
>            Priority: Critical
>             Fix For: 3.2
>
>
> I have detected (actually suffer) issues when, for whatever reason, the application container is shutdown while marmotta is busy (importing  triples, for instance). The consequence is system-config.properties file is overwritten by the default one in the next startup.
> I'd need to find a way to check what's the actual content of the file in the small temporal window since the server stops and the context is reinitialized.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)