Upgraded to new version, huge log files and crash after maint.data.purge

jmo

Hi, I upgraded a site to 1.13.0 and have log files getting extremely large.

INFO 2012-05-16 11:58:25,171 (org.directwebremoting.util.CommonsLoggingOutput.info:51) - Exec: WatchListDwr.init()
INFO 2012-05-16 11:58:25,171 (org.directwebremoting.util.CommonsLoggingOutput.info:51) - Exec: WatchListDwr.getDateRangeDefaults()
INFO 2012-05-16 11:58:25,218 (org.directwebremoting.util.CommonsLoggingOutput.info:51) - Exec: MiscDwr.doLongPoll()
INFO 2012-05-16 11:58:25,468 (org.directwebremoting.util.CommonsLoggingOutput.info:51) - Exec: MiscDwr.resetWatchlistState()
INFO 2012-05-16 11:58:25,656 (org.directwebremoting.util.CommonsLoggingOutput.info:51) - Exec: MiscDwr.doLongPoll()
INFO 2012-05-16 11:58:30,859 (org.directwebremoting.util.CommonsLoggingOutput.info:51) - Exec: MiscDwr.terminateLongPoll()

also have a crash after Data Purge,
INFO 2012-05-16 03:05:00,000 (com.serotonin.mango.rt.maint.DataPurge.executeImpl:65) - Data purge started
INFO 2012-05-16 03:05:01,703 (com.serotonin.mango.rt.maint.DataPurge.executeImpl:76) - Data purge ended, 0 point values deleted
WARN 2012-05-16 04:31:32,796 (com.serotonin.mango.rt.dataSource.PollingDataSource.scheduleTimeout:63) - LS: poll at 2012/05/16 04:31:32 aborted because a previous poll started at 2012/05/16 04:31:12 is still running
a bunch of the same here.
WARN 2012-05-16 17:08:47,906 (com.serotonin.mango.rt.dataSource.PollingDataSource.scheduleTimeout:63) - LS: poll at 2012/05/16 17:08:28 aborted because a previous poll started at 2012/05/16 17:04:08 is still running

ERROR 2012-05-16 17:49:03,953 (com.serotonin.mango.rt.maint.BackgroundProcessing$1.run:57) - Error in work item
java.lang.OutOfMemoryError: Java heap space

I have 2 installs at this site. One with modbus only, working fine, but huge logfiles.
One with opc, a little buggy anyway, but it works fine till the purge.

Any ideas?

Thanks,

Jim

mlohbihler

You can reduce the amount of logging by editing the WEB-INF/classes/log4J.xml file. At the bottom of the file you should find this:

  &lt;root&gt;
    &lt;level value="info"/&gt;
    &lt;appender-ref ref="async"/&gt;
    &lt;appender-ref ref="stdout"/&gt;
  &lt;/root&gt;

Change "info" to "warn" or "error", depending on what you want in your logs. You can also edit the category tags. See the log4j documentation for more information about the file.

Not sure what the issue with the OPC data source is (i didn't write it). But, out of memory exceptions usually mean that you should allocate more memory to your instance.