I'm working with an older code base which I suspect is not closing reports properly. Due to the design of the application it isn't easy to fix the architecture to prevent this sort of thing from happening in the short term. In the mean time I was hoping there was a way to check how many open processing jobs there are so that I can go through the application and identify what actions and behaviors may be causing the number of jobs to increase.
I've done a number of Google searches on the subject but I did not find any documentation which would point me to acquiring this number. I have seen examples of creating a custom reporting pool but unfortunately that would be difficult to implement and probably just drag out the time it's going to take to fix the problem for good.
So can anyone recommend some resources on determining how many processing jobs exist in the ReportAppServer? Thanks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.