SVT: Cannot stop a liberty "Start in container" session from the Liberty dashboard.

[rumanaHaque]

As part of this TER - https://github.ibm.com/websphere/system-test/issues/922

When I start the application in a container - the server seems to start, but it is waiting for the app to start -

[INFO] [AUDIT   ] CWWKF1037I: The server added the [appClientSupport-2.0, appSecurity-5.0, cdi-4.0, connectors-2.1, enterpriseBeans-4.0, enterpriseBeansHome-4.0, enterpriseBeansLite-4.0, enterpriseBeansPersistentTimer-4.0, enterpriseBeansRemote-4.0, expressionLanguage-5.0, federatedRegistry-1.0, json-1.0, jsonb-3.0, jsonp-2.1, jwt-1.0, ldapRegistry-3.0, localConnector-1.0, mdb-4.0, messaging-3.1, messagingClient-3.0, messagingSecurity-3.0, messagingServer-3.0, microProfile-6.0, monitor-1.0, mpConfig-3.0, mpFaultTolerance-4.0, mpHealth-4.0, mpJwt-2.1, mpMetrics-5.0, mpOpenAPI-3.1, mpRestClient-3.0, mpTelemetry-1.0, pages-3.1, persistence-3.1, persistenceContainer-3.1, restfulWS-3.1, restfulWSClient-3.1, servlet-6.0, transportSecurity-1.0, xmlBinding-4.0, xmlWS-4.0] features to the existing feature set.
[INFO] [AUDIT   ] CWWKF0012I: The server installed the following features: [appClientSupport-2.0, appSecurity-5.0, cdi-4.0, connectors-2.1, distributedMap-1.0, enterpriseBeans-4.0, enterpriseBeansHome-4.0, enterpriseBeansLite-4.0, enterpriseBeansPersistentTimer-4.0, enterpriseBeansRemote-4.0, expressionLanguage-5.0, federatedRegistry-1.0, jdbc-4.2, jndi-1.0, json-1.0, jsonb-3.0, jsonp-2.1, jwt-1.0, ldapRegistry-3.0, localConnector-1.0, mdb-4.0, messaging-3.1, messagingClient-3.0, messagingSecurity-3.0, messagingServer-3.0, microProfile-6.0, monitor-1.0, mpConfig-3.0, mpFaultTolerance-4.0, mpHealth-4.0, mpJwt-2.1, mpMetrics-5.0, mpOpenAPI-3.1, mpRestClient-3.0, mpTelemetry-1.0, pages-3.1, persistence-3.1, persistenceContainer-3.1, restfulWS-3.1, restfulWSClient-3.1, servlet-6.0, ssl-1.0, transportSecurity-1.0, xmlBinding-4.0, xmlWS-4.0].
[INFO] [AUDIT   ] CWWKF0013I: The server removed the following features: [appClientSupport-1.0, appSecurity-2.0, appSecurity-3.0, batch-1.0, beanValidation-2.0, cdi-2.0, concurrent-1.0, ejb-3.2, ejbHome-3.2, ejbLite-3.2, ejbPersistentTimer-3.2, ejbRemote-3.2, el-3.0, j2eeManagement-1.1, jacc-1.5, jaspic-1.1, javaMail-1.6, javaee-8.0, jaxb-2.2, jaxrs-2.1, jaxrsClient-2.1, jaxws-2.2, jca-1.7, jcaInboundSecurity-1.0, jms-2.0, jpa-2.2, jpaContainer-2.2, jsf-2.3, jsonb-1.0, jsonp-1.1, jsp-2.3, managedBeans-1.0, mdb-3.2, servlet-4.0, wasJmsClient-2.0, wasJmsSecurity-1.0, wasJmsServer-1.0, webProfile-8.0, websocket-1.1].
[INFO] [AUDIT   ] CWWKF0011I: The defaultServer server is ready to run a smarter planet. The defaultServer server started in 78.240 seconds.
[INFO] [AUDIT   ] CWWKZ0022W: Application AcmeWebEjbEar has not started in 30.001 seconds.
exit
exit
exit

Once in this mode - I cannot stop the server.
Using Stop for the dashboard only shows "exit" as shown above, and doesn't stop the server.

[rumanaHaque]

As @TrevCraw mentioned - As for "stop" not working in the previous scenario - I think the problem there is that the container had started, but dev mode was not fully started yet - so we're in that weird in between spot where we can run into problems like that.

The server hadn't started completely, so it wasn't able to stop it.
But when I reran the command, and it showed this message

