Home Forums Kamanja Forums Enhancement Requests & Contributions doc enhancement: cover ALL ERROR MESSAGES

This topic contains 1 reply, has 2 voices, and was last updated by  Shilpa 1 year, 3 months ago.

  • Author
    Posts
  • #17428 Reply

    Greg Makowski
    Moderator

    Hello,

    I realize the intent of the forum is for issues to be brought up as people come across them.  This is a request for a new documentation section (to support our “ease of use” goal), to cover all error messages by plan (instead of just the ones tripped over to date).  The list below is written with the intent of “maximizing ease of use”.  I realize developer time needs to be balanced practically.

    1. what is the unique error message? (used for matching with a text search)
    2. how severe is the error message?   error vs. warning?
    3. Would it be okay to have this message in a high reliability production system?  If so, can “noise” messages be suppressed so the production system can meet a “no error message” standard?
    4. describe what it means.  If it is “too hard to describe” because it covers to many different situations – then what should we do to improve “ease of use” to get a more narrow or meaningful error message?  Provide links to related documentation sections, to provide better context for the reader.
    5. give at least an example of how the message can be generated.  Is it covered by a specific regression test?  In that example, what is done to resolve the issue.
    6. what should be done to get more information to diagnose the problem?
    7. what are ways to resolve the problem?
    8. should we have a unique error ID, that could be used when searching across forums and error documentation.
    9. should each error have its own documentation section link?  This way, when a person reports an issue in the forum, they can include the link, and just describe how they are different.
    10. Going forward, as developers generate new error messages, they add to this documentation as part of the sprint.

     

    SLF4J: Class path contains multiple SLF4J bindings.

    SLF4J: Found binding in [jar:file:/Users/Udgata/Downloads/Kamanja-1.4.1_2.11/lib/system/ExtDependencyLibs2_2.11-1.4.1.jar!/org/slf4j/impl/StaticLoggerBinder.class]

    SLF4J: Found binding in [jar:file:/Users/Udgata/Downloads/Kamanja-1.4.1_2.11/lib/system/ExtDependencyLibs_2.11-1.4.1.jar!/org/slf4j/impl/StaticLoggerBinder.class]

    SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.

    SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory]

    [1]System

     

    • This topic was modified 1 year, 3 months ago by  Greg Makowski.
  • #17465 Reply

    Shilpa

    SLF4J: Class path contains multiple SLF4J bindings.

    SLF4J: Found binding in [jar:file:/Users/Udgata/Downloads/Kamanja-1.4.1_2.11/lib/system/ExtDependencyLibs2_2.11-1.4.1.jar!/org/slf4j/impl/StaticLoggerBinder.class]

    SLF4J: Found binding in [jar:file:/Users/Udgata/Downloads/Kamanja-1.4.1_2.11/lib/system/ExtDependencyLibs_2.11-1.4.1.jar!/org/slf4j/impl/StaticLoggerBinder.class]

    SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.

    SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory]

    [1]System

    The error shown above occurs when you have not uploaded the cluster config json file and are running the “add message”/”add model” command without specifying the message/model name. The messages except the last line are warning messages which can be ignored. The last line displays only System node and no tenant nodes.  So, kafka is looking for tenant_id nodes when there aren’t any on the server.

    Upload the config file and run the command again. List of tenant_ids will be displayed, choose the one you need and proceed (as shown below – after uploading the config file):

    $ kamanja add message

     

    Using default configuration /Users/Udgata/Downloads/Kamanja-1.4.1_2.11/config/MetadataAPIConfig.properties

     

    WARN [main] – DATABASE_SCHEMA remains unset

    WARN [main] – DATABASE_LOCATION remains unset

    WARN [main] – DATABASE_HOST remains unset

    WARN [main] – ADAPTER_SPECIFIC_CONFIG remains unset

    WARN [main] – SSL_PASSWD remains unset

    WARN [main] – AUDIT_PARMS remains unset

    WARN [main] – DATABASE remains unset<

     

    SLF4J: Class path contains multiple SLF4J bindings.

    SLF4J: Found binding in [jar:file:/Users/Udgata/Downloads/Kamanja-1.4.1_2.11/lib/system/ExtDependencyLibs2_2.11-1.4.1.jar!/org/slf4j/impl/StaticLoggerBinder.class]

    SLF4J: Found binding in [jar:file:/Users/Udgata/Downloads/Kamanja-1.4.1_2.11/lib/system/ExtDependencyLibs_2.11-1.4.1.jar!/org/slf4j/impl/StaticLoggerBinder.class]

    SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.

    SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory]

    ERROR [main] – Node Undefined not found in metadata

    [1]tenant1

    [2]System

    Enter your choice(If more than 1 choice, please use commas to seperate them): 1

Reply To: doc enhancement: cover ALL ERROR MESSAGES
Your information: