Avoid per-request Pattern.compile() calls. [SPR-9749]

[spring-projects-issues]

Patrick Linskey opened SPR-9749 and commented

---

Affects: 3.1.1, 3.1.2, 3.2 M2

Issue Links:

• #15429 MemoryLeak in AntPathMatcher during caching AntPathStringMatcher instances

[spring-projects-issues]

Patrick Linskey commented

GitHub commit for 3.1.1: pcl@ca2bc82
GitHub commit for master: pcl@f038321

'./gradlew build' succeeds with this patch on master. I'm still trying to figure out how to get 3.1.1 to build on my machine (http://forum.springsource.org/showthread.php?129846-Spring-3-1-1-compilation&p=423733#post423733)

[spring-projects-issues]

Patrick Linskey commented

FYI, this eliminates 3% of the CPU burn in my Spring-MVC app.

[spring-projects-issues]

Patrick Linskey commented

If the per-instance maps are a concern, it looks like the string matchers could also be cached statically / at a higher level, and shared among multiple parent matchers.

[spring-projects-issues]

Rossen Stoyanchev commented

This change has been applied to master and 3.1.x. Thanks!