[jboss-jira] [JBoss JIRA] (WFLY-5563) Login Module changes via CLI not getting reflected without jboss restart
Darran Lofthouse (JIRA)
issues at jboss.org
Thu Oct 22 08:52:00 EDT 2015
[ https://issues.jboss.org/browse/WFLY-5563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Darran Lofthouse resolved WFLY-5563.
------------------------------------
Fix Version/s: 10.0.0.CR4
Resolution: Won't Fix
We don't currently support runtime updates to the login module list within the security domain definition.
In addition to this we are currently working to replace the existing security subsystem so not planning any enhancements to the legacy security subsystem at this time.
The best option would be to create the security domain and it's list of login modules within a composite operation so that the whole domain can be constructed in one step within the server.
> Login Module changes via CLI not getting reflected without jboss restart
> ------------------------------------------------------------------------
>
> Key: WFLY-5563
> URL: https://issues.jboss.org/browse/WFLY-5563
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Reporter: J Prasanna Venkatesan
> Assignee: Darran Lofthouse
> Fix For: 10.0.0.CR4
>
>
> I am running few login module related commands through cli add() .
>
> It is successfully added in standalone-full.xml. But this is not getting reflected without jboss restart.
>
> I tried adding {allow-resource-service-restart=true} at the end of the command. But no luck.
>
> I tried to reload using 'reload' command, but I am getting the following exception and the whole application goes down :-(
>
> Caused by: java.net.ConnectException: JBAS012174: Could not connect to http-remoting://localhost:9990. The connection failed
> at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:117)
> at org.jboss.as.protocol.ProtocolConnectionManager$EstablishingConnection.connect(ProtocolConnectionManager.java:256)
> at org.jboss.as.protocol.ProtocolConnectionManager.connect(ProtocolConnectionManager.java:70)
> at org.jboss.as.protocol.mgmt.FutureManagementChannel$Establishing.getChannel(FutureManagementChannel.java:204)
> at org.jboss.as.cli.impl.CLIModelControllerClient.getOrCreateChannel(CLIModelControllerClient.java:169)
> at org.jboss.as.cli.impl.CLIModelControllerClient$2.getChannel(CLIModelControllerClient.java:129)
> at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:117)
> at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:92)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeRequest(AbstractModelControllerClient.java:236)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:141)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:127)
> ... 13 more
> Caused by: java.net.ConnectException: Connection refused
> at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
> at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717)
> at org.xnio.nio.WorkerThread$ConnectHandle.handleReady(WorkerThread.java:319)
> at org.xnio.nio.WorkerThread.run(WorkerThread.java:539)
> at ...asynchronous invocation...(Unknown Source)
> at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:272)
> at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:253)
> at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:351)
> at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:339)
> at org.jboss.as.protocol.ProtocolConnectionUtils.connect(ProtocolConnectionUtils.java:78)
> at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:109)
> ... 23 more
>
> I like to see the changes getting reflected without jboss restart.
>
> Am I doing something wrong? Please give me some solution or alternatives.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
More information about the jboss-jira
mailing list