NPE on Transaction.abort()

Hello. I am using the latest version of je 3.3.75.
I am getting a NPE when I believe abort() is called twice:
Caused by: java.lang.NullPointerException
at com.sleepycat.je.Transaction.abort(Transaction.java:90)
In the code, here's where I believe this is coming from:
90: txn.abort(false); // no sync required
This seems like a really small issue. It would be nice to be able to tell the state of a transaction. At the very least, an error besides NPE would be necessary.
Where is the issue tracker for sleepycat?
Cheers,
-Adrian

I'm sorry Adrian, I didn't answer your question earlier.
While BDB is available under an open-source license, we don't make public some of the facilities that other projects do. All of the following are private to Oracle and will remain so for the foreseeable future:
- Issue tracking system
- Source control system
- Road map and other internal documentation
The ticket number for this fix is #16214, and you'll see that in the change log when the release with the fix comes out.
Thanks,
--mark

Similar Messages

Transaction aborts after installing ODAC 12c Release 3

I have .net code that used a transaction scope which works fine using ODAC 11g Release 4, but fails with "Unable to enlist in a distributed transaction" using ODAC 12c Release 1,2, or 3. The transaction to a single database. I am at a loss for what could be the issue.
This issue occurs on both Windows 7 and Windows Server 2008 R2.
I have reviewed the trace logs for both the Microsoft Distributed Transaction Server, and the Oracle Services for Microsoft Transactions Services. The MSDTC trace logs indicate that the transaction abort was request was received from the calling application ("RECEIVED_ABORT_REQUEST_FROM_BEGINNER"). The ORAMTS trace logs indicate an OCI error and that there was an attempt to begin a distributed transaction with out logging on ("OCI_ERROR - 2048." , "ORA-02048: attempt to begin distributed transaction without logging on")
I can reproduce this error with a simple code example with just tried to insert records into a table. If I change the data provider to "System.Data.OracleClient", or uninstall 12c and install 11g this code works fine.
DataSet1TableAdapters.DataTable1TableAdapter da = new DataSet1TableAdapters.DataTable1TableAdapter();
            using (TransactionScope scope = new TransactionScope())
                Transaction txn = Transaction.Current;
                try
                   da.Insert(0, "This ia a title");
                    scope.Complete();
                    lblmessage.Text = "Transaction Succeeded.";
                catch (Exception ex)
                    txn.Rollback();
                    lblmessage.Text = "Transaction Failed.";
Can anyone provide any ideas what is happening? I really would like to use ODAC 12c.
Thanks.

Moving to the ODP.NET forum to get a wider audience.

Snapshot isolation transaction aborted due to update conflict

Hi Forum,
Can anyone help me to give the solution for this below problem.
We are developing MVC3 application with SQL Server 2008, we are facing as
Snapshot isolation transaction aborted due to update conflict
Snapshot isolation transaction aborted due to update conflict. You cannot use snapshot isolation to access table 'dbo.Tb_M_Print' directly or indirectly in database 'DB_Production' to update, delete, or insert the row that has been modified or deleted
by another transaction. Retry the transaction or change the isolation level for the update/delete statement .
Please tell me the solution how to proceed for the above problem
Rama

change the isolation level for the update/delete statement .
The error message already mentions the solution.
See also MSDN
Lesson 1: Understanding the Available Transaction Isolation Levels => Update Conflicts
Olaf Helper
[ Blog] [ Xing] [ MVP]

Transaction abort Entity framework - Oracle 10g

Hi.
I have a problem using entity framework and Oracle 10g, i m using a transactionScope in my code, but when the transaction is finishing is throwed a exception "Transaction Abort" , it's a problem only when i am using Oracle i don't have any problem with SQL server.
Thanks in advance for your help.

Hi.
I have a problem using entity framework and Oracle 10g, i m using a transactionScope in my code, but when the transaction is finishing is throwed a exception "Transaction Abort" , it's a problem only when i am using Oracle i don't have any problem with SQL server.
Thanks in advance for your help.

Getting error 'root transaction wanted to commit, but transaction aborted'

We have a module in our project, which reads data from XML file and merges the data into the database. This merging at one end happens to a SQL Server 2005/SQL Server 2000 datbase. At the other end it happens to a Oracle database. We have a portal application developed in ASP.NET from where, we merge the data.
When the data to be merged is very huge, we get this message. 'The root transaction wanted to commit, but transaction aborted'. Right now we are getting this message, when we try to merge data on to a oracle database.
But this problem is very intermittent. It happens only when there is huge amount of data to be inserted to one table.
As i have mentioned in my post, we use Windows server 2003 operation system with service pack 2. This error does not come when we do the same operation with service pack 1.
So is it OS dependent?

Please find the details of the log file.
DMS_CORE_DAL_DBERROR
at Oracle.DataAccess.Client.OracleException.HandleErrorHelper(Int32 errCode, OracleConnection conn, IntPtr opsErrCtx, OpoSqlValCtx* pOpoSqlValCtx, Object src, String procedure)
at Oracle.DataAccess.Client.OracleCommand.ExecuteNonQuery()
at Oracle.DataAccess.Client.OracleCommand.ExecuteNonQuery()
at CoreServices.DAL.DataManager.ExecuteNonQueryProc(DBConnection foConn, String fProcName, DOList foParamDOList)
*** ORA-02291: integrity constraint (ADVTVS.FK_JCARD_JCARD_LAB) violated - parent key not found
ORA-06512: at "ADVTVS.PKG_SYNC_MERGE_TRNS_SERVICE", line 318
ORA-06512: at line 1 ---
Server stack trace:
at CoreServices.Pipeline.TransactionPipeline.Process(IPipelineable& foPipeLineDataObject, PipelineOperation fiPipelineOprn)
at System.Runtime.Remoting.Messaging.Message.Dispatch(Object target, Boolean fExecuteInContext)
at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg, Int32 methodPtr, Boolean fExecuteInContext)
Exception rethrown at [0]:
at DataSync.MergeData.MergeDataManager.Merge(Int32 fiDealerId)
at Client.DataSync.cmdMerge_Click(Object sender, EventArgs e)
DATASYNC_MERGE
at System.Runtime.InteropServices.Marshal.ThrowExceptionForHR(Int32 errorCode, IntPtr errorInfo)
at System.EnterpriseServices.Thunk.Callback.DoCallback(Object otp, IMessage msg, IntPtr ctx, Boolean fIsAutoDone, MemberInfo mb, Boolean bHasGit)
at System.EnterpriseServices.ServicedComponentProxy.CrossCtxInvoke(IMessage reqMsg)
at System.EnterpriseServices.ServicedComponentProxy.Invoke(IMessage request)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
at CoreServices.Pipeline.TransactionPipeline.Process(IPipelineable& foPipeLineDataObject, PipelineOperation fiPipelineOprn)
at DataSync.MergeData.MergeDataManager.Merge(Int32 fiDealerId) at System.Runtime.InteropServices.Marshal.ThrowExceptionForHR(Int32 errorCode, IntPtr errorInfo)
at System.EnterpriseServices.Thunk.Callback.DoCallback(Object otp, IMessage msg, IntPtr ctx, Boolean fIsAutoDone, MemberInfo mb, Boolean bHasGit)
at System.EnterpriseServices.ServicedComponentProxy.CrossCtxInvoke(IMessage reqMsg)
at System.EnterpriseServices.ServicedComponentProxy.Invoke(IMessage request)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
at CoreServices.Pipeline.TransactionPipeline.Process(IPipelineable& foPipeLineDataObject, PipelineOperation fiPipelineOprn)
at DataSync.MergeData.MergeDataManager.Merge(Int32 fiDealerId)
*** The root transaction wanted to commit, but transaction aborted ---
The ORA codes are ORA-02291 and ORA-06512.
We are not getting any of these errors, when we merge same data from Windows 2003 server SP1. But if we execute it from SP2, we are getting this error.
Are there any hotfixes provided by MS to fix this problem.

Root transaction wanted to commit, but transaction aborted

Our client is getting error when trying to do bulk insert into one of the tables. Oracle version is 10g. The error says Root transaction wanted to commit, but transaction aborted. Client is using Windows server 2003 service pack 2.
This error is not appearing when the application is accessed from Windows server 2003 service pack 1. All other application settings are similar.
We have a module in our project, which reads data from XML file and merges the data into the database. We have a portal application developed in ASP.NET from where, we merge the data into oracle database.
When the data to be merged is very huge, we get this message. 'The root transaction wanted to commit, but transaction aborted'.
But this problem is very intermittent. It happens only when there is huge amount of data to be inserted to one table.
As i have mentioned in my post, we use Windows server 2003 operation system with service pack 2. This error does not come when we do the same operation with service pack 1.
So is it OS dependent?
Edited by: user8662578 on Jul 29, 2009 8:34 PM

Our client is getting error when trying to do bulk insert into one of the tables. Oracle version is 10g. The error says Root transaction wanted to commit, but transaction aborted. Client is using Windows server 2003 service pack 2.
This error is not appearing when the application is accessed from Windows server 2003 service pack 1. All other application settings are similar.
We have a module in our project, which reads data from XML file and merges the data into the database. We have a portal application developed in ASP.NET from where, we merge the data into oracle database.
When the data to be merged is very huge, we get this message. 'The root transaction wanted to commit, but transaction aborted'.
But this problem is very intermittent. It happens only when there is huge amount of data to be inserted to one table.
As i have mentioned in my post, we use Windows server 2003 operation system with service pack 2. This error does not come when we do the same operation with service pack 1.
So is it OS dependent?
Edited by: user8662578 on Jul 29, 2009 8:34 PM

IDoc Adapter 151 - Transaction aborted

Hi fellows,
after patching our XI-System to SP19 we try to do a new IDoc2File Szenario. We have one from the old XI-Level which runs really good. It's going from external R/3 to our XI server into the file system.
the new scenario has some selfmade IDoc and i already checked EVERYTHING (we20, we21, sm58, sm59, idx1, idx2, idx5, sm21) Following i give some hints what kind of problems i see. perhaps u can help me?!
in the sender-system:
sm58: IDOC_INBOUND_ASYNCHRONOUS, some mistake in IDX1 saying RFC-Destination is corrupt. But i can successfully use the remote login and the connection test.
in the receiver system:
idx5: nothing displayed concerning the new szenario
sm21:Transaction aborted IDOC_ADAPTER 151
I have no clue what it can be, has someone had same experiences?!
thx best regards, Jens

Thx!
> From SE91 the error message IDOC_ADAPTER 151 means:
>
> Short Text
> Transaction IDX1: Port &1, client &2, RFC destination
> &3 contain error
>
> Diagnosis
> Transaction IDX1: Port &1, client &2, RFC destination
> &3 contain errors
>
> System response
> You tried to fetch the metadata for the current IDoc
> from the reference system, using RFC.
>
> In doing so, an error occurred that was caused by one
> of the following:
>
> 1. You have not yet assigned a port/client to the RFC
> destination.
>
> 2. You have not yet created the RFC destination or it
> contains errors.
>
> 3. The target system is unable to receive.
>
> Procedure
> 1. Check your RFC destination in transaction SM58.
>
Yes, SM58 in the sender system says an error concerning IDX1. RFC destination is wrong - BUT it's all working fine. in case of reading the metadata i also configured IDX2 in XI System to get the metadata in advance. RFC remote login and Connection test runs fine!!
I have no clue again because when i use WE19 with the old IDoc-Scenario and the SAME parameters of sending the IDoc it's working, with the new one it doesn't.
some ideas
null

Transaction aborted (possibly due to transaction time out) - Question

