Great find with the linked issue! However, that specific root cause should be fixed in the APM Agent version you are using (1.36.0) unless there is a regression. It would be great if you could help us narrow it down.
I don't think that your specific problem is caused by the executor instrumentation, but maybe by our servlet-API instrumentation.
Could you try the following steps:
- change the
classes_excluded_from_instrumentationtoorg.jboss.weld.proxies.HttpServletRequest*to verify that actually an instrumentation of that proxy-class is causing the issue - try without the
classes_excluded_from_instrumentationbut with-Delastic.apm.enable_type_pool_cache=false. If the problem does not occur, we might indeed have a regression of the linked issue.