The Aerospike Knowledge Base has moved to https://support.aerospike.com. Content on https://discuss.aerospike.com is being migrated to either https://support.aerospike.com or https://docs.aerospike.com. Maintenance on articles stored in this repository ceased on December 31st 2022 and this article may be stale. If you have any questions, please do not hesitate to raise a case via https://support.aerospike.com.
FAQ - Are non-retryable exceptions in Java threadPool passed to caller?
Detail
The Aerospike Java Client offers the use of custom threadpool configuration. If the Java client ClientPolicy.threadPool is configured to use ThreadPoolExecutor and a non-retryable exception is thrown due to ressource exhaustion, would that exception be passed to the caller?
Answer
All non-retryable exceptions are passed back to the caller. In Aerospike Java client, assuming a caller’s threadPool.execute() fails, the RejectedExecutionException is passed to the caller. (for example: the caller of the scanAll method).
Notes
Java API exceptions handling
Keywords
JAVA API EXCEPTIONS
Timestamp
October 2021