On an existing long standing application, after an upgrade to tomcat9 and jersey3, attempts to hit the application cause tomcat to return the following response:

```
HTTP Status 400 – Bad Requestbody {font-family:Tahoma,Ari
al,sans-serif;} h1, h2, h3, b {color:white;background-color:#525D76;} h1 {font-size:22px;} h2 {font-size:16px;} h3 {font-size:14px;} p {font-size:12px;} a {color:black;} .
line {height:1px;background-color:#525D76;border:none;}

HTTP Status 400 – Bad Request

Type Status Report

Message Bad Request

Description The server cannot or will not process the request due to something that is perceived to be a client error (e.g., malformed
request syntax, invalid request message framing, or deceptive request routing).

Apache Tomcat/9.0.65

Jersey needs a property that can be passed to the JDK that causes Jersey to output full stacktraces out of the front door for forensic debugging.

Server side logging is impossible to configure without already knowing what the problem is.