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

[James Perkins (JIRA)]

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

James Perkins commented on WFLY-3397:
-------------------------------------

Not really as there is no way to know what the address and port the management resources are bound to. This will actually break in WildFly 10 anyway. Ideally you'd want to check the process rather than the stdout anyway.

> 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)