PQ85363: PETSTORE FAILS TO POPULATE THE CLOUDSCAPE DATABASE. 04/04/21 PTF PECHANGE

 A fix is available

Obtain the fix for this APAR



APAR status
Closed as program error.

Error description
Customer ran jobs BBODEFR and BBOINST to install the cloudscape
jdbc driver and Petstore application.  Upon executing the url
to start Petstore and enter the store.  The Petstore application
fails to populate the cloudscape database.
.
The traceback in the job output shows the following:
.
BBOO0220E PMGR0000E: Call stack:
 com.ibm.ws.ejbpersistence.utilpm.PersistenceManagerException:
PMGR6022E: Error using adapter to create or execute an
 Interaction.
com.ibm.ws.rsadapter.cci.WSInteractionImpl@538b87a1
com.ibm.ws.ejbpersistence.dataaccess.DataAccessRequestImpl.execu
teOneRowFBPK(Unknown Source)
com.ibm.ws.ejbpersistence.beanextensions.ConcreteBeanStatefulIns
tanceExtensionImpl.fetchRecordFromDataStore(Unknown
 Source)
com.ibm.ws.ejbpersistence.beanextensions.ConcreteBeanStatefulIns
tanceExtensionImpl.getRecordForLoad(Unknown Source)
com.ibm.ws.ejbpersistence.beanextensions.ConcreteBeanStatefulIns
tanceExtensionImpl.executeLoad(Unknown Source)
com.ibm.ws.ejbpersistence.beanextensions.CBReadyState.ejbLoad(Un
known Source)
com.ibm.ws.ejbpersistence.beanextensions.ConcreteBeanStatefulIns
tanceExtensionImpl.ejbLoad(Unknown Source)
com.sun.j2ee.blueprints.signon.user.ejb.ConcreteUserEJB_892a7022
.ejbLoad(Unknown Source)
com.ibm.ejs.container.ContainerManaged2_0BeanO.loadForEnlist(Con
tainerManaged2_0BeanO.java:343)
com.ibm.ejs.container.EntityBeanO.enlist(EntityBeanO.java:722)
com.ibm.ejs.container.activator.OptCEntityActivationStrategy.atA
ctivate(OptCEntityActivationStrategy.java:117)
com.ibm.ejs.container.activator.Activator.activateBean(Activator
.java:524)
com.ibm.ejs.container.EJSHome.activateBean_Common(EJSHome.java:1
257)
com.ibm.ejs.container.EJSHome.activateBean_Local(EJSHome.java:11
73)
com.sun.j2ee.blueprints.signon.user.ejb.EJSCMPUserEJBHomeBean_89
2a7022.findByPrimaryKey_Local(Unknown Source)
com.sun.j2ee.blueprints.signon.user.ejb.EJSLocalCMPUserEJBHome_8
92a7022.findByPrimaryKey(Unknown Source)
com.sun.j2ee.blueprints.petstore.tools.populate.UserPopulator.cr
eateUser(UserPopulator.java:106)
com.sun.j2ee.blueprints.petstore.tools.populate.UserPopulator.ac
cess$000(UserPopulator.java:51)
com.sun.j2ee.blueprints.petstore.tools.populate.UserPopulator$1.
create(UserPopulator.java:77)
com.sun.j2ee.blueprints.petstore.tools.populate.XMLDBHandler.end
Element(XMLDBHandler.java:145)
org.apache.xerces.parsers.AbstractSAXParser.endElement(AbstractS
AXParser.java(Compiled Code))
org.apache.xerces.impl.XMLNamespaceBinder.handleEndElement(XMLNa
mespaceBinder.java(Compiled Code))
org.apache.xerces.impl.XMLNamespaceBinder.endElement(XMLNamespac
eBinder.java(Compiled Code))
org.apache.xerces.impl.dtd.XMLDTDValidator.handleEndElement(XMLD
TDValidator.java(Compiled Code))
org.apache.xerces.impl.dtd.XMLDTDValidator.endElement(XMLDTDVali
dator.java(Compiled Code))
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.handleEndE
lement(XMLDocumentFragmentScannerIm
.
Also the nested traceback shows the following:
.
DSRA0302E:  XAException occurred.  Error code is: XAER_NOTA
BBOO0220E J2CA0027E: An exception occurred whileinvoking
rollback on an
XA Resource.
Adapter from dataSource jdbc/petstore/PetStoreDB
 within transaction ID com.ibm.ws390.tx.XidImpl|6:
db2j.bn.d.we_(Unknown Source).
db2j.bn.d.rollback(Unknown Source).
com.ibm.ws.rsadapter.spi.WSRdbXaResourceImpl.rollback(WSRdbXaRes
ourceImp
com.ibm.ejs.j2c.XATransactionWrapper.rollback(XATransactionWrapp
er.java:
com.ibm.ws390.tx.XAResourceWrapper.rollback(XAResourceWrapper.ja
va:442).
com.ibm.ws390.tx.XAResourceWrapper.rollback(XAResourceWrapper.ja
va:426).
com.ibm.ws390.tx.XAUnitOfWork.rollback(XAUnitOfWork.java:517).
com.ibm.ws390.tx.TransactionImpl.rollbackXA(TransactionImpl.java
:867).
com.ibm.ws390.tx.TransactionImpl.changeToNextState(TransactionIm
pl.java:
com.ibm.ws390.tx.TransactionImpl.rollbackRRS(TransactionImpl.jav
a:853).
com.ibm.ws390.tx.TransactionImpl.changeToNextState(TransactionIm
pl.java:
com.ibm.ws390.tx.TransactionImpl.rollback(TransactionImpl.java:1
143).
com.ibm.ws390.tx.TransactionManagerImpl.rollback(TransactionMana
gerImpl.
com.ibm.ws390.tx.TransactionManagerSet.rollback(TransactionManag
erSet.ja
com.ibm.ws390.tx.jts.CurrentImpl.rollback(CurrentImpl.java:178).
com.ibm.ejs.csi.TranStrategy.rollback(TranStrategy.java:784).
com.ibm.ejs.csi.TranStrategy.handleException(TranStrategy.java:1
93).
com.ibm.ejs.csi.TransactionControlImpl.postInvoke(TransactionCon
trolImpl
com.ibm.ejs.container.EJSContainer.postInvoke(EJSContainer.java:
3102).
com.sun.j2ee.blueprints.signon.user.ejb.EJSLocalCMPUserEJBHome_8
92a7022.
com.sun.j2ee.blueprints.petstore.tools.populate.UserPopulator.cr
eateUser
com.sun.j2ee.blueprints.petstore.tools.populate.UserPopulator.ac
cess$000
com.sun.j2ee.blueprints.petstore.tools.populate.UserPopulator$1.
create(U
com.sun.j2ee.blueprints.petstore.tools.populate.XMLDBHandler.end
Element(
Local fix
Change the Cloudscape Statement Cache Size from 10 to 0
JDBC Providers > Samples Cloudscape 5.0 XA Provider > Data
Sources > PetstoreDB > Statement Cache Size
.
JDBC Providers > Samples Cloudscape 5.0 XA Provider > Data
Sources > CatalogDB > Statement Cache Size
.
Be sure to set your scope to "Server" and click apply,
otherwise you will not see the Datasource
Samples Cloudscape 5.0 XA Provider
.
Also after making the above changes, it is necessary to
recycle the application server in order for the change to
take affect.
Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 V5.0 for z/OS                                *
****************************************************************
* PROBLEM DESCRIPTION: A PersistenceManagerException with      *
*                      error message PMGR6022E occurs when     *
*                      Petstore sample uses Cloudscape with a  *
*                      5.0 Cloudscape JDBC datasource after    *
*                      the initial install of the samples.     *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
After installing the samples at the W502002 Service Level of
WebSphere Application Server for z/OS, when the petstore sample
or one of the other samples is used with the 5.0 Cloudscape
datasources that are created by the install jacl, a
PersistenceManagerException with error message PMGR6022E occurs.
The problem is manifested by the fact that the statement cache
size associated with the created 5.0 cloudscape JDBC datasources
is incorrectly set to 10 instead of 0. The incorrect setting of
the statement cache size occurs when the datasources are created
because the datasource properties retrieved from the
jdbc-resource-provider-templates.xml are for the 5.1 cloudscape
provider instead of the 5.0 cloudscape provider. The incorrect
selection of the datasource properties is a result of the 5.0
and 5.1 providers having datasource xmids that start with the
same text (e.g., DataSource_4.... or DataSource_3....). Since
the jacl searches the jdbc templates for a datasource that
starts with DataSource_3 or DataSource_4 (in the case of XA),
it finds the first match which happens to be the datasource
information for the 5.1 cloudscape provider. When this happens,
all the datasource properites selected are the same as what
would have been selected for the 5.0 provider except for the
statementCacheSize value which is 10 instead of 0. This thus
leads to the failure that ultimately occurred. .
Problem conclusion
To correct the problem, the datasource xmids associated with
the 5.0 cloudscape non-XA and XA JDBC providers will be set
back to what they were prior to W502002 (i.e., DataSource_3
and DataSource_4, respectively). The datasource xmids
associated with the 5.1 cloudscape non-XA and XA JDBC
providers will be changed to DataSource_51_3_2 and
DataSource_51_4_2 respectively.

APAR PQ85363 is associated with SERVICE LEVEL W502006 of
WebSphere Application Server V5.0 for z/OS.
Temporary fix Comments
APAR information
APAR number PQ85363
Reported component name WEBSPHERE FOR Z
Reported component ID 5655I3500
Reported release 500
Status CLOSED PER
PE YesPE
HIPER NoHIPER
Special Attention NoSpecatt
Submitted date 2004-03-01
Closed date 2004-04-08
Last modified date 2004-05-05

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
BBOUBINF          

Publications Referenced

Fix information
Fixed component name WEBSPHERE FOR Z
Fixed component ID 5655I3500

Applicable component levels
R500 PSY UQ87201    UP04/04/19 P F404 

  Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.


Document Information


Current web document: swg1PQ85363.html
Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server for z/OS
Operating system(s):
Software version: 500
Software edition:
Reference #: PQ85363
IBM Group: Software Group
Modified date: May 5, 2004