DDC-3674: Additional informations when closing EntityManager #4510

New Issue

admin · 2026-01-22T14:43:34+01:00

admin commented

2026-01-22 14:43:34 +01:00

Originally created by @doctrinebot on GitHub (Apr 8, 2015).

Originally assigned to: @beberlei on GitHub.

Jira issue originally created by user dmecke:

When the EntityManager is closed there is no way to find out why it has been closed afterwards. For example it would be nice if ORMException::entityManagerClosed() could add the information which query caused it to close. That would ease debugging a lot.
Maybe the EntityManager::close() method could get a parameter which stores the query or informations about it in a property next to the EntityManager::closed property?

Originally created by @doctrinebot on GitHub (Apr 8, 2015). Originally assigned to: @beberlei on GitHub. Jira issue originally created by user dmecke: When the EntityManager is closed there is no way to find out _why_ it has been closed afterwards. For example it would be nice if `ORMException::entityManagerClosed()` could add the information which query caused it to close. That would ease debugging a lot. Maybe the `EntityManager::close()` method could get a parameter which stores the query or informations about it in a property next to the `EntityManager::closed` property?

admin added the Improvement label 2026-01-22 14:43:34 +01:00

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: doctrine/archived-orm#4510