[ https://issues.apache.org/jira/browse/BROOKLYN-552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16247710#comment-16247710 ]
Duncan Grant commented on BROOKLYN-552: --------------------------------------- I'm going to close this issue as I've been unable to reproduce the original problem. However I'm replacing it with these issues which are all reproducible. https://issues.apache.org/jira/browse/BROOKLYN-557 https://issues.apache.org/jira/browse/BROOKLYN-556 https://issues.apache.org/jira/browse/BROOKLYN-555 > 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)