Hi all,

We are having issues where users are submitting WebFocus reports, but then deciding that they are taking too long to return a result or they have input bad selection criteria. So they are closing down their Internet explorer session that is launched on submitting a report and thinking that this has cancelled their report. However the agent is still running on the server. They then submit another report and we have 2 agents running.

This is causing us quite a few problems and we are trying to educate the users into never cancelling the session, but to contact our tech desk so we can kill the agent, but this does not always happen!

Is there any way that a user can kill their own agent/report if they decide that the report is taking too long or is wrong?

Or are there any measures we can implement to detect that a session has been terminated and therefore to kill an agent.

Does anyone else find this is a problem?

Many thanks

Mark

This message has been edited. Last edited by: mark66,

Hi Mark

Think there is a way to give a user rights to kill their own agent in 7.1.4.

An ultimate solution which I'm trying to do is to keep the deferred reports as unlimited and throttle the resource per report for interactive stuff. Problemo is that we need to set up a new server to access a new group of agents cos MRE and dev studio share the same sets of agents currently.

Will try to keep you posted or would be interested to hear from anyone who's done this.

sorry for 'new server' read 'new node'

We too have struggled with this problem of users submitting reports that run to long and tie up browser sessions to the point where they simply close the browser window and start again. First and foremost is education. Emphasize the use of deferred reports. In fact, we encourge our users to submit almost everything deferred.

To take it to the next level you can start playing with the connection_limit and cpu_limit on the service defintions for your reporting server. Drive these down to whatever seems reasonable for your shop. But be careful here if you also use ReportCaster.

You see, ReportCaster will only use the Default service on a given reporting server. You cannot re-direct ReportCaster to a different service. Also, the default service is normally used for your adhoc queries as well. So, unless you do something special to either re-direct the ReportCaster jobs to a different reporting server, or send the adhoc queries to a different service, both of your adhoc queries and your ReportCaster jobs will be governed by the connction_limit and cpu_limit you set.

Bryan