Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 900359 - (JBPAPP6-1208) CLONE - Create subsystem for JMS bridge
CLONE - Create subsystem for JMS bridge
Status: CLOSED CURRENTRELEASE
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: HornetQ (Show other bugs)
6.0.0
Unspecified Unspecified
high Severity high
: ---
: EAP 6.1.0
Assigned To: Jeff Mesnil
http://jira.jboss.org/jira/browse/JBP...
eap601candidate
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-05-03 10:37 EDT by Miroslav Novak
Modified: 2014-06-28 08:34 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
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)


External Trackers
Tracker ID Priority Status Summary Last Updated
JBoss Issue Tracker JBPAPP6-1208 Major Closed CLONE - Create subsystem for JMS bridge 2014-05-26 01:44:31 EDT
JBoss Issue Tracker PRODMGT-305 Major Closed EAP6 Generic JMS Resource Adapter to Integrate with Tibco EMS 2014-05-26 01:44:32 EDT

  None (edit)
Description Miroslav Novak 2012-05-03 10:37:58 EDT
Affects: Release Notes
project_key: JBPAPP6

Currently there is no pre-defined way to deploy a JMS bridge (i.e. org.hornetq.jms.bridge.impl.JMSBridgeImpl) in AS7.  In JBoss AS 6 and earlier you could deploy the bridge as an MBean or JBoss MC bean, but the current configuration schema in AS7 simply doesn't support it.  The bridge is a nice feature so we need a way to deploy it.
 
It doesn't make sense to add the JMS bridge to a <hornetq-server> because the bridge can operate independently of a local HornetQ server.  It really needs its own subsystem.
Comment 1 Miroslav Novak 2012-05-03 10:37:59 EDT
Link: Added: This issue Cloned from AS7-4268
Comment 2 Miroslav Novak 2012-05-03 10:39:13 EDT
Workflow: Removed: GIT Pull Request workflow  Added: jira
Security: Added: Public
Docs QE Status: Added: NEW
Comment 7 Anne-Louise Tangring 2012-05-07 10:14:38 EDT
Release Notes Docs Status: Added: Not Yet Documented
Affects: Added: Release Notes
Forum Reference: Removed: https://community.jboss.org/thread/195025, https://community.jboss.org/message/727899#727899 Added: https://community.jboss.org/thread/195025, https://community.jboss.org/message/727899#727899
Comment 8 Anne-Louise Tangring 2012-05-23 14:50:50 EDT
This issue has been triaged and decided to not block/prevent/hold the EAP 6 release. To comply with Release Criteria stating that no issues with Critical or Blocker priority setting can be open for the release, this is changed to priority Major. 
Comment 9 Rostislav Svoboda 2012-06-07 07:36:41 EDT
Link: Added: This issue is a dependency of JBPAPP-9188
Comment 10 Tom WELLS 2012-06-07 20:08:48 EDT
Release Notes Docs Status: Removed: Not Yet Documented Added: Documented as Known Issue
Release Notes Text: Added: There is currently no pre-defined way to deploy a JMS bridge (i.e. org.hornetq.jms.bridge.impl.JMSBridgeImpl). In JBoss AS 6 and earlier the bridge could be deployed as an MBean or JBoss MC bean, but the current configuration schema doesn't support it.
Forum Reference: Removed: https://community.jboss.org/thread/195025, https://community.jboss.org/message/727899#727899 Added: https://community.jboss.org/thread/195025, https://community.jboss.org/message/727899#727899
Comment 11 Rajesh Rajasekaran 2012-06-07 20:09:43 EDT
Link: Removed: This issue is a dependency of JBPAPP-9188 
Comment 12 Rajesh Rajasekaran 2012-07-11 15:43:57 EDT
Labels: Removed: eap6_need_triage Added: eap601candidate
Comment 13 Dimitris Andreadis 2012-09-14 08:47:12 EDT
This should really be scheduled for inclusion into EAP 6.1. I don't see the version in JIRA, though.
Comment 15 Anne-Louise Tangring 2012-11-13 15:46:38 EST
Release Notes Docs Status: Removed: Documented as Known Issue 
Release Notes Text: Removed: There is currently no pre-defined way to deploy a JMS bridge (i.e. org.hornetq.jms.bridge.impl.JMSBridgeImpl). In JBoss AS 6 and earlier the bridge could be deployed as an MBean or JBoss MC bean, but the current configuration schema doesn't support it. 
Docs QE Status: Removed: NEW 
Comment 16 Jimmy Wilson 2013-01-02 18:03:27 EST
Link: Added: This issue relates to PRODMGT-305
Comment 17 Miroslav Novak 2013-02-19 04:59:13 EST
Checked in EAP 6.1.0.DR4. JMS bridge can be configured there. Even when there are issues. Setting as verified.

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