Create a gist now

Instantly share code, notes, and snippets.

Script to install JBoss Wildfly 10.x as service in Linux
#!/bin/bash
#title :wildfly-install.sh
#description :The script to install Wildfly 10.x
#more :http://sukharevd.net/wildfly-8-installation.html
#author :Dmitriy Sukharev
#date :2016-06-18T02:45-0700
#usage :/bin/bash wildfly-install.sh
#tested-version1 :10.0.0.CR3
#tested-distros1 :Ubuntu 15.10; Debian 7,8; CentOS 7; Fedora 22
#tested-version2 :10.0.0.Final
#tested-distros2 :Debian 8
WILDFLY_VERSION=10.0.0.Final
WILDFLY_FILENAME=wildfly-$WILDFLY_VERSION
WILDFLY_ARCHIVE_NAME=$WILDFLY_FILENAME.tar.gz
WILDFLY_DOWNLOAD_ADDRESS=http://download.jboss.org/wildfly/$WILDFLY_VERSION/$WILDFLY_ARCHIVE_NAME
INSTALL_DIR=/opt
WILDFLY_FULL_DIR=$INSTALL_DIR/$WILDFLY_FILENAME
WILDFLY_DIR=$INSTALL_DIR/wildfly
WILDFLY_USER="wildfly"
WILDFLY_SERVICE="wildfly"
WILDFLY_MODE="standalone"
WILDFLY_STARTUP_TIMEOUT=240
WILDFLY_SHUTDOWN_TIMEOUT=30
SCRIPT_DIR="$( cd "$( dirname "${BASH_SOURCE[0]}" )" && pwd )"
if [[ $EUID -ne 0 ]]; then
echo "This script must be run as root."
exit 1
fi
echo "Downloading: $WILDFLY_DOWNLOAD_ADDRESS..."
[ -e "$WILDFLY_ARCHIVE_NAME" ] && echo 'Wildfly archive already exists.'
if [ ! -e "$WILDFLY_ARCHIVE_NAME" ]; then
wget -q $WILDFLY_DOWNLOAD_ADDRESS
if [ $? -ne 0 ]; then
echo "Not possible to download Wildfly."
exit 1
fi
fi
echo "Cleaning up..."
rm -f "$WILDFLY_DIR"
rm -rf "$WILDFLY_FULL_DIR"
rm -rf "/var/run/$WILDFLY_SERVICE/"
rm -f "/etc/init.d/$WILDFLY_SERVICE"
echo "Installation..."
mkdir $WILDFLY_FULL_DIR
tar -xzf $WILDFLY_ARCHIVE_NAME -C $INSTALL_DIR
ln -s $WILDFLY_FULL_DIR/ $WILDFLY_DIR
useradd -s /sbin/nologin $WILDFLY_USER
chown -R $WILDFLY_USER:$WILDFLY_USER $WILDFLY_DIR
chown -R $WILDFLY_USER:$WILDFLY_USER $WILDFLY_DIR/
#mkdir -p /var/log/$WILDFLY_SERVICE
echo "Registrating Wildfly as service..."
# if should use systemd
if [ -x /bin/systemctl ]; then
# Script from $WILDFLY_DIR/docs/contrib/scripts/systemd/launch.sh didn't work for me
cat > $WILDFLY_DIR/bin/launch.sh << "EOF"
#!/bin/sh
if [ "x$WILDFLY_HOME" = "x" ]; then
WILDFLY_HOME="/opt/wildfly"
fi
if [ "x$1" = "xdomain" ]; then
echo 'Starting Wildfly in domain mode.'
$WILDFLY_HOME/bin/domain.sh -c $2 -b $3
#>> /var/log/$WILDFLY_SERVICE/server-`date +%Y-%m-%d`.log
else
echo 'Starting Wildfly in standalone mode.'
$WILDFLY_HOME/bin/standalone.sh -c $2 -b $3
#>> /var/log/$WILDFLY_SERVICE/server-`date +%Y-%m-%d`.log
fi
EOF
# $WILDFLY_HOME is not visible here
sed -i -e 's,WILDFLY_HOME=.*,WILDFLY_HOME='$WILDFLY_DIR',g' $WILDFLY_DIR/bin/launch.sh
#sed -i -e 's,$WILDFLY_SERVICE,'$WILDFLY_SERVICE',g' $WILDFLY_DIR/bin/launch.sh
chmod +x $WILDFLY_DIR/bin/launch.sh
cp $WILDFLY_DIR/docs/contrib/scripts/systemd/wildfly.service /etc/systemd/system/$WILDFLY_SERVICE.service
WILDFLY_SERVICE_CONF=/etc/default/$WILDFLY_SERVICE
# To install multiple instances of Wildfly replace all hardcoding in systemd file
sed -i -e 's,EnvironmentFile=.*,EnvironmentFile='$WILDFLY_SERVICE_CONF',g' /etc/systemd/system/$WILDFLY_SERVICE.service
sed -i -e 's,User=.*,User='$WILDFLY_USER',g' /etc/systemd/system/$WILDFLY_SERVICE.service
sed -i -e 's,PIDFile=.*,PIDFile=/var/run/wildfly/'$WILDFLY_SERVICE'.pid,g' /etc/systemd/system/$WILDFLY_SERVICE.service
sed -i -e 's,ExecStart=.*,ExecStart='$WILDFLY_DIR'/bin/launch.sh $WILDFLY_MODE $WILDFLY_CONFIG $WILDFLY_BIND,g' /etc/systemd/system/$WILDFLY_SERVICE.service
systemctl daemon-reload
#systemctl enable $WILDFLY_SERVICE.service
fi
# if non-systemd Debian-like distribution
if [ ! -x /bin/systemctl -a -r /lib/lsb/init-functions ]; then
cp $WILDFLY_DIR/docs/contrib/scripts/init.d/wildfly-init-debian.sh /etc/init.d/$WILDFLY_SERVICE
sed -i -e 's,NAME=wildfly,NAME='$WILDFLY_SERVICE',g' /etc/init.d/$WILDFLY_SERVICE
WILDFLY_SERVICE_CONF=/etc/default/$WILDFLY_SERVICE
fi
# if non-systemd RHEL-like distribution
if [ ! -x /bin/systemctl -a -r /etc/init.d/functions ]; then
cp $WILDFLY_DIR/docs/contrib/scripts/init.d/wildfly-init-redhat.sh /etc/init.d/$WILDFLY_SERVICE
WILDFLY_SERVICE_CONF=/etc/default/wildfly.conf
chmod 755 /etc/init.d/$WILDFLY_SERVICE
fi
# if neither Debian nor RHEL like distribution
if [ ! -x /bin/systemctl -a ! -r /lib/lsb/init-functions -a ! -r /etc/init.d/functions ]; then
cat > /etc/init.d/$WILDFLY_SERVICE << "EOF"
#!/bin/sh
### BEGIN INIT INFO
# Provides: ${WILDFLY_SERVICE}
# Required-Start: $local_fs $remote_fs $network $syslog
# Required-Stop: $local_fs $remote_fs $network $syslog
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Short-Description: Start/Stop ${WILDFLY_FILENAME}
### END INIT INFO
WILDFLY_USER=${WILDFLY_USER}
WILDFLY_DIR=${WILDFLY_DIR}
case "$1" in
start)
echo "Starting ${WILDFLY_FILENAME}..."
start-stop-daemon --start --background --chuid $WILDFLY_USER --exec $WILDFLY_DIR/bin/standalone.sh
exit $?
;;
stop)
echo "Stopping ${WILDFLY_FILENAME}..."
start-stop-daemon --start --quiet --background --chuid $WILDFLY_USER --exec $WILDFLY_DIR/bin/jboss-cli.sh -- --connect command=:shutdown
exit $?
;;
log)
echo "Showing server.log..."
tail -500f $WILDFLY_DIR/standalone/log/server.log
;;
*)
echo "Usage: /etc/init.d/wildfly {start|stop}"
exit 1
;;
esac
exit 0
EOF
sed -i -e 's,${WILDFLY_USER},'$WILDFLY_USER',g; s,${WILDFLY_FILENAME},'$WILDFLY_FILENAME',g; s,${WILDFLY_SERVICE},'$WILDFLY_SERVICE',g; s,${WILDFLY_DIR},'$WILDFLY_DIR',g' /etc/init.d/$WILDFLY_SERVICE
chmod 755 /etc/init.d/$WILDFLY_SERVICE
fi
if [ ! -z "$WILDFLY_SERVICE_CONF" ]; then
echo "Configuring service..."
echo JBOSS_HOME=\"$WILDFLY_DIR\" > $WILDFLY_SERVICE_CONF
echo JBOSS_USER=$WILDFLY_USER >> $WILDFLY_SERVICE_CONF
echo WILDFLY_HOME=\"$WILDFLY_DIR\" > $WILDFLY_SERVICE_CONF
echo WILDFLY_USER=\"$WILDFLY_USER\" > $WILDFLY_SERVICE_CONF
echo STARTUP_WAIT=$WILDFLY_STARTUP_TIMEOUT >> $WILDFLY_SERVICE_CONF
echo SHUTDOWN_WAIT=$WILDFLY_SHUTDOWN_TIMEOUT >> $WILDFLY_SERVICE_CONF
echo WILDFLY_CONFIG=$WILDFLY_MODE.xml >> $WILDFLY_SERVICE_CONF
echo WILDFLY_MODE=$WILDFLY_MODE >> $WILDFLY_SERVICE_CONF
echo WILDFLY_BIND=0.0.0.0 >> $WILDFLY_SERVICE_CONF
fi
echo "Configuring application server..."
sed -i -e 's,<deployment-scanner path="deployments" relative-to="jboss.server.base.dir" scan-interval="5000",<deployment-scanner path="deployments" relative-to="jboss.server.base.dir" scan-interval="5000" deployment-timeout="'$WILDFLY_STARTUP_TIMEOUT'",g' $WILDFLY_DIR/$WILDFLY_MODE/configuration/$WILDFLY_MODE.xml
sed -i -e 's,<inet-address value="${jboss.bind.address:127.0.0.1}"/>,<any-address/>,g' $WILDFLY_DIR/$WILDFLY_MODE/configuration/$WILDFLY_MODE.xml
sed -i -e 's,<socket-binding name="ajp" port="${jboss.ajp.port:8009}"/>,<socket-binding name="ajp" port="${jboss.ajp.port:28009}"/>,g' $WILDFLY_DIR/$WILDFLY_MODE/configuration/$WILDFLY_MODE.xml
sed -i -e 's,<socket-binding name="http" port="${jboss.http.port:8080}"/>,<socket-binding name="http" port="${jboss.http.port:28080}"/>,g' $WILDFLY_DIR/$WILDFLY_MODE/configuration/$WILDFLY_MODE.xml
sed -i -e 's,<socket-binding name="https" port="${jboss.https.port:8443}"/>,<socket-binding name="https" port="${jboss.https.port:28443}"/>,g' $WILDFLY_DIR/$WILDFLY_MODE/configuration/$WILDFLY_MODE.xml
sed -i -e 's,<socket-binding name="osgi-http" interface="management" port="8090"/>,<socket-binding name="osgi-http" interface="management" port="28090"/>,g' $WILDFLY_DIR/$WILDFLY_MODE/configuration/$WILDFLY_MODE.xml
[ -x /bin/systemctl ] && systemctl start $WILDFLY_SERVICE || service $WILDFLY_SERVICE start
echo "Done."
@aHumanBeing

