[09:05:25 CDT(-0500)] <JoeMoore> Our stats recorder quit recording a few days ago--I haven't found the log message yet
[09:05:51 CDT(-0500)] <EricDalquist> hrm, there was an issue around stats stopping writing to the db a while ago
[09:05:58 CDT(-0500)] <JoeMoore> Is there any way to get it to retry without restarting tomcat/uportal?
[09:06:04 CDT(-0500)] <EricDalquist> I think it was pinned down to needing to update the quartz library
[09:06:15 CDT(-0500)] <EricDalquist> If it is the quartz bug, probably not
[09:06:31 CDT(-0500)] <JoeMoore> This was while our instance had been running for a few weeks without any changes
[09:06:50 CDT(-0500)] <EricDalquist> not seeing any errors in the logs?
[09:07:25 CDT(-0500)] <JoeMoore> Not any ongoing errors
[09:07:57 CDT(-0500)] <EricDalquist> how does memory usage look?
[09:08:30 CDT(-0500)] <JoeMoore> It seems like once it saw the error it quit retrying
[09:09:22 CDT(-0500)] <JoeMoore> It sounds like the original question is somewhat moot-the server is going to need to be restarted anyway-I'll see if the logs start up on reboot
[09:10:25 CDT(-0500)] <JoeMoore> In answer to your memory question-the server needs memory (don't we all 
-it's on order
[09:10:49 CDT(-0500)] <EricDalquist> just asking because what I believe has been seen before is the quartz job dies for some reason
[09:10:59 CDT(-0500)] <EricDalquist> and stats events just start filling up the queue
[09:11:03 CDT(-0500)] <EricDalquist> since it isn't being flushed
General
Content
Integrations