PQ77871: In WebSphere version 4.0.5 with with PQ71967 the wscp prompt returns prior to the command/request finishing.

 A fix is available

PQ77871: The default timeout of wscp is changed



APAR status
Closed as program error.

Error description
In WebSphere version 4.0.5 and prior when you issued the WSCP
command to start an application server the prompt would only
return once it was started. After applying PQ71967 the prompt
returns almost immediately. If you have a second WSCP command
line open and do a quick ApplicationServer Show for example it
will reply that the CurrentState is Initializing.

PQ71967 is the APAR that introduced this new behavior while
resolving a hang situation. 
PQ75725 has been created for PTF 6
as PQ71967 was included in PTF 6.

Please include to this fix the new property parameter that
was introduced with 
PQ75725:

com.ibm.ejs.sm.ejscp.defaultStartStopTimeout = <int value>

NOTE: PQ71967 is included in WAS_SysMgmt_05-01-2003_4.0.5-4.0.4-
4.0.3-4.0.2_AE_*PLATFORM*_cumulative_Fix so this fix is not
required for customers who have applied this fix to 4.0.5 or
those on 4.0.6 or greater.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: Websphere Application Server users of the    *
*                 wscp admin client.                           *
****************************************************************
* PROBLEM DESCRIPTION: WSCP default timeout of 30 seconds      *
*                      results in many requests being unable   *
*                      to return their completion status.      *
****************************************************************
* RECOMMENDATION: Changed default to 10 minutes.  If shorter   *
*                 or longer waits are desired then the wscp    *
*                 property com.ibm.ejs.sm.ejscp.               *
*                 defaultStartStopTimeout may be used to       *
*                 specify those values.                        *
****************************************************************
The default wscp timeout was set to 30 seconds from its
previous value of no timeouts.  Perviously customers
had scripts which used to return with a success or
failure message.  Now with 30 seconds they are unable
to determine the status for application start/stop,
which take longer than 30 seconds.   The basic idea
of the timeout is good but the default was too low.
Now we have changed it to 10 minutes to let most prior
scripts get through.  For the rest the wscp property
would be useful.
Problem conclusion
I changed the default timeout from 30 seconds to
10 minutes.  The module is DefaultScriptCmdHandler and
the field is DEFAULTWAITTIME.
Temporary fix
Fix has been uploaded to 
pq99999 on Sep 24. Customer
downloaded.  Asked for feedback.
Comments
Customer supplied with test fix on September 24, 2003.
Feedback expected anytime.
APAR information
APAR number PQ77871
Reported component name WEBSPHERE AE AI
Reported component ID 5630A2200
Reported release 400
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Submitted date 2003-08-27
Closed date 2003-10-13
Last modified date 2003-10-13

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
DefaultS Handler criptCmd      

SRLS

Fix information

Applicable component levels
R400 PSY    UP


Document Information


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