This forum is now a read-only archive. All commenting, posting, registration services have been turned off. Those needing community support and/or wanting to ask questions should refer to the Tag/Forum map, and to http://spring.io/questions for a curated list of stackoverflow tags that Pivotal engineers, and the community, monitor.
No announcement yet.
Recommended log4j.xml configurationPage Title Module
INFO or even WARN is usually enough for a mature application.
If you can afford the overhead and disk space, it is often useful to run with DEBUG at first so you can see messages flowing through and track down issues more easily. Having the ability to change log levels dynamically mitigates this somewhat, but I tend to like having too much logging at first, and cut back as things settle down. (This is my experience for any app, not just Spring Integration).