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

Posted to dev@usergrid.apache.org by "Yigit Sapli (JIRA)" <ji...@apache.org> on 2014/05/21 19:14:38 UTC

[jira] [Reopened] (USERGRID-149) [CHOP] Cannot read stack.json of a redeployed runner.jar

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

Yigit Sapli reopened USERGRID-149:
----------------------------------


It turns out after the fix, although it doesn't give any exceptions, it uses old values instead of the changed stack.json in redeployed runner.jar.

> [CHOP] Cannot read stack.json of a redeployed runner.jar
> --------------------------------------------------------
>
>                 Key: USERGRID-149
>                 URL: https://issues.apache.org/jira/browse/USERGRID-149
>             Project: Usergrid
>          Issue Type: Bug
>          Components: Chop
>            Reporter: Yigit Sapli
>            Assignee: Yigit Sapli
>
> If a runner.jar is deployed to coordinator with existing commitId, username and maven module, its stack.json cannot be read while setting up its stack.
> However, if coordinator is restarted after the runner.jar is redeployed, it works fine. This might be related to URLClassLoader and its usage in CoordinatorUtils.



--
This message was sent by Atlassian JIRA
(v6.2#6252)