Dear list, We upgraded from DSpace 5.8 to 6.3 a few days ago and the database load went up significantly. Users report very long wait times and timeouts during item submission, taking items from the workflow, and approving items. You can see in the attached graph that we have a large number of connections waiting for locks.
When I look at the PostgreSQL status I see over 2,000 locks: $ psql -c 'SELECT * FROM pg_locks pl LEFT JOIN pg_stat_activity psa ON pl.pid = psa.pid;' | wc -l 2071 Looking at the locks I see at least half of them "idle in transaction" with the query being some SELECT statement. Why is Hibernate BEGINing transactions and not committing or rolling them back before returning them to the pool? We are using DSpace 6.3 on Tomcat 7.0.104 with Tomcat's JDBC connection pool provided via JNDI. Any help or pointers would be appreciated. Our editors can barely work now... -- Alan Orth [email protected] https://picturingjordan.com https://englishbulgaria.net https://mjanja.ch -- All messages to this mailing list should adhere to the DuraSpace Code of Conduct: https://duraspace.org/about/policies/code-of-conduct/ --- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/CAKKdN4VM7U-q-rPMF4zXK_ZjaTtWONGojdfuQgEdZ1vd2nLY7w%40mail.gmail.com.
