[jbosstools-issues] [JBoss JIRA] (JBIDE-22259) Debugging of OS 3 application creates a new replication controller

[Fred Bricon (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-22259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13197906#comment-13197906 ] 

Fred Bricon commented on JBIDE-22259:
-------------------------------------

We're indeed modifying the current IDeploymentConfig https://github.com/jbosstools/jbosstools-openshift/blob/master/plugins/org.jboss.tools.openshift.core/src/org/jboss/tools/openshift/internal/core/server/debug/OpenShiftDebugUtils.java#L119.

[~jcantrill] would it make sense to change the deployment instead?

> Debugging of OS 3 application creates a new replication controller
> ------------------------------------------------------------------
>
>                 Key: JBIDE-22259
>                 URL: https://issues.jboss.org/browse/JBIDE-22259
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: openshift
>    Affects Versions: 4.4.0.Alpha1
>            Reporter: Marián Labuda
>            Priority: Critical
>              Labels: openshift_v3, server_adapter
>
> Restart in debug on OS 3 server adapter of eap 6.4 application and related workspace project creates a new replication controller. Every time server is stopped and started, new replication controller is created (although server has been stopped and then started) and a this new replication controller is still debugging (has set debug port).



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)