BowerStudios.com

Know-it-all: "Hey God! Make a rock so big you can't pick it up."

God: "***OKAY***"
God turns ENTIRE Universe to rock.

God: "***There is no more up.***"
Somewhere in middle of rock is stone likeness of deceased Know-it-all.

-- Daniel Bower

Unfortunately, this isn't straightforward. Here is a question/answer from stackoverflow that may help.

A nice guide on how to verify the key you have for an ssl cert is the correct key is available from the University of Wisconsin

From: digitalOcean.com

keytool -delete -alias -keystore lib/security/cacerts -storepass changeit

I used to think that the brain was the most wonderful organ in
my body. Then I realized who was telling me this.

I was having difficulty getting UFW working with NAT, but this guide from James T worked out for me.

In particular, I was leaving off the commit afterwards in the beforerules file. I thought the file would only handle one commit, but 2 seemed to work just fine.

The other thing main thing to do was updating the config file for ufw in /etc/default/ufw.

Configuration for NAT

An excellent writeup as usual from Mr Haki

The Log4j extras javadocs are here

There's a nice description of the different types of timeouts that can be used with HttpClient at baeldung.com

Was tearing my hair out why this was failing yesterday.
sql.call('{call PACKAGE.MY_STORED_PROC(?,?,?,?,?) }',
[studentId, firstAssignmentDate, lastAssignmentDate, sectionCode, termCode])

The Error:
Message: Invalid column type
Line | Method
->> 8921 | setObjectCritical in oracle.jdbc.driver.OraclePreparedStatement
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
| 8396 | setObjectInternal in ''
| 9176 | setObjectInternal in ''
| 5024 | setObject in oracle.jdbc.driver.OracleCallableStatement
| 234 | setObject . . . . in oracle.jdbc.driver.OraclePreparedStatementWrapper


It failed with that error after I added some validation code. However, I could copy the code to the Grails Console, and it would work. If I called the Service from the Console, it would not work.

???

Apparently the Stored Procedure functionality of Groovy does not play well with @CompileStatic. I had added that with the validation code as an afterthought, and it was apparently the wrong thing.