You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@geode.apache.org by "Jared Stewart (JIRA)" <ji...@apache.org> on 2017/09/01 18:45:00 UTC

[jira] [Resolved] (GEODE-3547) Simplify behavior for non-writable deploy directory

     [ https://issues.apache.org/jira/browse/GEODE-3547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jared Stewart resolved GEODE-3547.
----------------------------------
    Resolution: Fixed

> Simplify behavior for non-writable deploy directory
> ---------------------------------------------------
>
>                 Key: GEODE-3547
>                 URL: https://issues.apache.org/jira/browse/GEODE-3547
>             Project: Geode
>          Issue Type: Improvement
>          Components: management
>            Reporter: Jared Stewart
>            Assignee: Jared Stewart
>             Fix For: 1.3.0
>
>
> The JarDeployer that writes user-deployed jar files to disk has some needlessly complex retry logic for when the specified deploy directory is not writable, that involves waiting up to 200 seconds for permissions to write to that directory to appear.  It would be much simpler to fail immediately when we don't have security permissions to write to the deploy directory.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)