topic tFileFetch throwing "INFO: Response content length is not known" message to console - How to suppress Message in Talend Studio

tFileFetch throwing "INFO: Response content length is not known" message to console - How to suppress Message

Edith1 — Fri, 09 Jul 2021 19:26:59 GMT

The child job is going through PROXY and I keep getting this message:

org.apache.commons.httpclient.HttpMethodBase readResponseBody

INFO: Response content length is not known

When I use the option to Print Response to Console for tFileFetch component, I am seeing the Content-Length.

Status Line: HTTP/1.1 200 OK

*** Response Header ***

access-control-allow-origin: *

content-type: application/json

date: Fri, 09 Jul 2021 19:14:14 GMT

server: xxx

strict-transport-security: max-age=xxx

x-tw-requestid: xxx

Content-Length: 323

Connection: keep-alive

Why am I getting this info message?

I tried to suppress the message using the Project Settings > LOG4J2, but it didn't work. Here's the java code I inserted:

<?xml version="1.0" encoding="UTF-8"?>

</Console>

</Appenders>

</Root>

<Logger name="org.apache.commons.httpclient.HttpMethodBase" level="INFO">

</Logger>

</Loggers>

</Configuration>

gjeremy1617088143 — Mon, 12 Jul 2021 07:49:41 GMT

HI, it's not an error message it's just info, you can set the level you want for log4j:

https://help.talend.com/r/nAXiZW0j0H~2~YApZIsRFw/mh_X7GKiBIpVqK4azL5cwQ

Send me Love and kudos

Edith1 — Tue, 13 Jul 2021 17:55:34 GMT

Thanks @guenneguez jeremy for the reply. The link you shared is out of date and that version of log4j will be or is decommissioned. I found new article Configuring Log4j • Talend Big Data Platform Studio User Guide • Reader • Welcome to Talend Help Center, but the logger I am configuring is not suppressing it at all. I'm sure I'm doing something wrong in the configuration, which I cannot figure out.

gjeremy1617088143 — Thu, 15 Jul 2021 10:04:26 GMT

also some components will just throw a message on the console but doesnt log it

(eg, TFilecopy error with die on error unchecked).

You can test it with a tlogcatcher