|
Problem(Abstract) |
After upgrading to WebSphere® Application Server V5.0.2.7,
5.1.0.4, 5.1.0.5, or 5.1.1, an EJB fails with the PMGR1012E and PMGR0000E
messages in the SystemOut.log file. |
|
|
|
Cause |
The SystemOut.log file contains the following
errors:
[9/21/04 12:01:21:602 EDT] 45728fc5
ConcreteBeanC E PMGR1012E: The current backend id DB2UDBNT_V72_1, does not
match the datasource connected to.
[9/21/04 12:01:21:611 EDT] 45728fc5 ConcreteBeanC E PMGR0000E: Call
stack:
com.ibm.ws.ejbpersistence.utilpm.PersistenceManagerException:
PMGR1012E: The current backend id DB2UDBNT_V72_1, does not match the
datasource connected to.
at
com.ibm.ws.ejbpersistence.beanextensions.ConcreteBeanClassExtensionImpl.createPMException(Unknown
Source)
at
com.ibm.ws.ejbpersistence.beanextensions.ConcreteBeanClassExtensionImpl.bind(Unknown
Source)
at
com.ibm.ws.ejbpersistence.beanextensions.ConcreteBeanClassExtensionImpl.checkBinding(Unknown
Source)
at
com.ibm.ws.ejbpersistence.beanextensions.ConcreteBeanStatefulInstanceExtensionImpl.setPMHomeInfo(Unknown
Source)
at
com.ibm.ejs.container.ContainerManaged2_0BeanO.<init>(ContainerManaged2_0BeanO.java:114) |
The cause of this problem is that the currentBackendId in the EJB does
not match one that is defined for WebSphere Application Server. Some
earlier versions of WebSphere Studio Application Developer or the
WebSphere Application Server Application Assembly Tool (AAT) allowed
values for the CurrentBackendId that are not recognized by the Application
Server. The more recent versions of WebSphere Application Server are now
enforcing checks to make sure that these values do match.
The currentBackendId is one of the fields in the ejbbnd of the
ibm-ejb-jar-bnd.xmi file.
<ejbbnd:EJBJarBinding
xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI"
xmlns:ejbbnd="ejbbnd.xmi" xmlns:ejb="ejb.xmi" xmlns:common="common.xmi"
xmi:id="EJBJarBinding_1067203829274"
currentBackendId="DB2UDBNT_V72_1"> |
|
|
|
Resolving the
problem |
The recommended way to correct this problem is to use
WebSphere Studio Application Developer or WebSphere Application Server AAT
to set the backend ID to the correct value. This is done by fixing the
deployment data for the EJB.
Using AAT,
- Open the EAR that contains the EJB.
- Click on the EJB.
- Click File.
- Click Generate Deployment Code.
- On the screen that is presented, select the correct Database type;
click Generate Now.
- Then re-install the EAR.
 |
|
|
|
|
Cross Reference information |
Segment |
Product |
Component |
Platform |
Version |
Edition |
Application Servers |
Runtimes for Java Technology |
Java SDK |
|
|
|
|
|
|