Seeking Assistance: Persistent JDBC Connection Leak (Idle in Transaction) on DSpace startup

[Nada Mehmoud Ahmed Ibrahim Aboueata]

Dear DSpace Community,

I am writing to seek assistance with a critical and persistent issue regarding database connection management immediately following application startup on my DSpace 6.3 instance.

Immediately after restarting my Tomcat service running DSpace 6.3 (using PostgreSQL and Apache Commons DBCP2/Hibernate), the database connection pool rapidly fills up with connections in the idle in transaction state. This eventually exhausts the pool, leading to application-wide errors (Timeout waiting for idle object) and general slowness. Browsing and performing functions as approving rejected or uploading files, is extremely slow, and sometimes it fails. 

Can you please assist, as this is a production env.