Skip to content

WildFly does not stop if different ports are configured #636

@marher

Description

@marher

Hello,

I configured different ports for WildFly in standalone.xml because 8080 is used:

<socket-binding-group name="standard-sockets" default-interface="public" port-offset="${jboss.socket.binding.port-offset:0}">
        <socket-binding name="ajp" port="${jboss.ajp.port:48009}"/>
        <socket-binding name="http" port="${jboss.http.port:48080}"/>
        <socket-binding name="https" port="${jboss.https.port:48443}"/>
        <socket-binding name="management-http" interface="management" port="${jboss.management.http.port:49990}"/>
        <socket-binding name="management-https" interface="management" port="${jboss.management.https.port:49993}"/>
        <socket-binding name="txn-recovery-environment" port="44712"/>
        <socket-binding name="txn-status-manager" port="44713"/>
        <outbound-socket-binding name="mail-smtp">
            <remote-destination host="${jboss.mail.server.host:localhost}" port="${jboss.mail.server.port:25}"/>
        </outbound-socket-binding>
</socket-binding-group>

I also configured the http port in the server config:
"jboss.server.port": "48080",

Starting WildFly is working fine. But if I want to stop it, an error occures:

Failed to connect to the controller: The controller is not available at localhost:9990: java.net.ConnectException: WFLYPRT0053: Could not connect to remote+http://localhost:9990. The connection failed: WFLYPRT0053: Could not connect to remote+http://localhost:9990. The connection failed: Connection refused: getsockopt

The reason is obvious. WildFly management port is configured to 49990 in standalone.xml but the JBoss Toolkit tries to access on port 9990.
I only can stop the server by CLI when I connect to the correct management port.

It would be great to add a config parameter jboss.management.port or similar to the server config.
A bit odd: If I add -Djboss.management.http.port=49990 to args.vm.override.string it is deleted each time I save the file.

(I saw #412)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions