mirror of
https://github.com/spring-projects/spring-boot.git
synced 2024-09-03 04:26:12 +08:00
d241171fff
When nested jars are being used, hasMoreElements requires opening a connection for an entry in every nested jar. If that entry doesn't exist, a FileNotFoundException is thrown to indicate that a particular jar doesn't contain the requested entry. This exception is used to indicate the lack of an entry and is then swallowed, i.e. its stack trace is of no importance. This means that the performance of hasMoreElements can be improved by switching on fast exceptions while it's being called. When fast exceptions are switched on a general purpose pre-initialized FileNotFoundException is thrown rather than creating a new FileNotFoundException instance each time. In certain situations, the use of fast exceptions as described above can improve performance fairly significantly. The JRE's default SAAJ implementation uses META-INF/services-based discovery for _every_ request that's handled by Spring Web Services. Each discovery attempt results in hasMoreElements being called making its performance critical to throughput. See gh-3640 |
||
|---|---|---|
| .. | ||
| spring-boot-configuration-processor | ||
| spring-boot-dependency-tools | ||
| spring-boot-gradle-plugin | ||
| spring-boot-loader | ||
| spring-boot-loader-tools | ||
| spring-boot-maven-plugin | ||
| pom.xml | ||