On 27/11/2020 19:56, Hrafn Malmquist wrote: > Great. Thanks. > > Glad it was a simple fix. > > By the way, why would you choose DBCP2 over Tomcat? Intuitively, I would > assume a pool designed specifically for Tomcat would be more efficient than > a more generic Apache library?
There is very little between them in terms of performance, especially if you configure them for equivalent behaviour. I'd summarise the differences as: - DBCP2 follows the JDBC specs a little more closely by default - jdbc-pool has marginally better performance under high load - jdbc-pool has better JMX monitoring - issues tend to get fixed sooner in DBCP2 I tend to value spec compliance so that gives DBCP2 the edge for me. Mark > > Hrafn > > > On Fri, Nov 27, 2020 at 8:24 AM Mark Thomas <ma...@apache.org> wrote: > >> On 26/11/2020 22:52, Hrafn Malmquist wrote: >>> Ahhhh >>> >>> How silly of me. It's right there staring me in the face nested inside >> the >>> host in server.xml, right? >> >> Right. >> >> The changes to GlobalResources look good. >> >> You'll probably want to revert the change you made to appBase. >> >>> So, best practice is to remove contexts from host and place either under >>> [engine]/[host] or directly in META-INF in app? >> >> Generally, yes although I'd recommend changing one thing at a time so >> get the DataSource working before you start moving config files around. >> >> You'll want something like: >> >> <Context path="" docBase="/dspace/webapps/xmlui"> >> <ResourceLink name="jdbc/dspace" >> global="jdbc/dspaceWeb" >> type="javax.sql.DataSource" >> /> >> </Context> >> >> in server.xml >> >> Mark >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org >> For additional commands, e-mail: users-h...@tomcat.apache.org >> >> > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
