You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@brooklyn.apache.org by "Duncan Grant (JIRA)" <ji...@apache.org> on 2017/11/09 11:24:00 UTC

[jira] [Created] (BROOKLYN-552) Tomcat entity stop / start fails as entity id changes which update run_dir but tc obviously not moved

Duncan Grant created BROOKLYN-552:
-------------------------------------

             Summary: Tomcat entity stop / start fails as entity id changes which update run_dir but tc obviously not moved
                 Key: BROOKLYN-552
                 URL: https://issues.apache.org/jira/browse/BROOKLYN-552
             Project: Brooklyn
          Issue Type: Bug
            Reporter: Duncan Grant
            Priority: Critical


Reproduce:
Deploy tomcat with:
name: Test Tomcat
location:
centos7_gce_europe
services:
type: org.apache.brooklyn.entity.webapp.tomcat.TomcatServer
after entity is running do 
br app <appid> ent <entityid> stop
br app <appid> ent <entityid> start
The isrunning check will never pass as the run_dir sensor will have upated but obviously the directory is not moved on the vm
This is presumably a problem with all blueprints that use the standard pid check for running???




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