[jboss-jira] [JBoss JIRA] (WFLY-1073) Replicating JNDI tree to another server

[RH Bugzilla Integration (Jira)]

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

RH Bugzilla Integration commented on WFLY-1073:
-----------------------------------------------

Carlo de Wolf <cdewolf at redhat.com> changed the Status of [bug 913618|https://bugzilla.redhat.com/show_bug.cgi?id=913618] from NEW to CLOSED

>  Replicating JNDI tree to another server
> ----------------------------------------
>
>                 Key: WFLY-1073
>                 URL: https://issues.jboss.org/browse/WFLY-1073
>             Project: WildFly
>          Issue Type: Feature Request
>          Components: Naming
>            Reporter: Miroslav Novak
>            Priority: Major
>
> Description of problem:
> This use case is taken from one of our user which we were able to handle using HA-JNDI in EAP 5:
> 1. JMS Client will create Context with two URL  (node1, node2) (java.naming.provider.url property)
> 2. For some reason client is connected to node2 first which will have no JMS admin objects registered in JNDI (this happens when this node is configured as HornetQ backup) 
> 3. Node2 has replicated JNDI tree from node1. So connection factory will connect client to node1 and queue/topics are deployed on node1.
> Can be this functionality provided in EAP 6, please?



--
This message was sent by Atlassian Jira
(v7.12.1#712002)