PQ73525: "THE OPERATION DID NOT COMPLETE IN THE EXPECTED AMOUNT OF TIME...." ERROR, BUT THE COMMAND IS COMPLETED.

 A fix is available

5.0.2: WebSphere Application Server Version 5.0 Fix Pack 2 (Version 5.0.2)



APAR status
Closed as program error.

Error description
Through the console you can execute an operation like installing
or starting etc. and receive the following error:
"The operation did not complete in the expected amount of time.
It may have completed succesfully. Check the logs for details."
Many times the command completes but the timeout time is 10
seconds.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server 5.0 users who   *
*                 are trying to start/stop Applications        *
****************************************************************
* PROBLEM DESCRIPTION: When using deployment manager to stop   *
*                      or start an application; the following  *
*                      error message is received:              *
*                      "The operation did not complete in the  *
*                      expected amount of time.  It may have   *
*                      completed succesfully. Check the logs   *
*                      for details. "                          *
*                      One of timer value ( not configurable)  *
*                      in GUI code in application deployment,  *
*                      which is set to 10 seconds              *
*                      is timing out.                          *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The problem is that even though, there is a the SOAP connector
request timeout for mBean access is set to 600 seconds
by default, and it is configurable via the console.
The webUI timeout value in waitForResponse() method of
ApplicationDeploymentCollectionAction.java is hardcoded
to 10 seconds and is much shorter than the SOAP timeout.
The 10-second webUI timeout occurs before the 600-second
SOAP timeout.
Problem conclusion
Currently, a fix for the customer was issued with changing the
timeout value in ApplicationDeploymentCollectionAction.java,
- waitForResponse() method to 10 minutes.  The code is now
changed to 3 minutes timeout instead of 10 seconds, since 10
seconds was too small.
Temporary fix
Increased time out value to 600 seconds (from 10 seconds).
Comments
APAR information
APAR number PQ73525
Reported component name WAS BASE 5.0
Reported component ID 5630A3600
Reported release 00A
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Special Attention NoSpecatt
Submitted date 2003-04-24
Closed date 2003-06-13
Last modified date 2003-10-09

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
WEBUI          

Publications Referenced

Fix information

Applicable component levels
R003 PSY    UP
R00A PSY    UP
R00H PSY    UP
R00I PSY    UP
R00P PSY    UP
R00S PSY    UP
R00W PSY    UP


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s):
Software version: 00A
Software edition:
Reference #: PQ73525
IBM Group: Software Group
Modified date: Oct 9, 2003