[jboss-jira] [JBoss JIRA] (WFLY-3239) Changing the JNDI bound values in the naming subsystem requires reload.

[Brian Stansberry (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-3239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12960799#comment-12960799 ] 

Brian Stansberry commented on WFLY-3239:
----------------------------------------

"Still the OLD JNDI name entry remains in the memory. So the XML configuration and the Runtimedetail remains totally unsync."

That's what reload-required state means. The runtime state is out of sync with the persistent configuration.

Eduardo, this proposed change probably should not happen unless the user provides the "allow-resource-service-restart" header which can be checked by seeing if OperationContext.isResourceServiceRestartAllowed() returns 'true'. I assume the JNDI binding change would result in restart of a number of other services, in particular the application components (servlets, EJBs etc) that use that binding. See "Applying Updates to Runtime Services" on https://docs.jboss.org/author/display/WFLY8/Management+API+reference for more on this, particularly the "resource-services" bullet point.
                
> Changing the JNDI bound values in the naming subsystem requires reload.
> -----------------------------------------------------------------------
>
>                 Key: WFLY-3239
>                 URL: https://issues.jboss.org/browse/WFLY-3239
>             Project: WildFly
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Naming
>    Affects Versions: 8.0.1.Final
>         Environment: All
>            Reporter: Jay Kumar SenSharma
>            Assignee: Eduardo Martins
>
> - Changing the values which are binded in the naming subsystem shows "reload-required", which it ideally should not.  The JNDI naming should follow the "rebind" feature of InitialContext.   The values should be rebinded in the JNDI.
> - Ideally the  JNDI value should not have required the reload and in the runtime only the JNDI value should have changed.

--
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