akronenw opened a new pull request, #5478:
URL: https://github.com/apache/netbeans/pull/5478
This solves the same issue as mentioned in #5453, but a cleaner.
The problem: Wildfly servers are configured with XML files like
`standalone.xml`. Those contain socket binding groups that comprise a bunch of
ports and can have a port offset defined. One such group is the
`standard-sockets` group in which for example the management port is defined.
All variables in the config file can (must?) be written like
`${jboss.socket.binding.port-offset:10000}`, that is, a variable and the
fallback (or default) value separated by a `:`.
NetBeans does not set the port-offset variable, hence the default from the
config file is used, but NetBeans does not parse it either so the Wildfly
server runs on a different port as known by NetBeans. That leads to a correctly
started server that can't be restarted, stopped or refreshed from the NetBeans
server context view (but it is possible to start it regularly).
I fixed this by parsing the config and extracting the default port offset
from the standard socket group. The offset is then added to the admin port
value (which can be set in the add server wizard) in the deployment manager.
I did not add the offset to the regular port, because I have not yet found
an issue with that (most likely I will, sooner or later) and that would mean
touching a lot more files.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
