JCP forced traces on routine U00003620 Routine 'com.automic.agents.impl.AgentLogBridge'
search cancel

JCP forced traces on routine U00003620 Routine 'com.automic.agents.impl.AgentLogBridge'

book

Article ID: 268415

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine

Issue/Introduction

Repeated JCP forced traces are seen on the routine U00003620 Routine 'com.automic.agents.impl.AgentLogBridge'. at various intervals with error below:

Parse exception: HttpParser{s=HEADER,0 of -1} for HttpChannelOverHttp@786b2bb8{s=HttpChannelState@3f456c56{s=IDLE rs=BLOCKING os=OPEN is=IDLE awp=false se=false i=true al=0},r=0,c=false/false,a=IDLE,uri=null,age=0}
20230614/041638.843 - 641    U00045014 Exception 'org.eclipse.jetty.http.BadMessageException: "400: No Host"' at 'org.eclipse.jetty.http.HttpParser.parseFields():1203'.
20230614/041638.843 - 641    U00003620 Routine 'com.automic.agents.impl.AgentLogBridge' forces trace because of error.

Environment

Release: 21.0.5 HF4

Cause

Known defect.

Resolution

Solution:

Update to a fix version listed below or a newer version if available.


Fix version:

Component(s): Automation Engine

Automation.Engine 21.0.8 - Available

Powered by Wolken Software