Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 6913223
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 27, 20262026-05-27T09:11:27+00:00 2026-05-27T09:11:27+00:00

There is a pattern that happens every now and then. I have a method

  • 0

There is a pattern that happens every now and then. I have a method called many times, and it contains this snippet:

Foo foo = getConfiguredFoo();
if (foo == null) {
  logger.warn("Foo not configured");
  foo = getDefaultFoo();
}

Then my log file is cluttered with this warning a hundred times. I know I can grep it out, but I wonder if there is a better way to see this warning only once.

Note: the duplication of messages is a correct behavior by default, so this is not about avoiding unintentional duplicate log message. I tagged my question as log4j, but I’m open to other java logging frameworks.

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-27T09:11:28+00:00Added an answer on May 27, 2026 at 9:11 am

    Here is what I can come up with: a class that accumulates warnings which can be dumped at the end. It’s in groovy, but you can get the point. The dumping part can be customized to use a logger, of course.

    class BadNews {
      static Map<String,List<Object>> warnings = [:];
    
      static void warn(String key, Object uniqueStuff) {
        def knownWarnings = warnings[key]
        if (! knownWarnings) {
          knownWarnings = []
          warnings[key] = knownWarnings
        }
        knownWarnings << uniqueStuff
      }
    
      static void dumpWarnings(PrintStream out) {
        warnings.each{key, stuffs ->
          out.println("$key: " + stuffs.size())
          stuffs.each{
            out.println("\t$it")
          }
        }
      }
    }
    
    class SomewhereElse {
      def foo(Bar bar) {
        if (! bar)
          BadNews.warn("Empty bar", this)
      }
    }
    
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

Is there a pattern that I could apply to refactor this code? The only
Is there a pattern that is good to use when saving and loading different
Is there a specific pattern that developers generally follow? I never really gave it
Is there a multiple instances pattern in F# somewhere? Consider that I'm working on
I have a feeling that there must be client-server synchronization patterns out there. But
I have some code that uses the shared gateway pattern to implement an inversion
I have many cursors that all return rows with the same fields: a numeric
This is a topic that has been part of almost every application I've ever
Likewise are there design patterns that should be avoided?
Are there any mnemonics or patterns that make memorizing emacs key combos easier?

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.