PQ58248: DEPLOY A NEW EAR FILE USING XMLCONFIG WITH NO DOWN TIME

 A fix is available

System Management Component Cumulative Fix for 4.0.2/4.0.3/4.0.4 /4.0.5



APAR status
Closed as program error.

Error description
eBay does their own software updates is that they have a
policy that there are NO outages or reductions in quality of
service when the software is rolled out.  The term they've
been using here is "Incremental rollout".  This basically means
that they do a rolling release of new software across all of
their servers, with no more than a single server being off-line
at any time.
.
The problem comes in with those changes that cannot
go in as hot deployment -- like adding a new EJB, and
dealing with all of the changes to the servlet code that
have to deal with the new EJB.  Here, we basically need
to deploy a new EAR file.    That's the issue.  We need to
deploy a new EAR across all servers, but we can't bring
down all of the clones of that server -- we have to keep
them running (bringing down only one at a time) while we
start up the new servers.  So, anyway, we've worked out
a procedure for this.  However, the procedure relies on
what is probably a bug in XMLConfig.
Local fix
There is no process in place currently that will allow
deployment of an EJB using XMLConfig with no down time.
Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server clients who     *
*                 define multiple virtual hosts.               *
****************************************************************
* PROBLEM DESCRIPTION: WebSphere needs to create multi virtual *
*                      hosts with different names but          *
*                      duplicate the alias list in the Admin   *
*                      Console and to deploy multiple web      *
*                      applications with the same virtual host *
*                      without seeing an error message.        *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
To keep all clients consistent (XMLConfig, AdminConsole and
WSCP), the admin console will also allow the users to
create virtual hosts with different names but duplicate alias
without throwing the error message.  The Admin console and WSCP
also allow the user to install applications with the same
context root and same virtual hosts without throwing
"duplicate context root" error.
Problem conclusion
Changes were made in AdminGUI and WSCP codes.
Temporary fix Comments
APAR information
APAR number PQ58248
Reported component name WEBSPHERE AE NT
Reported component ID 5630A2201
Reported release 400
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Submitted date 2002-02-21
Closed date 2002-03-06
Last modified date 2002-03-06

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros

SRLS

Fix information
Fixed component name WEBSPHERE AE NT
Fixed component ID 5630A2201

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 #: PQ58248
IBM Group: Software Group
Modified date: Mar 6, 2002