The isDbRunning() method within AI.mcp.server.memory.DatabaseLifecycleService was previously creating a new ChromaClient instance for every check, leading to unnecessary overhead. This ticket documents the improvement to leverage the already instantiated ChromaManager singleton's client for performing the heartbeat() check.
This approach aligns with the goal of integrating Neo.mjs core into the MCP servers by utilizing existing singletons and their managed resources, while also being more efficient.
Acceptance Criteria
- The
isDbRunning() method in AI.mcp.server.memory.DatabaseLifecycleService imports the ChromaManager singleton.
- The
isDbRunning() method uses ChromaManager.client.heartbeat() within a try...catch block to check for a running ChromaDB instance.
- The method correctly returns
true if heartbeat() succeeds and false if it fails (e.g., due to ChromaManager.client being null or the database not being reachable).
The
isDbRunning()method withinAI.mcp.server.memory.DatabaseLifecycleServicewas previously creating a newChromaClientinstance for every check, leading to unnecessary overhead. This ticket documents the improvement to leverage the already instantiatedChromaManagersingleton's client for performing theheartbeat()check.This approach aligns with the goal of integrating Neo.mjs core into the MCP servers by utilizing existing singletons and their managed resources, while also being more efficient.
Acceptance Criteria
isDbRunning()method inAI.mcp.server.memory.DatabaseLifecycleServiceimports theChromaManagersingleton.isDbRunning()method usesChromaManager.client.heartbeat()within atry...catchblock to check for a running ChromaDB instance.trueifheartbeat()succeeds andfalseif it fails (e.g., due toChromaManager.clientbeing null or the database not being reachable).