[
https://issues.redhat.com/browse/WFCORE-5067?page=com.atlassian.jira.plug...
]
Cedric HENRY commented on WFCORE-5067:
--------------------------------------
I have just tested the above solution also on Wildfly 19.0.0.Final (for the standalone
configuration) and it work fine there too.
*Some Considerations*
* In the case of port offset, the {{CONTROLLER}} variable shall be edited accordingly as
it may be cause of the shutdown not being executed
* Based on the shutdown delays applied by hosted application(s), the service may not be
stopping in timely fashion, hence 2 possible options:
** Increase the Windows Service operation timeout as explained
in [https://www.coretechnologies.com/blog/windows-services/increase-shutd...
** Use the shutdown timeout feature (i.e. _:shutdown(timeout=60)_ instead of just
_:shutdown_) in the _service.bat_ script
Wildfly as Windows Service fails to stop in a timely fashion
------------------------------------------------------------
Key: WFCORE-5067
URL:
https://issues.redhat.com/browse/WFCORE-5067
Project: WildFly Core
Issue Type: Bug
Reporter: Cedric HENRY
Assignee: Jeff Mesnil
Priority: Major
As already discussed under WFCORE-1719, there a problem when stopping the
'Wildfly' Windows service resulting in error dialog about the service not stopping
in a timely fashion.
Further details got also provided in the
comment https://issues.redhat.com/browse/WFCORE-1719?focusedCommentId=143...
--
This message was sent by Atlassian Jira
(v7.13.8#713008)