<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<br>
<br>
<div class="moz-cite-prefix">On 06/09/2015 09:59 PM, Chao Wang
wrote:<br>
</div>
<blockquote cite="mid:5576F142.3030307@redhat.com" type="cite">
<meta http-equiv="content-type" content="text/html;
charset=windows-1252">
Hi all,<br>
<br>
<span class="final-path">The Wildfly start-up as service scripts
wildfly-init-redhat.sh</span> and <span class="final-path">wildfly-init-debian.sh
currently depend on a grep action of key message '</span><span
class="pl-s">WFLYSRV0025:' in console log to determinate whether
service start is successful. The log message indication is
accurate, however, it's not that robust since user can always
remove console handler from logging subsystem. I have opened a
WFCORE enhancement jira <a moz-do-not-send="true"
class="moz-txt-link-freetext"
href="https://issues.jboss.org/browse/WFCORE-747">https://issues.jboss.org/browse/WFCORE-747</a>
for it.<br>
<br>
For the moment, I have tried three options, they're all not that
perfect to implement<br>
<br>
1. Stay with exact log message, users need to define their jboss
log directory such as $JBOSS_HOME/standalone/log/server.log for
standalone and $JBOSS_HOME/domain/log/host-controller.log for
domain instead of searching in console log. This is more like
another workaround since it is also </span>volatile once we
update log message in future release.(EAP has 'JBAS015874:')<br>
<br>
2. Use service pid, this is not precise because a long start-up
can crash in the last second. It needs to wait a suitable seconds
before checking pid
<meta http-equiv="content-type" content="text/html;
charset=windows-1252">
existence. and still it can not avoid fake success in rare case
just before timeout. <br>
<br>
3. Use read-attribute server-state through CLI connection as I did
in Pull Request on Jira. This is declined as it is possible that
authentication is required before connection. In such case, any
non encrypted password is not advised in configuration files.<br>
</blockquote>
<br>
I have opened a PR to change the log key message dependency in start
script <a class="moz-txt-link-freetext" href="https://github.com/wildfly/wildfly-core/pull/859">https://github.com/wildfly/wildfly-core/pull/859</a> <br>
<br>
A jboss start marker file in temporary directory can be added to
record launch result and its timestamp when it starts. <span
class="final-path">wildfly-init-redhat.sh / </span><span
class="final-path"><span class="final-path">wildfly-init-debian.sh</span>
will exam its content to get server start result (success/error,
or nonexistent file means start failure). The timestamp can be
used to identify this marker file's age </span><span
class="final-path"><span class="final-path">in case of previous
abnormal termination</span>. Once server is normally shutdown,
it can be removed as part of service stop.<br>
<br>
If anyone is interested in this, please take a look at the PR, and
feel free to reply this or leave a comment.<br>
<br>
Thanks,<br>
<br>
</span>
<blockquote cite="mid:5576F142.3030307@redhat.com" type="cite"> <span
class="pl-s"> </span> <br>
Therefore, I would like to listen for your opinions for them. Any
other suggestion is certainly welcomed in mail or on jira.<br>
<br>
Best regards,<br>
<br>
Chao<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
wildfly-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:wildfly-dev@lists.jboss.org">wildfly-dev@lists.jboss.org</a>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/wildfly-dev">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a></pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Chao Wang
Software Engineer
JBoss by Red Hat</pre>
</body>
</html>