[jboss-jira] [JBoss JIRA] (AS7-6605) Replicating JNDI tree to another server

[RH Bugzilla Integration (JIRA)]

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

RH Bugzilla Integration commented on AS7-6605:
----------------------------------------------

Brian Stansberry <brian.stansberry at redhat.com> made a comment on [bug 913618|https://bugzilla.redhat.com/show_bug.cgi?id=913618]

EAP 6.1 is way past the feature development phase.

John Bailey no longer works for Red Hat, so he should not be a default assignee for anything in Bugzilla.
                
>  Replicating JNDI tree to another server
> ----------------------------------------
>
>                 Key: AS7-6605
>                 URL: https://issues.jboss.org/browse/AS7-6605
>             Project: Application Server 7
>          Issue Type: Feature Request
>          Components: Naming
>    Affects Versions: 7.1.2.Final (EAP)
>            Reporter: Miroslav Novak
>            Assignee: Eduardo Martins
>            Priority: Critical
>             Fix For: 7.2.0.CR1
>
>
> 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 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