stopping a fex

September 28, 2006, 10:11 AM

Mark1

stopping a fex

So, our programs run on a server that is located in the IT building. If I run a program that is taking forever, I have heard that we cannot stop it or cancel it ourselves. We have to call IT and get them to stop it. Does anybody know a way around this? Thanks!

September 28, 2006, 10:48 AM

Tony A

Mark,

You will need to have admin access to the reporting server console where you would access WorkSpace / Monitor / Agents. After identifying the correct agent process, left click to access a context menu and then choose Kill Agent. The agent will be closed in a "controlled" manner waiting for rollbacks etc.

If you don't have this access to the server console then it's a call to your IT group

In FOCUS since 1986	WebFOCUS Server 8.2.01M, thru 8.2.07 on Windows Svr 2008 R2
	WebFOCUS App Studio 8.2.06 standalone on Windows 10

September 28, 2006, 10:50 AM

Francis Mariani

If you have access to the WebFOCUS Server Console, and you can identify which server agent is the culprit, you can kill the agent.

The WebFOCUS server console URL is something like this: http://server-name:8121/cgiatt.exe

If the server runs in secure mode, you will require the administrator User ID and Password.

Francis

Give me code, or give me retirement. In FOCUS since 1991

Production: WF 7.7.05M, Dev Studio, BID, MRE, WebSphere, DB2 / Test: WF 8.1.05M, App Studio, BI Portal, Report Caster, jQuery, HighCharts, Apache Tomcat, MS SQL Server

September 28, 2006, 11:14 AM

TexasStingray

All, Yes you can stop a fex on the Reporting Server. However, The Request may still be running inside the Database Server. At that point you will have to have a Database Administrator or someone with that provilage to kill the request in the database.

Scott

September 28, 2006, 11:16 AM

Tony A

Hence -

quote:
The agent will be closed in a "controlled" manner waiting for rollbacks etc.

In FOCUS since 1986	WebFOCUS Server 8.2.01M, thru 8.2.07 on Windows Svr 2008 R2
	WebFOCUS App Studio 8.2.06 standalone on Windows 10

September 28, 2006, 12:28 PM

susannah

v.7 has a 'hard kill' option, as well, i've noticed; Maybe, to T's point, the death is more instantaneous and won't wait for rollbacks, etc.

In Focus since 1979///7706m/5 ;wintel 2008/64;OAM security; Oracle db, ///MRE/BID

September 29, 2006, 02:56 PM

newtofocus

We have 7.1.4 and even a hard kill is not stopping on DB2. One of the side effects of killing a query that talks to a DBMS is that it could affect the entire server if the corresponding DBMS thread is not killed.

WF7.1.4 Prod/Test, MRE, self serve, DM