PQ62748: APPLICATION MUST PASS STATIC ORB TO CREATESESSION() METHOD WHEN USING LOTUS API TO COMMUNICATE WITH DOMINO BACKEND

Fixes are available
WebSphere Application Server Version 3.5 Fix Pack 7 (3.5.7)
WebSphere Application Server Version 4.0 Fix Pack 5 (Version 4.0.5)

APAR

APAR status
Closed as program error.

Error description
Applications are required to pass a static Orb to the Notes crea
teSession() call when using Notes api to communicate from WebSph
ere application to Lotus Domino Server.  We don't not support us
ing the createSession() to create a new instance of an Orb that
requires a subsequent call to the Orb's shutdown method
Local fix
Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server Users of        *
*                 servlet/jsp along with Domino client which   *
*                 is ncsow.jar                                 *
****************************************************************
* PROBLEM DESCRIPTION: When a user does not use single static  *
*                      ORB programming practice in servlet     *
*                      and JSP, minor memory leaks will be     *
*                      experienced in ORB's component and      *
*                      its related IIOP sockets                *
***************************************************************** RECOMMENDATION:                                              *
****************************************************************
When using remote access by NCSOW.jar between WebSphere
Servlet/JSP and Domino Server, WebSphere's JavaIDL listener
threads are not cleaned up after each completion of the
servlet and causes a memory leak in the WebSphere
Application Server. The root cause is the listener threads
have not released its resources back to the current ORB object
while the ORB object is waiting and depending on these
listeners before making a completed stop and cleaning of
itself.  When a user re-invokes a servlet by refreshing the
browser, a new ORB and JavaIDL listeners are being created;
and at the same moment, the current ORB and JavaIDL listeners
are still sitting there expecting a client's incoming call.
As a result, the old ORB and JavaIDL listener threads were
not being removed and new ORB and JavaIDL listener threads are
being created.  These old and new ORB and JavaIDL listeners
will eventually use up all of the available memory and the JVM
will throw an out of memory exception when it is full.
This is an additional efix for PQ53456.  This Efix, PQ62748,
corrects the behavior of IIOP sockets which are being not
closed after each Domino session. To further correct the minor
memory leaking issue, this efix requires base ORB team to
provide additional SOV efix. Each efix contains ORB components
from both the WebSphere ORB team and base ORB team.
Problem conclusion
WebSphere ORB component cleans up the remaining open sockets
after each Domino session and the base ORB team disables the
IOR caching logic to prevent memory leaking.
Temporary fix
Comments
APAR information
APAR numberPQ62748
Reported component nameWAS ADVANCED AI
Reported component ID5648C8400
Reported release350
StatusCLOSED PER
PENoPE
HIPERNoHIPER
Submitted date2002-06-28
Closed date2002-09-03
Last modified date2002-09-03

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:APAR is sysrouted FROM one or more of the following:


Modules/Macros
ORB
APAR is sysrouted TO one or more of the following:Modules/Macros

Fix information
Fixed component nameWAS ADVANCED AI
Fixed component ID5648C8400

Applicable component levels
R350 PSYUP











Document Information

Product categories: Software, Application Servers, Distributed Application & Web Servers, WebSphere Application Server, General
Software version: 350
Reference #: PQ62748
IBM Group: Software Group
Modified date: 2002-09-03