Bug 779920 (SOA-2280)

Summary:	JBoss Messaging client libraries are not included after switching to HornetQ
Product:	[JBoss] JBoss Enterprise SOA Platform 5	Reporter:	Martin Vecera <mvecera>
Component:	EAP	Assignee:	Julian Coleman <jcoleman>
Status:	CLOSED UPSTREAM	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	5.1.0.ER1, 5.2.0 ER1	CC:	ataylor, tcunning
Target Milestone:	---
Target Release:	FUTURE
Hardware:	Unspecified
OS:	Unspecified
URL:	http://jira.jboss.org/jira/browse/SOA-2280
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	There is a problem when using HornetQ with the JBoss Messaging Client. The client's libraries are not transferred over after the user has switched to HornetQ. As a result, users cannot access these libraries in HornetQ. To work around this, users should add the JBM client libraries to the application itself.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2025-02-10 03:14:43 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Martin Vecera 2010-09-08 13:04:13 UTC

project_key: SOA

Both HornetQ and JBM client libraries are supposed to be present in the client directory but the JBM client library is removed after switching to HornetQ. This is inherited from EAP.

Comment 1 Martin Vecera 2010-09-08 13:23:39 UTC

Link: Added: This issue depends JBPAPP-5041

Comment 2 Rajesh Rajasekaran 2010-09-08 15:39:11 UTC

Martin, JBPAPP-5041 has been redefined. Can you check if it would cause any issues on the SOA side?

Comment 3 Martin Vecera 2010-09-10 09:25:08 UTC

Thanks Rajesh, I updated the issue.

Comment 4 Anne-Louise Tangring 2010-09-22 12:45:47 UTC

This was triaged for SOA 5.1.0. Not in SOA 5.1.0

Comment 5 Len DiMaggio 2011-07-29 15:38:15 UTC

Link: Added: This issue relates to SOA-3228

Comment 6 Julian Coleman 2011-08-03 15:04:39 UTC

HornetQ will be reintroduced.

Comment 7 Andy Taylor 2011-09-08 10:04:09 UTC

It doesn't make sense to have the JBoss Messaging client libs available when the default messaging provider is HornetQ. If a user wants to use a JBM client (that would be talking to a remote JBM server anyway) they would add the JBM client libs to the application itself, however this is unlikely.

Comment 8 Anne-Louise Tangring 2012-01-31 16:56:23 UTC

Maybe putting them in a separate "extras" folder or renaming them?

Comment 9 tcunning 2012-06-15 11:41:28 UTC

For ESB at least, jboss-messaging-client.jar seems to be a required JAR for a remote service invoker invocation against a SOA-P server using jboss-messaging.   Even if you are running hornetq locally, you may want to invoke a service on another SOA-P server.

Comment 11 Suz 2012-07-02 03:37:53 UTC

    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
There is a problem when using HornetQ with the JBoss Messaging Client. The client's libraries are not transferred over after the user has switched to HornetQ. As a result, users cannot access these libraries in HornetQ. To work around this, users should add the JBM client libraries to the application itself.

Comment 14 Red Hat Bugzilla 2025-02-10 03:14:43 UTC

This product has been discontinued or is no longer tracked in Red Hat Bugzilla.