PQ70448: USING MULTIPLE J2C CONNNECTORS WITHIN AN APPLICATION SERVER, THEY ALL CONNECT THROUGH ONE CONNECTOR | |||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||
APAR status Closed as documentation error. Error description Customer has defined 5 j2c adapters to connection to 5 different CICS connections. If he accesses the connnectors through different application servers, they all will connnect to the appropriate system. However if they are all accessed within the same application server, all requests flow to the first j2c adapter used. This is caused by the all objects end up being bound to the same object in the naming layer. The documentation for websphere needs to document how to use multiple j2c connnectors within an application server.Local fix Use separate application server for each j2c adapterProblem summary **************************************************************** * USERS AFFECTED: WebSphere Application Server users who have * * several EJB modules, each of which uses the * * same package name for their home stub. * **************************************************************** * PROBLEM DESCRIPTION: When a user has several EJBs using * * local jndi lookups for J2C Connection * * Factories and each EJB is * * configured to go to a different * * Connection Factory, however, they are * * all going to the same one. * **************************************************************** * RECOMMENDATION: * **************************************************************** User has 5 EJBs, each of which referenced the same home, and 5 J2C connection factories. The Connection Factories were configured to go to different CICS regions, and each EJB module had resource reference that "pointed" to their respective region. The intent was to provide tracking for each region. Solutions for problem: It's possible that the res-ref bindings are not set properly. Check ibm-application-bnd.xmi in %WAS_HOME%\installedApps\[ApplicationName]\META-INF\. Another possibility is that the EJB references are bound to the same instance of their home class. This can happen when the EJBs have the same package and class name. The result is that only one instance of the home will be created on the server, and only one res-ref mapping will take effect. This can be checked through the dumpnamespace tool, here's an example : 2 (top)/CICSAdapterLog com.cna.im.CICS.Adapters._CICSAdapterLogHome_Stub 5 (top)/CICSTapAdapter com.cna.im.CICS.Adapters._CICSTapAdapterHome_Stub 113 (top)/CH3.CICSAdapterLog com.cna.im.CICS.Adapters._CICSAdapterLogHome_Stub All three bean references are bound to com.cna.im.CICS.Adapters._CICSAdapterLogHome_Stub.Problem conclusion Close this APAR as a documentation change. The updated information will be available to the customers after 05/23/2003.Temporary fix Comments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros
|
Document Information |
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ70448
IBM Group: Software Group
Modified date: Apr 4, 2003
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.