[jboss-jira] [JBoss JIRA] (WFLY-3397) Redhat/Debian script problem when deleting Console Handler
[
https://issues.jboss.org/browse/WFLY-3397?page=com.atlassian.jira.plugin....
]
Jorge Solorzano commented on WFLY-3397:
---------------------------------------
In that case I can make the check to the process status and not verify the log output....
but this way it will return OK right away even if there is an error in the start, for
example problems of permissions, etc. Since the process is really started but not fully
operational.
BTW is a bad practice to remove the console handler since it makes difficult to diagnose
possible problems on startup.
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)