Kuali Rice Development
  1. Kuali Rice Development
  2. KULRICE-3335

Failover is not working properly in the KSB in the case of a 404 coming back from a service

        Details

        • Similar issues:
          KULRICE-8075fix broken service failover tests in ServiceCallClusterTest.java
          KULRICE-12270Disable failover on topic messages in KSB
          KULRICE-5188Need to remove ImmutableListAdapter and ImmutableCollectionAdapter from our service definitions and come up with a better solution because it is producing undesirable XML
          KULRICE-2346Improve how the KSB handles "dead" services
          KULRICE-6509Synchronize with remote services on KSB startup
          KULRICE-13491Test failover of Rice components
          KULRICE-1517Strange transaction demarcation when invoking exception handler from KSB
          KULRICE-1753KSB service configurations are not getting cleared on KSB shutdown
          KULRICE-2209KSB failover implementation is inadequate
          KULRICE-4222Look into work done with KSB-only context when working on modularization of Rice for 1.1
        • Rice Module:
          KSB

          Description

          The failover code in the KSB seems to be really fragile. It seems to only be failing over in the case that a "Service removal exception" occurs. We need to allow it to failover properly in the case that any error occurs (especially a 404!). We'll want to report to the kuali Rice project (create a KULRICE jira) and then make a fix in our local copy and contribute back.

          this will fix EN-1250 (IU implementation of rice)

            Issue Links

            relates to

            Bug Fix - A problem which impairs or prevents the functions of the product. KULRICE-4287 Intermittent issues with KSB service lookup while running on embedded mode.

            • Critical - Crashes, loss of data, severe memory leak.
            • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

              Activity

              Hide
              Permalink
              Eric Westfall added a comment -

              Looking at this, this was actually fixed in 1.0.1 when the serviceRemovalResponseCodes were added to BusClientFailureProxy (that list includes 404 and 503)

              Show
              Eric Westfall added a comment - Looking at this, this was actually fixed in 1.0.1 when the serviceRemovalResponseCodes were added to BusClientFailureProxy (that list includes 404 and 503)

                People

                • Assignee:
                  Saurabh Ajmera (Inactive)
                  Reporter:
                  Saurabh Ajmera (Inactive)
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  0 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:

                    Structure Helper Panel