Bug 913618

Summary:	Replicating JNDI tree to another server
Product:	[JBoss] JBoss Enterprise Application Platform 6	Reporter:	Miroslav Novak <mnovak>
Component:	Naming	Assignee:	emartins
Status:	CLOSED WONTFIX	QA Contact:
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.1.0	CC:	atangrin, rsvoboda
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-03-01 12:28:23 UTC	Type:	Feature Request
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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.