[jboss-jira] [JBoss JIRA] (WFLY-3397) Redhat/Debian script problem when deleting Console Handler

[Jorge Solorzano (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-3397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13028071#comment-13028071 ] 

Jorge Solorzano edited comment on WFLY-3397 at 12/16/14 2:02 PM:
-----------------------------------------------------------------

This is due to the wait it takes to start and check if started successfully.

 ¨[~jamezp] do you know a reliable way to check if the server is running, maybe using jboss-cli?


was (Author: jorsol):
This is due to the wait it takes to start... ¨[~jamezp] do you know a reliable way to check if the server is running, maybe using jboss-cli?

> Redhat/Debian script problem when deleting Console Handler
> ----------------------------------------------------------
>
>                 Key: WFLY-3397
>                 URL: https://issues.jboss.org/browse/WFLY-3397
>             Project: WildFly
>          Issue Type: Bug
>          Components: Scripts
>    Affects Versions: 8.1.0.CR2
>            Reporter: Marcial Atiénzar Navarro
>            Assignee: James Perkins
>            Priority: Minor
>
> The scripts to start wildfly as service on redhat/debian use this code:
> {code}
> until [ $count -gt $STARTUP_WAIT ]
> 		do
> 			grep 'JBAS015874:' "$JBOSS_CONSOLE_LOG" > /dev/null
> 			if [ $? -eq 0 ] ; then
> 				launched=1
> 				break
> 			fi
> 			sleep 1
> 			count=$((count + 1));
> 		done
> {code}
> But if you have delete console handler in production enviroment, and increase the startup_wait because you have more applications deployed on server, it takes to start all the time specified on STARTUP_WAIT



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)