zookeeper-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mohammad arshad <mohammad.ars...@huawei.com>
Subject Unncessary Jline logs in zk client Consle
Date Mon, 15 Jun 2015 12:49:42 GMT

Hi  All,
Every time I connect to zookeeper through console zkCli.sh, I get following logs

[INFO] Unable to bind key for unsupported operation: backward-delete-word
[INFO] Unable to bind key for unsupported operation: backward-delete-word
[INFO] Unable to bind key for unsupported operation: down-history
[INFO] Unable to bind key for unsupported operation: up-history
[INFO] Unable to bind key for unsupported operation: up-history
[INFO] Unable to bind key for unsupported operation: down-history
[INFO] Unable to bind key for unsupported operation: up-history
[INFO] Unable to bind key for unsupported operation: down-history
[INFO] Unable to bind key for unsupported operation: up-history
[INFO] Unable to bind key for unsupported operation: down-history
[INFO] Unable to bind key for unsupported operation: up-history
[INFO] Unable to bind key for unsupported operation: down-history


The log is coming from jline.jar third party jar.  JLine is a Java library for handling console
input and here mainly used for command completion

This library is not using log4j or any other logging library. It is directly  printing logs
to console
Also it is not providing any configuration to control the logging level.
Log is being generated from jline.console.ConsoleKeys and finally printed by jline.internal.Log
to console



Is there any way to filter above logs without modifying jline jar?



Thanks & Regards
Mohammad Arshad


Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message