Bug 780409 (SOA-2840) - Teiid does not handle failover correctly
Summary: Teiid does not handle failover correctly
Keywords:
Status: CLOSED WONTFIX
Alias: SOA-2840
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: EDS
Version: 5.1.0.ER7
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 5.1.0 GA
Assignee: Van Halbert
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-01-24 15:13 UTC by Boris Belovic
Modified: 2011-02-09 10:03 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-02-09 10:03:30 UTC
Type: Bug

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


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SOA-2840 0 Major Closed Teiid does not handle failover correctly 2013-08-08 10:16:57 UTC
Red Hat Issue Tracker TEIID-1451 0 Major Closed Teiid does not handle failover correctly 2013-08-08 10:16:58 UTC

Description Boris Belovic 2011-01-24 15:13:25 UTC 
project_key: SOA

See TEIID-1451 for the details.
Comment 1 Boris Belovic 2011-01-24 15:23:33 UTC 
Link: Added: This issue related TEIID-1451
Comment 4 Van Halbert 2011-01-31 18:40:27 UTC 
Release Notes Docs Status: Added: Documented as Known Issue
Release Notes Text: Added: Teiid supports fail over and load balance among servers defined on the URL at connection time.      Fail over will not occur during execution due to transactional boundary issues.
Comment 5 Boris Belovic 2011-02-01 16:15:14 UTC 
Van,
why is this issue marked as Resolved? This issue was fixed by updating Release notes? If yes, which Release notes were updated? Release notes for ER8 or for GA?
Comment 6 Boris Belovic 2011-02-09 10:03:30 UTC 
With ER9 bits client shows better behaviour in failover scenario. When node1 is killed it switches to node2, when node2 is killed (and node1 bring up again) client now switches to node1 and continues retrieving data from active node.
Note You need to log in before you can comment on or make changes to this bug.