This one is driving me insane!
Bellow you will find the code, the descriptor stuff and the exception. The code belongs to a CMP EJB using CMT (transactions). This gets called from a session bean. Please help.
Here is the code:
public Object ejbCreate( String id )
 throws CreateException {
 s_logger.debug( "ejbCreate()" ); // this prits
 //setId( id );
 return null;
public void ejbPostCreate( String id )
 throws CreateException {
 s_logger.debug( "ejbPostCreate()" ); // this also prints
here is descriptor stuff:
<container-transaction>
<method>
<ejb-name>AgentBean</ejb-name>
<method-name>*</method-name>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>
here is the !@#$ exception (sorry been tracing this one for hours):
RemoteException occurred in server thread; nested exception is:
java.rmi.RemoteException: Transaction aborted (possibly due to transaction time out).; nested exception is: javax.transaction.RollbackException: Transaction marked for rollback; nested exception is:
javax.transaction.RollbackException: Transaction marked for rollback
java.rmi.ServerException: RemoteException occurred in server thread; nested exception is:
java.rmi.RemoteException: Transaction aborted (possibly due to transaction time out).; nested exception is: javax.transaction.RollbackException: Transaction marked for rollback; nested exception is:
javax.transaction.RollbackException: Transaction marked for rollback
java.rmi.RemoteException: Transaction aborted (possibly due to transaction time out).; nested exception is: javax.transaction.RollbackException: Transaction marked for rollback; nested exception is:
javax.transaction.RollbackException: Transaction marked for rollback
javax.transaction.RollbackException: Transaction marked for rollback
<<no stack trace available>>

It usually means that you're doing something which creates a loop in your locking. Something like setting a value in each instance from an update method of one of the instances. Your posted code doesn't seem to be the trouble, but I could be missing something.
Success,
S.

Javax.ejb.EJBException: Transaction aborted

Hello everyone, I am new in javaEE6. When i try to develop and simple example i meet this error but i can't find which code line cause it. I use JSF EJB3.1 EclipseLink JPA 2.0 in Glassfish v3 and developed in Netbean6.8. Here is my Stack trace .
Caused by: javax.ejb.EJBException: Transaction aborted
 at com.sun.ejb.containers.BaseContainer.completeNewTx(BaseContainer.java:4997)
 at com.sun.ejb.containers.BaseContainer.postInvokeTx(BaseContainer.java:4756)
 at com.sun.ejb.containers.BaseContainer.postInvoke(BaseContainer.java:1955)
 at com.sun.ejb.containers.BaseContainer.postInvoke(BaseContainer.java:1906)
 at com.sun.ejb.containers.EJBLocalObjectInvocationHandler.invoke(EJBLocalObjectInvocationHandler.java:198)
 at com.sun.ejb.containers.EJBLocalObjectInvocationHandlerDelegate.invoke(EJBLocalObjectInvocationHandlerDelegate.java:84)
 at $Proxy158.createUsers(Unknown Source)
 at home.tuan.bussiness.__EJB31_Generated__UsersEJB__Intf____Bean__.createUsers(Unknown Source)
 at home.tuan.controller.UsersController.doCreateUser(UsersController.java:40)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:597)
 at com.sun.el.parser.AstValue.invoke(AstValue.java:234)
 at com.sun.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:297)
 at com.sun.faces.facelets.el.TagMethodExpression.invoke(TagMethodExpression.java:98)
 at javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:88)
 ... 32 more
Caused by: javax.transaction.RollbackException: Transaction marked for rollback.
 at com.sun.enterprise.transaction.JavaEETransactionImpl.commit(JavaEETransactionImpl.java:450)
 at com.sun.enterprise.transaction.JavaEETransactionManagerSimplified.commit(JavaEETransactionManagerSimplified.java:837)
 at com.sun.ejb.containers.BaseContainer.completeNewTx(BaseContainer.java:4991)
 ... 48 more
Caused by: Exception [EclipseLink-4002] (Eclipse Persistence Services - 2.0.0.v20091127-r5931): org.eclipse.persistence.exceptions.DatabaseException
Internal Exception: java.sql.SQLSyntaxErrorException: Syntax error: Encountered "." at line 1, column 29.
Error Code: -1
Call: INSERT INTO ChatDatabase.dbo.Users (UserName, Pass) VALUES (?, ?)
 bind => [er, w]
