Update notes for 2019-03-24

content/posts/2019-03.md

@@ -698,4 +698,18 @@ org.postgresql.util.PSQLException: This statement has been closed.
 - I compiled this [TomcatJdbcConnectionTest](https://github.com/gnosly/TomcatJdbcConnectionTest) and created a bunch of database connections and waited a few minutes but they never got abandoned until I created over `maxActive` (75), after which almost all were purged at once
   - So perhaps our settings are not working right, but at least I know the logging works now...
 
+## 2019-03-24
+
+- I did some more tests with the [TomcatJdbcConnectionTest](https://github.com/gnosly/TomcatJdbcConnectionTest) thing and while monitoring the number of active connections in jconsole and after adjusting the limits quite low I eventually saw some connections get abandoned
+- I forgot that to connect to a remote JMX session with jconsole you need to use a dynamic SSH SOCKS proxy (as I originally [discovered in 2017-11]({{< relref "2017-11.md" >}}):
+
+```
+$ jconsole -J-DsocksProxyHost=localhost -J-DsocksProxyPort=3000 service:jmx:rmi:///jndi/rmi://localhost:5400/jmxrmi -J-DsocksNonProxyHosts=
+```
+
+- I need to remember to check the active connections next time we have issues with blank item pages on CGSpace
+- In other news, I've been running G1GC on DSpace Test (linode19) since 2018-11-08 without realizing it, which is probably a good thing
+- I deployed the latest `5_x-prod` branch on CGSpace (linode18) and added more validation to the JDBC pool in our Tomcat config
+  - This includes the new `testWhileIdle` and `testOnConnect` pool settings as well as the two new JDBC interceptors: `StatementFinalizer` and `ConnectionState` that should hopefully make sure our connections in the pool are valid
+
 <!-- vim: set sw=2 ts=2: -->