[
https://issues.jboss.org/browse/JBIDE-22259?page=com.atlassian.jira.plugi...
]
Marián Labuda edited comment on JBIDE-22259 at 4/27/16 1:13 PM:
----------------------------------------------------------------
Well, it is not bad, that we modify deployment config and trigger a new deployment
(replication controller). What I found useless is creating so many replication
controllers, even it is not necessary.
In best scenario it would be nice to have only distinct replication controllers - that
mean there would be just 2 replication controllers. But at the moment there will be so
many rcs as Restarting in Debug and starting in normal mode (which is broken at the moment
but its gonna be done in JBIDE-22066).
was (Author: mlabuda):
Well, it is not bad, that we modify deployment config and trigger a new deployment
(replication controller). What I found useless is creating so many replication
controllers, even it is not necessary.
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)