Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 913189

Summary:	Backward compatibility for JMS clients with JNDI lookups
Product:	[JBoss] JBoss Enterprise Application Platform 6	Reporter:	Miroslav Novak <mnovak>
Component:	Remoting, Naming	Assignee:	Andrig T Miller <anmiller>
Status:	CLOSED EOL	QA Contact:
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	6.1.0	CC:	atangrin, brian.stansberry, dandread, david.lloyd, jdoyle, mmillson, myarboro, rsvoboda
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Known Issue
Doc Text:	.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-08-02 07:33:33 UTC	Type:	Enhancement
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-20 15:49:06 UTC

Description of problem:
From the last update of document "Backward compatibility between EAP releases" [1] by Andrig Miller we should support backward compatibility of JMS clients communicating with HornetQ provider across EAP releases. 
Backward compatibility for JMS clients means that old JMS clients with EAP 5 client libraries will be able to communicate to EAP 6 server. 
There is new implementation of JNDI in EAP 6 which is incompatible with JNDI in EAP 5. This breaks backward compatibility of JMS clients because they need to look up connection factories and queues/topics in JNDI.

[1] https://docspace.corp.redhat.com/docs/DOC-111225

Additional info:
JMS client with JNDI in EAP 5 uses following EAP 5 client libraries:
hornetq-core-client.jar
hornetq-jms-client.jar
jnp-client.jar
jboss-javaee.jar
netty.jar

and should without modification communicate to EAP 6 server. 

Testing showed that old EAP 5 HornetQ client libraries are compatible and can communicate to newer HornetQ server/component in EAP 6. Problematic components are remoting and JNDI.

Comment 1 Miroslav Novak 2013-02-22 12:01:38 UTC

Changing component and removing target release. Should be set by pm.

Comment 4 Miroslav Novak 2013-02-27 12:21:01 UTC

Reassigning to David as remoting3 is in EAP 6.

Comment 5 David M. Lloyd 2013-02-27 14:02:35 UTC

We have no plans now or in the future to create an EAP 5-compatible Remoting or JNDI layer.

Comment 6 Miroslav Novak 2013-02-27 14:24:23 UTC

Hi Andy,

it seems that there are no plans to create an EAP 5-compatible Remoting or JNDI layer. Could you review the document for "Backward compatibility between EAP releases" [1] if it's really necessary. (see comment above from David) We would like to have your feedback if it's blocker or we're fine with current status.

Thanks,
Mirek

[1] https://docspace.corp.redhat.com/docs/DOC-111225

Comment 17 Dimitris Andreadis 2013-04-23 20:26:58 UTC

Not sure if it's the right workflow but I'm '-' the blocker flag. This issue may  be important but it's unrealistic to hold the 6.1.0 release since we don't have either the time and resources and clear technical idea how exactly will be solved. 

It has to go either in the planning for 6.2 or be a change request for 6.1 after is released, although in both case it will be developed upstream and ported back, with the know caveat of resourcing/priorities, etc.

Comment 18 Dimitris Andreadis 2013-04-23 20:30:07 UTC

Also changing the type to 'Enhancement'.

Comment 22 John Doyle 2013-11-05 17:20:00 UTC

In order for this RFE to be met, NO changes on the client side is allowed.

Comment 26 Miroslav Novak 2013-12-13 08:25:19 UTC

There is work on this thanks to Emmanuel Hugonnet and Carlo de Wolf. More info can be found in [1][2].

At this moment this is still under development.

[1] https://mojo.redhat.com/docs/DOC-928901
[2] https://mojo.redhat.com/docs/DOC-929745