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.

AnnouncementAnnouncement Module

Collapse

No announcement yet.

DM Server simultaneously logging to all historical logs after rolloverPage Title Module

DM Server simultaneously logging to all historical logs after rollover

Apr 15th, 2010, 08:35 PM

Has anyone else seen this problem? Intermittently under dm server, one of our application’s bundles’ logs will roll over (using sifted rolling file appender) and then start logging simultaneously to all the historical log files for that application (log_1.log, log_2.log, etc.) as well as the current one (log.log). Once this happens, application performance is severely degraded.

We are using dm server 2.0.0.RELEASE running under either Windows XP or Windows 7 (problem has been seen on both). All of the application code has been updated to use slf4j logging and all references to log4j and apache commons logging have been removed from the bundle builds. (Third-party libraries it is using using may still be using log4j.)

The only logging configuration for the app is the serviceability.xml file in the dm server config directory. There are 4 active bundles deployed - a war file and 3 bundle jar files. To make these log into their own logs, they are currently deployed as separate plans, one of which is not scoped since it is shared (so logs into the default log).

Here is the serviceability.xml file contents: (The logging levels are currently as high as possible without preventing dm server from starting, to cause rollovers to occur quickly.)