PQ76733: After installing EE 5.0.2, the BPEClient webmodule can not start

 A fix is available

PQ76733; 5.0.2: After installing EE 5.0.2, the BPEClient webmodule can not start



APAR status
Closed as program error.

Error description
After installing EE 5.0.2, the BPEClient webmodule can not start
because the '/bpe' context root is already in use by old
bpe-container's webclient module.
After installing the 5.0.2 fix pack, attemped to start server1.
It started but new BPEWebClient application failed to start.
In looking at the logs, it failed because context root '/bpe' is
already used by BP Container application's webclient module.
So there are 2 web modules with same '/bpe' context root.
To workaround this, the context root in BP Container app
was modified and it worked fine.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: Customers using the Process Choreographer    *
*                 feature of the WebSphere App Server          *
*                 Enterprise Edition ver. 5.0.2 who match one  *
*                 or more of the following cases:              *
*                 1. Users of a Webclient created pre 5.0.2.   *
*                 2. Those using compensation and an oracle    *
*                 DB if the bpe container was configured with  *
*                 pre 5.0.2.                                   *
*                 3. Those upgrading a Process Choreographer   *
*                 configuration from 5.0 GA level.             *
****************************************************************
* PROBLEM DESCRIPTION: 1. After applying PTF2, a previously    *
*                      configured Webclient has JNDI lookup    *
*                      failures.                               *
*                      2. Compensation no longer works.        *
*                      (compensation table changes not taken   *
*                      into account).                          *
*                      3. the upgrade of a WAS-E 5.0 GA        *
*                      sample Process Choreographer            *
*                      configuration aborts due to EJB name    *
*                      changes                                 *
****************************************************************
* RECOMMENDATION: use the new bpeupgrade.jacl provided with    *
*                 this fix                                     *
****************************************************************
1. After applying PTF2, a previously configured Webclient has
JNDI lookup failures because the Webclient's EJB reference
gets set to the default.
2. Compensation no longer works with oracle since the
'currentBackendId' gets reset to the default.
3. the upgrade of a WAS-E 5.0 GA Process Choreographer
configuration aborts due to EJB name changes. Therefore,
compensation tables do not get updated correctly.
Problem conclusion
To avoid these problems a new bpeupdate.jacl is provided
Temporary fix Comments
APAR information
APAR number PQ76733
Reported component name WAS ENTERPRISE
Reported component ID 5630A3700
Reported release 00W
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Special Attention NoSpecatt
Submitted date 2003-07-24
Closed date 2003-08-11
Last modified date 2003-08-11

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros

Publications Referenced

Fix information

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


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > Enterprise Edition (EE)
Operating system(s):
Software version: 00W
Software edition:
Reference #: PQ76733
IBM Group: Software Group
Modified date: Aug 11, 2003