PQ60610: THE WAS REPOSITORY IS NOT REMOVING THE JNDI REFERENCE FROM THE BINDINGBEANTBL AFTER STOP OR EJB REMOVAL.

A fix is available
WebSphere Application Server Version 3.5 Fix Pack 7 (3.5.7)

APAR

APAR status
Closed as program error.

Error description
When you stop a Model and subsequent clones the BINDINGBEANTBL
in the WAS repository should no longer show the EJB's that
are associated to the Model. NOTE: If the EJBs are deployed
in more than one Model or another indepenant Appliation
Server the reference should still show in the table, unless
all instances are stopped. Upon deletion of all instances of an
EJB the BINDINGBEANTBL should also be updated. This is not
working properly as deleted EJBs are still showing as well as
when all instances of an EJB are stopped. This occurs in single
and multi-node environments on WAS 3.5.4.
.
This can be determined with the use of the dbcheck tool or a
query of the database for the BINDINGBEANTBL.
.
Errors are thrown when you attempt to redeploy a previously
deleted EJB due to the repository not being cleaned up. The
following error will be in the tracefile:
.
ClientAccessB < getRepositoryObjectInfo
javax.transaction.TransactionRolledbackException: CORBA
TRANSACTION_ROLLEDBACK 0 No; nested exception is:following error will be in the tracefile:., ClientAccessB<, getRepositoryObjectInfojavax.transaction.TransactionRolledbackException: CORBA
org.omg.CORBA.TRANSACTION_ROLLEDBACK:TRANSACTION_ROLLEDBACK 0 No; nested exception is:
com.ibm.websphere.csi.CSITransactionRolledbackException at java.io.IOException.<init>(IOException.java:37) at java.rmi.RemoteException.<init>(RemoteException.java:48) at com.ibm.websphere.csi.CSIException.<init>(CSIException.java:18) at com.ibm.websphere.csi.CSITransactionRolledbackException.<init>(C SITransactionRolledbackException.java:19) at com.ibm.ejs.csi.TranStrategy.handleException(TranStrategy.java:1 13) at com.ibm.ejs.csi.TransactionControlImpl.postInvoke(TransactionCon trolImpl .java(Compiled Code)) at com.ibm.ejs.container.EJSContainer.postInvoke(EJSContainer.java( Compiled Code)) at com.ibm.ejs.sm.beans.EJSRemoteVirtualHost.getNumContainedObjects (EJSRemoteVirtualHost.java:180) at com.ibm.ejs.sm.beans._RepositoryObject_Stub.getNumContainedObjec ts(_RepositoryObject_Stub.java:737) at com.ibm.ejs.sm.beans.ClientAccessBean.getRepositoryObjectInfo(Cl ientAccessBean.java(Compiled Code)) at com.ibm.ejs.sm.beans.ClientAccessBean.listContainedObjects(Clien tAccessBean.java(Compiled Code)) at com.ibm.ejs.sm.beans.EJSRemoteClientAccess.listContainedObjects( EJSRemoteClientAccess.java:119) at com.ibm.ejs.sm.beans._EJSRemoteClientAccess_Tie._invoke(_EJSRemo teClientAccess_Tie.java:206) at com.ibm.CORBA.iiop.ExtendedServerDelegate.dispatch(ExtendedServe rDelegate.java:506) at com.ibm.CORBA.iiop.ORB.process(ORB.java:2282) at com.ibm.CORBA.iiop.WorkerThread.run(WorkerThread.java:195) at com.ibm.ejs.oa.pool.ThreadPool$PooledThread.run(ThreadPool.java:org.omg.CORBA.TRANSACTION_ROLLEDBACK:com.ibm.websphere.csi.CSITransactionRolledbackExceptionat java.io.IOException.(IOException.java:37)at java.rmi.RemoteException.(RemoteException.java:48)atcom.ibm.websphere.csi.CSIException.(CSIException.java:18)atcom.ibm.websphere.csi.CSITransactionRolledbackException.(CSITransactionRolledbackException.java:19)atcom.ibm.ejs.csi.TranStrategy.handleException(TranStrategy.java:113)atcom.ibm.ejs.csi.TransactionControlImpl.postInvoke(TransactionControlImpl .java(Compiled Code))atcom.ibm.ejs.container.EJSContainer.postInvoke(EJSContainer.java(CompiledCode))atcom.ibm.ejs.sm.beans.EJSRemoteVirtualHost.getNumContainedObjects(EJSRemoteVirtualHost.java:180)atcom.ibm.ejs.sm.beans._RepositoryObject_Stub.getNumContainedObjects(_RepositoryObject_Stub.java:737)atcom.ibm.ejs.sm.beans.ClientAccessBean.getRepositoryObjectInfo(ClientAccessBean.java(Compiled Code))atcom.ibm.ejs.sm.beans.ClientAccessBean.listContainedObjects(ClientAccessBean.java(Compiled Code))atcom.ibm.ejs.sm.beans.EJSRemoteClientAccess.listContainedObjects(EJSRemoteClientAccess.java:119)atcom.ibm.ejs.sm.beans._EJSRemoteClientAccess_Tie._invoke(_EJSRemoteClientAccess_Tie.java:206)atcom.ibm.CORBA.iiop.ExtendedServerDelegate.dispatch(ExtendedServerDelegate.java:506)at com.ibm.CORBA.iiop.ORB.process(ORB.java:2282)at com.ibm.CORBA.iiop.WorkerThread.run(WorkerThread.java:195)at
535) minor code: 0 completed: No org.omg.CORBA.TRANSACTION_ROLLEDBACK:com.ibm.ejs.oa.pool.ThreadPool$PooledThread.run(ThreadPool.java:535)minor code: 0 completed: No
com.ibm.websphere.csi.CSITransactionRolledbackException
org.omg.CORBA.TRANSACTION_ROLLEDBACK:com.ibm.websphere.csi.CSITransactionRolledbackException
Local fix
Workaround: None as we do not suggest manual edit of the WAS
repository.
Problem summary
****************************************************************
* USERS AFFECTED: All WebSphere Application Server 3.5 users   *
*                 that create clones of app servers.           *
****************************************************************
* PROBLEM DESCRIPTION: After removing an EJB from the system,  *
*                      it still appears in the JNDI namespace. *
*                      In some scenarios, if the EJB name is   **                      reused, various error messages may      *
*                      be reported - these contain the string, *
*                      "duplicate".                            *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Problem has to do with logic used to remove EJBs from
the table, BINDINGBEANTBL, in the WAS repository when cloned
application servers are in use.
Problem conclusion
Added logic so that if bean is removed and there are no
references to it, then the code will remove it from the table.
Temporary fix
The testfix has posted on the wasdoc0\apars and wait for the fee
dback.
Comments
APAR information
APAR numberPQ60610
Reported component nameWAS ADVANCED AI
Reported component ID5648C8400
Reported release350
StatusCLOSED PER
PENoPE
HIPERNoHIPER
Submitted date2002-04-29
Closed date2002-06-25
Last modified date2002-06-25

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
ADMINSVR
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 #: PQ60610
IBM Group: Software Group
Modified date: 2002-06-25