<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">That just monitors console output.<div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Jun 12, 2015, at 11:32 AM, Jorge Solórzano <<a href="mailto:jorsol@gmail.com" class="">jorsol@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div class="gmail_default" style="font-family:verdana,sans-serif"><span id="result_box" class="" lang="en">It has been considered the use of Java Service Wrapper[1]? it depends on native binaries but almost all platforms are supported. <br class=""></span></div><div class="gmail_default" style="font-family:verdana,sans-serif"><br class="">[1] <a href="http://wrapper.tanukisoftware.com/" class="">http://wrapper.tanukisoftware.com</a><br class=""></div><div class="gmail_extra"><br clear="all" class=""><div class=""><div class="gmail_signature"><br class="">Jorge Solórzano<br class=""><a href="http://www.jorsol.com/" target="_blank" class="">http://www.jorsol.com</a></div></div>
<br class=""><div class="gmail_quote">On Fri, Jun 12, 2015 at 8:27 AM, Brian Stansberry <span dir="ltr" class=""><<a href="mailto:brian.stansberry@redhat.com" target="_blank" class="">brian.stansberry@redhat.com</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">How does EAP 5 deal with this? IIRC disabling console logging is not<br class="">
something new in EAP 6.<br class="">
<span class=""><br class="">
On 6/11/15 6:29 PM, Chao Wang wrote:<br class="">
> Thanks for your reply. Please see in-line below<br class="">
><br class="">
> On 06/11/2015 12:44 AM, Brian Stansberry wrote:<br class="">
>> A couple thoughts:<br class="">
>><br class="">
>> 1) Looking at wildfly-init-redhat.sh at least, I don't see how that<br class="">
>> check is actually testing for successful startup. It looks like it's<br class="">
>> just trying to delay start() returning for a while, max 30 secs.<br class="">
>><br class="">
>> So, what purpose is this fulfilling?<br class="">
> My bad about issue background. It's actually an case in EAP 6 (not yet<br class="">
> in wildfly). EAP 6.x script has launched state like:<br class="">
> <a href="https://github.com/jbossas/jboss-eap/blob/6.4.x/build/src/main/resources/bin/init.d/jboss-as-standalone.sh#L110" rel="noreferrer" target="_blank" class="">https://github.com/jbossas/jboss-eap/blob/6.4.x/build/src/main/resources/bin/init.d/jboss-as-standalone.sh#L110</a><br class="">
> (not in wildfly's script). Also, console log handler has been removed<br class="">
> only in EAP full-ha mode long time ago due to performance<br class="">
> concern.(wildfly keeps it for the moment). This leads to issue in<br class="">
</span>> bz1224170 <<a href="https://bugzilla.redhat.com/show_bug.cgi?id=1224170" rel="noreferrer" target="_blank" class="">https://bugzilla.redhat.com/show_bug.cgi?id=1224170</a>>.<br class="">
<div class=""><div class="h5">> That's why I try to seek an better option than current behavior from<br class="">
> wildfly.<br class="">
>><br class="">
>> 2) How does other software solve this problem? If it's solving a valid<br class="">
>> problem, it seems like there would be a typical solution.<br class="">
> I have checked some other application servers, most of them let users<br class="">
> themselves to write a script to run as service for their OS. Geronimo<br class="">
> does provide a script, Although I did damage to its configuration file<br class="">
> to make a fatal error, terminal output still displays "Server started".<br class="">
> In fact, process does not event exist and detail error can be seen in<br class="">
> log file.<br class="">
>> On 6/9/15 8:59 AM, Chao Wang wrote:<br class="">
>>> Hi all,<br class="">
>>><br class="">
>>> The Wildfly start-up as service scripts wildfly-init-redhat.sh and<br class="">
>>> wildfly-init-debian.sh currently depend on a grep action of key message<br class="">
>>> 'WFLYSRV0025:' in console log to determinate whether service start is<br class="">
>>> successful. The log message indication is accurate, however, it's not<br class="">
>>> that robust since user can always remove console handler from logging<br class="">
>>> subsystem. I have opened a WFCORE enhancement jira<br class="">
>>> <a href="https://issues.jboss.org/browse/WFCORE-747" rel="noreferrer" target="_blank" class="">https://issues.jboss.org/browse/WFCORE-747</a> for it.<br class="">
>>><br class="">
>>> For the moment, I have tried three options, they're all not that perfect<br class="">
>>> to implement<br class="">
>>><br class="">
>>> 1. Stay with exact log message, users need to define their jboss log<br class="">
>>> directory such as $JBOSS_HOME/standalone/log/server.log for standalone<br class="">
>>> and $JBOSS_HOME/domain/log/host-controller.log for domain instead of<br class="">
>>> searching in console log. This is more like another workaround since it<br class="">
>>> is also volatile once we update log message in future release.(EAP has<br class="">
>>> 'JBAS015874:')<br class="">
>>><br class="">
>>> 2. Use service pid, this is not precise because a long start-up can<br class="">
>>> crash in the last second. It needs to wait a suitable seconds before<br class="">
>>> checking pid existence. and still it can not avoid fake success in rare<br class="">
>>> case just before timeout.<br class="">
>>><br class="">
>>> 3. Use read-attribute server-state through CLI connection as I did in<br class="">
>>> Pull Request on Jira. This is declined as it is possible that<br class="">
>>> authentication is required before connection. In such case, any non<br class="">
>>> encrypted password is not advised in configuration files.<br class="">
>>><br class="">
>>> Therefore, I would like to listen for your opinions for them. Any other<br class="">
>>> suggestion is certainly welcomed in mail or on jira.<br class="">
>>><br class="">
>>> Best regards,<br class="">
>>><br class="">
>>> Chao<br class="">
>>><br class="">
>>><br class="">
>>> _______________________________________________<br class="">
>>> wildfly-dev mailing list<br class="">
>>> <a href="mailto:wildfly-dev@lists.jboss.org" class="">wildfly-dev@lists.jboss.org</a><br class="">
>>> <a href="https://lists.jboss.org/mailman/listinfo/wildfly-dev" rel="noreferrer" target="_blank" class="">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a><br class="">
>>><br class="">
>><br class="">
><br class="">
> [1] <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1224170" rel="noreferrer" target="_blank" class="">https://bugzilla.redhat.com/show_bug.cgi?id=1224170</a><br class="">
><br class="">
> --<br class="">
> Chao Wang<br class="">
> Software Engineer<br class="">
> JBoss by Red Hat<br class="">
><br class="">
><br class="">
><br class="">
> _______________________________________________<br class="">
> wildfly-dev mailing list<br class="">
> <a href="mailto:wildfly-dev@lists.jboss.org" class="">wildfly-dev@lists.jboss.org</a><br class="">
> <a href="https://lists.jboss.org/mailman/listinfo/wildfly-dev" rel="noreferrer" target="_blank" class="">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a><br class="">
><br class="">
<br class="">
<br class="">
</div></div><span class=""><font color="#888888" class="">--<br class="">
Brian Stansberry<br class="">
Senior Principal Software Engineer<br class="">
JBoss by Red Hat<br class="">
</font></span><div class=""><div class="h5">_______________________________________________<br class="">
wildfly-dev mailing list<br class="">
<a href="mailto:wildfly-dev@lists.jboss.org" class="">wildfly-dev@lists.jboss.org</a><br class="">
<a href="https://lists.jboss.org/mailman/listinfo/wildfly-dev" rel="noreferrer" target="_blank" class="">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a><br class="">
</div></div></blockquote></div><br class=""></div></div>
_______________________________________________<br class="">wildfly-dev mailing list<br class=""><a href="mailto:wildfly-dev@lists.jboss.org" class="">wildfly-dev@lists.jboss.org</a><br class="">https://lists.jboss.org/mailman/listinfo/wildfly-dev</div></blockquote></div><br class=""><div class="">
--<br class="">Jason T. Greene<br class="">WildFly Lead / JBoss EAP Platform Architect<br class="">JBoss, a division of Red Hat
</div>
<br class=""></div></body></html>