tree 6999db35ec142dae2bb233080dc557e05b8efe5c
parent 14db20f044be9faba00e41214d4aa8765b43b355
author Vernon Mauery <vernon.mauery@linux.intel.com> 1581009721 -0800
committer Vernon Mauery <vernon.mauery@linux.intel.com> 1581361990 +0000

Catch async errors so they do not throw

When running an async operation, it is not a good idea to throw because
the current running context is not the context that it was originally
registered from, it is the io run-loop context. So any methods that
*would* throw, must run in a try/catch and then set the error code
properly so that the handler will be notified of the error.

This was caught when a process (bmcweb) was used to invoke a call that
had a bad path. That was not caught and it caused bmcweb to abort
because of an unhandled exception.

Change-Id: Ie66a029066a3f463759089b44368b7518d0de8ce
Signed-off-by: Vernon Mauery <vernon.mauery@linux.intel.com>