Opened 18 years ago

Last modified 11 years ago

#144 new enhancement

IZ859: JAPI Needs Its Own Error Codes

Reported by: templedf Owned by:
Priority: low Milestone:
Component: sge Version: 6.0beta
Severity: Keywords: Sun SunOS cleanup


[Imported from gridengine issuezilla]

        Issue #:      859              Platform:     Sun           Reporter: templedf (templedf)
       Component:     gridengine          OS:        SunOS
     Subcomponent:    cleanup          Version:      6.0beta          CC:    None defined
        Status:       NEW              Priority:     P4
      Resolution:                     Issue type:    ENHANCEMENT
                                   Target milestone: ---
      Assigned to:    andreas (andreas)
      QA Contact:     ernst
       * Summary:     JAPI Needs Its Own Error Codes
   Status whiteboard:

     Issue 859 blocks:   [DEL: 1195 :DEL] 1195
   Votes for issue 859:

   Opened: Mon Mar 15 09:07:00 -0700 2004 

At the moment, JAPI uses the DRMAA error codes.
In several places, the DRMAA error codes are
unable to accurately represent JAPI errors.  JAPI
needs to have its own set of error codes that can
be mapped to the DRMAA error codes.

   ------- Additional comments from templedf Wed May 5 06:59:12 -0700 2004 -------
See Issue #1013 for an example.

   ------- Additional comments from templedf Wed May 5 08:28:53 -0700 2004 -------
Perhaps instead of making a new set of JAPI error codes, JAPI could be
changed to reuse the GDI error codes.

   ------- Additional comments from templedf Thu Sep 30 07:45:23 -0700 2004 -------
I just looked into reusing the GDI error codes, and it doesn't look
promising.  The problem is that most of the GDI error codes map to
needs to return error codes not covered by GDI, such as session and
attribute errors.
It looks like the best solution is for JAPI to have a set of hybrid
error codes, and let DRMAA map the GDI/JAPI errors to INTERNAL_ERROR
and DENIED_BY_DRM errors.  However, what we are still lacking is a
compelling reason to make the change.  Issue 1195 wouldn't be helped
by new error codes.  Issue 1013 wouldn't really be helped either
because we'd still have to map the JAPI code back into a GDI code.

   ------- Additional comments from sgrell Mon Dec 12 02:58:23 -0700 2005 -------
Changed the Subcomponent.


   ------- Additional comments from ernst Wed Aug 20 07:34:28 -0700 2008 -------
Changed subcomponent

Change History (0)

Note: See TracTickets for help on using tickets.