Resolution:
Description:
============
In TIBCO MDM, DBloader failed a CORBA TRANSACTION_ROLLEDBACK exception.


Symptoms:
========
The following exception is thrown when running the DB Load.

2010-06-29 17:57:11,135 [TIBCO EMS Session Dispatcher (4509)] DEBUG com.tibco.mdm.repository.engine.initialload.AsyncDBLoader - DBLoader process failed.....
<MqException: BEGIN>
Code: JAV-8012
ID: 0A5E0039_8ADE80B92985DFBB012985EDA442008C
DATETIME: Tue Jun 29 17:57:10 CDT 2010
EXCEPTIONMESSAGE: javax.transaction.TransactionRolledbackException: CORBA TRANSACTION_ROLLEDBACK 0x0 No; nested exception is:
        org.omg.CORBA.TRANSACTION_ROLLEDBACK: javax.transaction.TransactionRolledbackException:  ; nested exception is:
        com.ibm.websphere.csi.CSITransactionRolledbackException: Transaction marked rollbackonly  vmcid: 0x0  minor code: 0  completed: No
STACKTRACE: javax.transaction.TransactionRolledbackException: CORBA TRANSACTION_ROLLEDBACK 0x0 No; nested exception is:
        org.omg.CORBA.TRANSACTION_ROLLEDBACK: javax.transaction.TransactionRolledbackException:  ; nested exception is:
        com.ibm.websphere.csi.CSITransactionRolledbackException: Transaction marked rollbackonly  vmcid: 0x0  minor code: 0  completed: No
        at com.ibm.CORBA.iiop.UtilDelegateImpl.mapSystemException(UtilDelegateImpl.java:281)
        at com.ibm.CORBA.iiop.UtilDelegateImpl.wrapException(UtilDelegateImpl.java:740)
        at javax.rmi.CORBA.Util.wrapException(Util.java:296)
        at com.tibco.mdm.session.repository.engine.initialload._DBLoaderSsnRemote_Stub.bulkInsertProductKey(_DBLoaderSsnRemote_Stub.java:702)
        at com.tibco.mdm.session.repository.engine.initialload.DBLoaderBusinessDelegate.bulkInsertProductKey(DBLoaderBusinessDelegate.java:103)
        at com.tibco.mdm.session.repository.engine.initialload.DBLoaderSsnBean.importRowsForDBLoader(DBLoaderSsnBean.java:175)
        at com.tibco.mdm.session.repository.engine.initialload.EJSRemoteStatelessDBLoaderSsn_8c12a46c.importRowsForDBLoader(Unknown Source)
        at com.tibco.mdm.session.repository.engine.initialload._DBLoaderSsnRemote_Stub.importRowsForDBLoader(_DBLoaderSsnRemote_Stub.java:540)
        at com.tibco.mdm.session.repository.engine.initialload.DBLoaderBusinessDelegate.importRowsForDBLoader(DBLoaderBusinessDelegate.java:69)
        at com.tibco.mdm.repository.engine.initialload.AsyncDBLoader.processForRecord(AsyncDBLoader.java:458)
        at com.tibco.mdm.repository.engine.initialload.AsyncDBLoader.onAsyncCall(AsyncDBLoader.java:181)
        at com.tibco.mdm.integration.messaging.AsyncCallMessageListener.onMessage(AsyncCallMessageListener.java:56)
        at com.tibco.mdm.integration.messaging.message.MqNativeMessageListener.onMessage(MqNativeMessageListener.java:93)
        at com.tibco.tibjms.TibjmsxSessionImp._submit(TibjmsxSessionImp.java:3774)
        at com.tibco.tibjms.TibjmsxSessionImp._dispatchAsyncMessage(TibjmsxSessionImp.java:2048)
        at com.tibco.tibjms.TibjmsxSessionImp$Dispatcher.run(TibjmsxSessionImp.java:3300)
Caused by: org.omg.CORBA.TRANSACTION_ROLLEDBACK: javax.transaction.TransactionRolledbackException:  ; nested exception is:
        com.ibm.websphere.csi.CSITransactionRolledbackException: Transaction marked rollbackonly  vmcid: 0x0  minor code: 0  completed: No
        at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:45)
        at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:39)
        at java.lang.reflect.Constructor.newInstance(Constructor.java:515)
        at com.ibm.rmi.util.ProxyUtil.copyObject(ProxyUtil.java:328)
        at com.ibm.CORBA.iiop.UtilDelegateImpl.copyObject(UtilDelegateImpl.java:845)
        at javax.rmi.CORBA.Util.copyObject(Util.java:333)
        at com.tibco.mdm.session.repository.engine.initialload._DBLoaderSsnRemote_Stub.bulkInsertProductKey(_DBLoaderSsnRemote_Stub.java:698)
        ... 12 more
ERRORMESSAGE: Failed to  import rows
Code: Failed to start process of DBLoader .....



Resolution:
==========
This could be resolved by

1).Changing the values for the connection poolsize and the maximum transaction timeout in the WebSphere console to to be 40 and 0 respectively. 
2).Increasing the ecmdatasource transaction timeout parameter in the stand.