When we run tests/benchmarks, we should register the default uncaught exception handler to handle uncaught exceptions

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Unknown
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Java Drivers
    • None
    • None
    • None
    • None
    • None
    • None

      • Any uncaught exceptions that are not VirtualMachineError, we may log via the driver logging mechanism. If it is not available, them we should handle them by calling t.getThreadGroup().uncaughtException(e, t), if t.getThreadGroup() is not null (it is null only if t has terminated), where t is the first argument of UncaughtExceptionHandler.uncaughtException, otherwise Thread.currentThread().getThreadGroup().uncaughtException(e, Thread.currentThread()).
      • If we encounter VirtualMachineError, we should terminate the process.
        • We still should try and handle such errors the same way we handle other uncaught exceptions, but make sure the VM terminates even if logging fails.

      For more details see

            Assignee:
            Unassigned
            Reporter:
            Valentin Kavalenka
            None
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: