[Slackbuilds-users] wildfly start/stop script

[Willy Sudiarto Raharjo]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> i found that removing "controller=127.0.0.1:9999" from the shutdown command
> makes it work (i also removed the "cd wildfly home" part earlier but i
> don't think it matters much. maybe the rc script shouldn't have that by
> default so it just works as expected.

>> has anybody used the rc.wildfly script included in wildfly to stop the
>> service? it seems to silently fail. when i ran the command directly [
>> $/usr/share/wildfly/bin/jboss-cli.sh --connect controller=127.0.0.1:9999command=:shutdown ] i see that its getting a connection refused error. it
>> appears that the config file is not setup to allow local connections to
>> control wildfly.
>>
>> can the wildfly buildscript be packaged such that it either falls back to
>> a simple `kill $wildflypid` command and/or patch the standalone.xml to
>> allow local connections.
>>
>> the local connection method is a bit less secure unless a wildfly user is
>> somehow generated.
>>
>> either way, its not obvious that `rc.wildfly stop` does not work without
>> further configuration so at the very least it should be noted.

Just to make sure the maintainer gets this, i'm CCing to him as well


- --
Willy Sudiarto Raharjo
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlMs4noACgkQiHuDdNczM4H8tQCfZEA9gQ9ZnTZVcY1jtsYkCpk8
Z78AoI4f1mo1l+THf6zmmXs9dKf6Ts2j
=bKrF
-----END PGP SIGNATURE-----