Red Hat Bugzilla – Bug 856500
Administration and Configuration Guide Chapter 13.2.3 Note section's description are inaccurate.
Last modified: 2013-03-15 00:27:50 EDT
Description of problem:
Administration and Configuration Guide Chapter 13.2.3 Note section:
" If you use a standalone server, modify Management CLI commands by removing the /profile=default from the beginning of any Management CLI commands.
But when I try this command:
The following Exception threw:
Failed to get the list of the operation properties: "JBAS014753: There is no operation writeattribute registered at address [
("subsystem" => "web"),
("connector" => "HTTPS"),
("ssl" => "configuration")
Also, when I try this:
The following Error threw:
"outcome" => "failed",
"failure-description" => "JBAS014807: Management resource '[
(\"subsystem\" => \"web\"),
(\"connector\" => \"HTTPS\"),
(\"ssl\" => \"configuration\")
]' not found",
"rolled-back" => true
Version-Release number of selected component (if applicable):
JBoss EAP 6.0.0
Do SSL configuration as Documents 13.2.3 say.
CLI execute failed and roll back
CLI can execute successful.
The problem here is that the connector name is case-sensitive. Use the following command and it should work properly:
Note that this topic has had signficant updates since the 6.0.0 GA and is now significantly different on internal documentation stage. Please check there and let me know if more updates are needed.
Link from above is not working anymore. Changing status to assigned -- please provided information about current status of this issue.
The corrected link to the section 13.2.3 is at . Note that at  there is a typo in the first paragraph - "SSL-encryoted" should be "SSL-encrypted". This has already been corrected.
First of all AFAIK the most reset docs are 
in example 13.4
the connector is being referred to as "https" even though it was named "HTTPS" in previous example -- name it consistently "HTTPS"
Also because of this I believe that this issue is in fact a duplicate of BZ887219. However I'm not entirely sure about it. Close this issue if I'm right, thanks.
(1) You're correct in that I provided the wrong link. Sorry for that.
(2) You're also correct that this is a duplicate of BZ#887219. I checked that BZ ticket and the corrections have been made in that ticket so I have closed this as a duplicate.
*** This bug has been marked as a duplicate of bug 887219 ***