In our documentation there is a paragraph named "7.1.4. Securing a Remote Connector" which references a socket binding which is not defined:

/subsystem=messaging-activemq/server=default/remote-acceptor=mySslAcceptor:add(socket-binding=netty,params={ssl-enabled=true, key-store-path=PATH/TO/server.jks, key-store-password=${VAULT::server-key::key-store-password::sharedKey}})

When trying to use an existing socket binding, e.g.:

/subsystem=messaging-activemq/server=default/remote-acceptor=mySslAcceptor:add(socket-binding=https,params={ssl-enabled=true, key-store-path=/opt/rh/eap7/root/usr/share/wildfly/standalone/configuration/keystore-remote.jks, key-store-password=redhat})

we get the following error:

Caused by: java.lang.IllegalStateException: AMQ229230: Failed to bind acceptor mySslAcceptor to 172.31.87.74:8443

For this reason, the procedure should define what the 'netty' socket binding is, in such a way that the user doesn't hit that error.