UT000199 exception logs bogus timestamp

Solution Verified - Updated -

Issue

  • We added a read/write-timeout to our undertow listener. When a timeout is reached, we see this produces a UT000199 org.xnio.channels.ReadTimeoutException message with a bogus timestamp:
DEBUG [io.undertow.request.io] (default I/O-14) UT005013: An IOException occurred: org.xnio.channels.ReadTimeoutException: UT000199: Read timed out after 1638571000771 milliseconds.

Environment

  • JBoss Enterprise Application Platform (EAP) 7.4.6 and earlier

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content