PQ75725: In WebSphere version 4.0.6, wscp command "ApplicationServer start" returns the prompt prior to the Application starting. | |||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||
![]() 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 PTF6 the prompt returns almost immediately. If you have a second WSCP command line open and do a quick ApplicationServer Show it will reply that the CurrentState is Initializing. PQ71967 is the APAR that introduced this new behavior while resolving a hang situation. This fix went into PTF6 which is why seeing this behavior. IBM did catch that this behavior was not correct and an internal defect was opened. This internal defect is included inLocal fix the system management cumulative fix for 4.0.2, 4.0.3, 4.0.4, and 4.0.5 versions. In addition it will be included in PTF 7. This leaves a whole for those customers who are on 4.0.6. The workaround of the -wait is not a solution for the customer base as they have many scripts and to have to manually update them all or wait until PTF 7 is not acceptable. Opening this APAR so we have an external method to provide the original internal defect for tracking purposes. LOCAL FIX: The -wait option can be added to the command and then the prompt will return only after the application server starts or until the wait time has expired if prior to the application server start.Problem summary **************************************************************** * USERS AFFECTED: Users running WSCP client, for WebSphere * * Application Server 4.0.6 or if customer * * applied May 1,2003 SM Cumulative Fix patch. * **************************************************************** * PROBLEM DESCRIPTION: WSCP commands "start" and "stop" * * returns to prompt before commands * * complete. * **************************************************************** * RECOMMENDATION: * **************************************************************** After customer applied System Management 5-1-2003 Cumulative Fix or fix pack 6, customer may notice WSCP start and stop commands returns to prompt before commands acutally complete.Problem conclusion After fix pack 6 or System Management 5-01-2003 Cumulative Fix, WSCP default timeout for start and stop commands is set to 30 seconds. This is reasonable for most customers, but for some, the timeout is too short on their environment for commands to complete. System configurations like hardware or number of applications, for example, can affect start/stop time. To resolve this issue, a new config property for WSCP is being introduced to allow customer to modify the default timeout suitable for their environment. Customer needs to modify wscp property file (e.g. .wscprc) and add the following property: com.ibm.ejs.sm.ejscp.defaultStartStopTimeout = <int value> If the property is not set, the default 30 seconds will be used. A value of 0 means the timeout is "infinite", WSCP will not timeout and return prompt until notification of completion is received from the server.Temporary fix Comments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros
SRLS
|
Document Information |
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ75725
IBM Group: Software Group
Modified date: Jul 21, 2003
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.