Opened 51 years ago

Last modified 10 years ago

#918 new defect

IZ648: "UndeclaredThrowableException" when registering/unregistering listener to Configuration Service

Reported by: easymf Owned by:
Priority: normal Milestone:
Component: hedeby Version: 1.0u3_Beta-1
Severity: Keywords: Sun bootstrap


[Imported from gridengine issuezilla]

        Issue #:      648             Platform:     Sun            Reporter: easymf (easymf)
       Component:     hedeby             OS:        All
     Subcomponent:    bootstrap       Version:      1.0u3_Beta-1      CC:    None defined
        Status:       NEW             Priority:     P3
      Resolution:                    Issue type:    DEFECT
                                  Target milestone: 1.0u5next
      Assigned to:    adoerr (adoerr)
      QA Contact:     adoerr
       * Summary:     "UndeclaredThrowableException" when registering/unregistering listener to Configuration Service
   Status whiteboard:

     Issue 648 blocks:
   Votes for issue 648:     Vote for this issue

   Opened: Thu Apr 30 09:51:00 -0700 2009 


   The user can spot "UndeclaredThrowableException" in the log file of resource
   provider when he tries to add/remove the service to system and during the
   operation the configuration Service is shutdown (cs_vm is shutdown) or user can
   spot the exception when he registers/unregisters the
   ConfigurationServiceListener in Configuration Service using an API call.


   Middle priority - does not affect primary functionality, but is annoying from
   the user perspective.

   Suggested Fix/Work Around:

   No workaround possible, fix is neccessary.
   To fix, it is enough to change the signatures of the methods in following way:
   public interface ConfigurationService extends GrmComponent {
   public void
   addConfigurationServiceEventListener(ConfigurationServiceEventListener lis)
   throws GrmRemoteException;

   public void
   removeConfigurationServiceEventListener(ConfigurationServiceEventListener lis)
   throws GrmRemoteException;



   Problem is caused by not declaring the possibility of throwing the
   "GrmRemoteException" in
   ConfigurationService#removeConfigurationServiceEventListener and
   ConfigurationService#addConfigurationServiceEventListener. This fact causes,
   that component proxy infrastructure does not know how to handle the exception
   that occurs when remote object is not longer available.

   How to test:

   IMO the test is not necessary, as it is matter of component proxy framework
   (if we test the two methods mentioned in issue, then we should do it for all

   ATC: 0.5 PD
   ETC:     PD
               ------- Additional comments from rhierlmeier Thu May 7 23:52:44 -0700 2009 -------
   I will fix it together with issue 643
               ------- Additional comments from rhierlmeier Thu May 7 23:53:08 -0700 2009 -------
               ------- Additional comments from rhierlmeier Wed Jul 15 23:42:52 -0700 2009 -------
   Issue has not been fixed with 643, because exception handling requires some
   changes in classes that are using the add/remove methods.
               ------- Additional comments from rhierlmeier Wed Nov 25 07:21:11 -0700 2009 -------
   Milestone changed

Change History (0)

Note: See TracTickets for help on using tickets.