I have noticed a dramatic increase in the following error in dspace.log org.hibernate.exception.GenericJDBCException: Unable to acquire JDBC Connection [Cannot get a connection, pool error Timeout waiting for idle object, borrowMaxWaitDuration=PT9.999999728S] [n/a]
In general, are there any recommendations for tuning the trio of database settings in dspace.cfg in terms of relative server load? i.e. what are reasonable values for a large and busy site? Given the limited setting available here, is connection pooling using a tomcat jndi resource a better option? I have seen this mentioned in the docs and here: https://github.com/DSpace/DSpace/issues/3070, but are there detailed instructions on how to implement this available? Thanks for any thoughts, ~~Bill -- ______________________________________ Bill Tantzen University of Minnesota Libraries 612-626-9949 (U of M) 612-325-1777 (mobile) -- All messages to this mailing list should adhere to the Code of Conduct: https://lyrasis.org/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 visit https://groups.google.com/d/msgid/dspace-tech/CADgrb7GKrKBrW-zM9Rmmuv%2BYC37UvRUopnqnA8_LvNY_DvLC7g%40mail.gmail.com.
