[KULRICE-2209] KSB failover implementation is inadequate Created: 26/Aug/08  Updated: 21/May/15  Resolved: 06/Sep/10

Status: Closed
Project: Kuali Rice Development
Component/s: Development
Affects Version/s: None
Fix Version/s: Not version specific

Type: Bug Fix Priority: Major
Reporter: Eric Westfall Assignee: Eric Westfall
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: 2 days
Time Spent: Not Specified
Original Estimate: 2 days

Issue Links:
Relate
relates to KULRICE-4287 Intermittent issues with KSB service ... Closed
Similar issues:
KULRICE-3335Failover is not working properly in the KSB in the case of a 404 coming back from a service
KULRICE-13491Test failover of Rice components
KULRICE-12270Disable failover on topic messages in KSB
KULRICE-9151Document in the guide on clustering that session failover should be implemented for full reliability
KULRICE-6125Document the Implementation Considerations guide for KSB
KULRICE-291Implement a Grails connector for the KSB
KULRICE-3860Make KSB unit tests work with JPA
KULRICE-509Implement Store and Forward cability for KSB
KULRICE-7633BusClientFailoverProxy needs to be handling org.apache.cxf.transport.http.HTTPException as a failover exception
KULRICE-5193Move KSB implementation code which is currently in rice-impl module to rice-ksb-impl module
Rice Module:
KSB

 Description   

Failover purports to be implemented in BusClientFailureProxy however it looks like it only fails over once (i.e. doesn't keep trying multiple endpoints until it succeeds). I suppose that could be the desired effect so as not to illicit an extended block on the client application if waiting for a timeout to occur but it still seems like a sub-par implementation.



 Comments   
Comment by Eric Westfall [ 06/Sep/10 ]

Setting fix version to 1.0.3 since this is related to KULRICE-4287

Comment by Eric Westfall [ 06/Sep/10 ]

Actually, this jira is incorrect. The failover is trying multiple endpoints (notice the do-while loop surrounding service invocation)

Generated at Fri Nov 22 08:41:23 CST 2019 using JIRA 6.1.5#6160-sha1:a61a0fc278117a0da0ec9b89167b8f29b6afdab2.