Query: InsertObjectQuery(home.tuan.model.Users@825299)My Entity is:
package home.tuan.model;
import java.io.Serializable;
import javax.persistence.Column;
import javax.persistence.Entity;
import javax.persistence.Id;
import javax.persistence.NamedQueries;
import javax.persistence.NamedQuery;
import javax.persistence.Table;
* @author minhtuan
@Entity
@Table(name = "Users", catalog = "ChatDatabase", schema = "dbo")
public class Users implements Serializable {
 private static final long serialVersionUID = 1L;
 @Id
 @Column(name = "UserName")
 private String userName;
 @Column(name = "Pass")
 private String pass;
 public Users() {
 public Users(String userName, String pass) {
 this.userName = userName;
 this.pass = pass;
 public String getUserName() {
 return userName;
 public void setUserName(String userName) {
 this.userName = userName;
 public String getPass() {
 return pass;
 public void setPass(String pass) {
 this.pass = pass;
}My session bean is:
package home.tuan.bussiness;
import home.tuan.model.Users;
import java.util.ArrayList;
import java.util.List;
import javax.ejb.Stateless;
import javax.persistence.EntityManager;
import javax.persistence.PersistenceContext;
import javax.persistence.Query;
* @author minhtuan
@Stateless
public class UsersEJB {
@PersistenceContext(unitName="MavenTestPU")
private EntityManager em ;
public Users createUsers(Users newUser){
 em.persist(newUser);
 return newUser;
}My controller class is:
package home.tuan.controller;
import home.tuan.bussiness.UsersEJB;
import home.tuan.model.Users;
import java.util.ArrayList;
import java.util.List;
import javax.ejb.EJB;
import javax.faces.bean.ManagedBean;
import javax.faces.bean.RequestScoped;
import javax.persistence.EntityTransaction;
import javax.persistence.Persistence;
import javax.transaction.UserTransaction;
* @author minhtuan
@ManagedBean(name="UsersController")
@RequestScoped
public class UsersController {
 /** Creates a new instance of UsersController */
 @EJB
 UsersEJB userEJB;
 Users newUser = new Users();
 List<Users> listUsers = new ArrayList<Users>();
 public String doNewUser(){
 return "index.jsp";
 public String doCreateUser(){
 System.out.println("Den day rui");
 System.out.println(newUser.getUserName());
 System.out.println(newUser.getPass());
 newUser = userEJB.createUsers(newUser);
 return "index.jsp";
 public List<Users> getListUsers() {
 return listUsers;
 public void setListUsers(List<Users> listUsers) {
 this.listUsers = listUsers;
 public Users getNewUser() {
 return newUser;
 public void setNewUser(Users newUser) {
 this.newUser = newUser;
}And my persistence.xml is:
<persistence version="2.0" xmlns="http://java.sun.com/xml/ns/persistence"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_2_0.xsd">
<persistence-unit name="MavenTestPU" transaction-type="JTA">
 <provider>org.eclipse.persistence.jpa.PersistenceProvider</provider>
 <class>home.tuan.model.Users</class>
 <properties>
 
 <property name="eclipselink.target-database" value="SQLSERVER"/>
 <property name="eclipselink.jdbc.driver" value="com.microsoft.sqlserver.jdbc.SQLServerDriver"/>
 <property name="eclipselink.jdbc.url" value="jdbc:sqlserver://localhost:1433;databaseName=ChatDatabase"/>
 
 
 <property name="eclipselink.jdbc.user" value="sa"/>
 <property name="eclipselink.jdbc.password" value="12345"/>
 
 
 <property name="eclipselink.logging.level" value="INFO"/>
 </properties>
</persistence-unit>
</persistence>Thanks in advance
Edited by: ActiveDean on Dec 24, 2009 4:38 PM

You need to step through a debugger and find the source of your problem as something is clearly going wrong and causing the transaction to roll back. That is all that message tells us.
m

Essbase Error(1003050): Data Load Transaction Aborted With Error (1220000)

Hi
We are using 10.1.3.6, and got the following error for just one of the thousands of transactions last night.
cannot end dataload. Essbase Error(1003050): Data Load Transaction Aborted With Error (1220000)
The data seems to have loaded, regardless of the error. Should we be concerned, and does this suggest something is not right somewhere?
Your assistance is appreciated.
Cheers

Hi John
Not using a load rule.
There were two other records which rejected based on absentee members. The error message was different for them, and easily fixed.
But this error doesn't tell us much. I will monitor the next run to see if the problem persists.
Thanks

Automatch by Account in processing ICP Transaction aborted

Hi,
While trying the oracle tutorial for Managing Intercompany Transactions, the Automatch by Account option is getting aborted. In ErrorLogViewer, it just says "One or more errors occurred during processing of command."
What could be the reason for this?
Any help would be appreciated.
Thanks,
A

EastSales,WestSales,SalesInterco,P3000_Phones,Electronic_City,National_Accts,[None] USD 3400
WestSales,EastSales,PurchasesInterco,P3000_Phones,Electronic_City,National_Accts,[None] USD 3400
These are the following ICP transactions entered for Actual, 1999, March. This is from the Comma application. ICP transaction was successful but I don't see the elimination entry of USD 3400 in the Unitedstates.EastRegion which is the common parent. Unitedstates is the common parent. In the data grid does the accont also needs to be the common parent of SalesInterco and PurchasesInterco?

Transaction Aborted Exceptions are seen when service downloading data

Hi,
We are getting two different types of exceptions while one service trying to download data from another service
There are two scenarios where we are getting these transaction exceptions that are seen when client's service downloads data from server's service.
1. The first kind of transaction exception is seen when service is trying to send the message to messaging queue in the InitialReceiveNext() method. The queue.send method throws this exception and the stack trace is as mentioned below:
04 Jun 2014 19:16:12,805 [BridgeExchanger] TRACE - Sending queue message 00000000-0000-0000-0000-000000000000\0 to queue private$\msgqueue
04 Jun 2014 19:16:12,806 [ClientBridgeEndpoint] ERROR - Error occurred during Receive!
System.Transactions.TransactionException: The operation is not valid for the state of the transaction. ---> System.TimeoutException: Transaction Timeout
— End of inner exception stack trace —
at System.Transactions.TransactionState.Promote(InternalTransaction tx)
at System.Transactions.Transaction.Promote()
at System.Transactions.TransactionInterop.ConvertToOletxTransaction(Transaction transaction)
at System.Transactions.TransactionInterop.GetDtcTransaction(Transaction transaction)
at System.Messaging.MessageQueue.StaleSafeSendMessage(MQPROPS properties, IntPtr transaction)
at System.Messaging.MessageQueue.SendInternal(Object obj, MessageQueueTransaction internalTransaction, MessageQueueTransactionType transactionType)
at CI.Platform.Bus.Bridge.Client.BridgeExchanger.InitialReceiveNext(DownloadEndpoint endpoint)
at CI.Platform.Bus.Bridge.Client.BridgeExchanger.ReceiveNext()
at CI.Platform.Bus.Bridge.Client.ClientBridgeEndpoint.Exchange(Object state)
2. The second kind of exception is seen at the transaction.complete statement in the InitialReceiveNext() method. The stack trace is as shown below:
04 Jun 2014 23:15:59,152 [BridgeExchanger] DEBUG - Skipping the download message as the message is already downloaded..No new message is added to queue private$\msgqueue
04 Jun 2014 23:15:59,153 [ClientBridgeEndpoint] ERROR - Error occurred during Receive!
System.Transactions.TransactionAbortedException: The transaction has aborted. ---> System.TimeoutException: Transaction Timeout
— End of inner exception stack trace —
at System.Transactions.TransactionStateAborted.BeginCommit(InternalTransaction tx, Boolean asyncCommit, AsyncCallback asyncCallback, Object asyncState)
at System.Transactions.CommittableTransaction.Commit()
at System.Transactions.TransactionScope.InternalDispose()
at System.Transactions.TransactionScope.Dispose()
at CI.Platform.Bus.Bridge.Client.BridgeExchanger.InitialReceiveNext(DownloadEndpoint endpoint)
at CI.Platform.Bus.Bridge.Client.BridgeExchanger.ReceiveNext()
at CI.Platform.Bus.Bridge.Client.ClientBridgeEndpoint.Exchange(Object state)
If anybody has any insight please reply.
Thanks in advance!!!

Hello,
Your two questions are both related to MSMQ forum. Please post threads on that forum for more effective response. Please refer to
http://social.msdn.microsoft.com/Forums/windowsdesktop/en-US/home?forum=msmq. Thank you for understanding.
Regards,
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Data Load Transaction Aborted With Error [1130203]

I can't to load data by using rule file . How can I fixthis problem? it shown error message "Data Load TransactionAborted With Error [1130203]".My Essbase is ver 7.0.0.

Don't have that message. Have you lookedin the Application log to see if there is any more information - this is the best place to start. Is the file that you are trying to load the same format as previous files loaded - has anything changed ? maybe you need to open the load rue, and then open the file to see if teh data lines up with the expected format and setup of the load rule .

How to Abort all opened Transactions at once?

Hi,
Is there any way to abort all open transactions at once ?
Thanks for any help.
Thanks,
reddy

Reddy,
No, you need to call Transaction.abort() on each transaction individually.
Regards.
Linda

Aborted multi-machine transaction stays in BB

I have a distributed transaction going across 2 machines. I'm testing
out what happens when I abort the transaction. If I go into tmadmin,
and do a pt, I get the following printout. The problem is the
OK_ORATMSGRP in the first machine is specified being remote and as the
coord group and has a status of TMGACTIVE. The same group on the other
machine (where the group is local) has a status of TMGABORTED. Now this
is exactly the same group, but one machine thinks it is TMGACTIVE and
the other machine thinks it's TMGABORTED (this is the correct status).
The transaction will remain in the bulletin board until the timeout
value expires. This shouldn't happen. I thought as soon as I called
tx_rollback the whole transaction should be aborted. What is going on?
This is causing a problem because before we didn't specify a transaction
timeout and the BB was being filled with Aborted transactions that had
that one group marked as TMGACTIVE when it shouldn't have been.
Subsequently the BB became full and new transactions couldn't be
started.
index=2 gtrid=x0 x3d25495d xa61
: Machine id: IRGVELOCITY, Transaction status: TMGABORTED
Group count: 2, timeout: 30, transaction timed out
Known participants:
group: OK_ORATMSGRP, status: TMGACTIVE, remote, coord
group: OK_FXNTGRP, status: TMGABORTED, local
Machine id: CDDEV, Transaction status: TMGABORTED
Group count: 4, timeout: 30, transaction timed out
Known participants:
group: OK_ORATMSGRP, status: TMGABORTED, local, coord
group: OK_MQTMSGRP, status: TMGABORTED, local
group: OK_TUXTMSGRP, status: TMGABORTED, local
group: OK_FXNTGRP, status: TMGABORTED, remote

So it would be fair to say that as a rule, you should always specify a reasonably
low transaction timeout so the BB doesn't become full of aborted transactions? I
still think that an aborted transaction should be removed from the BB at some point
(especially for aborted transactions with no timeout value). Maybe there should
be a different timeout value, separate from the transaction timeout value that determines
how long an aborted transaction should remain in the bulletin board.
Peter Holditch <[email protected]> wrote:
Frank,
The timeout is in there to prevent the scenario where a transaction aborts
and
is deleted, and then another message on behalf of the same transaction arrives.
With the records having been deleted, the system has no option but to
create a
new GTT entry for the apparently new transaction and then wait for it to
time out.
I know that this timeout is also in the WLS implementation. I do not believe
that it is infinite!
Note also that the only trandactions that will ever hit the TLOG are ones
that
have decided to commit, by which time this timeout is not relevant any more.
That's my recollection of the reasoning, I hope it sheds some light...
Regards,
Peter.
Frank Clarijs wrote:
Failed (rolled back) distributed transactions remain in the BB until
timeout, by design. I'm not sure why, but this behaviour is the one BEA
(or its predecessors) explicitely implemented.
This has of course strange consequences: if your application aborts
transactions quite often, either you need a big TLOG and even higher
setting of "maximum global transactions" in the UBB (or you can't
restart your application after a crash), or you need to set the timeout
quite low, with all risks from that...
Don't worry, it's even worse in Weblogic, where the bean for an aborted
transaction never disappears, by design.
Frank
Anthony Fryer wrote:
I have a distributed transaction going across 2 machines. I'm testing
out what happens when I abort the transaction. If I go into tmadmin,
and do a pt, I get the following printout. The problem is the
OK_ORATMSGRP in the first machine is specified being remote and as the
coord group and has a status of TMGACTIVE. The same group on the other
machine (where the group is local) has a status of TMGABORTED. Now
this is exactly the same group, but one machine thinks it is TMGACTIVE
and the other machine thinks it's TMGABORTED (this is the correct
status). The transaction will remain in the bulletin board until the
timeout value expires. This shouldn't happen. I thought as soon as I
called tx_rollback the whole transaction should be aborted. What is
going on? This is causing a problem because before we didn't specifya
transaction timeout and the BB was being filled with Aborted
transactions that had that one group marked as TMGACTIVE when it
shouldn't have been. Subsequently the BB became full and new
transactions couldn't be started.
index=2 gtrid=x0 x3d25495d xa61
: Machine id: IRGVELOCITY, Transaction status: TMGABORTED
Group count: 2, timeout: 30, transaction timed out
Known participants:
group: OK_ORATMSGRP, status: TMGACTIVE, remote, coord
group: OK_FXNTGRP, status: TMGABORTED, local
Machine id: CDDEV, Transaction status: TMGABORTED
Group count: 4, timeout: 30, transaction timed out
Known participants:
group: OK_ORATMSGRP, status: TMGABORTED, local, coord
group: OK_MQTMSGRP, status: TMGABORTED, local
group: OK_TUXTMSGRP, status: TMGABORTED, local
group: OK_FXNTGRP, status: TMGABORTED, remote

NPE on Transaction.abort()

Similar Messages

Maybe you are looking for