# An excessive number of EA connections causes slowness in the system and high RAM usage

### Description

* Too many open connections observed when OpsHubEAWindowsService is running as console application and OpsHubEAWindowsService is forced closed using cancel button.
* Observations:
  * High RAM consumption
  * Slowness in the system because of too many EA connections remaining open.

### Cause

* This happens when the OpsHubEAWindowsService is being launched via console application and it has been forcibly closed using the cancel button.

### Solution

* Stop the OpsHubEAWindowsService (Recommend to close by pressing enter key).
* Press Windows + R to open the Run Dialog.
* Type 'taskmgr' and click OK to open Task Manager.

<div align="center"><img src="/files/8pqGUgZ6feAaoPwHxapk" alt="" width="800"></div>

* In the 'Background processes' section locate 'Enterprise Architect - UML Development Tool' processes.
* Right click on each process and select 'End task' to terminate it and release the resource.

<div align="center"><img src="/files/W7eDCUJPgHvEMSDi0wRO" alt="" width="900"></div>

> **Note**: To release all the connections properly when closing OpsHubEAWindowsService, we recommend to close OpsHubEAWindowsService using Enter key. Refer to [Setting up OpsHubEAWindowsService](/opstech-docs/connectors/enterprise-architect.md#setting-up-opshubeawindowsservice)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://opstech.gitbook.io/opstech-docs/help-center-index/faqs/enterprise-architect-faqs/an-excessive-number-of-ea-connections-causes-slowness-in-the-system-and-high-ram-usage.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.