[
https://issues.jboss.org/browse/AS7-2627?page=com.atlassian.jira.plugin.s...
]
jaikiran pai commented on AS7-2627:
-----------------------------------
Recently support has been added to get the server version and the "codename" of
the server via management operations (so you can get it from the CLI, for example).
However, since you are using a SNAPSHOT version, the server version value will not be much
useful since it won't say which commit id that snapshot corresponds to. You could
however, open of the JBoss AS jars from the JBOSS_HOME/modules/org/jboss/as/... and check
the MANIFEST.MF for the git commit id. But the easiest way is to check with whoever
provided you the binary and see which build it comes from.
P.S: I don't completely remember, but I think in previous EAP/AS versions we used to
print out the SVN id on which the server was built. I think we could perhaps do something
similar in AS7, if that's useful. But that should be a separate JIRA.
Connecting to the HTTP Host Management by Accident Results in a hung
Process
----------------------------------------------------------------------------
Key: AS7-2627
URL:
https://issues.jboss.org/browse/AS7-2627
Project: Application Server 7
Issue Type: Feature Request
Components: CLI
Reporter: Jim Tyrrell
Assignee: Alexey Loubyansky
Labels: eap6-ux
When having the default http (9990) and cli (9999) management ports
When running this command, trying to connect to the http management port:
./jboss-admin.sh --controller=localhost:9990 -c
You end up with a hung process, it does not appear to time out. You need to do a kill -9
on the process, if it trys to connect to an invalid host it should error out.
If it can not connect it should time out.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira