Hi Ralph, On 27/08/2013 07:29, Ralph Goers wrote:
First, you are referring to Log4j 1.x.
Correct. > Most of our work is currently
focused on Log4j 2. That said, you would have the same issue with Log4j 2, Logback or even java.util.logging.
Understood.
What possible reason could you have for creating a logger per subscriber? The key to us being able to provide a solution is to know what you are attempting to accomplish by doing that. You cannot possibly configure 10 million loggers so it can't possibly have anything to do with that. If it is to have some mechanism to identify the subscriber than there are much better ways to do that.
No, they are not all created in 1 go: they are created dynamically as the subscriber might use the system. The main reason for making the subscriber part of the category is to be able to do tracing per subscriber.
I would suggest reading through the Log4j 2 manual at http://logging.apache.org/log4j/2.x/manual/index.html and seeing if the facilities it has provide a solution.
Sure. 2.x been in the works for just of a year now, so about time to plan migration.
-- __Deon_______________________________________________ TruTeq Wireless (Pty) Ltd. Tel: +27 12 667 1530 http://www.truteq.co.za Fax: +27 12 667 1531 Timezone: SAST GMT+2 Copyright&Legal: http://truteq.co.za/legal_notice.pdf --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
