The Simple Logger is is internally thread safe starting from version 2.0.0.
However, an overall thread safety cannot be guaranteed since the thread safety strongly depends from the externally set output channel. If that output channel is thread safe then the Simple Logger is thread-safe, too.
The logger name cannot be set directly (or is overriden when successfully tried) when using the Spring Framework integration code from Simple Logger.
This is due to the fact that it is almost impossible to set a dynamic value inside Spring Framework easily.
Therefore the logger name is not used when logging the 'logger name' section in the log. Instead, the stack trace is analyzed and the class where the logger is referenced is analytically guessed by filtering class names from standard Java modules and known proxy class names used by Spring. Although, this approach was successfully tested, there is a chance that a wrong class name is guessed.
Also, a possible performance loss is taken into account for simplicity of usage caused by the stack trace analysis. However, this is considered low in small and medium scaled applications.