PQ52184: EJB INITIALCONTEXT CONNECTION IS NEVER CLOSED | |||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description After a servlet has used an InitialContext to access a WebSphere Application Server for z/OS and OS/390 V4.0 EJB, the TCP connection to InitialContext is never closed. Servlet code looks like: service(..,...) try response.setContentType("text/html"); PrintWriter out = response.getWriter(); try javax.naming.InitialContext initialContext = new javax.naming.InitialContext(getInitialProperties()); out.println("<HTML><HEAD><TITLE>Hello World</TITLE></HEAD><BODY>"); System.out.println("Getting HelloWorldSession home"); Object HelloHomeLooked=initialContext.lookup("Hello"); HelloHome HelloH=(HelloHome) . javax.rmi.PortableRemoteObject.narrow(HelloHomeLooked . ,HelloHome.class); System.out.println("Got HelloWorldSession home"); System.out.println("Create New HelloWorldSession "); Hello HelloWorld = HelloH.create(); out.println("<BIG>"+HelloWorld.sayHello("Salut le gars")+"</BIG>... HelloWorld.remove(); // initialContext.close(); catch .... ..." As a result, each new call to the servlet adds a connection to the V4.0 LDAP server for the Application Server. After some time LDAP is overloaded by TCP connections.Local fix Do caching of InitialContext object.Problem summary **************************************************************** * USERS AFFECTED: All Users of the WebSphere Application * * Server Version 4.0 for z/OS and OS/390. * **************************************************************** * PROBLEM DESCRIPTION: After a servlet has used an * * InitialContext to access an Enterprise * * Java Bean (EJB), the TCP connection to * * InitialContext between the WebSphere * * Application Server for z/OS and OS/390 * * and the Lightweight Directory Access * * Protocol (LDAP) server is never closed. * **************************************************************** * RECOMMENDATION: * **************************************************************** After a servlet has used an InitialContext to access an Enterprise Java Bean (EJB), the TCP connection to InitialContext between the WebSphere Application Server for z/OS and OS/390 and the Lightweight Directory Access Protocol (LDAP) server is never closed. Consequently, each new call adds a new connection between the WebSphere Application server for z/OS and OS/390 and the Lightweight Directory Access Protocol (LDAP) server. Eventually the LDAP server has too many TCP connections and hangs.Problem conclusion The WebSphere Application server has been modified to close the TCP connection to InitialContext. COMPID 5655A9800 R400 is affected by this APAR. The code changes are stored in CMVC under defect PQ52184. 400Y EJSJWBJR * Cross Reference between External and Internal NamesTemporary fix Comments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: UQ60995 Modules/Macros
|
Document Information |
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server for z/OS
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ52184
IBM Group: Software Group
Modified date: Jan 3, 2002
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.