Home/ Questions/Q 8581181
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-11T20:59:11+00:00

I am developing a game server based on the top of someone else framework,

  • 0

I am developing a game server based on the top of someone else framework, netty and spring.

And I wonder whether it is a good approach to generate a separate file using log4j for every game room or not. Since with many game room servers has to keep open a lot of log files. On the other hand with only one log file it would be a total mess up which would required parsing and filtering when analyzing a problem.

If many log files is still a good approach when I need to know how to implement that. I have had a look at this question configure log4j to log to custom file at runtime, but first answer is not clear, how to minimize lines of code required in every attempt to write to a separate log file. I have tried the second answer with putting in config file

log4j.appender.logfile.File=${logfile.name}

but the framework has

PropertyConfigurator.configure(System.getProperty("log4j.configuration"));

which fails if log file is not specified at the start time.

Any ideas and comments are welcome! Thanks

UPD: This link also seems helpful in my case. Log4j logging to separate files But still: is it good idea and how to switch dynamically the output log file with minimal coding.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Really, when it comes down to it, having more than one log file for the game rooms would be overkill. The file I/O would have an effect on performance, even if that was negligible. Furthermore, as programmers, we have so many tools at our disposal for parsing and filtering information that it seems much more reasonable to do this after the fact.

    For instance, as long as each game room matches a specific pattern when logging, you could easily use grep and the Linux > operator to parse all of the data for game room X and write to another file where you could analyze it separately. Having your production server do this, when you may or may not even be looking at the logs, isn’t the best use of resources.

    As an example, running this command could quickly get me all the information I need about game room X:

    grep "game room x" mainLog.log > outputToAnalyze.log
    • 0