vishesh92 opened a new pull request, #13427:
URL: https://github.com/apache/cloudstack/pull/13427

   ### Description
   
   Production logs show a recurring WARN at startup:
     "could not get type for name org.conscrypt.AllocatedBuffer"
     (org.reflections.ReflectionsException / ClassNotFoundException)
   
   Root cause: ReflectUtil.getClassesWithAnnotation() uses 
ClasspathHelper.forPackage() to collect URLs to scan, but this returns all 
classpath entries (JARs/directories), not just those containing the target 
package. The Reflections library then scans every .class file in every JAR — 
including Netty's ConscryptAlpnSslEngine$BufferAdapter which references the 
optional org.conscrypt.AllocatedBuffer type. During expandSuperTypes(), 
Reflections tries Class.forName() on that type and fails because Conscrypt is 
not (and need not be) on the classpath.
   
   The fix adds a FilterBuilder that restricts bytecode scanning to only 
classes whose fully-qualified names match the requested packages. This prevents 
Reflections from processing unrelated classes (e.g., io.netty.handler.ssl.*), 
eliminating the warning and reducing startup time by skipping thousands of 
irrelevant class files.
   
   <!--- Describe your changes in DETAIL - And how has behaviour functionally 
changed. -->
   
   <!-- For new features, provide link to FS, dev ML discussion etc. -->
   <!-- In case of bug fix, the expected and actual behaviours, steps to 
reproduce. -->
   
   <!-- When "Fixes: #<id>" is specified, the issue/PR will automatically be 
closed when this PR gets merged -->
   <!-- For addressing multiple issues/PRs, use multiple "Fixes: #<id>" -->
   <!-- Fixes: # -->
   
   <!--- 
******************************************************************************* 
-->
   <!--- NOTE: AUTOMATION USES THE DESCRIPTIONS TO SET LABELS AND PRODUCE 
DOCUMENTATION. -->
   <!--- PLEASE PUT AN 'X' in only **ONE** box -->
   <!--- 
******************************************************************************* 
-->
   
   ### Types of changes
   
   - [ ] Breaking change (fix or feature that would cause existing 
functionality to change)
   - [ ] New feature (non-breaking change which adds functionality)
   - [ ] Bug fix (non-breaking change which fixes an issue)
   - [ ] Enhancement (improves an existing feature and functionality)
   - [ ] Cleanup (Code refactoring and cleanup, that may add test cases)
   - [ ] Build/CI
   - [ ] Test (unit or integration test code)
   
   ### Feature/Enhancement Scale or Bug Severity
   
   #### Feature/Enhancement Scale
   
   - [ ] Major
   - [ ] Minor
   
   #### Bug Severity
   
   - [ ] BLOCKER
   - [ ] Critical
   - [ ] Major
   - [ ] Minor
   - [ ] Trivial
   
   ### Screenshots (if appropriate):
   
   ### How Has This Been Tested?
   
   <!-- Please describe in detail how you tested your changes. -->
   <!-- Include details of your testing environment, and the tests you ran to 
-->
   
   #### How did you try to break this feature and the system with this change?
   
   <!-- see how your change affects other areas of the code, etc. -->
   
   <!-- Please read the 
[CONTRIBUTING](https://github.com/apache/cloudstack/blob/main/CONTRIBUTING.md) 
document -->
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to