INFO] [AUDIT   ] CWWKF0011I: The defaultServer server is ready to run a smarter planet. The defaultServer server started in 87.229 seconds.
[INFO] CWWKM2015I: Match number: 1 is [10/30/23, 22:34:37:313 UTC] 00000029 com.ibm.ws.kernel.feature.internal.FeatureManager            A CWWKF0011I: The defaultServer server is ready to run a smarter planet. The defaultServer server started in 87.229 seconds..
[INFO] [AUDIT   ] CWWKZ0022W: Application AcmeWebEjbEar has not started in 30.019 seconds.
[INFO] ************************************************************************
[INFO] *    Liberty is running in dev mode.
[INFO] *        Automatic generation of features: [ Off ]
[INFO] *        h - see the help menu for available actions, type 'h' and press Enter.
[INFO] *        q - stop the server and quit dev mode, press Ctrl-C or type 'q' and press Enter.
[INFO] *        
[INFO] *    Liberty container port information:
[INFO] *        Internal container HTTP port [ 9080 ] is mapped to container host port [ 9080 ]
[INFO] *        Internal container HTTPS port [ 9443 ] is mapped to container host port [ 9443 ]
[INFO] *        Liberty debug port mapped to container host port: [ 7777 ]
[INFO] *        
[INFO] *    Container network information:
[INFO] *        Container name: [ liberty-dev ]
[INFO] *        IP address [ 10.88.0.2 ] on container network [ podman ]
[INFO] ************************************************************************

even though the app wasn't installed, I was able to stop the server using the "Stop" command from the dashboard.

[INFO] Stopping container...
[INFO] [AUDIT   ] CWWKE0085I: The server defaultServer is stopping because the JVM is exiting.
[INFO] [AUDIT   ] CWWKE1100I: Waiting for up to 30 seconds for the server to quiesce.
[INFO] [AUDIT   ] CWWKT0017I: Web application removed (default_host): http://db298c12d8a1:9080/jwt/
[INFO] [AUDIT   ] CWWKT0017I: Web application removed (default_host): http://db298c12d8a1:9080/openapi/ui/
[INFO] [AUDIT   ] CWWKT0017I: Web application removed (default_host): http://db298c12d8a1:9080/health/
[INFO] [AUDIT   ] CWWKT0017I: Web application removed (default_host): http://db298c12d8a1:9080/metrics/
[INFO] [AUDIT   ] CWWKT0017I: Web application removed (default_host): http://db298c12d8a1:9080/openapi/
[INFO] [AUDIT   ] CWWKT0017I: Web application removed (default_host): http://db298c12d8a1:9080/ibm/api/
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary for acme-ee10 0.0.1-SNAPSHOT:
[INFO] 
[INFO] acme-ee10 .......................................... SUCCESS [  0.564 s]
[INFO] AcmeCommon ......................................... SUCCESS [  0.318 s]
[INFO] AcmeAnnuityCommon .................................. SUCCESS [  4.144 s]
[INFO] AcmeAnnuityJAXRSCommon ............................. SUCCESS [  1.023 s]
[INFO] AcmeAnnuityEJB3 .................................... SUCCESS [  0.201 s]
[INFO] AcmeAnnuityEJB3JAXWS ............................... SUCCESS [  0.037 s]
[INFO] AcmeAnnuityEJB3JAXWS_CDI ........................... SUCCESS [  0.037 s]
[INFO] AcmeAnnuityEJB3MDB ................................. SUCCESS [  0.096 s]
[INFO] AcmeAnnuityJAXRSWSes_jaxrs11_m1 .................... SUCCESS [  0.156 s]
[INFO] AcmeAnnuityJAXRSWSes_jaxrs11_m2 .................... SUCCESS [  0.021 s]
[INFO] AcmeAnnuityJAXRSWSes_jaxrs20 ....................... SUCCESS [  0.020 s]
[INFO] AcmeAnnuityPojoWSes ................................ SUCCESS [  0.034 s]
[INFO] AcmeAnnuityWeb ..................................... SUCCESS [  0.057 s]
[INFO] AcmeWebEjbEar ...................................... SUCCESS [11:37 min]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  11:44 min
[INFO] Finished at: 2023-10-30T17:39:59-05:00
[INFO] ------------------------------------------------------------------------

[TrevCraw]

Workaround added to https://github.com/OpenLiberty/liberty-tools-vscode/wiki/Known-Problems-and-Limitations.
Need to think about how we can address this issue - may really be something that dev mode needs to handle.
However, we may need to investigate devc a bit further to see if there is an issue stopping while things are working "normally".