Uploaded image for project: 'OpenNMS'
  1. OpenNMS
  2. NMS-14061

Revisit error/exception handling in SshScriptingServiceImpl

    XMLWordPrintable

Details

    • Story
    • Status: Resolved (View Workflow)
    • Minor
    • Resolution: Fixed
    • 30.0.0
    • 30.0.0
    • None
    • Security Level: Default (Default Security Scheme)
    • 2
    • Horizon 22 - March 16 - 30
      • Error/Exception handling allows to identify error types (connection, scripting, ...)
      • Stacktraces are still available for debbuging/logging purposes

    Description

      While working on NMS-14039, I realize, that the error/exception handling is strange inside SshScriptingServiceImpl. It uses an Optional<Failure> which makes it pretty hard to distinguish between connection errors, scripting error, timeout issues and so on. Furthermore there is no way to access the stacktrace of the original exceptions anymore.

      Attachments

        Activity

          People

            cpape Christian Pape
            cpape Christian Pape
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: