You are accessing the
Dynamic Workload Console with
Internet Explorer 6.0, service pack 2, on a slow workstation (for
example: Pentium 4, CPU 1.8
GHz) and are performing one of the following actions, which does not
complete:
- You are querying objects in the plan, but on navigating through
the result pages the browser hangs while drawing a result page, leaving
the page with just the table header and footer shown and none of the
result rows displayed. The hang of the browser can be resolved by
clicking a button or link, but the missing data is not displayed.
- You are performing either a Save, Edit,
or Search operation in the Workload Designer,
which hangs for about 60 seconds and then displays one of these two
error messages:
AWSUI6171E The operation could not be
completed because the Tivoli Dynamic Workload Console server is unreachable.
Possible causes are that the Tivoli Dynamic Workload Console server
has been stopped or that your login authentication has expired or
has become invalid.
AWSUI6182E The operation
could not be completed because an internal error occurred. The internal
error is: the service name has not been provided.
Cause and solution:
What exactly causes the problem has not been ascertained (it might
be a bug in Internet Explorer), but it can be resolved by increasing
the value of one of the configurable timeouts in the application server.
Do the following:
- Identify the instance of WebSphere® Application Server running
the Dynamic Workload Console where
this workstation normally connects to (if it connects to more than
one, perform the procedure for all of them)
- On that instance, edit the WebSphere Application Server configuration
file "server.xml". The default location is
<TWA_home>/eWAS/profiles/TIPProfile/config/cells/DefaultNode/
nodes/DefaultNode/servers/twaserver
- Increase the value of the persistentTimeout of
the HTTPInboundChannel related to the WCInboundAdminSecure chain
section of the file. The default value is 30, but for the given
example (Pentium IV, CPU
1.8 GHz) a suggested value to set is 120. An example using
the relevant parts of a modified server.xml is as
follows:
- Identify the WCInboundAdminSecure chain by looking
in the chains section:
<chains
xmi:id="Chain_1226491023533"
name="WCInboundAdminSecure"
enable="true"
transportChannels="TCPInboundChannel_1226491023530
SSLInboundChannel_1226491023530
HTTPInboundChannel_1226491023531
WebContainerInboundChannel_1226491023531"/>
Note
the value of the HTTPInboundChannel.
- Use the value of the HTTPInboundChannel to locate
its entry:
:<transportChannels
xmi:type="channelservice.channels:HTTPInboundChannel"
xmi:id="HTTPInboundChannel_1226491023531"
name="HTTP_3"
discriminationWeight="10"
maximumPersistentRequests="100"
keepAlive="true"
readTimeout="60"
writeTimeout="60"
persistentTimeout="120"
enableLogging="false"/>
Modify persistentTimeout as
has already been done here.
- Stop the instance of WebSphere Application Server using
the stopWas command.
- If a Tivoli Workload Scheduler component
is also running under the same instance of the WebSphere Application Server, you
need take no further action, as appservman will automatically restart
the application server. Otherwise, use the startWas command.
- Test the modified value to see if it has resolved the problem.
If not, repeat the operation with a larger value, until the problem
is resolved.