Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
First Last Prev Next    This bug is not in your last search results.
Bug 779920 - (SOA-2280) JBoss Messaging client libraries are not included after switching to HornetQ
JBoss Messaging client libraries are not included after switching to HornetQ
Status: MODIFIED
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: EAP (Show other bugs)
5.1.0.ER1,5.2.0 ER1
Unspecified Unspecified
high Severity high
: ---
: FUTURE
Assigned To: Julian Coleman
http://jira.jboss.org/jira/browse/SOA...
:
Depends On:
Blocks:
  Show dependency tree / graph
 
Reported: 2010-09-08 09:04 EDT by Martin Vecera
Modified: 2015-03-12 07:24 EDT (History)
3 users (show)

See Also:
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: 2011-06-20 15:10:38 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


External Trackers
Tracker ID Priority Status Summary Last Updated
JBoss Issue Tracker SOA-2280 Major Closed JBoss Messaging client libraries are not included after switching to HornetQ 2013-05-09 10:00:01 EDT

  None (edit)
Description Martin Vecera 2010-09-08 09:04:13 EDT 
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 09:23:39 EDT 
Link: Added: This issue depends JBPAPP-5041
Comment 2 Rajesh Rajasekaran 2010-09-08 11:39:11 EDT 
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 05:25:08 EDT 
Thanks Rajesh, I updated the issue.
Comment 4 Anne-Louise Tangring 2010-09-22 08:45:47 EDT 
This was triaged for SOA 5.1.0. Not in SOA 5.1.0
Comment 5 Len DiMaggio 2011-07-29 11:38:15 EDT 
Link: Added: This issue relates to SOA-3228
Comment 6 Julian Coleman 2011-08-03 11:04:39 EDT 
HornetQ will be reintroduced.
Comment 7 Andy Taylor 2011-09-08 06:04:09 EDT 
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 11:56:23 EST 
Maybe putting them in a separate "extras" folder or renaming them?
Comment 9 tcunning 2012-06-15 07:41:28 EDT 
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-01 23:37:53 EDT 
    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.
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.