Bug 1035234 - Document: JMS bridge cannot be deployed to backup in dedicated HA topology
Summary: Document: JMS bridge cannot be deployed to backup in dedicated HA topology
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Documentation
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: GA
: EAP 6.3.0
Assignee: David Michael
QA Contact: Russell Dickenson
David Michael
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-27 11:01 UTC by Miroslav Novak
Modified: 2014-08-14 15:21 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-06-28 15:43:10 UTC
Type: Bug

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

Description Miroslav Novak 2013-11-27 11:01:18 UTC 
Description of problem:
In scenarios where there are two servers in dedicated HA topology, the JMS bridge cannot be deployed to backup and is connected backup to backup server.
Comment 2 Miroslav Novak 2014-05-26 09:09:32 UTC 
Hi David,

we should add warning or important block to chapter "18.3. About Bridges" with something like:
"JMS bridge cannot be deployed to EAP 6 server which have HornetQ configured as dedicated backup. Reason is that Transaction Manager on dedicated backup server is not able to recover transactions which were previously started on HornetQ live server."

Thanks,
Mirek
Comment 5 Miroslav Novak 2014-05-29 07:18:30 UTC 
Thanks David! Setting as verified.
Note You need to log in before you can comment on or make changes to this bug.