SyslogAppender retains stack trace when it shouldn't

[kumar k]

Hello,

I am attempting to configure the drop wizard application to send logs to 

syslog for centralized logging. I've located the correct logger, and I've successfully 

configured a SyslogAppender to send the events to syslog, but I'm 

getting an odd bit of  a stack trace in the syslog, even though I think 

It shouldn't.

When the line gets logged to syslog, I see the first line correctly, but 

that line is followed by a stack trace, except that the beginning of the 

stack trace is replaced with the string "#011". What I want is no stack 

trace at all, which I ought to be able to get with %nopex, except that 

doesn't seem to work.Can you please help me on this issue?

Drop Wizard version:0.9.2

Log Back version: 1.1.2

drop wizard logging config:

syslog:

    enabled: 'true'

    threshold: ALL

    host: localhost

    facility: local6

    logFormat: "MMJ: %p [%logger{0} %t] %c{30} [%X] %m %nopex"

Log snippet from syslog:

2020-04-27T13:20:46+00:00 MMJ MMJ: ERROR [ConcurrentAuditPersisterQueueSubscriber qe_Event_Queue_AUDIT-1] t.h.w.a.s.ConcurrentAuditPersisterQueueS ubscriber Error processing message payload  [] 

2020-04-27T13:20:46+00:00 MMJ #011net.liftweb.json.JsonParser$ unknown token <#012Near:

2020-04-27T13:20:46+00:00 MMJ #011at scala.Option.orElse(Option.scala:289)

2020-04-27T13:20:46+00:00 MMJ #011at scala.collection.immutab

Thanks,

Kumar