void release() throws InterruptedException
Note: The implementation is encouraged to release the associated
ByteBuffer if there are no remaining allocations
against it and MAY made the slice of the buffer available for
InterruptedException MAY be thrown. This allows us
to handle cases where a concurrent process (such as a query) was
halted and its component threads were interrupted. By looking for the
interrupt, we can avoid attempts to release an allocation in some
thread where the entire
DirectBufferPoolAllocator.IAllocationContext has already been
released by another thread.
Copyright © 2006–2019 SYSTAP, LLC DBA Blazegraph. All rights reserved.