[POOL-320] Use more efficient stack walking mechanisms for usage tracking

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.4.2
• Fix Version/s: 2.4.3
• Assignee: Matt Sicker
• Reporter: Matt Sicker
• Created: 03/Mar/17 18:10
• Updated: 29/Oct/17 16:07
• Resolved: 04/Mar/17 20:20

Description

When usage tracking is enabled, pooled object users are discovered by creating an exception. This is slower than optimal which could be done via various strategies such as a SecurityManager, reflection on the internal Reflection class, or for Java 9 users, the new StackWalker API.