PQ83194; 5.0.1: Corrupt WorkArea contest in a
loop-back Scenario
Downloadable files
Abstract
Corrupt WorkArea contest in a loop-back Scenario
Download Description
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® Application Server Enterprise Edition 5.0 and
5.0.1.
PROBLEM SUMMARY:
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 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. 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.