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

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

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

ASF subversion and git services commented on GEODE-3547:
--------------------------------------------------------

Commit 836451a5acd939d54b1d45ad8701fac7ec54ac53 in geode's branch refs/heads/develop from [~jstewart]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=836451a ]

GEODE-3547: Simplify behavior for non-writable deploy directory

 - Also fixes the flaky JarDeployerIntegrationTest


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