APAR status
Closed as program error.
Error description
In some situation while storing objects, TADDM marks objects as deleted and later such object cannot be accessed causing exception like this: 2012-11-27 13:15:17,794 TopologyManager [RMI TCP Connection(508)-10.147.199.131] ERROR jdo.BaseJdo - Cannot make object transient: javax.jdo.JDOUserException: Cannot make object transient since object is new, deleted and not yet committed FailedObject:826ABE6011023BA2A718C3A3F5E5E090-0 at org.datanucleus.jdo.NucleusJDOHelper.getJDOExceptionForNu cleusException(NucleusJDOHelper.java:367) at org.datanucleus.jdo.JDOPersistenceManager.jdoMakeTransien t(JDOPersistenceManager.java:801) at org.datanucleus.jdo.JDOPersistenceManager.makeTransient(J DOPersistenceManager.java:820) at org.datanucleus.jdo.JDOPersistenceManager.makeTransient(J DOPersistenceManager.java:830) at com.ibm.cdb.topomgr.jdo.BaseJdo.makeTransient(BaseJdo.jav a:3032) at com.collation.topomgr.jdo.topology.net.IpInterfaceJdo.gui d_(IpInterfaceJdo.java:807) at com.ibm.cdb.topomgr.jdo.BaseJdo.updateArrayAttribute(Base Jdo.java:5254) at com.ibm.cdb.topomgr.jdo.BaseJdo.updateArrayAttribute(Base Jdo.java:5419) at com.ibm.cdb.topomgr.jdo.util.JdoArrayUpdate.apply(JdoArra yUpdate.java:184) at com.ibm.cdb.topomgr.jdo.BaseJdo.updatePersistentStore(Bas eJdo.java:3350) at com.collation.topomgr.jdo.topology.sys.vmware.VirtualCent erJdo.persistJdo(VirtualCenterJdo.java:879) Another case of this issue may be seen logged like this: ================= 2012-12-18 11:51:06,417 TopologyManager [RMI TCP Connection(1037)-10.147.199.131] WARN jdo.BaseJdo - [BaseJdo.E.26] BaseJdo.updateArrayAttribute() failed 2012-12-18 11:51:06,417 TopologyManager [RMI TCP Connection(1037)-10.147.199.131] DEBUG jdo.BaseJdo - BaseJdo.updateArrayAttribute() failed javax.jdo.JDOUserException: Cannot read fields from a deleted object FailedObject:2A30AB4E6FFF3D16AC7AC0EBF92533EE-0 at org.datanucleus.jdo.state.PersistentDeleted.transitionReadField( PersistentDeleted.java:116) at org.datanucleus.state.AbstractStateManager.transitionReadField(A bstractStateManager.java:551) at org.datanucleus.jdo.state.JDOStateManagerImpl.isLoaded(JDOStateM anagerImpl.java:1989) at com.collation.topomgr.jdo.topology.net.IpInterfaceJdo.jdoGetguid _(IpInterfaceJdo.java) at com.collation.topomgr.jdo.topology.net.IpInterfaceJdo.getGuid(Ip InterfaceJdo.java:785) at com.ibm.cdb.topomgr.jdo.BaseJdo.getGuid(BaseJdo.java:3043) at com.ibm.cdb.topomgr.jdo.BaseJdo.isArrayChanged(BaseJdo.java:5398 ) at com.ibm.cdb.topomgr.jdo.BaseJdo.updateArrayAttribute(BaseJdo.jav a:4941) =================
Local fix
Problem summary
In some situation while storing objects, TADDM marks objects as later such object cannot be accessed causing exception like this: 2012-11-27 13:15:17,794 TopologyManager [RMI TCP Connection(508)-10.147.199.131] ERROR jdo.BaseJdo - Cannot make object transient: javax.jdo.JDOUserException: Cannot make object transient since object is new, deleted and not yet committed FailedObject:826ABE6011023BA2A718C3A3F5E5E090-0 at org.datanucleus.jdo.NucleusJDOHelper.getJDOExceptionForNu cleusException(NucleusJDOHelper.java:367) at org.datanucleus.jdo.JDOPersistenceManager.jdoMakeTransien t(JDOPersistenceManager.java:801) at org.datanucleus.jdo.JDOPersistenceManager.makeTransient(J DOPersistenceManager.java:820) at org.datanucleus.jdo.JDOPersistenceManager.makeTransient(J DOPersistenceManager.java:830) at com.ibm.cdb.topomgr.jdo.BaseJdo.makeTransient(BaseJdo.jav a:3032) at com.collation.topomgr.jdo.topology.net.IpInterfaceJdo.gui d_(IpInterfaceJdo.java:807) at com.ibm.cdb.topomgr.jdo.BaseJdo.updateArrayAttribute(Base Jdo.java:5254) at com.ibm.cdb.topomgr.jdo.BaseJdo.updateArrayAttribute(Base Jdo.java:5419) at com.ibm.cdb.topomgr.jdo.util.JdoArrayUpdate.apply(JdoArra yUpdate.java:184) at com.ibm.cdb.topomgr.jdo.BaseJdo.updatePersistentStore(Bas eJdo.java:3350) at com.collation.topomgr.jdo.topology.sys.vmware.VirtualCent erJdo.persistJdo(VirtualCenterJdo.java:879)
Problem conclusion
The fix for this APAR is contained in the following maintenance packages: | Fix Pack | 7.2.1-TIV-ITADDM-FP0004 Check the IBM Software Support web site for availability of the above maintenance packages.
Temporary fix
Comments
APAR Information
APAR number
IV33125
Reported component name
APP DEPENDENCY
Reported component ID
5724N5500
Reported release
721
Status
CLOSED PER
PE
NoPE
HIPER
YesHIPER
Special Attention
NoSpecatt
Submitted date
2012-12-07
Closed date
2013-02-22
Last modified date
2013-02-22
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
APP DEPENDENCY
Fixed component ID
5724N5500
Applicable component levels
R721 PSY UP
FP04
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSPLFC","label":"Tivoli Application Dependency Discovery Manager"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"721","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
22 February 2013