[
https://issues.jboss.org/browse/JBIDE-22648?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-22648:
-------------------------------------
Manual test cases:
Prereq: Create an RSE connection to a remote host, rse+fs or rse+mgmt (or test both...
ugh, so many to do)
Test: Perform actions required below, and make sure debug view is properly cleaned up or
represented with launches.
In general, you will want a launch to be visible while the server is up, and disappear
when you stop the server.
The launch should have 1 "process" attached to it, and may or may not include a
debugging connection, depending on settings
Scenarios:
1) Run Mode
a) Start server in run mode,
b) right-click on the process in debug view and select "Properties". Verify
a command is visible
c) then stop server
2) Debug Mode
a) Start server in Debug mode,
b) right-click on the process in debug view and select "Properties". Verify
a command is visible.
c) Copy this command to clipboard, you will use it later when we switch to externally
launched
d) then stop server
3) Open server editor and mark server as externally managed, save the changes
4) Switch to your terminal, and start the DEBUG command you copied from 2b) on the remote
system.
5) Externally-managed Run Mode
a) Start server in run mode,
b) right-click on the process in debug view and select "Properties". Verify
command is NOT VISIBLE / IS EMPTY
c) then stop server
6) Externally-managed Debug Mode
a) Start server in Debug mode,
b) Verify a launch is visible, with a process AND a debug connection!
b) right-click on the process in debug view and select "Properties". Verify
command is NOT VISIBLE / IS EMPTY
c) then stop server
TERMINATION TESTS
7) Externally-managed Run Mode Termination
a) Start server in run mode,
b) right-click on the PROCESS (not debugger) in debug view and verify you CANNOT
terminate the process
c) then stop server
8) Externally-managed Debug Mode Termination
a) Start server in Debug mode,
b) right-click on the PROCESS (not debugger) in debug view and verify you CANNOT
terminate the process
c) then stop server
9) Open server editor and mark server as NOT externally managed, save the changes
10) Switch to your terminal, and KILL the process or shut down the server
11) Run Mode
a) Start server in run mode,
b) right-click on the process in debug view and select "terminate". Verify
the server properly shuts down and all processes are cleaned up in debug view
c) then stop server
12) Debug Mode
a) Start server in Debug mode,
b) right-click on the process in debug view and select "terminate". Verify
the server properly shuts down and all processes are cleaned up in debug view
c) then stop server
Switch to RSE+MGMT and perform all 12 again ;)
If you see a usecase which doesn't work as outlined above, OR if you see a usecase
which *does* function as above but you think it shouldn't, tell me and we can discuss
it! :D
RSE launches stick around in debug view forever
-----------------------------------------------
Key: JBIDE-22648
URL:
https://issues.jboss.org/browse/JBIDE-22648
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: server
Affects Versions: 4.4.1.M1
Reporter: Rob Stryker
Assignee: Rob Stryker
Fix For: 4.4.1.M1
When launching remote rse wildfly / eap / etc, launches get stuck and left behind, never
cleaned up.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)