PQ83194: Corrupt WorkArea contest in a loop-back Scenario

 A fix is available

PQ83194; 5.0.1: Corrupt WorkArea contest in a loop-back Scenario



APAR status
Closed as program error.

Error description
An issue has been found where WorkArea context is incorrect in
an application that consists of a loop-back scenario.  A
loop-back consists of one application in a server (server1)
calling another application in a second server (server2).  The
second application then calls back to the first.  This throws a
null pointer exception indicting there is no WorkArea context.
This occurs in WebSphere PME 5.0 and 5.0.1.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: Users of the WebSphere Application Server    *
*                 PME 5.0 and 5.0.1 which have multiple        *
*                 applications using the WorkArea service,     *
*                 where application 1 calls a second           *
*                 application which calls back to the first.   *
****************************************************************
* PROBLEM DESCRIPTION: A NullPointerException is encountered   *
*                      in a loopback scenario whereby an       *
*                      application (using WorkArea) makes a    *
*                      remote call to another application      *
*                      and in turn that application calls      *
*                      back to the originating (first)         *
*                      application.                            *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
A NullPointerException is encounteredin a loopback scenario
whereby an application (using WorkArea) makes a remote call to
another application and in turn that application calls back to
the originating (first) application.  Invalid WorkArea context
in a loopback scenaro.
WorkArea context will remain after completiong of
the loopback scenario. When the remote call
finished and control returns to the
first application, the WorkArea
context owned by that app is lost.
This results in a
NullPointerException when the user
tries to access the context in the
WorkArea.  The reason for the NPE is
that since the context got lost after
the loopback scenario, the WorkArea
points to a null object.
Problem conclusion
There is no work around.  Applying this fix will ensure that
loopback scenario described above will work correctly.
Temporary fix Comments
APAR information
APAR number PQ83194
Reported component name WAS ENTERPRISE
Reported component ID 5630A3700
Reported release 00W
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Special Attention NoSpecatt
Submitted date 2004-01-13
Closed date 2004-01-27
Last modified date 2004-01-27

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 #: PQ83194
IBM Group: Software Group
Modified date: Jan 27, 2004