Uploaded image for project: 'Kuali Rice Development'
  1. Kuali Rice Development
  2. KULRICE-13852

Implement the capability for applications integrated with the KSB service registry to startup even if the registry is offline

          Details

          • Type: Improvement
          • Status: Open
          • Priority: Major
          • Resolution: Unresolved
          • Affects Version/s: None
          • Fix Version/s: Backlog
          • Component/s: Quality Assurance
          • Labels:
          • Rice Team:
            QA

            Description

            In Rice 1.0.x, client applications connected to the registry directly through the database layer. This had the advantage that the database, being a fairly high availability service, is usually online and operational when a client application starts up.

            Now that client apps connect through a SOAP service, that means that the entire Rice Standalone Server needs to be online (since it's not possible to just run the registry as an independent app) in order for client applications to come online. Considering the number of pieces in the Rice standalone server, this is going to be a problematic requirement for some I imagine since they may need to do maintenance on portions of the rice server that really have nothing to do with the registry and that will adversely affect other applications connecte to the bus.

            A client application should really be allowed to come online in these scenarios, they just might not be able to function properly but would begin functioning properly once the bus comes back online.

              Attachments

                Issue Links

                discovered by

                Improvement - An improvement or enhancement to an existing feature or task. KULRICE-4816 Implement interaction with the service registry so that it goes over remote connection instead of direct database access

                • Critical - Crashes, loss of data, severe memory leak.
                • Closed
                is related to

                New Feature - A new feature of the product, which has yet to be developed. KULRICE-13369 Make it easy to run the KSB Service Registry as a separate standalone application

                • Major - Major loss of function.
                • Open
                Trackbacks

                [Confluence: Kuali Rice] Impact in Upgrading to Kuali Rice 2.1.0 instead of 2.0.0 Overview At a recent meeting of the Kuali Rice Implementation Group, the fact that Kuali Rice version 2.1.0 will be released prior to our Rice 2.0 production date of August 5th, 2012 was discussed....

                  Activity

                  Ascending order - Click to sort in descending order
                  Hide
                  Permalink
                  jcoltrin Jessica Coltrin (Inactive) added a comment -

                  as soon as we can after 2.0 is released.

                  Show
                  jcoltrin Jessica Coltrin (Inactive) added a comment - as soon as we can after 2.0 is released.
                  Hide
                  Permalink
                  gilesp Peter Giles (Inactive) added a comment -

                  Added estimate. talked to Eric, got his WAG estimate and padded it a bit.

                  Show
                  gilesp Peter Giles (Inactive) added a comment - Added estimate. talked to Eric, got his WAG estimate and padded it a bit.
                  Hide
                  Permalink
                  wgomes Will Gomes (Inactive) added a comment -

                  At UMD we implemented a patch so on startup it will wait and retry for registry to come back online, so far it stalls the client, but at least it doesn't error. We plan on expanding this patch to also make use of the BusClientFailOverProxy for the registry service endpoint, so it can properly failover.

                  We were planning on contributing the patch back. Not sure if anyone had ideas on letting it startup without stalling.

                  Show
                  wgomes Will Gomes (Inactive) added a comment - At UMD we implemented a patch so on startup it will wait and retry for registry to come back online, so far it stalls the client, but at least it doesn't error. We plan on expanding this patch to also make use of the BusClientFailOverProxy for the registry service endpoint, so it can properly failover. We were planning on contributing the patch back. Not sure if anyone had ideas on letting it startup without stalling.

                    People

                    • Assignee:
                      eghm-kuali-m Erik Meade
                      Reporter:
                      ewestfal Eric Westfall
                    • Votes:
                      0 Vote for this issue
                      Watchers:
                      1 Start watching this issue

                      Dates

                      • Created:
                        Updated:

                        Time Tracking

                        Estimated:
                        Original Estimate - 1 week, 2 days, 4 hours
                        1w 2d 4h
                        Remaining:
                        Remaining Estimate - 1 week, 2 days, 4 hours
                        1w 2d 4h
                        Logged:
                        Time Spent - Not Specified
                        Not Specified