Details
Minor Description
It would be nice to call getState().reset() in ClientProxyImpl.invoke() final block. My use case is JAXRSClientFactoryBean in thread-local configuration, which combined with big thread pool can cause a kind of memory leak. I never need to access the state after I get result from the proxy, but if you think somebody may need, let's make it configurable.
There is "timeToKeepState" of course, but it's far from ideal because response objects still cannot be garbage collected immediately and there's small added overhead of having all that extra threads.