[jboss-jira] [JBoss JIRA] (WFLY-2194) Difficulty Enabling SSL for Management Interfaces Using CLI
Darran Lofthouse created WFLY-2194:
--------------------------------------
Summary: Difficulty Enabling SSL for Management Interfaces Using CLI
Key: WFLY-2194
URL: https://issues.jboss.org/browse/WFLY-2194
Project: WildFly
Issue Type: Task
Components: CLI, Domain Management, Security
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Fix For: 8.0.0.Beta1
Trying to enable the HTTPS port for the HTTP management interface using the CLI results in
the following: -
{code}
[standalone@localhost:9990 /]
./core-service=management/management-interface=http-interface:write-attribute(name=secure-socket-binding,
value=management-https)
Communication error: java.util.concurrent.ExecutionException: Operation failed: Operation
failed: Channel closed
{code}
Server side the following is logged: -
{code}
17:59:54,193 INFO [org.jboss.as.server] (management-handler-thread - 4) JBAS015890:
Creating http management service using socket-binding (management-http) and
secure-socket-binding (management-https)
17:59:54,212 INFO [org.jboss.as.server] (management-handler-thread - 4) JBAS015888:
Creating http management service using socket-binding (management-http)
17:59:54,236 WARN [org.jboss.as.controller.management-operation]
(management-handler-thread - 4) JBAS014626: Operation was interrupted before stability
could be reached
{code}
i.e. What appears to be happening is that as communication is lost with the client the
update is being detected as a failure.
As interface updates do result in restarting the services used to make the updates it may
be better to switch these to reload required updates instead of being immediate - also the
chances are that security realm updates would be made simultaneously and those also
require a reload.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira