Service Virtualization

We are seeing the error below in the registry log.  It starts around 3:15 am and is written to the log every few seconds. Any ideas on how to resolve this error?

2017-05-04 17:24:10,721Z (12:24) [Event Handler 60] ERROR com.itko.lisa.history.HistoryWriteSupport - Error capturing report data for Database: The database writer cannot keep up with the number of events being generated
com.itko.lisa.test.EventDeliveryException: The database writer cannot keep up with the number of events being generated
at com.itko.lisa.history.HistoryWriteSupport.batchWriteToDb(HistoryWriteSupport.java:503)
at com.itko.lisa.history.HistoryWriteSupport.writeObject(HistoryWriteSupport.java:420)
at com.itko.lisa.history.HistoryWriteSupport.writeMetricEvent(HistoryWriteSupport.java:408)
at com.itko.lisa.history.HistoryWriteSupport.pushEventFromCoordinator(HistoryWriteSupport.java:268)
at com.itko.lisa.report.DefaultReportToDataModel.pushEvent(DefaultReportToDataModel.java:225)
at com.itko.lisa.coordinator.ReportGenerator.testEvent(ReportGenerator.java:520)
at com.itko.lisa.test.TestEventMgr.pushEvent(TestEventMgr.java:315)
at com.itko.lisa.net.RemoteEventDeliverySupport.pushEvent(RemoteEventDeliverySupport.java:142)
at com.itko.lisa.test.TestEventMgr.pushEvent(TestEventMgr.java:283)
at com.itko.lisa.coordinator.BaseCoordinator.fireTestEvent(BaseCoordinator.java:400)
at com.itko.lisa.coordinator.BaseCoordinator.fireTestEvents(BaseCoordinator.java:433)
at com.itko.lisa.simulator.EventHandler.dump(EventHandler.java:332)
at com.itko.lisa.simulator.EventHandler.run(EventHandler.java:275)
at java.lang.Thread.run(Thread.java:745)

Normally you get this error when too many events are being generated and the Coordinator cannot keep up.

I would look at what type of Reporting you are doing. Change all your staging docs to use Load Test Report Generator instead of Default Report Generator.

Let me know if this helps.

Rich,

Did Marcy's recommendations help you out regarding this issue?

Regards,

Reid

Reid/Marcy,

We are currently taking a different approach.  The database has grown to 70 GB and the issue seems to start around the time we are taking our database backup.  It appears that we cannot access the database shortly after we start the backup and eventually we lose connectivity to the registry causing DevTest to fail.  We have truncated the database and are monitoring the system.  Since truncating the database, we have not seen this issue.

Good news.  Going forward, so as not to incur a lot of data, you might ought set the Report Cleaner properties in the local.properties file of where the Registry is running to something like this:

# In order to check for expired reports,
# set autoExpire = true.
# Set the expiration period -- an integer followed by (w=week,d=day,h=hour,m=minute).
# The default expiration period is 30d (30 days).

perfmgr.rvwiz.whatrpt.autoExpire=true
perfmgr.rvwiz.whatrpt.expireTimer=7d