29.01.2013 Views

WebSphere Application Server V7.0: Concepts ... - IBM Redbooks

WebSphere Application Server V7.0: Concepts ... - IBM Redbooks

WebSphere Application Server V7.0: Concepts ... - IBM Redbooks

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

14.6.4 Resource Access Control Facility (RACF) integration<br />

FRCA services can be restricted. If access is restricted (the SERVAUTH class<br />

and the FRCA resource are defined) in your environment, then <strong>WebSphere</strong><br />

<strong>Application</strong> <strong>Server</strong> must be granted access.<br />

If the access is restricted, the message seen in Example 14-2 will be issued.<br />

Example 14-2 FRCA access denied message<br />

BBOOnnnnE FRCA INITIALIZATION FAILED. SERVER NOT AUTHORIZED TO USE FRCA<br />

SERVICES. IOCTL RV=%d, RC=%d, RSN=%08X<br />

The RACF command in Example 14-3 enables access to the FRCA services.<br />

Example 14-3 RACF command to enable FRCA service<br />

PERMIT EZB.FRCAACCESS.your_system_name.your_TCPIP_procname CLASS<br />

(SERVAUTH) ID (your_control_reggion_userid) ACCESS (READ)<br />

SETROPTS RACLIST (SERVAUTH) REFRESH<br />

14.7 Thread Hang Recovery<br />

14.7.1 Overview<br />

This section describes the new Thread Hang Recovery option available on z/OS.<br />

<strong>WebSphere</strong> <strong>Application</strong> <strong>Server</strong> for z/OS <strong>V7.0</strong> contains a new technique called<br />

Thread Hang Recovery. A hung thread will end up with one of the following<br />

situations:<br />

► It simply hangs around, only blocking threads and application environment<br />

resources, such as connections, tables, and so forth.<br />

► It ends in a loop state, not only blocking other resources but in addition<br />

consuming CP or zAAP resources. What kind of processor is being used<br />

depends on whether a zAAP is available at all and in what step of the<br />

application the error occurs.<br />

Thread Hang Recovery directly addresses both of these issues. It allows you to<br />

define actions that should be started if a timeout occurs.<br />

It allows you to specify thresholds for processor usage and actions that should be<br />

performed if a single request exceeds this value. This is of real value if your<br />

452 <strong>WebSphere</strong> <strong>Application</strong> <strong>Server</strong> <strong>V7.0</strong>: <strong>Concepts</strong>, Planning, and Design

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!