Hi,

Thanks for this script it works great! Is there one available for uninstalling as well? Or would it be OK to somehow reverse engineer it?

@thermz
thermz commented Mar 21, 2014

Well done!

@wilkinsbrian

This is good, but I had trouble setting up new users. Had to change the nologin for the useradd on wildfly so I could run add-users.sh.

@ianellis90

Hey @wilkinsBrian what did you change exactly to get ass-uders.sh to run? I'm having trouble running the service I'm getting the following after trying to run:

/etc/init.d/wildfly start
Starting wildfly: chown: missing operand after /var/run/wildfly' Trychown --help' for more information.

Any Ideas?

@o6s
o6s commented Jun 25, 2014

Thanks for scripts!
@ianellis90 You must add the default user in the script if not using config.For example:
if [ -z "$JBOSS_USER" ]; then
JBOSS_USER=wildfly
fi

@svenkata

Where can I change the bind address ?
Currently when i start (sudo service wildfly start), its binding to 127.0.0.1:8080

In case of starting the jboss from command line we used ./standalone.sh -Djboss.bind.address=ip-address

www.techiesinfo.com

@Korrozia
Korrozia commented Jan 9, 2015

Run this script om CentOS 6.6, everything installed.

Thank you!

@ManuelB
ManuelB commented Jan 17, 2015

Worked for me as well on:

$ uname -a
Linux v-apaxo-de 3.16-0.bpo.3-amd64 #1 SMP Debian 3.16.5-1~bpo70+1 (2014-11-02) x86_64 GNU/Linux

Good job!

@abogatyrev

Дима спасибо за скрипт! Очень помог :)

@shriharshmishra

Awesome work! Thanks!

@bioinfornatics

to support multiple version of wildfly I use alternatives.

