A way to use ThreadPoolExecutor in SegmentContextExecutors.newSegmentContextExecutor()

[task4233]

Hello,

Currently, SegmentContextExecutors.newSegmentContextExecutor provides an Executor which uses ForkJoinPool.commonPool().

However, as ForkJoinPool.commonPool() spends a long time on heavy tasks including I/O processing such as HTTP connections, there is a demand for using ThreadPoolExecutor which is shared in a single task queue.

For now, this problem might be resolved by using the setTraceEntity()` as below.

final Entity entity = AWSXRay.getTraceEntity();
CompletableFuture<?> completableFuture = CompletableFuture.supplyAsync(
  () -> {
    AWSXRay.setTraceEntity(entity);
    // do something ... 
  }, customedThreadPool);

However, as setTraceEntity() is deprecated, this way is not good for the future. Hence, if there's a way to resolve this problem, I'd like to know that.

Thanks in advance.

[wangzlei]

Thanks for raising this question. Yes, the current SegmentContextExecutor only run runnable in ForkJoin common pool. We should improve it to wrap an Executor user provides in input param. I label this as a feature.
Currently we shift the emphasis to OpenTelemetry, we suggest xray user try to migrate to OpenTelemetry.
https://github.com/open-telemetry/opentelemetry-java/blob/main/context/src/main/java/io/opentelemetry/context/Context.java#L233