First IT failure on second run in dev mode fails due to connection pooling issues

[scottkurz]

I see errors like this:

[9/17/19, 17:07:01:337 EDT] 000003d5 SystemErr R Caused by: java.io.EOFException
[9/17/19, 17:07:01:338 EDT] 000003d5 SystemErr R at org.postgresql.core.PGStream.receiveChar(PGStream.java:323)
[9/17/19, 17:07:01:338 EDT] 000003d5 SystemErr R at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1978)
[9/17/19, 17:07:01:338 EDT] 000003d5 SystemErr R at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:309)
[9/17/19, 17:07:01:339 EDT] 000003d5 SystemErr R ... 71 more

when running the ITs in this project a second time in dev mode.

At first I thought it was an issue with the JaxrsJsonIT.testCreatePerson() failing a second time, but tried @TestMethodOrder and noticed whichever test ran first would fail.

I'd guess this issue:
MicroShed/microshed-testing#56
was opened in recoginition of this underlying problem.