> I mean once you hit that all bets are off, you need to restart your process...basically I think we shouldn't be messing with that.
Yeah, the most important thing to do is get out of the way and let the process exit with a non-zero status code.
So the options as I see it are:
(1) Do something ugly (like pass the original fetch request to byteBufferAllocate) for the purposes of a valiant but possible futile logging attempt (there is no guarantee we will be able to allocate the logging Strings we are already asking for, everything we ad makes that less likely).
(2) Just rethrow e after a logging attempt in byteBufferAllocate.
My preference is (2), but if someone prefers (1) that's a reasonable trade off.