In sling-org-apache-sling-connection-timeout-agent commit 01d35c7 an OSGi-specific fix was applied but there was no corresponding integration test.
The potential fix is to add a Pax-Exam tests which adds:
- a HTTP client bundle ( any of the supported ones should do )
- a client using the HTTP client bundle
And then assert that the requested class was transformed. It may be a good idea to do the assertion using JMX.
The only issue to consider is that I did not find good information on running Pax-Exam with JUnit 5. We currently use JUnit 5 for the connection timeout agent.