In Exalate case, it could be linked to a big number of active connections on your Jira on-premise and the number of other plugins installed and activated on your machine.
To resolve this issue, you may disactivate Exalate synchronisation connections that you are not using any more.
As well as, augment the “heap” memory size of your Jira’s JVM: