-
Notifications
You must be signed in to change notification settings - Fork 426
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Resolve high thread count when using findSocketUsingThreading (#2104)
* Close a resource leak to prevent thread spawn. * Add resource leak fix. * Added test for thread count during find socket using threading. * Changed threshold to 5x * Changing servername from 'localhost' to prevent test failures. * Replace explicit close for socket, with try * Delete test.java that shouldn't have been pushed * Playing with the threadPoolExecutor thread limit. * .. * Increase threshold. * Removed TODO * After catching exception, we should continue. * Removed lingering artifacts. * Added debugging * More debugging * Even more debugging. * More debugging... * Try sleep change. * Trying without fix again to see coco behaviour with a final weight of 20000. * 10,000 * Addded some debugging in the IOBUffer * ... * Added condition to force multithreading. * More debugging earlier on * Edit test * More debugging. * Added print statements further up in the call stack. * for some reason, we're not logging * More debug * Trying without setting localhost in the test as this messes things up. * Manually set the iNetAddress to confirm the test is actually running. * Cleanup * Final cleanup before review. * Test cleanup. * We can't ignore the InterruptedException. If we catch, log, and interrupt the thread. * We don't want to continue, we don't to reinterrupt. * A different try with reflection. * One more try with reflection. * Exclude junit test from DB and DW. * whitespace * Remove localhost? * Moved back in localhost, otherwise the correct condition is not reached, and the multithread route is not used. * Check for localhost + PR comments * ... * Resolve failures that came up after inserting assertTrue() statement * Cleanup again
- Loading branch information
1 parent
7e476f4
commit 0eec249
Showing
3 changed files
with
73 additions
and
2 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters