[ https://issues.jboss.org/browse/JBIDE-20377?page=com.atlassian.jira.plugi... ] Jeff Cantrill commented on JBIDE-20377: --------------------------------------- [~adietish] I feared this would come up. This is caused by the limitation in the current design where the port forward process is associated with the capability. If you refresh the pod, then you get a new instance which means you no longer have reference to the process. I presume the process is still running too but now you have no way stop it at all, even if you exit Eclipse. Possible solutions: * Modify the refresh logic such that you update the object after reload. This is similar to what happened in v2 where significant properties were copied from one object to another * Add a singleton of some sort for managing the port forward process instances. This would alleviate needing to update objects. Opinions? -- This message was sent by Atlassian JIRA (v6.3.15#6346)