[Slackbuilds-users] wildfly start/stop script

Miguel De Anda miguel at thedeanda.com
Fri Mar 21 21:20:55 UTC 2014


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.


On Fri, Mar 21, 2014 at 2:01 PM, Miguel De Anda <miguel at thedeanda.com>wrote:

> 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.
>
> thanks,
> miguel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20140321/483d1400/attachment.html>


More information about the SlackBuilds-users mailing list