Thanks. I'll try the logging change to see if i can at least narrow it down
a bit more.
On Wed, Feb 21, 2018 at 7:49 PM, Konstantin Kolinko
wrote:
> 2018-02-21 22:19 GMT+03:00 Alex O'Ree :
> > That's the error message. The problem is I have no idea which client it
> is
> > and what character it
2018-02-21 22:19 GMT+03:00 Alex O'Ree :
> That's the error message. The problem is I have no idea which client it is
> and what character it is sending that is causing the issue. Thus I would
> like to get the offending header logged in some way.
The "http-nio-8080-exec-3" in the message is the th
On 21/02/18 19:19, Alex O'Ree wrote:
> That's the error message. The problem is I have no idea which client it is
> and what character it is sending that is causing the issue. Thus I would
> like to get the offending header logged in some way.
That sounds like an enhancement request for the log me
That's the error message. The problem is I have no idea which client it is
and what character it is sending that is causing the issue. Thus I would
like to get the offending header logged in some way.
On Tue, Feb 20, 2018 at 4:25 PM, Coty Sutherland
wrote:
> On Tue, Feb 20, 2018 at 4:01 PM, Alex
On Tue, Feb 20, 2018 at 4:01 PM, Alex O'Ree wrote:
> I keep running into the an IllegalArgumentException at or near startup of
> tomcat 8.5 with a bunch of cxf web services deployed and I have no idea
> what's causing it. The error message mentions turning on logging at the
> debug level.
Random
I keep running into the an IllegalArgumentException at or near startup of
tomcat 8.5 with a bunch of cxf web services deployed and I have no idea
what's causing it. The error message mentions turning on logging at the
debug level.
Question: Assuming i need to edit the logging.properties file, whic