version=8.2.0
mkdir -p /opt/wildfly/${version}
cd /opt/wildfly/
curl -LO http://download.jboss.org/wildfly/${version}.Final/wildfly-${version}.Final.tar.gz
tar xvf wildfly-${version}.Final.tar.gz
cp -r wildfly-${version}.Final/* /opt/wildfly/${version}/
adduser  -M wildfly
chown wildfly -R /opt/wildfly/${version}/
alternatives    --install /usr/local/bin/wildfly        wildfly             /opt/wildfly/${version}/bin/standalone.sh ${version//./}            \
                --slave /usr/local/bin/wildfly_domain   wildfly_domain      /opt/wildfly/${version}/bin/domain.sh                    \
                --slave /usr/local/jboss-modules.jar    jboss-modules       /opt/wildfly/${version}/jboss-modules.jar                \
                --slave /usr/local/appclient            appclient           /opt/wildfly/${version}/appclient                        \
                --slave /usr/local/domain               domain              /opt/wildfly/${version}/domain                           \
                --slave /usr/local/modules              modules             /opt/wildfly/${version}/modules                          \
                --slave /usr/local/standalone           standalone          /opt/wildfly/${version}/standalone                       \
                --slave /etc/init.d/wildfly             wildfly_service     /opt/wildfly/${version}/bin/init.d/wildfly-init-redhat.sh 

to run it:

$ wildfly &
@gothicx
gothicx commented Mar 25, 2015

The default HTTP port is 28080 :)

@kamilkkonieczka

Great :) Thanks a lot

@farshad6730

hi please help me

error:

ho-sadegh:/ # ./wildfly-auto.sh
Cleaning up...
Installation...
Registrating Wildfly as service...
Configuring service...
Configuring application server...
/etc/init.d/wildfly: line 157: log_daemon_msg: command not found
/etc/init.d/wildfly: line 193: log_end_msg: command not found
WildFly Application Server hasn't started within the timeout allowed warning
please review file "/var/log/wildfly/console.log" to see the status of the serv warning
Done.
ho-sadegh:/ #

info:

ho-sadegh:/Desktop # uname -a
Linux ho-sadegh 3.0.13-0.27-default #1 SMP Wed Feb 15 13:33:49 UTC 2012 (d73692b) x86_64 x86_64 x86_64 GNU/Linux
ho-sadegh:
/Desktop # cat /etc/*-release
LSB_VERSION="core-2.0-noarch:core-3.2-noarch:core-4.0-noarch:core-2.0-x86_64:core-3.2-x86_64:core-4.0-x86_64"
SUSE Linux Enterprise Server 11 (x86_64)
VERSION = 11
PATCHLEVEL = 2

@dilworks

Neato!

Any way you could update it for systemd compatibility? (as in creating the unit files and stuff - I'm going to test future deployments on Debian Jessie, on which systemd is now the default init system)

@umitmert

Everything is ok but standalone.sh is not executable as warning. why?

@demelvin

Awesome Job man. I did this all manually before. Saved me a lot of time.

@itsjimbo
itsjimbo commented Aug 5, 2015

Nice script.. Thanks!

Just one small change for me though, no need to change the ports from 8080 to 28080

vi +395 wildfly-9.0.1.Final/standalone/configuration/standalone.xml

Change the port offset variable to shift all of the ports by 10 or 100 or 1000

 port-offset="${jboss.socket.binding.port-offset:10}"
@ptofanelli

Nice! just installed on my raspberry pi 2.

How can I make the wildfly service start automatically?

Thanks!

@lfantinel

Hi Sukharev.
It's the best script.

I would like suggest two implementations.

first, optional parameter to choice wildfly version:

if [[ !-z $1 ]]
then
   WILDFLY_VERSION=$1
else
   WILDFLY_VERSION=9.0.1.Final
fi

second, progress filter to improve download user response

progressfilter() {
    local flag=false c count cr=$'\r' nl=$'\n'
    while IFS='' read -d '' -rn 1 c
    do
        if $flag
        then
            printf '%c' "$c"
        else
            if [[ $c != $cr && $c != $nl ]]
            then
                count=0
            else
                ((count++))
                if ((count > 1))
                then
                    flag=true
                fi
            fi
        fi
    done
}

...

wget --progress=bar:force $WILDFLY_DOWNLOAD_ADDRESS 2>&1 | progressfilter

Hugs.

@yghandor

on debian it install every thing but service not started

debian :~$ sudo service wildfly start
Failed to start wildfly.service: Unit wildfly.service failed to load: No such file or directory.

@theider
theider commented Oct 14, 2015

Nice job! Works great on Ubuntu 14.04. Thank you.

@theider
theider commented Oct 15, 2015

I was able to get Wildfly to auto-start on Ubuntu 14 with:
sudo update-rc.d wildfly defaults

@florianrusch

Problem solved
You have to create a wildfly.service file in the /usr/lib/systemd/system directory.
You can find the content for this file here: https://gist.github.com/marekjelen/8568448

Original Problem
I have a similiar problem like @yghandor.

If I run the script I became this messages:

user@host:~$ sudo ./wildfly-install.sh 
Downloading: http://download.jboss.org/wildfly/9.0.1.Final/wildfly-9.0.1.Final.tar.gz...
Wildfly archive already exists.
Cleaning up...
Installation...
useradd: user 'wildfly' already exists
Registrating Wildfly as service...
Configuring service...
Configuring application server...
Failed to start wildfly.service: Unit wildfly.service failed to load: No such file or directory.
Done.

If I try to start the service with '/etc/init.d/wildfly start', I became this message:

user@host:~$ sudo /etc/init.d/wildfly start
[....] Starting wildfly (via systemctl): wildfly.serviceFailed to start wildfly.service: Unit wildfly.service failed to load: No such file or directory.
 failed!

Could be the problem that the script doesn't work with systemd?

@kvandake

How can I start wildfly with standalone-full.xml?

@rohitchhetri

It installed properly but I can't get access to web-based console. I even try to run through CLI
failed to connect to the controller: The controller is not available at localhost:9990: java.net.ConnectException: WFLYPRT0053: Could not connect to http-remoting://localhost:9990. The connection failed: WFLYPRT0053: Could not connect to http-remoting://localhost:9990. The connection failed: Connection refused

This is what I get in error

@jcuero
jcuero commented Apr 26, 2016

Hi,

Bug fix

tested-version :9.x - 10.0.0.Final

tested-distros :Scientific Linux release 6.7 (Carbon)

Starting wildfly: chown: missing operand after /var/run/wildfly' Trychown --help' for more information.

Replace the following lines:

    echo JBOSS_USER=$WILDFLY_USER >> $WILDFLY_SERVICE_CONF
    echo WILDFLY_HOME=\"$WILDFLY_DIR\" > $WILDFLY_SERVICE_CONF
    echo WILDFLY_USER=\"$WILDFLY_USER\" > $WILDFLY_SERVICE_CONF

For these:

    echo JBOSS_USER=\"$WILDFLY_USER\" >> $WILDFLY_SERVICE_CONF
    echo WILDFLY_HOME=\"$WILDFLY_DIR\" >> $WILDFLY_SERVICE_CONF
    echo WILDFLY_USER=\"$WILDFLY_USER\" >> $WILDFLY_SERVICE_CONF
@jlanza
jlanza commented May 3, 2016 edited

I think you should include another variable just in case you need the full setup:
WILDFLY_CONFIG="standalone-full"

Then you should change the config line to:
echo WILDFLY_CONFIG=$WILDFLY_CONFIG.xml >> $WILDFLY_SERVICE_CONF

Then the sed command on the configuration files will be similar.

Please note that in the final Wildfly 10 version there is no osgi-http in the configuration.

Thanks for the great job.

@DroidUnknown
DroidUnknown commented Jul 20, 2016 edited

After installation I am unable to start the server. This is what i am facing.
By using the command

service wildfly start

This happens after I run above command

1

The server log is

2016-07-20 09:18:10,571 INFO  [org.jboss.modules] (main) JBoss Modules version 1.5.1.Final
2016-07-20 09:18:11,255 INFO  [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final
2016-07-20 09:18:11,499 INFO  [org.jboss.as] (MSC service thread 1-2) WFLYSRV0049: WildFly Full 10.0.0.Final (WildFly Core 2.0.10.Final) starting
2016-07-20 09:18:11,502 DEBUG [org.jboss.as.config] (MSC service thread 1-2) Configured system properties:
    [Standalone] = 
    awt.toolkit = sun.awt.X11.XToolkit
    file.encoding = UTF-8
    file.encoding.pkg = sun.io
    file.separator = /
    java.awt.graphicsenv = sun.awt.X11GraphicsEnvironment
    java.awt.headless = true
    java.awt.printerjob = sun.print.PSPrinterJob
    java.class.path = /opt/wildfly/jboss-modules.jar
    java.class.version = 52.0
    java.endorsed.dirs = /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.91-0.b14.10.amzn1.x86_64/jre/lib/endorsed
    java.ext.dirs = /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.91-0.b14.10.amzn1.x86_64/jre/lib/ext:/usr/java/packages/lib/ext
    java.home = /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.91-0.b14.10.amzn1.x86_64/jre
    java.io.tmpdir = /tmp
    java.library.path = /usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib
    java.net.preferIPv4Stack = true
    java.runtime.name = OpenJDK Runtime Environment
    java.runtime.version = 1.8.0_91-b14
    java.specification.name = Java Platform API Specification
    java.specification.vendor = Oracle Corporation
    java.specification.version = 1.8
    java.util.logging.manager = org.jboss.logmanager.LogManager
    java.vendor = Oracle Corporation
    java.vendor.url = http://java.oracle.com/
    java.vendor.url.bug = http://bugreport.sun.com/bugreport/
    java.version = 1.8.0_91
    java.vm.info = mixed mode
    java.vm.name = OpenJDK 64-Bit Server VM
    java.vm.specification.name = Java Virtual Machine Specification
    java.vm.specification.vendor = Oracle Corporation
    java.vm.specification.version = 1.8
    java.vm.vendor = Oracle Corporation
    java.vm.version = 25.91-b14
    javax.management.builder.initial = org.jboss.as.jmx.PluggableMBeanServerBuilder
    javax.xml.datatype.DatatypeFactory = __redirected.__DatatypeFactory
    javax.xml.parsers.DocumentBuilderFactory = __redirected.__DocumentBuilderFactory
    javax.xml.parsers.SAXParserFactory = __redirected.__SAXParserFactory
    javax.xml.stream.XMLEventFactory = __redirected.__XMLEventFactory
    javax.xml.stream.XMLInputFactory = __redirected.__XMLInputFactory
    javax.xml.stream.XMLOutputFactory = __redirected.__XMLOutputFactory
    javax.xml.transform.TransformerFactory = __redirected.__TransformerFactory
    javax.xml.validation.SchemaFactory:http://www.w3.org/2001/XMLSchema = __redirected.__SchemaFactory
    javax.xml.xpath.XPathFactory:http://java.sun.com/jaxp/xpath/dom = __redirected.__XPathFactory
    jboss.home.dir = /opt/wildfly
    jboss.host.name = ip-172-31-25-47
    jboss.modules.dir = /opt/wildfly/modules
    jboss.modules.system.pkgs = org.jboss.byteman
    jboss.node.name = ip-172-31-25-47
    jboss.qualified.host.name = ip-172-31-25-47
    jboss.server.base.dir = /opt/wildfly/standalone
    jboss.server.config.dir = /opt/wildfly/standalone/configuration
    jboss.server.data.dir = /opt/wildfly/standalone/data
    jboss.server.deploy.dir = /opt/wildfly/standalone/data/content
    jboss.server.log.dir = /opt/wildfly/standalone/log
    jboss.server.name = ip-172-31-25-47
    jboss.server.persist.config = true
    jboss.server.temp.dir = /opt/wildfly/standalone/tmp
    line.separator = 

    logging.configuration = file:/opt/wildfly/standalone/configuration/logging.properties
    module.path = /opt/wildfly/modules
    org.jboss.boot.log.file = /opt/wildfly/standalone/log/server.log
    org.jboss.resolver.warning = true
    org.xml.sax.driver = __redirected.__XMLReaderFactory
    os.arch = amd64
    os.name = Linux
    os.version = 4.4.11-23.53.amzn1.x86_64
    path.separator = :
    sun.arch.data.model = 64
    sun.boot.class.path = /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.91-0.b14.10.amzn1.x86_64/jre/lib/resources.jar:/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.91-0.b14.10.amzn1.x86_64/jre/lib/rt.jar:/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.91-0.b14.10.amzn1.x86_64/jre/lib/sunrsasign.jar:/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.91-0.b14.10.amzn1.x86_64/jre/lib/jsse.jar:/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.91-0.b14.10.amzn1.x86_64/jre/lib/jce.jar:/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.91-0.b14.10.amzn1.x86_64/jre/lib/charsets.jar:/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.91-0.b14.10.amzn1.x86_64/jre/lib/jfr.jar:/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.91-0.b14.10.amzn1.x86_64/jre/classes
    sun.boot.library.path = /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.91-0.b14.10.amzn1.x86_64/jre/lib/amd64
    sun.cpu.endian = little
    sun.cpu.isalist = 
    sun.io.unicode.encoding = UnicodeLittle
    sun.java.command = /opt/wildfly/jboss-modules.jar -mp /opt/wildfly/modules org.jboss.as.standalone -Djboss.home.dir=/opt/wildfly -Djboss.server.base.dir=/opt/wildfly/standalone
    sun.java.launcher = SUN_STANDARD
    sun.jnu.encoding = UTF-8
    sun.management.compiler = HotSpot 64-Bit Tiered Compilers
    sun.os.patch.level = unknown
    user.country = US
    user.dir = /opt/wildfly-10.0.0.Final/bin
    user.home = /root
    user.language = en
    user.name = root
    user.timezone = Etc/UTC
2016-07-20 09:18:11,502 DEBUG [org.jboss.as.config] (MSC service thread 1-2) VM Arguments: -D[Standalone] -Xms2048m -Xmx2048m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Dorg.jboss.boot.log.file=/opt/wildfly/standalone/log/server.log -Dlogging.configuration=file:/opt/wildfly/standalone/configuration/logging.properties 
2016-07-20 09:18:16,598 INFO  [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)
2016-07-20 09:18:16,664 INFO  [org.xnio] (MSC service thread 1-2) XNIO version 3.3.4.Final
2016-07-20 09:18:16,708 INFO  [org.xnio.nio] (MSC service thread 1-2) XNIO NIO Implementation Version 3.3.4.Final
2016-07-20 09:18:16,919 INFO  [org.jboss.remoting] (MSC service thread 1-2) JBoss Remoting version 4.0.18.Final
2016-07-20 09:18:17,066 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 46) WFLYNAM0001: Activating Naming Subsystem
2016-07-20 09:18:16,992 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 38) WFLYCLINF0001: Activating Infinispan subsystem.
2016-07-20 09:18:17,085 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 53) WFLYSEC0002: Activating Security Subsystem
2016-07-20 09:18:17,104 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 56) WFLYWS0002: Activating WebServices Extension
2016-07-20 09:18:16,975 INFO  [org.jboss.as.jsf] (ServerService Thread Pool -- 44) WFLYJSF0007: Activated the following JSF Implementations: [main]
2016-07-20 09:18:17,087 WARN  [org.jboss.as.txn] (ServerService Thread Pool -- 54) WFLYTX0013: Node identifier property is set to the default value. Please make sure it is unique.
2016-07-20 09:18:17,363 INFO  [org.wildfly.extension.io] (ServerService Thread Pool -- 37) WFLYIO001: Worker 'default' has auto-configured to 2 core threads with 16 task threads based on your 1 available processors
2016-07-20 09:18:17,433 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 55) WFLYUT0003: Undertow 1.3.15.Final starting
2016-07-20 09:18:17,849 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0003: Undertow 1.3.15.Final starting
2016-07-20 09:18:17,861 INFO  [org.jboss.as.security] (MSC service thread 1-1) WFLYSEC0001: Current PicketBox version=4.9.4.Final
2016-07-20 09:18:17,850 INFO  [org.jboss.as.connector] (MSC service thread 1-2) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar 1.3.2.Final)
2016-07-20 09:18:18,081 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 33) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
2016-07-20 09:18:18,162 INFO  [org.jboss.as.naming] (MSC service thread 1-1) WFLYNAM0003: Starting Naming Service
2016-07-20 09:18:18,173 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-2) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default]
2016-07-20 09:18:18,708 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-2) WFLYJCA0018: Started Driver service with driver-name = h2
2016-07-20 09:18:19,244 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 55) WFLYUT0014: Creating file handler for path '/opt/wildfly/welcome-content' with options [directory-listing: 'false', follow-symlink: 'false', case-sensitive: 'true', safe-symlink-paths: '[]']
2016-07-20 09:18:19,731 INFO  [org.jboss.as.ejb3] (MSC service thread 1-1) WFLYEJB0482: Strict pool mdb-strict-max-pool is using a max instance size of 4 (per class), which is derived from the number of CPUs on this host.
2016-07-20 09:18:19,733 INFO  [org.jboss.as.ejb3] (MSC service thread 1-2) WFLYEJB0481: Strict pool slsb-strict-max-pool is using a max instance size of 16 (per class), which is derived from thread worker pool sizing.
2016-07-20 09:18:19,943 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0012: Started server default-server.
2016-07-20 09:18:20,327 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0006: Undertow HTTP listener default listening on 0.0.0.0:28080
2016-07-20 09:18:20,328 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0018: Host default-host starting
2016-07-20 09:18:21,779 INFO  [org.jboss.ws.common.management] (MSC service thread 1-1) JBWS022052: Starting JBossWS 5.1.3.Final (Apache CXF 3.1.4) 
2016-07-20 09:18:22,045 INFO  [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-1) ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.0.Final
2016-07-20 09:18:22,208 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-1) WFLYDS0013: Started FileSystemDeploymentService for directory /opt/wildfly/standalone/deployments
2016-07-20 09:18:22,208 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS]
2016-07-20 09:18:23,028 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management
2016-07-20 09:18:23,028 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990
2016-07-20 09:18:23,029 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 10.0.0.Final (WildFly Core 2.0.10.Final) started in 13530ms - Started 267 of 553 services (371 services are lazy, passive or on-demand)
2016-07-20 09:20:40,572 INFO  [org.jboss.as.server] (Thread-2) WFLYSRV0220: Server shutdown has been requested.
2016-07-20 09:20:40,617 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) WFLYJCA0010: Unbound data source [java:jboss/datasources/ExampleDS]
2016-07-20 09:20:40,762 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0019: Host default-host stopping
2016-07-20 09:20:40,780 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0008: Undertow HTTP listener default suspending
2016-07-20 09:20:40,781 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0007: Undertow HTTP listener default stopped, was bound to 0.0.0.0:28080
2016-07-20 09:20:40,781 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) WFLYJCA0019: Stopped Driver service with driver-name = h2
2016-07-20 09:20:40,785 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0004: Undertow 1.3.15.Final stopping
2016-07-20 09:20:40,815 INFO  [org.jboss.as] (MSC service thread 1-1) WFLYSRV0050: WildFly Full 10.0.0.Final (WildFly Core 2.0.10.Final) stopped in 206ms

@steamidea

Works on WildFly 10 final with CentOS 7

@avajadi
avajadi commented Aug 19, 2016

Lines 160 - 161 in the script both overwrite the file pointed to by $WILDFLY_SERVICE_CONF:
echo WILDFLY_HOME="$WILDFLY_DIR" > $WILDFLY_SERVICE_CONF
echo WILDFLY_USER="$WILDFLY_USER" > $WILDFLY_SERVICE_CONF

should be
echo WILDFLY_HOME="$WILDFLY_DIR" >> $WILDFLY_SERVICE_CONF
echo WILDFLY_USER="$WILDFLY_USER" >> $WILDFLY_SERVICE_CONF

@filipepgoes
filipepgoes commented Sep 6, 2016 edited

@rohitchhetri

I solved the problem of the non appearance of the management console by changing the value of JAVA_HOME in /etc/default/wildfly from /usr/lib/jvm/default-java (Ubuntu Cloud Server's pre-installed jre7) to /usr/lib/jvm/jdk1.8.0_102 (jdk8 installed by me).

@damgel
damgel commented Oct 9, 2016

hey why dont you remove -q flag on wget to get show progress?, it might be helpful on slow internet connections..

@talk2gupta

Dear Sir,

I am unable to start the server. Pls. help

root@ubuntu:~# /etc/init.d/wildfly start

  • Starting WildFly Application Server wildfly [ OK ]
  • WildFly Application Server hasn't started within the timeout allowed
  • please review file "/var/log/wildfly/console.log" to see the status of the service

root@ubuntu:~# cat /var/log/wildfly/console.log

JBoss Bootstrap Environment

JBOSS_HOME: /srv/wildfly

JAVA: /usr/lib/jvm/java-8-oracle/bin/java

JAVA_OPTS: -server -Xms2048m -Xmx8192m -XX:MetaspaceSize=1024M -XX:MaxMetaspaceSize=2048m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true

=========================================================================

Picked up _JAVA_OPTIONS: -Xmx8192m
16:07:45,042 INFO [org.jboss.modules] (main) JBoss Modules version 1.5.1.Final
16:07:45,250 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final
16:07:45,348 INFO [org.jboss.as] (MSC service thread 1-7) WFLYSRV0049: WildFly Full 10.0.0.Final (WildFly Core 2.0.10.Final) starting
16:07:47,066 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0015: Re-attempting failed deployment unifiedpush-server-wildfly.war
16:07:47,068 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0015: Re-attempting failed deployment unifiedpush-auth-server.war
16:07:48,122 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)
16:07:48,168 INFO [org.xnio] (MSC service thread 1-3) XNIO version 3.3.4.Final
16:07:48,179 INFO [org.xnio.nio] (MSC service thread 1-3) XNIO NIO Implementation Version 3.3.4.Final
16:07:48,215 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 41) WFLYCLINF0001: Activating Infinispan subsystem.
16:07:48,241 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 36) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
16:07:48,241 INFO [org.wildfly.extension.io] (ServerService Thread Pool -- 40) WFLYIO001: Worker 'default' has auto-configured to 12 core threads with 96 task threads based on your 6 available processors
16:07:48,256 INFO [org.wildfly.iiop.openjdk] (ServerService Thread Pool -- 42) WFLYIIOP0001: Activating IIOP Subsystem
16:07:48,282 WARN [org.jboss.as.txn] (ServerService Thread Pool -- 60) WFLYTX0013: Node identifier property is set to the default value. Please make sure it is unique.
16:07:48,286 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 48) WFLYJSF0007: Activated the following JSF Implementations: [main]
16:07:48,299 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 36) WFLYJCA0005: Deploying non-JDBC-compliant driver class org.postgresql.Driver (version 9.4)
16:07:48,301 INFO [org.jboss.remoting] (MSC service thread 1-3) JBoss Remoting version 4.0.18.Final
16:07:48,317 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 52) WFLYNAM0001: Activating Naming Subsystem
16:07:48,324 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 62) WFLYWS0002: Activating WebServices Extension
16:07:48,326 INFO [org.jboss.as.security] (ServerService Thread Pool -- 59) WFLYSEC0002: Activating Security Subsystem
16:07:48,350 INFO [org.jboss.as.security] (MSC service thread 1-4) WFLYSEC0001: Current PicketBox version=4.9.4.Final
16:07:48,396 INFO [org.jboss.as.connector] (MSC service thread 1-5) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar 1.3.2.Final)
16:07:48,413 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-4) WFLYJCA0018: Started Driver service with driver-name = h2
16:07:48,413 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-2) WFLYJCA0018: Started Driver service with driver-name = psqlup
16:07:48,423 INFO [org.jboss.as.naming] (MSC service thread 1-2) WFLYNAM0003: Starting Naming Service
16:07:48,431 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) WFLYUT0003: Undertow 1.3.15.Final starting
16:07:48,432 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 61) WFLYUT0003: Undertow 1.3.15.Final starting
16:07:48,433 INFO [org.jboss.as.mail.extension] (MSC service thread 1-1) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default]
16:07:48,603 INFO [org.jboss.as.ejb3] (MSC service thread 1-2) WFLYEJB0482: Strict pool mdb-strict-max-pool is using a max instance size of 24 (per class), which is derived from the number of CPUs on this host.
16:07:48,603 INFO [org.jboss.as.ejb3] (MSC service thread 1-7) WFLYEJB0481: Strict pool slsb-strict-max-pool is using a max instance size of 96 (per class), which is derived from thread worker pool sizing.
16:07:48,637 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 61) WFLYUT0014: Creating file handler for path '/srv/wildfly/welcome-content' with options [directory-listing: 'false', follow-symlink: 'false', case-sensitive: 'true', safe-symlink-paths: '[]']
16:07:48,663 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) WFLYUT0012: Started server default-server.
16:07:48,678 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0018: Host default-host starting
16:07:48,837 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) WFLYUT0006: Undertow HTTP listener default listening on 0.0.0.0:8080
16:07:48,982 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-3) WFLYJCA0001: Bound data source [java:jboss/datasources/UnifiedPushDS]
16:07:48,982 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS]
16:07:48,983 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-3) WFLYJCA0001: Bound data source [java:jboss/datasources/KeycloakDS]
16:07:49,045 INFO [org.wildfly.iiop.openjdk] (MSC service thread 1-5) WFLYIIOP0009: CORBA ORB Service started
16:07:49,254 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0027: Starting deployment of "unifiedpush-auth-server.war" (runtime-name: "unifiedpush-auth-server.war")
16:07:49,254 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0027: Starting deployment of "skymetups.war" (runtime-name: "skymetups.war")
16:07:49,389 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-1) WFLYDS0013: Started FileSystemDeploymentService for directory /srv/wildfly/standalone/deployments
16:07:49,365 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0027: Starting deployment of "unifiedpush-server-wildfly.war" (runtime-name: "unifiedpush-server-wildfly.war")
16:07:49,316 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221000: live Message Broker is starting with configuration Broker Configuration (clustered=false,journalDirectory=/srv/wildfly/standalone/data/activemq/journal,bindingsDirectory=/srv/wildfly/standalone/data/activemq/bindings,largeMessagesDirectory=/srv/wildfly/standalone/data/activemq/largemessages,pagingDirectory=/srv/wildfly/standalone/data/activemq/paging)
16:07:49,452 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-6) ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.0.Final
16:07:49,458 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-8) ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.0.Final
16:07:49,465 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221012: Using AIO Journal
16:07:49,698 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221043: Protocol module found: [artemis-server]. Adding protocol support for: CORE
16:07:49,703 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221043: Protocol module found: [artemis-amqp-protocol]. Adding protocol support for: AMQP
16:07:49,720 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221043: Protocol module found: [artemis-hornetq-protocol]. Adding protocol support for: HORNETQ
16:07:49,721 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221043: Protocol module found: [artemis-stomp-protocol]. Adding protocol support for: STOMP
16:07:49,903 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) WFLYUT0006: Undertow HTTPS listener https listening on 0.0.0.0:8443
16:07:50,049 INFO [org.jboss.ws.common.management] (MSC service thread 1-8) JBWS022052: Starting JBossWS 5.1.3.Final (Apache CXF 3.1.4)
16:07:52,114 INFO [org.jboss.weld.deployer] (MSC service thread 1-7) WFLYWELD0003: Processing weld deployment skymetups.war
16:07:52,215 INFO [org.hibernate.validator.internal.util.Version] (MSC service thread 1-7) HV000001: Hibernate Validator 5.2.3.Final
16:07:52,475 ERROR stderr:71 - log4j:ERROR Could not find value for key log4j.appender.warn
16:07:52,485 ERROR stderr:71 - log4j:ERROR Could not instantiate appender named "warn".
16:07:52,657 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-4) WFLYJCA0005: Deploying non-JDBC-compliant driver class org.postgresql.Driver (version 8.4)
16:07:52,658 INFO [org.jboss.weld.deployer] (MSC service thread 1-4) WFLYWELD0006: Starting Services for CDI deployment: skymetups.war
16:07:52,723 INFO [org.jboss.weld.Version] (MSC service thread 1-4) WELD-000900: 2.3.2 (Final)
16:07:52,774 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-8) WFLYJCA0018: Started Driver service with driver-name = skymetups.war_org.postgresql.Driver_8_4
16:07:52,774 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0009: Starting weld service for deployment skymetups.war
16:07:53,235 INFO [org.jboss.as.jpa] (MSC service thread 1-8) WFLYJPA0002: Read persistence.xml for unifiedpush-default
16:07:53,255 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry lib/snakeyaml-1.13.jar in /content/unifiedpush-auth-server.war/WEB-INF/lib/liquibase-core-3.4.1.jar does not point to a valid jar for a Class-Path reference.
16:07:53,367 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry jaxb-api.jar in /content/unifiedpush-auth-server.war/WEB-INF/lib/jaxb-impl-2.2.4.jar does not point to a valid jar for a Class-Path reference.
16:07:53,367 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry activation.jar in /content/unifiedpush-auth-server.war/WEB-INF/lib/jaxb-impl-2.2.4.jar does not point to a valid jar for a Class-Path reference.
16:07:53,367 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry jsr173_1.0_api.jar in /content/unifiedpush-auth-server.war/WEB-INF/lib/jaxb-impl-2.2.4.jar does not point to a valid jar for a Class-Path reference.
16:07:53,367 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry jaxb1-impl.jar in /content/unifiedpush-auth-server.war/WEB-INF/lib/jaxb-impl-2.2.4.jar does not point to a valid jar for a Class-Path reference.
16:07:53,395 INFO [org.jboss.as.jpa] (MSC service thread 1-5) WFLYJPA0002: Read persistence.xml for keycloak-default
16:07:53,666 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 65) WFLYJPA0010: Starting Persistence Unit (phase 1 of 2) Service 'unifiedpush-server-wildfly.war#unifiedpush-default'
16:07:53,700 INFO [org.hibernate.jpa.internal.util.LogHelper] (ServerService Thread Pool -- 65) HHH000204: Processing PersistenceUnitInfo [
name: unifiedpush-default
...]
16:07:53,733 WARN [org.jboss.as.dependency.private] (MSC service thread 1-7) WFLYSRV0018: Deployment "deployment.unifiedpush-auth-server.war" is using a private module ("org.codehaus.jackson.jackson-core-asl:main") which may be changed or removed in future versions without notice.
16:07:53,734 WARN [org.jboss.as.dependency.private] (MSC service thread 1-7) WFLYSRV0018: Deployment "deployment.unifiedpush-auth-server.war" is using a private module ("org.codehaus.jackson.jackson-mapper-asl:main") which may be changed or removed in future versions without notice.
16:07:53,734 WARN [org.jboss.as.dependency.private] (MSC service thread 1-7) WFLYSRV0018: Deployment "deployment.unifiedpush-auth-server.war" is using a private module ("org.infinispan:main") which may be changed or removed in future versions without notice.
16:07:53,760 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0003: Processing weld deployment unifiedpush-server-wildfly.war
16:07:54,508 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) WFLYEJB0473: JNDI bindings for session bean named 'HealthNetworkServiceImpl' in deployment unit 'deployment "unifiedpush-server-wildfly.war"' are as follows:

    java:global/ag-push/HealthNetworkServiceImpl!org.jboss.aerogear.unifiedpush.message.HealthNetworkService
    java:app/ag-push/HealthNetworkServiceImpl!org.jboss.aerogear.unifiedpush.message.HealthNetworkService
    java:module/HealthNetworkServiceImpl!org.jboss.aerogear.unifiedpush.message.HealthNetworkService
    java:global/ag-push/HealthNetworkServiceImpl
    java:app/ag-push/HealthNetworkServiceImpl
    java:module/HealthNetworkServiceImpl

16:07:54,537 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) WFLYEJB0473: JNDI bindings for session bean named 'MetricCollectionTrigger' in deployment unit 'deployment "unifiedpush-server-wildfly.war"' are as follows:

    java:global/ag-push/MetricCollectionTrigger!org.jboss.aerogear.unifiedpush.message.jms.MetricCollectionTrigger
    java:app/ag-push/MetricCollectionTrigger!org.jboss.aerogear.unifiedpush.message.jms.MetricCollectionTrigger
    java:module/MetricCollectionTrigger!org.jboss.aerogear.unifiedpush.message.jms.MetricCollectionTrigger
    java:global/ag-push/MetricCollectionTrigger
    java:app/ag-push/MetricCollectionTrigger
    java:module/MetricCollectionTrigger

16:07:54,537 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) WFLYEJB0473: JNDI bindings for session bean named 'ClientInstallationServiceImpl' in deployment unit 'deployment "unifiedpush-server-wildfly.war"' are as follows:

    java:global/ag-push/ClientInstallationServiceImpl!org.jboss.aerogear.unifiedpush.service.ClientInstallationService
    java:app/ag-push/ClientInstallationServiceImpl!org.jboss.aerogear.unifiedpush.service.ClientInstallationService
    java:module/ClientInstallationServiceImpl!org.jboss.aerogear.unifiedpush.service.ClientInstallationService
    java:global/ag-push/ClientInstallationServiceImpl
    java:app/ag-push/ClientInstallationServiceImpl
    java:module/ClientInstallationServiceImpl

16:07:54,537 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) WFLYEJB0473: JNDI bindings for session bean named 'VariantMetricInformationProducer' in deployment unit 'deployment "unifiedpush-server-wildfly.war"' are as follows:

    java:global/ag-push/VariantMetricInformationProducer!org.jboss.aerogear.unifiedpush.message.jms.VariantMetricInformationProducer
    java:app/ag-push/VariantMetricInformationProducer!org.jboss.aerogear.unifiedpush.message.jms.VariantMetricInformationProducer
    java:module/VariantMetricInformationProducer!org.jboss.aerogear.unifiedpush.message.jms.VariantMetricInformationProducer
    java:global/ag-push/VariantMetricInformationProducer
    java:app/ag-push/VariantMetricInformationProducer
    java:module/VariantMetricInformationProducer

16:07:54,538 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) WFLYEJB0473: JNDI bindings for session bean named 'PushMessageMetricsService' in deployment unit 'deployment "unifiedpush-server-wildfly.war"' are as follows:

    java:global/ag-push/PushMessageMetricsService!org.jboss.aerogear.unifiedpush.service.metrics.PushMessageMetricsService
    java:app/ag-push/PushMessageMetricsService!org.jboss.aerogear.unifiedpush.service.metrics.PushMessageMetricsService
    java:module/PushMessageMetricsService!org.jboss.aerogear.unifiedpush.service.metrics.PushMessageMetricsService
    java:global/ag-push/PushMessageMetricsService
    java:app/ag-push/PushMessageMetricsService
    java:module/PushMessageMetricsService

16:07:54,538 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) WFLYEJB0473: JNDI bindings for session bean named 'GenericVariantServiceImpl' in deployment unit 'deployment "unifiedpush-server-wildfly.war"' are as follows:

    java:global/ag-push/GenericVariantServiceImpl!org.jboss.aerogear.unifiedpush.service.GenericVariantService
    java:app/ag-push/GenericVariantServiceImpl!org.jboss.aerogear.unifiedpush.service.GenericVariantService
    java:module/GenericVariantServiceImpl!org.jboss.aerogear.unifiedpush.service.GenericVariantService
    java:global/ag-push/GenericVariantServiceImpl
    java:app/ag-push/GenericVariantServiceImpl
    java:module/GenericVariantServiceImpl

16:07:54,538 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) WFLYEJB0473: JNDI bindings for session bean named 'JmsClient' in deployment unit 'deployment "unifiedpush-server-wildfly.war"' are as follows:

    java:global/ag-push/JmsClient!org.jboss.aerogear.unifiedpush.message.util.JmsClient
    java:app/ag-push/JmsClient!org.jboss.aerogear.unifiedpush.message.util.JmsClient
    java:module/JmsClient!org.jboss.aerogear.unifiedpush.message.util.JmsClient
    java:global/ag-push/JmsClient
    java:app/ag-push/JmsClient
    java:module/JmsClient

16:07:54,538 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) WFLYEJB0473: JNDI bindings for session bean named 'HealthServiceImpl' in deployment unit 'deployment "unifiedpush-server-wildfly.war"' are as follows:

    java:global/ag-push/HealthServiceImpl!org.jboss.aerogear.unifiedpush.service.HealthDBService
    java:app/ag-push/HealthServiceImpl!org.jboss.aerogear.unifiedpush.service.HealthDBService
    java:module/HealthServiceImpl!org.jboss.aerogear.unifiedpush.service.HealthDBService
    java:global/ag-push/HealthServiceImpl
    java:app/ag-push/HealthServiceImpl
    java:module/HealthServiceImpl

16:07:54,538 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) WFLYEJB0473: JNDI bindings for session bean named 'MessageHolderWithVariantsProducer' in deployment unit 'deployment "unifiedpush-server-wildfly.war"' are as follows:

    java:global/ag-push/MessageHolderWithVariantsProducer!org.jboss.aerogear.unifiedpush.message.jms.MessageHolderWithVariantsProducer
    java:app/ag-push/MessageHolderWithVariantsProducer!org.jboss.aerogear.unifiedpush.message.jms.MessageHolderWithVariantsProducer
    java:module/MessageHolderWithVariantsProducer!org.jboss.aerogear.unifiedpush.message.jms.MessageHolderWithVariantsProducer
    java:global/ag-push/MessageHolderWithVariantsProducer
    java:app/ag-push/MessageHolderWithVariantsProducer
    java:module/MessageHolderWithVariantsProducer

16:07:54,538 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) WFLYEJB0473: JNDI bindings for session bean named 'MetricsCollector' in deployment unit 'deployment "unifiedpush-server-wildfly.war"' are as follows:

    java:global/ag-push/MetricsCollector!org.jboss.aerogear.unifiedpush.message.MetricsCollector
    java:app/ag-push/MetricsCollector!org.jboss.aerogear.unifiedpush.message.MetricsCollector
    java:module/MetricsCollector!org.jboss.aerogear.unifiedpush.message.MetricsCollector
    java:global/ag-push/MetricsCollector
    java:app/ag-push/MetricsCollector
    java:module/MetricsCollector

16:07:54,539 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) WFLYEJB0473: JNDI bindings for session bean named 'NotificationRouter' in deployment unit 'deployment "unifiedpush-server-wildfly.war"' are as follows:

    java:global/ag-push/NotificationRouter!org.jboss.aerogear.unifiedpush.message.NotificationRouter
    java:app/ag-push/NotificationRouter!org.jboss.aerogear.unifiedpush.message.NotificationRouter
    java:module/NotificationRouter!org.jboss.aerogear.unifiedpush.message.NotificationRouter
    java:global/ag-push/NotificationRouter
    java:app/ag-push/NotificationRouter
    java:module/NotificationRouter

16:07:54,539 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) WFLYEJB0473: JNDI bindings for session bean named 'NotificationDispatcher' in deployment unit 'deployment "unifiedpush-server-wildfly.war"' are as follows:

    java:global/ag-push/NotificationDispatcher!org.jboss.aerogear.unifiedpush.message.NotificationDispatcher
    java:app/ag-push/NotificationDispatcher!org.jboss.aerogear.unifiedpush.message.NotificationDispatcher
    java:module/NotificationDispatcher!org.jboss.aerogear.unifiedpush.message.NotificationDispatcher
    java:global/ag-push/NotificationDispatcher
    java:app/ag-push/NotificationDispatcher
    java:module/NotificationDispatcher

16:07:54,539 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) WFLYEJB0473: JNDI bindings for session bean named 'DeleteOldPushMessageInformationScheduler' in deployment unit 'deployment "unifiedpush-server-wildfly.war"' are as follows:

    java:global/ag-push/DeleteOldPushMessageInformationScheduler!org.jboss.aerogear.unifiedpush.service.metrics.DeleteOldPushMessageInformationScheduler
    java:app/ag-push/DeleteOldPushMessageInformationScheduler!org.jboss.aerogear.unifiedpush.service.metrics.DeleteOldPushMessageInformationScheduler
    java:module/DeleteOldPushMessageInformationScheduler!org.jboss.aerogear.unifiedpush.service.metrics.DeleteOldPushMessageInformationScheduler
    java:global/ag-push/DeleteOldPushMessageInformationScheduler
    java:app/ag-push/DeleteOldPushMessageInformationScheduler
    java:module/DeleteOldPushMessageInformationScheduler

16:07:54,539 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) WFLYEJB0473: JNDI bindings for session bean named 'ServiceDisposalScheduler' in deployment unit 'deployment "unifiedpush-server-wildfly.war"' are as follows:

    java:global/ag-push/ServiceDisposalScheduler!org.jboss.aerogear.unifiedpush.message.serviceHolder.ServiceDisposalScheduler
    java:app/ag-push/ServiceDisposalScheduler!org.jboss.aerogear.unifiedpush.message.serviceHolder.ServiceDisposalScheduler
    java:module/ServiceDisposalScheduler!org.jboss.aerogear.unifiedpush.message.serviceHolder.ServiceDisposalScheduler
    java:global/ag-push/ServiceDisposalScheduler
    java:app/ag-push/ServiceDisposalScheduler
    java:module/ServiceDisposalScheduler

16:07:54,539 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) WFLYEJB0473: JNDI bindings for session bean named 'PushApplicationServiceImpl' in deployment unit 'deployment "unifiedpush-server-wildfly.war"' are as follows:

    java:global/ag-push/PushApplicationServiceImpl!org.jboss.aerogear.unifiedpush.service.PushApplicationService
    java:app/ag-push/PushApplicationServiceImpl!org.jboss.aerogear.unifiedpush.service.PushApplicationService
    java:module/PushApplicationServiceImpl!org.jboss.aerogear.unifiedpush.service.PushApplicationService
    java:global/ag-push/PushApplicationServiceImpl
    java:app/ag-push/PushApplicationServiceImpl
    java:module/PushApplicationServiceImpl

16:07:54,539 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) WFLYEJB0473: JNDI bindings for session bean named 'TokenLoader' in deployment unit 'deployment "unifiedpush-server-wildfly.war"' are as follows:

    java:global/ag-push/TokenLoader!org.jboss.aerogear.unifiedpush.message.TokenLoader
    java:app/ag-push/TokenLoader!org.jboss.aerogear.unifiedpush.message.TokenLoader
    java:module/TokenLoader!org.jboss.aerogear.unifiedpush.message.TokenLoader
    java:global/ag-push/TokenLoader
    java:app/ag-push/TokenLoader
    java:module/TokenLoader

16:07:54,541 INFO [org.hibernate.Version] (ServerService Thread Pool -- 65) HHH000412: Hibernate Core {5.0.7.Final}
16:07:54,543 INFO [org.hibernate.cfg.Environment] (ServerService Thread Pool -- 65) HHH000206: hibernate.properties not found
16:07:54,545 INFO [org.hibernate.cfg.Environment] (ServerService Thread Pool -- 65) HHH000021: Bytecode provider name : javassist
16:07:54,554 WARN [org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl] (ServerService Thread Pool -- 65) HHH000059: Defining hibernate.transaction.flush_before_completion=true ignored in HEM
16:07:54,582 INFO [org.hibernate.orm.deprecation] (ServerService Thread Pool -- 65) HHH90000001: Found usage of deprecated setting for specifying Scanner [hibernate.ejb.resource_scanner]; use [hibernate.archive.scanner] instead
16:07:54,592 INFO [org.hibernate.annotations.common.Version] (ServerService Thread Pool -- 65) HCANN000001: Hibernate Commons Annotations {5.0.1.Final}
16:07:54,753 WARN [org.hibernate.orm.deprecation] (ServerService Thread Pool -- 65) HHH90000012: Recognized obsolete hibernate namespace http://hibernate.sourceforge.net/hibernate-mapping. Use namespace http://www.hibernate.org/dtd/hibernate-mapping instead. Support for obsolete DTD/XSD namespaces may be removed at any time.
16:07:54,836 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 66) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
16:07:54,839 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 66) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
16:07:54,844 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 67) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
16:07:54,845 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 67) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
16:07:54,857 INFO [org.jboss.weld.deployer] (MSC service thread 1-6) WFLYWELD0006: Starting Services for CDI deployment: unifiedpush-server-wildfly.war
16:07:54,870 INFO [org.jboss.weld.deployer] (MSC service thread 1-8) WFLYWELD0009: Starting weld service for deployment unifiedpush-server-wildfly.war
16:07:55,193 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 67) WFLYCLINF0002: Started client-mappings cache from ejb container
16:07:55,330 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 65) WFLYJPA0010: Starting Persistence Unit (phase 2 of 2) Service 'unifiedpush-server-wildfly.war#unifiedpush-default'
16:07:55,512 WARN [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (ServerService Thread Pool -- 65) IJ000407: No lazy enlistment available for UnifiedPushDS
16:07:55,529 INFO [org.hibernate.dialect.Dialect] (ServerService Thread Pool -- 65) HHH000400: Using dialect: org.hibernate.dialect.PostgreSQL92Dialect
16:07:55,752 INFO [org.hibernate.engine.jdbc.env.internal.LobCreatorBuilderImpl] (ServerService Thread Pool -- 65) HHH000424: Disabling contextual LOB creation as createClob() method threw error : java.lang.reflect.InvocationTargetException
16:07:55,755 INFO [org.hibernate.type.BasicTypeRegistry] (ServerService Thread Pool -- 65) HHH000270: Type registration [java.util.UUID] overrides previous : org.hibernate.type.UUIDBinaryType@51d7fdf1
16:07:55,761 INFO [org.hibernate.envers.boot.internal.EnversServiceImpl] (ServerService Thread Pool -- 65) Envers integration enabled? : true
16:07:55,933 WARN [org.hibernate.cfg.annotations.reflection.JPAOverriddenAnnotationReader] (ServerService Thread Pool -- 65) HHH000207: Property org.jboss.aerogear.unifiedpush.api.iOSVariant.certificateData not found in class but described in (possible typo error)
16:07:55,948 WARN [org.hibernate.cfg.AnnotationBinder] (ServerService Thread Pool -- 65) HHH000457: Joined inheritance hierarchy [org.jboss.aerogear.unifiedpush.api.Variant] defined explicit @DiscriminatorColumn. Legacy Hibernate behavior was to ignore the @DiscriminatorColumn. However, as part of issue HHH-6911 we now apply the explicit @DiscriminatorColumn. If you would prefer the legacy behavior, enable the hibernate.discriminator.ignore_explicit_for_joined setting (hibernate.discriminator.ignore_explicit_for_joined=true)
16:07:56,552 INFO [org.hibernate.tool.hbm2ddl.SchemaValidator] (ServerService Thread Pool -- 65) HHH000229: Running schema validator
16:12:32,358 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221014: 2% loaded
16:12:55,156 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0348: Timeout after [300] seconds waiting for service container stability. Operation will roll back. Step that first updated the service container was 'add' at address '[
("core-service" => "management"),
("management-interface" => "http-interface")
]'
16:12:55,174 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-7) WFLYJCA0019: Stopped Driver service with driver-name = skymetups.war_org.postgresql.Driver_8_4
16:12:55,197 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 70) WFLYJPA0011: Stopping Persistence Unit (phase 2 of 2) Service 'unifiedpush-server-wildfly.war#unifiedpush-default'
16:12:55,209 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 71) WFLYJPA0011: Stopping Persistence Unit (phase 1 of 2) Service 'unifiedpush-server-wildfly.war#unifiedpush-default'
16:12:55,286 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 72) WFLYCLINF0003: Stopped client-mappings cache from ejb container
16:12:55,308 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0028: Stopped deployment unifiedpush-server-wildfly.war (runtime-name: unifiedpush-server-wildfly.war) in 145ms
16:12:55,308 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0028: Stopped deployment skymetups.war (runtime-name: skymetups.war) in 146ms
16:12:55,318 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0028: Stopped deployment unifiedpush-auth-server.war (runtime-name: unifiedpush-auth-server.war) in 155ms
16:12:55,320 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) WFLYUT0008: Undertow HTTPS listener https suspending
16:12:55,320 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) WFLYUT0007: Undertow HTTPS listener https stopped, was bound to 0.0.0.0:8443
16:12:55,405 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221014: 4% loaded
16:12:55,615 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221014: 6% loaded
16:12:55,727 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221014: 8% loaded
16:12:55,980 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221014: 10% loaded
16:12:56,240 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221014: 12% loaded
16:12:56,501 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221014: 14% loaded
16:12:56,752 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221014: 16% loaded
16:12:56,867 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221014: 18% loaded
16:12:57,001 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221014: 20% loaded
16:12:57,132 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221014: 22% loaded
16:12:57,283 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221014: 24% loaded
16:12:57,411 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221014: 26% loaded
16:12:57,534 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221014: 28% loaded
16:12:57,726 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221014: 30% loaded
16:12:57,853 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221014: 32% loaded
16:12:57,984 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221014: 34% loaded
16:12:58,134 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221014: 36% loaded
16:12:58,273 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221014: 38% loaded
16:12:58,412 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221014: 40% loaded
16:12:58,526 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221014: 42% loaded
16:12:58,638 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221014: 44% loaded
16:12:58,819 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221014: 46% loaded
16:12:58,934 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221014: 48% loaded
16:12:59,059 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221014: 50% loaded
16:12:59,197 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221014: 52% loaded
16:12:59,321 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221014: 54% loaded
16:12:59,441 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221014: 56% loaded
16:12:59,576 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221014: 58% loaded
16:12:59,775 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221014: 60% loaded
16:12:59,898 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221014: 62% loaded
16:13:00,015 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221014: 64% loaded
16:13:00,116 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221014: 66% loaded
16:13:00,223 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221014: 68% loaded
16:13:00,329 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221014: 70% loaded
16:13:00,331 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0190: Step handler org.jboss.as.controller.AbstractControllerService$ModelControllerServiceInitializationBootStepHandler$1@3a41d897 for operation {"operation" => "boottime-controller-initializer-step","address" => []} at address [] failed handling operation rollback -- java.util.concurrent.TimeoutException: java.util.concurrent.TimeoutException
at org.jboss.as.controller.OperationContextImpl.waitForRemovals(OperationContextImpl.java:511)
at org.jboss.as.controller.AbstractOperationContext$Step.handleResult(AbstractOperationContext.java:1369)
at org.jboss.as.controller.AbstractOperationContext$Step.finalizeInternal(AbstractOperationContext.java:1328)
at org.jboss.as.controller.AbstractOperationContext$Step.finalizeStep(AbstractOperationContext.java:1311)
at org.jboss.as.controller.AbstractOperationContext$Step.access$300(AbstractOperationContext.java:1185)
at org.jboss.as.controller.AbstractOperationContext.executeResultHandlerPhase(AbstractOperationContext.java:767)
at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:644)
at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:370)
at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1344)
at org.jboss.as.controller.ModelControllerImpl.boot(ModelControllerImpl.java:485)
at org.jboss.as.controller.AbstractControllerService.boot(AbstractControllerService.java:387)
at org.jboss.as.controller.AbstractControllerService.boot(AbstractControllerService.java:349)
at org.jboss.as.server.ServerService.boot(ServerService.java:392)
at org.jboss.as.server.ServerService.boot(ServerService.java:365)
at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:299)
at java.lang.Thread.run(Thread.java:745)

16:13:00,332 ERROR [org.jboss.as.controller.client] (Controller Boot Thread) WFLYCTL0190: Step handler org.jboss.as.controller.AbstractControllerService$ModelControllerServiceInitializationBootStepHandler$1@3a41d897 for operation {"operation" => "boottime-controller-initializer-step","address" => []} at address [] failed handling operation rollback -- java.util.concurrent.TimeoutException
16:13:00,333 ERROR [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0022: Deploy of deployment "skymetups.war" was rolled back with no failure message
16:13:00,430 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221014: 72% loaded
16:13:00,610 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221014: 74% loaded
16:13:00,713 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221014: 76% loaded
16:13:00,825 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221014: 78% loaded
16:13:00,924 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221014: 80% loaded
16:13:01,038 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221014: 82% loaded
16:13:01,138 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221014: 84% loaded
16:13:01,254 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221014: 86% loaded
16:13:01,351 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221014: 88% loaded
16:13:01,514 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221014: 90% loaded
16:13:01,609 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221014: 92% loaded
16:13:01,704 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221014: 94% loaded
16:13:01,799 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221014: 96% loaded
16:13:01,895 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221014: 98% loaded
16:13:02,179 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-1) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor acceptor
16:13:02,180 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-5) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor-throughput acceptor
16:13:02,180 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-2) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor acceptor
16:13:02,180 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-8) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor-throughput acceptor
16:13:02,231 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221007: Server is now live
16:13:02,231 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221001: Apache ActiveMQ Artemis Message Broker version 1.1.0.wildfly-011 [nodeID=4a199291-2f14-11e6-8dd1-df02c005a29f]
16:13:02,235 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221003: trying to deploy queue jms.queue.WNSTokenBatchQueue
16:13:02,240 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 91) AMQ221003: trying to deploy queue jms.queue.AllBatchesLoadedQueue
16:13:02,246 INFO [org.apache.activemq.artemis.jms.server] (ServerService Thread Pool -- 89) AMQ121005: Invalid "host" value "0.0.0.0" detected for "http-connector" connector. Switching to "ubuntu". If this new address is incorrect please manually configure the connector to use the proper one.
16:13:02,269 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 89) WFLYMSGAMQ0002: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory
16:13:02,269 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 87) AMQ221003: trying to deploy queue jms.queue.BatchLoadedQueue
16:13:02,270 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 86) AMQ221003: trying to deploy queue jms.queue.AdmPushMessageQueue
16:13:02,271 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 88) WFLYMSGAMQ0002: Bound messaging object to jndi name java:/ConnectionFactory
16:13:02,271 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 80) AMQ221003: trying to deploy queue jms.queue.APNsPushMessageQueue
16:13:02,272 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 90) AMQ221003: trying to deploy queue jms.queue.SimplePushMessageQueue
16:13:02,273 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 84) AMQ221003: trying to deploy queue jms.queue.WNSPushMessageQueue
16:13:02,273 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 82) AMQ221003: trying to deploy queue jms.queue.MPNSTokenBatchQueue
16:13:02,274 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 81) AMQ221003: trying to deploy queue jms.queue.ExpiryQueue
16:13:02,274 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 79) AMQ221003: trying to deploy queue jms.queue.MPNSPushMessageQueue
16:13:02,275 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 83) AMQ221003: trying to deploy queue jms.queue.FreeServiceSlotQueue
16:13:02,276 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 85) AMQ221003: trying to deploy queue jms.queue.SimplePushTokenBatchQueue
16:13:02,276 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 77) AMQ221003: trying to deploy queue jms.queue.GCMPushMessageQueue
16:13:02,277 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 78) AMQ221003: trying to deploy queue jms.queue.APNsTokenBatchQueue
16:13:02,278 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 75) AMQ221003: trying to deploy queue jms.topic.MetricsProcessingStartedTopic
16:13:02,284 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 76) AMQ221003: trying to deploy queue jms.queue.AdmTokenBatchQueue
16:13:02,285 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 74) AMQ221003: trying to deploy queue jms.queue.GCMTokenBatchQueue
16:13:02,286 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 72) AMQ221003: trying to deploy queue jms.queue.TriggerVariantMetricCollectionQueue
16:13:02,286 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 73) AMQ221003: trying to deploy queue jms.queue.MetricsQueue
16:13:02,287 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 71) AMQ221003: trying to deploy queue jms.queue.DLQ
16:13:02,287 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 70) AMQ221003: trying to deploy queue jms.queue.TriggerMetricCollectionQueue
16:13:02,288 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 88) WFLYMSGAMQ0006: Unbound messaging object to jndi name java:/ConnectionFactory
16:13:02,289 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 89) WFLYMSGAMQ0006: Unbound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory
16:13:02,558 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 73) AMQ221002: Apache ActiveMQ Artemis Message Broker version 1.1.0.wildfly-011 [4a199291-2f14-11e6-8dd1-df02c005a29f] stopped
16:13:02,559 ERROR [org.jboss.as.server] (ServerService Thread Pool -- 37) WFLYSRV0022: Deploy of deployment "unifiedpush-auth-server.war" was rolled back with no failure message
16:13:02,559 ERROR [org.jboss.as.server] (ServerService Thread Pool -- 37) WFLYSRV0022: Deploy of deployment "unifiedpush-server-wildfly.war" was rolled back with no failure message
16:13:02,561 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0008: Undertow HTTP listener default suspending
16:13:02,561 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0007: Undertow HTTP listener default stopped, was bound to 0.0.0.0:8080
16:13:02,562 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-3) WFLYJCA0010: Unbound data source [java:jboss/datasources/UnifiedPushDS]
16:13:02,562 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-3) WFLYJCA0010: Unbound data source [java:jboss/datasources/KeycloakDS]
16:13:02,562 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-6) WFLYJCA0010: Unbound data source [java:jboss/datasources/ExampleDS]
16:13:02,568 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0019: Host default-host stopping
16:13:02,573 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0004: Undertow 1.3.15.Final stopping
16:13:02,580 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-2) WFLYJCA0019: Stopped Driver service with driver-name = h2
16:13:02,580 WARN [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (ServerService Thread Pool -- 44) IJ000615: Destroying active connection in pool: UnifiedPushDS (org.jboss.jca.adapters.jdbc.local.LocalManagedConnection@5ad4cd4e)
16:13:02,585 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-2) WFLYJCA0019: Stopped Driver service with driver-name = psqlup
16:13:02,603 FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
16:13:02,607 INFO [org.jboss.as.server] (Thread-2) WFLYSRV0220: Server shutdown has been requested.
16:13:02,615 INFO [org.jboss.as] (MSC service thread 1-1) WFLYSRV0050: WildFly Full 10.0.0.Final (WildFly Core 2.0.10.Final) stopped in 5ms
9421

@egv83
egv83 commented Dec 20, 2016

I can't start the service wildfly in centos 6, when I try it show me this message, how I fix it to work
/etc/init.d/wildfly start
Starting wildfly: chown: missing operand after /var/run/wildfly' Trychown --help' for more information.

@icharge
icharge commented Dec 24, 2016

Did you have a uninstall script ?
If no and how to ?

@daoudabeye

Hi, works well on CentOs 7...
Thank you

@JavaPauloMG

I'm using Ubutu 16.04 LST Server, but when i put the app inside "deployments" folder and start the service, the service dont start.

My app dosen't work, acess denied is the error in log file.

I need to create wildfly group? or i need to put wildfly user in super users group?

Thanks.

@xtecuan
xtecuan commented Feb 2, 2017

It work correctly in Red Hat Enterprise Linux Server release 7.2 (Maipo) , thanks for the script

@avreddy2

I'm able to install the wildfly as a service on RHEL 6.5. However, there is an issue with wildfly service. The wildfly service is stopping immediately after startup with following error message in logs:

WFLYSRV0220: Server shutdown has been requested via an OS signal

Any help you can provide would be greatly appreciated.

Thanks

@ymartin59

To leave official unzipped archive unmodified on disk, I create a "standalone" server structure out of installation directory with configuration, logs and applications, using startup properties to point to modules/lib at installation location. That way, it is easy to run multiple standalone instances or discard and rebuild an instance with scripts.

I recommend use of jboss-cli commands to configure application server instead of sed expressions on XML configuration file, to be robust to wildfly upgrades. See https://docs.jboss.org/author/display/WFLY10/CLI+Recipes

@jaywax
jaywax commented Mar 1, 2017

Works like a charm on Debian 8 and openjdk-8-jdk.
Thanks !

@dortegau

At idealista we have created an Ansible role based on this gist: https://github.com/idealista/wildfly-role/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment