Bug 913618 - Replicating JNDI tree to another server
Summary: Replicating JNDI tree to another server
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Naming
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: emartins
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-02-21 15:58 UTC by Miroslav Novak
Modified: 2019-03-01 12:28 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-03-01 12:28:23 UTC
Type: Feature Request
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker AS7-6605 0 Major Open Replicating JNDI tree to another server 2016-03-22 19:27:37 UTC

Description Miroslav Novak 2013-02-21 15:58:09 UTC
Description of problem:
This use case is taken from one of our customer 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?

Comment 1 Brian Stansberry 2013-02-22 15:18:11 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.