[
https://issues.jboss.org/browse/JBIDE-26160?page=com.atlassian.jira.plugi...
]
Jeff MAURY updated JBIDE-26160:
-------------------------------
Sprint: devex #154 September 2018, devex #155 September 2018, devex #156 October 2018,
devex #157 November 2019, devex #158 November 2018, devex #159 December 2018 (was: devex
#154 September 2018, devex #155 September 2018, devex #156 October 2018, devex #157
November 2019, devex #158 November 2018)
Server Adapter: erroneously stays in [Debugging] when you kill the
pod
----------------------------------------------------------------------
Key: JBIDE-26160
URL:
https://issues.jboss.org/browse/JBIDE-26160
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.6.0.AM3
Reporter: Andre Dietisheim
Assignee: Dmitrii Bocharov
Priority: Major
Labels: server_adapter
Fix For: 4.11.x
steps:
# EXEC: create an application (via ex. nodejs-mongo-persistent template), import the
project and create a server adapter for it
# ASSERT: server adapter is created
# EXEC: start the server adapter in Debugging
# ASSERT: sever adapter is in *[Debugging, Synchronized]* state
# ASSERT: select pod and pick "Port Forwarding..." and it states that the
forwarding is started
# EXEC: in Explorer: select the pod for your service and pick "Delete"
# ASSERT: pod gets deleted and recreated
# ASSERT: select pod and pick "Port Forwarding..." and it states that the
forwarding is stopped
Result:
The server adapter still says that is is *[Debugging, Synchronized]*, but debugging is
not working any more. Debugging doesn't work any more because the port forwarding was
stopped. To have it running again you need to restart the port forwarding for the new
pod.
Expected result:
Server adapter should get out of debugging and back into normal run mode *[Started,
Synchronized]*.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)