WebServer ThreadPoolExecutor was never shutdown, as it was assumed
HTTPServer.shutdown() would perform that.
In extreme cases 250 reloads could lead to a OutOfMemoryException due to
Heap size allocation for threads not being possible.
Change: Shut down ThreadPoolExecutor manually.
Since PluginData objects are more persistent than AnalysisContainer,
objects related to the each analysis can not be freed until the next
analysis has been performed, because a reference was held in each
PluginData object.
Change: set the reference to point to null in a finally block after
getServerData call. AnalysisContainer can now be freed by GC at any time
Affected issues: #685
Where possible replaced with PluginLogger or ErrorHandler calls,
some places removed a catch clause and added throws,
some places removed the log or benchmark completely.
Some places still need to be modified so that the required dependencies
can be injected.
Registered pages on ResponseHandler separately
Registered commands in PlanCommand and PlanBungeeCommand separately
Made WebServer Lazy in InfoSystems and ConnectionSystems
Moved Import data objects to system.importing.data
Moved Importer classes to system.importing.importers
Bound ImportSystem instances in SuperClassBindingModules
Added ImportSystem as injected parameter to PlanSystem
Injected ImportSystem to ManageImportCommand
Removed old references to ImporterManager and removed the class
Moved ImportBuilderTest to system.importing.data
- static final class variable names in PingCountTimerBukkit
- plugin field hiding protected variable in SpongeTaskSystem
- InspectPageResponse not overriding equals method
Old way:
Pre-render & cache the html for a player page when the player joins,
leaves or switches server
New way:
Render & cache the html when requested. Remove the rendered html from
cache if the player joins, leaves or switches server
This should prevent server from crashing if a bunch of bots join
Impacts #685
Reduced use of CachingSupplier in every DataContainer to reduce the
amount of String variables ending up in heap for a longer period of
time.
Impacts #685
