This process caused our CPU usage to spike from 9% to 100% on 7/20/2016. After killing the proc/process 6 more appeared. After a few hours the CPU and IO issue stopped. Usage was back down to 9 to 10% again.
I found that this process was included in CPS 12.0.11 release as a fix to "Functional Measure CPOE Lab & Rad measure."
Any idea as to what this process does and how we can avoid this from happening again?
I believe this is for CQR. It may have been trying to resend all of your data again starting from a certain date. This is all set within the subscriptions in Adminstration, so if anyone changed any of the settings on those subscriptions, it could cause a data resend.
Another reason could be because that stored procedure was stuck and couldn't finish. Which could be due to some blocking or a bug with the stored procedure.
The reason you couldn't just kill the process is because your JBOSS was continuing to create these as you killed them. You would need to stop the JBOSS service, kill those processes, and start JBOSS back up. Although, if you haven't figured out what was wrong with the LabRadEvent proc, then you might have it happen again.
When this issue occurred, we were having problems with our Subscriptions in Admin > Interoperability. As of 8/2/2016, subscriptions, QIE, and CQR are in working order.
According to the information you provided, this shouldn't happen again (since we resolved the subscriptions issue).
I really appreciate you responding and steering me in the right direction!