[JBoss JIRA] (WFLY-2207) CLI Unable to connect using https-remoting address.
by Darran Lofthouse (JIRA)
Darran Lofthouse created WFLY-2207:
--------------------------------------
Summary: CLI Unable to connect using https-remoting address.
Key: WFLY-2207
URL: https://issues.jboss.org/browse/WFLY-2207
Project: WildFly
Issue Type: Bug
Components: CLI
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Priority: Critical
Fix For: 8.0.0.Beta1
The CLI is failing to connect over https with the following: -
{code}
[disconnected /] connect https-remoting://localhost:9993
The controller is not available at localhost:9993: java.net.ConnectException: JBAS012144: Could not connect to https-remoting://localhost:9993. The connection timed out: JBAS012144: Could not connect to https-remoting://localhost:9993. The connection timed out
{code}
--
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
12 years, 1 month
[JBoss JIRA] (DROOLS-194) Add support in KIE to register custom Wagons
by Mario Fusco (JIRA)
[ https://issues.jboss.org/browse/DROOLS-194?page=com.atlassian.jira.plugin... ]
Mario Fusco resolved DROOLS-194.
--------------------------------
Fix Version/s: 6.0.0.CR5
Resolution: Done
> Add support in KIE to register custom Wagons
> --------------------------------------------
>
> Key: DROOLS-194
> URL: https://issues.jboss.org/browse/DROOLS-194
> Project: Drools
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Reporter: Kurt Stam
> Assignee: Mario Fusco
> Fix For: 6.0.0.CR5
>
> Attachments: kie-srampwagon.tgz
>
>
> The ManualWagonProvider subclass of Aether in KIE registers the HTTPWagon. It should be possible to add your own Wagon through config our automated machinery when another Wagon is put on the classpath and references in the build/extensions of a MavenProject. To get the SrampWagon to work we used the following code:
> {quote}
> private static class ManualWagonProvider implements WagonProvider {
> public Wagon lookup( String roleHint ) throws Exception {
> if ( "http".equals( roleHint ) ) {
> return new AhcWagon();
> }
> if ( "sramp".equals( roleHint ) ) {
> return new SrampWagon();
> }
> return null;
> }
> public void release( Wagon wagon ) { }
> }
> {quote}
--
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
12 years, 1 month
[JBoss JIRA] (DROOLS-194) Add support in KIE to register custom Wagons
by Mario Fusco (JIRA)
[ https://issues.jboss.org/browse/DROOLS-194?page=com.atlassian.jira.plugin... ]
Mario Fusco reassigned DROOLS-194:
----------------------------------
Assignee: Mario Fusco (was: Mark Proctor)
> Add support in KIE to register custom Wagons
> --------------------------------------------
>
> Key: DROOLS-194
> URL: https://issues.jboss.org/browse/DROOLS-194
> Project: Drools
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Reporter: Kurt Stam
> Assignee: Mario Fusco
> Attachments: kie-srampwagon.tgz
>
>
> The ManualWagonProvider subclass of Aether in KIE registers the HTTPWagon. It should be possible to add your own Wagon through config our automated machinery when another Wagon is put on the classpath and references in the build/extensions of a MavenProject. To get the SrampWagon to work we used the following code:
> {quote}
> private static class ManualWagonProvider implements WagonProvider {
> public Wagon lookup( String roleHint ) throws Exception {
> if ( "http".equals( roleHint ) ) {
> return new AhcWagon();
> }
> if ( "sramp".equals( roleHint ) ) {
> return new SrampWagon();
> }
> return null;
> }
> public void release( Wagon wagon ) { }
> }
> {quote}
--
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
12 years, 1 month
[JBoss JIRA] (WFLY-2200) NoSuchElementException after upgrade from Beta13 to Beta14
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-2200?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar resolved WFLY-2200.
-------------------------------
Resolution: Done
> NoSuchElementException after upgrade from Beta13 to Beta14
> ----------------------------------------------------------
>
> Key: WFLY-2200
> URL: https://issues.jboss.org/browse/WFLY-2200
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 8.0.0.Beta1
> Reporter: Juergen Zimmermann
> Assignee: Stuart Douglas
> Fix For: 8.0.0.Beta1
>
>
> I just switched to a newer WildFly snapshot having Undertow 1.0.0.Beta14. But I'm getting the following stacktrace caused by HttpServletRequestImpl.getParameterNames(). This error didn't happen with 1.0.0.Beta13.
> {code}
> SEVERE [javax.enterprise.resource.webcontainer.jsf.application] (default task-45) Error Rendering View[/index.xhtml]: java.util.NoSuchElementException
> at java.util.HashMap$HashIterator.nextEntry(HashMap.java:929) [rt.jar:1.7.0_40]
> at java.util.HashMap$KeyIterator.next(HashMap.java:960) [rt.jar:1.7.0_40]
> at io.undertow.servlet.spec.HttpServletRequestImpl.getParameterNames(HttpServletRequestImpl.java:605) [undertow-servlet-1.0.0.Beta14.jar:1.0.0.Beta14]
> at com.sun.faces.context.RequestParameterMap.getEntryIterator(RequestParameterMap.java:126) [jsf-impl-2.1.26.jar:2.1.26]
> at com.sun.faces.context.BaseContextMap$EntrySet.iterator(BaseContextMap.java:166) [jsf-impl-2.1.26.jar:2.1.26]
> at com.sun.faces.context.BaseContextMap$BaseSet.size(BaseContextMap.java:154) [jsf-impl-2.1.26.jar:2.1.26]
> at java.util.Collections$UnmodifiableCollection.size(Collections.java:1055) [rt.jar:1.7.0_40]
> at java.util.AbstractMap.size(AbstractMap.java:84) [rt.jar:1.7.0_40]
> at java.util.AbstractMap.isEmpty(AbstractMap.java:93) [rt.jar:1.7.0_40]
> at java.util.Collections$UnmodifiableMap.isEmpty(Collections.java:1336) [rt.jar:1.7.0_40]
> at com.sun.faces.facelets.util.DevTools.writeVariables(DevTools.java:330) [jsf-impl-2.1.26.jar:2.1.26]
> at com.sun.faces.facelets.util.DevTools.writeVariables(DevTools.java:199) [jsf-impl-2.1.26.jar:2.1.26]
> at com.sun.faces.facelets.util.DevTools.debugHtml(DevTools.java:186) [jsf-impl-2.1.26.jar:2.1.26]
> at com.sun.faces.facelets.tag.ui.UIDebug.writeDebugOutput(UIDebug.java:140) [jsf-impl-2.1.26.jar:2.1.26]
> at com.sun.faces.facelets.tag.ui.UIDebug.encodeBegin(UIDebug.java:122) [jsf-impl-2.1.26.jar:2.1.26]
> at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1817) [jsf-api-2.1.26.jar:2.1]
> at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1822) [jsf-api-2.1.26.jar:2.1]
> at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1822) [jsf-api-2.1.26.jar:2.1]
> at com.sun.faces.application.view.FaceletViewHandlingStrategy.renderView(FaceletViewHandlingStrategy.java:447) [jsf-impl-2.1.26.jar:2.1.26]
> at com.sun.faces.application.view.MultiViewHandler.renderView(MultiViewHandler.java:125) [jsf-impl-2.1.26.jar:2.1.26]
> at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286) [jsf-api-2.1.26.jar:2.1]
> at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286) [jsf-api-2.1.26.jar:2.1]
> at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286) [jsf-api-2.1.26.jar:2.1]
> at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:120) [jsf-impl-2.1.26.jar:2.1.26]
> at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) [jsf-impl-2.1.26.jar:2.1.26]
> at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139) [jsf-impl-2.1.26.jar:2.1.26]
> at javax.faces.webapp.FacesServlet.service(FacesServlet.java:594) [jsf-api-2.1.26.jar:2.1]
> at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:87) [undertow-servlet-1.0.0.Beta14.jar:1.0.0.Beta14]
> at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:93) [undertow-servlet-1.0.0.Beta14.jar:1.0.0.Beta14]
> at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) [undertow-servlet-1.0.0.Beta14.jar:1.0.0.Beta14]
> at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:81)
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.0.Beta14.jar:1.0.0.Beta14]
> at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:113) [undertow-servlet-1.0.0.Beta14.jar:1.0.0.Beta14]
> at io.undertow.security.handlers.AuthenticationCallHandler.handleRequest(AuthenticationCallHandler.java:52) [undertow-core-1.0.0.Beta14.jar:1.0.0.Beta14]
> at io.undertow.security.handlers.AuthenticationConstraintHandler.handleRequest(AuthenticationConstraintHandler.java:51) [undertow-core-1.0.0.Beta14.jar:1.0.0.Beta14]
> at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:45) [undertow-core-1.0.0.Beta14.jar:1.0.0.Beta14]
> at io.undertow.servlet.handlers.security.ServletSecurityConstraintHandler.handleRequest(ServletSecurityConstraintHandler.java:55) [undertow-servlet-1.0.0.Beta14.jar:1.0.0.Beta14]
> at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:58) [undertow-core-1.0.0.Beta14.jar:1.0.0.Beta14]
> at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:65) [undertow-servlet-1.0.0.Beta14.jar:1.0.0.Beta14]
> at io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:70) [undertow-core-1.0.0.Beta14.jar:1.0.0.Beta14]
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.0.Beta14.jar:1.0.0.Beta14]
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.0.Beta14.jar:1.0.0.Beta14]
> at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:209) [undertow-servlet-1.0.0.Beta14.jar:1.0.0.Beta14]
> at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:196) [undertow-servlet-1.0.0.Beta14.jar:1.0.0.Beta14]
> at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:69) [undertow-servlet-1.0.0.Beta14.jar:1.0.0.Beta14]
> at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:130) [undertow-servlet-1.0.0.Beta14.jar:1.0.0.Beta14]
> at io.undertow.server.HttpHandlers.executeRootHandler(HttpHandlers.java:36) [undertow-core-1.0.0.Beta14.jar:1.0.0.Beta14]
> at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:614) [undertow-core-1.0.0.Beta14.jar:1.0.0.Beta14]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_40]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_40]
> at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_40]
> {code}
--
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
12 years, 1 month
[JBoss JIRA] (WFLY-2200) NoSuchElementException after upgrade from Beta13 to Beta14
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-2200?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar commented on WFLY-2200:
-----------------------------------
Fixed in Undertow Beta 16
> NoSuchElementException after upgrade from Beta13 to Beta14
> ----------------------------------------------------------
>
> Key: WFLY-2200
> URL: https://issues.jboss.org/browse/WFLY-2200
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 8.0.0.Beta1
> Reporter: Juergen Zimmermann
> Assignee: Stuart Douglas
> Fix For: 8.0.0.Beta1
>
>
> I just switched to a newer WildFly snapshot having Undertow 1.0.0.Beta14. But I'm getting the following stacktrace caused by HttpServletRequestImpl.getParameterNames(). This error didn't happen with 1.0.0.Beta13.
> {code}
> SEVERE [javax.enterprise.resource.webcontainer.jsf.application] (default task-45) Error Rendering View[/index.xhtml]: java.util.NoSuchElementException
> at java.util.HashMap$HashIterator.nextEntry(HashMap.java:929) [rt.jar:1.7.0_40]
> at java.util.HashMap$KeyIterator.next(HashMap.java:960) [rt.jar:1.7.0_40]
> at io.undertow.servlet.spec.HttpServletRequestImpl.getParameterNames(HttpServletRequestImpl.java:605) [undertow-servlet-1.0.0.Beta14.jar:1.0.0.Beta14]
> at com.sun.faces.context.RequestParameterMap.getEntryIterator(RequestParameterMap.java:126) [jsf-impl-2.1.26.jar:2.1.26]
> at com.sun.faces.context.BaseContextMap$EntrySet.iterator(BaseContextMap.java:166) [jsf-impl-2.1.26.jar:2.1.26]
> at com.sun.faces.context.BaseContextMap$BaseSet.size(BaseContextMap.java:154) [jsf-impl-2.1.26.jar:2.1.26]
> at java.util.Collections$UnmodifiableCollection.size(Collections.java:1055) [rt.jar:1.7.0_40]
> at java.util.AbstractMap.size(AbstractMap.java:84) [rt.jar:1.7.0_40]
> at java.util.AbstractMap.isEmpty(AbstractMap.java:93) [rt.jar:1.7.0_40]
> at java.util.Collections$UnmodifiableMap.isEmpty(Collections.java:1336) [rt.jar:1.7.0_40]
> at com.sun.faces.facelets.util.DevTools.writeVariables(DevTools.java:330) [jsf-impl-2.1.26.jar:2.1.26]
> at com.sun.faces.facelets.util.DevTools.writeVariables(DevTools.java:199) [jsf-impl-2.1.26.jar:2.1.26]
> at com.sun.faces.facelets.util.DevTools.debugHtml(DevTools.java:186) [jsf-impl-2.1.26.jar:2.1.26]
> at com.sun.faces.facelets.tag.ui.UIDebug.writeDebugOutput(UIDebug.java:140) [jsf-impl-2.1.26.jar:2.1.26]
> at com.sun.faces.facelets.tag.ui.UIDebug.encodeBegin(UIDebug.java:122) [jsf-impl-2.1.26.jar:2.1.26]
> at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1817) [jsf-api-2.1.26.jar:2.1]
> at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1822) [jsf-api-2.1.26.jar:2.1]
> at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1822) [jsf-api-2.1.26.jar:2.1]
> at com.sun.faces.application.view.FaceletViewHandlingStrategy.renderView(FaceletViewHandlingStrategy.java:447) [jsf-impl-2.1.26.jar:2.1.26]
> at com.sun.faces.application.view.MultiViewHandler.renderView(MultiViewHandler.java:125) [jsf-impl-2.1.26.jar:2.1.26]
> at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286) [jsf-api-2.1.26.jar:2.1]
> at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286) [jsf-api-2.1.26.jar:2.1]
> at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286) [jsf-api-2.1.26.jar:2.1]
> at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:120) [jsf-impl-2.1.26.jar:2.1.26]
> at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) [jsf-impl-2.1.26.jar:2.1.26]
> at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139) [jsf-impl-2.1.26.jar:2.1.26]
> at javax.faces.webapp.FacesServlet.service(FacesServlet.java:594) [jsf-api-2.1.26.jar:2.1]
> at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:87) [undertow-servlet-1.0.0.Beta14.jar:1.0.0.Beta14]
> at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:93) [undertow-servlet-1.0.0.Beta14.jar:1.0.0.Beta14]
> at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) [undertow-servlet-1.0.0.Beta14.jar:1.0.0.Beta14]
> at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:81)
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.0.Beta14.jar:1.0.0.Beta14]
> at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:113) [undertow-servlet-1.0.0.Beta14.jar:1.0.0.Beta14]
> at io.undertow.security.handlers.AuthenticationCallHandler.handleRequest(AuthenticationCallHandler.java:52) [undertow-core-1.0.0.Beta14.jar:1.0.0.Beta14]
> at io.undertow.security.handlers.AuthenticationConstraintHandler.handleRequest(AuthenticationConstraintHandler.java:51) [undertow-core-1.0.0.Beta14.jar:1.0.0.Beta14]
> at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:45) [undertow-core-1.0.0.Beta14.jar:1.0.0.Beta14]
> at io.undertow.servlet.handlers.security.ServletSecurityConstraintHandler.handleRequest(ServletSecurityConstraintHandler.java:55) [undertow-servlet-1.0.0.Beta14.jar:1.0.0.Beta14]
> at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:58) [undertow-core-1.0.0.Beta14.jar:1.0.0.Beta14]
> at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:65) [undertow-servlet-1.0.0.Beta14.jar:1.0.0.Beta14]
> at io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:70) [undertow-core-1.0.0.Beta14.jar:1.0.0.Beta14]
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.0.Beta14.jar:1.0.0.Beta14]
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.0.Beta14.jar:1.0.0.Beta14]
> at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:209) [undertow-servlet-1.0.0.Beta14.jar:1.0.0.Beta14]
> at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:196) [undertow-servlet-1.0.0.Beta14.jar:1.0.0.Beta14]
> at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:69) [undertow-servlet-1.0.0.Beta14.jar:1.0.0.Beta14]
> at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:130) [undertow-servlet-1.0.0.Beta14.jar:1.0.0.Beta14]
> at io.undertow.server.HttpHandlers.executeRootHandler(HttpHandlers.java:36) [undertow-core-1.0.0.Beta14.jar:1.0.0.Beta14]
> at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:614) [undertow-core-1.0.0.Beta14.jar:1.0.0.Beta14]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_40]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_40]
> at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_40]
> {code}
--
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
12 years, 1 month
[JBoss JIRA] (WFLY-2194) Difficulty Enabling SSL for Management Interfaces Using CLI
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/WFLY-2194?page=com.atlassian.jira.plugin.... ]
Darran Lofthouse commented on WFLY-2194:
----------------------------------------
The 'NativeManagementWriteAttributeHandler' which was previously the default entry point for the CLI required a reload so the 'HttpManagementWriteAttributeHandler' should be updated to match.
> 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
> Affects Versions: 8.0.0.Alpha4
> 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
12 years, 1 month