Rollback a transaction

Dear All,
I am calling an RFC from VB.
The RFC first executes a BDC, then a BAPI and finally inserts data in z-table.
In case operation fails in any one process, I want to rollback.
Is this possible ? if yes then plz let me know.
Thanks.

Hi,
In BAPI we can use BAPI_TRANSACTION_ROLLBACK.
FORM commit_work .
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
    EXPORTING
      wait = ' '.
ENDFORM.                    " COMMIT_WORK
For BDC we can commit in following way.
CALL TRANSACTION 'SE38' USING BDCDATA MODE 'N'
                           MESSAGES INTO ITAB.
A call transaction ends successfully for the following reasons:
1. COMMIT WORK
2. Next screen = 0
3. LEAVE TO TRANSACTION SPACE.
If any errors are found they get stored in itab as above.
We can handle that error message and commit the work.
If itab[] is initial.
commit and wait.
endif.
Hope this helps you.
plz reward if useful.
thanks,
dhanashri.

Similar Messages

Rollback a transaction in a session bean BMP?

The following code would work correctly if executed in a stateless session bean BMP?
InitialContext ic = new InitialContext();
javax.sql.DataSource dataSource = (javax.sql.DataSource) ic.lookup("java:comp/env/jdbc/OracleDS");
Connection conn = dataSource.getConnection();
conn.setAutoCommit(false);
Statement stmt = conn.createStatement("UPDATE TABLE_A SET NAME = 'Duke' WHERE ID = 7");
stmt.executeUpdate();
if (someCondition) {
conn.commit();
} else {
conn.rollback();
My question:
It�s possible to rollback a transaction using rollback() from Connection class in a stateless
session bean BMP?

Dear JDC member:
With EJB, you can gain the benefit of transactions without performing any transaction programming. That is, your enterprise beans never explicitly issue a begin, commit, or abort statement. The container performs it to you. But you have to tell the container how to do it. As you might know, the deploment descriptor is the place for it.
But nothing prevent you to do do programmatic transaction as you want.. For that case you have to know JTA (Java Transaction API) and more.
Suppose the transaction aborts, you have to throw an exception back to the client or try it again. The issue here is with stateless sesssion beans, there is no in-memory conversational state. You might think to implement javax.ejb.SessionSynchronization interface with your business methods....
You see there is a lot to know. You can take care of transactions in the client code, but it is a bad design.
You have to understand today most application servers (Websphere, Weblogic...) are designed to minimize those issues in order to make developers' tasks easier. The container takes care of transactions.
Be careful when you write stateless session beans BMP (BMP are for entiti beans)
Regards,
Armand Komenan

How can I rollback a transaction using EJBContext.rollbackOnly()?

I failed to rollback a "required" method of a seesion bean using EJBContext.rollbackOnly() , but it rollbacked if I throw EJBException , how can I rollback a transaction by
EJBContext.rollbackOnly() ? Thanks for your help.
regards,
dean

The full and partial updates (whether it be Thunderbird, Firefox or SeaMonkey) from mozilla.org are only provided to the official builds and not builds built yourself or by a third-party.
The openSUSE and other Linux distro provided builds have their own ways of package updates in their package manager.
However if the poster is using Thunderbird for Linux from http://www.mozilla.org/en-US/thunderbird/ (64-bit Linux is on ftp) then those preferences would be valid and work.
Nothing is being gutted as it has been this way since forever with third-party builds whether on Windows, Mac OSX and Linux.

Rollback per transaction issue

hi
i found in our live database Rollback per transaction: 92.86% how i can troubleshoot this value and what is the rezone and how i can solve it

Hi,
this is more likely to be an application issue, not a database one. I heard of webservers that do a rollback after each query (!), maybe it's one of them, or a similar error in the application design. I have also once come across a case when there was a great number of fake commits on the system (so called "readonly commits") which were caused by an internal Oracle bug. The problem was resolved by applying a patch -- so you may want to check MOS articles for similar symptoms.
Best regards,
Nikolay

Get IllegalStateException when rollback client transaction while thansaction is already rollbacked by Container

Hi,
          I use WL5.1.0 + SP8. When I start a client-demarcated transaction and
          call two methods in EJB, the second method will throw a system level
          exception (such as RemoteException), the container rollback the
          transaction so that when I catch the exception in client and try to
          rollback by myself, I got an IllegalStateException: There is no
          transaction associated with this thread.
          In SP8, I thought they fixed this problem and the container is supposed
          to mark the transaction rollbacked and throw
          TransactionRolledbackException to client instead of rollback this
          transaction.. But obviously it still doesn't work in SP8.
          Is this still a bug or am I missing something?
          Thanks a lot!
          Tao


Hi,
          I use WL5.1.0 + SP8. When I start a client-demarcated transaction and
          call two methods in EJB, the second method will throw a system level
          exception (such as RemoteException), the container rollback the
          transaction so that when I catch the exception in client and try to
          rollback by myself, I got an IllegalStateException: There is no
          transaction associated with this thread.
          In SP8, I thought they fixed this problem and the container is supposed
          to mark the transaction rollbacked and throw
          TransactionRolledbackException to client instead of rollback this
          transaction.. But obviously it still doesn't work in SP8.
          Is this still a bug or am I missing something?
          Thanks a lot!
          Tao

Statspack Rollback per transaction % vs Log Miner rollback = 1

Hi,
I'm investigating high Rollback per transaction % = 30% in our 9.2.0.8 EE databse .
First think was checking all archive logs from period equal to statspack snapshot range
but looks like there is huge discrepancy between that two tools .
What I've found from v$logmnr_contents where rollback = 1 was that
only 0,5% transactions was rollbacked .
I'm wondering what could cause such difference is that true
unique constraint violation (or other exceptions) is not recorded in redologs as rollbacked transaction ?
Any ideas ?
Major problem is still what is causing high rollback % .
Regards
G

I'm investigating increase in undo usage and Rollback per transaction % = 30 .
Strange issue because v$transacion is not showing demanding transacions , rather small quick (oltp system).
Here is sp report:
DB Name     DB Id Instance   Inst Num Release   Cluster Host
XXXX     1497360911 XXXXX        1 9.2.0.8.0 NO   XXXXX
       Snap Id   Snap Time   Sessions Curs/Sess Comment
Begin Snap:   89346 23-Sep-09 08:00:02   638   13.0
End Snap:   89365 23-Sep-09 20:00:05   710   19.1
Elapsed:       720.05 (mins)
Cache Sizes (end)
~~~~~~~~~~~~~~~~~
        Buffer Cache:   3,072M   Std Block Size:     8K
      Shared Pool Size:   2,048M     Log Buffer:   2,000K
Load Profile
~~~~~~~~~~~~              Per Second    Per Transaction
         Redo size:      344,858.21       6,796.87
       Logical reads:      131,932.52       2,600.28
       Block changes:       2,211.70         43.59
       Physical reads:       7,457.34        146.98
      Physical writes:        236.52         4.66
         User calls:       6,197.31        122.14
           Parses:       2,236.26         44.07
        Hard parses:         20.63         0.41
           Sorts:        330.72         6.52
           Logons:         0.34         0.01
          Executes:       3,097.97         61.06
        Transactions:         50.74
% Blocks changed per Read: 1.68 Recursive Call %:   35.95
Rollback per transaction %: 30.58    Rows per Sort:   31.38
Instance Efficiency Percentages (Target 100%)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
      Buffer Nowait %: 99.97    Redo NoWait %: 100.00
      Buffer Hit %: 94.37 In-memory Sort %: 100.00
      Library Hit %: 99.63    Soft Parse %:   99.08
     Execute to Parse %: 27.82     Latch Hit %:   99.83
Parse CPU to Parse Elapsd %: 30.18   % Non-Parse CPU:   95.65
Shared Pool Statistics    Begin End
       Memory Usage %: 100.00 100.00
% SQL with executions>1: 38.24 35.74
% Memory for SQL w/exec>1: 76.94 86.29
Top 5 Timed Events
~~~~~~~~~~~~~~~~~~                           % Total
Event                        Waits Time (s) Ela Time
CPU time                           109,020 32.54
db file sequential read            40,144,341   96,883 28.91
db file scattered read             26,524,497   66,948 19.98
sbtwrite2                    4,141,351   23,994   7.16
SQL*Net message from dblink          33,497,630   17,097   5.10
     -------------------------------------------------------------

Rollback on transaction failes

Hi,
I have got a problem when I try to rollback a transaction using a JDBC driver, but I don't understand why. Maybe someone can help me.
My problem is as follows:
on a connection with AutoCommit set to true, I define some INSERT actions on a certain table. Hereafter I do a commitTransaction(). This generates a SQLException, which I catch. In this catch I do a connection.rollback(). This results in the following error:
[SQLServer JDBC Driver]Not in local manual transaction mode
Does anyone know what this means and what causes this?
Regards,
Onno Kievit

Hi Onno,
If you have enabled "auto commit", then you cannot call methods like "commit()" or "rollback()". After you have executed your INSERT, a "commit" automatically happens -- if the INSERT succeeds -- or a "rollback" automatically happens (if the INSERT fails). You are calling the "commit()" method when there is no open transaction -- which is wrong and therefore you get an error (SQLException).
Same problem occurs when you catch the error caused by your "commit" and try to "rollback" -- you cannot "rollback" when there is no open transaction.
As I see it, you have two choices:
1. disable auto commit, or
2. remove the calls to "commit()" and "rollback()"
Hope this helps you.
Good Luck,
Avi.

Difference between Transaction.rollback() and Transaction.setRollBackOnly()

Hi,
I wanted to know the difference between what typical implementations of Transaction.rollback() and Transaction.setRollbackOnly().
I have used setRollbackOnly()? in distributed transaction scenarios. How is it different from rollback()?
Thanks
Shailesh

I would really recommend posting this question in a forum where somebody might understand what you are talking about. This is the XML forum.

Rollback per transaction too high

Hi, I am investigating performance problems on our database which is used by a third party application.
Using the stats' pack I have established that the
Rollback per transaction % is very high (between 60-70%).
I am on version 8.17 or Oracle, the application is written in powerbuilder. And it users lots of sessions per user.
A typical user users 5-7 sessions .
How can i find what is causing all this rollback?
could it be related to all these sessions ?

Hi,
The Rollback Per Transaction statistic will report on all statements that were rolled back, regardless of whether there is anything to rollback or not.
You can see more information about statspack report into metlink note 228913.1 - Systemwide Tuning using STATSPACK Reports
Nicolas.

Java.sql.SQLException: Cannot rollback a transactional connection

Hi
This is what i am trying to do:
try{
conn = getConnection();
conn.setAutoCommit(false);
execQuery(sql_1);
execQuery(sql_2);
conn.commit();
}catch(Exception ex){
conn.rollback();
i have made an error in sql_2 so i get an Exception. My queries use the same "conn" so the rollback should applay to the first query but it has made a commit. How do i get rollback to work?
I read this in an other topic:
Make sure that you configure your database connection in the jboss.jcml and not in the bean (or servlet) itself.
Then, make a lookup via jndi. On this way, the driver gets bound to the transactionManager and the rollback() works finde.
But i don�t know how to configure the connections, and how does the trasactionManager work.
Can some one help me?

Maybe i should ad that i am using Oracle db an the
code is in a Entity BeanThis changes the way you want to do rollbacks. Rollbacks in ejbs are handled by the container. In order to do rollbacks, you need to flag the transaction as to be rolled back. To do this, you need to call the method setRollbackOnly() in the ejb's SessionContext - sessionContext.setRollbackOnly();
For this to work correctly, you must declare the method in the ejb's deployment descriptor as requiring to handle transactions by specifying the appropriate value for the <tran-attribute> element of you ejb's dd.
BTW, you'd be better off posting EJB related question in the J2EE SDK forum.

How to rollback previous transaction in a series of Adapters in BPEL

in Bpel process we integrate 3 db adapters,
2 adapters are successfully complted,3rd adpter failed.
inthis situation how we rollback the 3 adapter transaction with out using of compensate handling

hey,i have made the code plz chk it and do rep soon as ma project sbmission date is very near =((
i am snaping an image from the web cam then comparing it with the red colored jpg image made in paint.
the jpg image is converted to give input image to imaq match vi.but after the comparison it gives the same output.
on the front pannel the snapped image is displayed,the red colored image that is converted in to its respective pixels is displayed and the image that is obtained after cheking the image in the draw fails vi...the pic converted to pixels is all the time displayed.and the pass/fail icon always denotes one pass led on..plz chk the code =((.
also can u provide me some guide line for using thr hough transform for the red color detection in lab view..i dont have to import the matlab code..i have to purely make it using the lb view libraries.
also one more request pl rep me regularly as i really need your golden piece of advice for ma success.
thnx
Attachments:
picture to image(BY ME).vi ‏102 KB
untitled.JPG ‏3 KB

Needed to ROLLBACK failed Transaction

Hi Oracle Expertz,
QRY will Look Like
BEGIN
INSERT into tab3 RETURNING INTO v_exer_num
UPDATE tab1
SET col1 = ''
WHERE exer_num = v_exer_num
UPDATE tab2
SET col1 = ''
WHERE exer_num = v_exer_num
END ;
Example :
1st record:
Participant A
Exer 1 Success
Exer 2 Success
2nd record
Participant B
Exer 1 Failed due to dead lock or some other exception.
3rd Record
Participant C
Exer 1 Success
Now in this transaction, I need to only rollback for Participant B ( failed Record) . Participants A and C should have committed the transaction. Can any one suggest me on this?
Possiblities Of Exception :
successful of INSERT , UPDATE , UPDATE will be considered as a completed tranasaction.
For a particular record ( exer_num) , If insertion is executed successfully ,and updates failed for the corresponding exernum , I need to rollback the inserted record .
Regards,
Maran
Edited by: Maran on Aug 6, 2009 1:17 PM

Hey Sven ,
thanks for your response. No these three DML statements would be executed inside my procedure. We can not run it in different session. the reason is
as i said, completion of these 3 DML statements , then only will conisdered as a successful transaction else i need to roll back .
also this will be called in a Batch JOB. we have a commit for whole transaction.
Lets these are all the possibilites :
1) INSERT FAILED ( ROW 1 )
2) INSERT SUCCESS (ROW 2 )
1st UPDATE Failed
3) INSERT SUCCESS ( ROW 3 )
1st UPDATE SUCCESS
2nd UPDATE D FAILED
4) INSERT SUCCESS ( ROW 4)
UPDATE SUCCESS
UPDATE SUCCESS
Now for these scenario none of three statements got executed successfully . So if it fail between any of the statements , I need to rollback that particular row.
Hope you understand the problem well now.
Now can anyone suggest me that How can i handle this exception and need to keep going my transaction even if it fails in between.
Objective over this problem is :
Need to rollback Failed rows.
Need to keep continue the Program , need to commit successful rows.
Regards,
MARAN
Edited by: Maran on Aug 10, 2009 6:19 PM

How to commit/rollback a transaction encompasing multiple EJBs

I have 2 Stateless Session Beans 'RulesManager' and 'BankManager'. Each EJB method in them gets a connection, perform the task, close the connection and return the results.
Now in RulesManager I have an EJB method processRules(). And in BankManager I have an EJB method updateTransactions().
I have a requirement that means I first have to call BankManager's updateTransactions() method; if successful then call RulesManager's processRules() method. IF its successfull as well then commit else rollback.
I dont know how to do this. Can anybody help me in this regard?
Thanks

Thanks kdgregory. This is how the things work out in our application.
I have a class BankDelegate which has each public method in BankManager SSB without the throws clause. Inside each method I get remote interface of BankManager SSB and then calls the corresponding EJB method.
Similarly I have a RulesDelegate class which has each public method in RulesManager SSB without the throws clause. Inside each method I get remote interface of RulesManager SSB and then calls the corresponding EJB method.
User press Update button on JSP which submits the form to another JSP. That JSP creates an instance of BankDelegate and call its updateTransactions() method.
Each EJB method is using container managed transactions. Inside each EJB method, if anything failed then i issued a rollback using this._sessionContext.setRollbackOnly();
I am using MS SQL Server 2000.
Thanks

Rollback CMP Transaction

Hi
I am checking for one object and if that is null i want to throw Application exception from my EJB. Now if i thorw application exception container does not rollback the data. We need to set ctx.setRollbackOnly.
say i have method
public void setData(ValueObject MyVO)
if(MyVO!=null)
// do something
else
ctx.setRollbackOnly()
throw new myexception("Null obj VO");
am i on the right track. I beleive this will allow me to throw application exception as well as rollback the transcation.
I am using weblogic 7.0 with ejb2.0 and CMR relations. All my transactions attributes are set to Required
Pranav

Hey thanks for your input.
But just a quick question for you.
Can i create a application exception extends EJBException
so that now when i thorw MyExp it will not have to call ctx.setRollbackOnly.
Like this
TestEJB.java
public void setData(MyVO vo)
if(vo==null)
thorw new MyExp("Cannot be null");
in this even if i dont call rollback on context still it will rollback cos now my exception is child of ejbexception(system exception)
am i right
which is the best way to do though.
This one or one which i asked as first quesrtion
thanks
pranav

Internal JTA transaction rollback errors

Hello,
I seem to be having an issue where WLS 9.1 is swallowing JTA errors. Our application is using container-managed transactions to perform some database and JMS work inside various MDBs. We are running in a cluster with two managed servers, and we are using the Microsoft SQL Server 2005 Beta 2 JDBC drivers. We have been running the application in development for quite a while and we thought it was working fine, with the exception of an occasional message that reaches its redelivery limit due to database locking issues. However, I was just digging around in our server logs for information related to a different problem and I noticed that the error message below is littered throughout our logs on a fairly regular basis. What does this error mean, and how can it be resolved? Are we losing data and/or JMS messages without knowing it?
Regards,
Sabrina
<Feb 6, 2006 8:46:50 AM EST> <Notice> <EJB> <BEA-010017> <Exception occurred during rollback of transaction Xid=BEA1-61E52279C065F462EB9B(12892320),Status=Rolled back. [Reason=weblogic.transaction.internal.AppSetRollbackOnlyException],HeuristicErrorCode=XA_HEURHAZ,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=3,seconds left=60,XAServerResourceInfo[WLStore_our_domain_our_filestore]=(ServerResourceInfo[WLStore_our_domain_our_filestore]=(state=new,assigned=none),xar=null,re-Registered = false),XAServerResourceInfo[OurXADataSource]=(ServerResourceInfo[OurXADataSource]=(state=rolledback,assigned=managed_server_2),xar=OurXADataSource,re-Registered = true),SCInfo[our_domain+managed_server_2]=(state=rolledback),SCInfo[our_domain+managed_server_1]=(state=rolledback),properties=({}),local properties=({weblogic.jdbc.jta.OurXADataSource=[ No XAConnection is attached to this TxInfo ]}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=managed_server_2+ouripaddress:8002+our_domain+t3+, XAResources={SecondXADataSource, ThirdXADataSource},NonXAResources={})],CoordinatorURL=managed_server_1+ouripaddress:8001+our_domain+t3+): javax.transaction.SystemException: Heuristic hazard: (OurXADataSource, HeuristicHazard, (javax.transaction.xa.XAException: java.sql.SQLException: ROLLBACK:Status:0 msg:*** SQLJDBC_XA DTC_ERROR Context: xa_rollback, state=1, StatusCode:-4 (0xFFFFFFFC) ***))
     at weblogic.transaction.internal.ServerTransactionImpl.internalRollback(ServerTransactionImpl.java:405)
     at weblogic.transaction.internal.ServerTransactionImpl.rollback(ServerTransactionImpl.java:371)
     at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:485)
     at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:332)
     at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:289)
     at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:3824)
     at weblogic.jms.client.JMSSession.execute(JMSSession.java:3786)
     at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:4228)
     at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
.>

Thanks so much for your response, Joe. Here is a detailed stack trace from one of these occurrences since I turned on the debug flags. If you'd still like me to post our config.xml, let me know - I thought I'd post this much to begin with since it's pretty lengthy.
Regards,
Sabrina
####<Feb 7, 2006 12:04:46 PM EST> <Debug> <JTAXA> <machine-name> <managed_server_2> <[ACTIVE] ExecuteThread: '46' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-0ED82BD605F5F462EB9B> <> <1139331886688> <000000> <ResourceDescriptor[OurXADataSource]: getOrCreate gets rd: name = OurXADataSource
resourceType = 2
registered = true
scUrls = managed_server_2+ouripaddress:8002+our_domain+t3+
xar = OurXADataSource
healthy = true
lastAliveTimeMillis = 1139331886656
numActiveRequests = 0
>
####<Feb 7, 2006 12:04:46 PM EST> <Debug> <JTAXA> <machine-name> <managed_server_2> <[ACTIVE] ExecuteThread: '46' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-0ED82BD605F5F462EB9B> <> <1139331886688> <000000> <BEA1-0ED82BD605F5F462EB9B: null: XA.start(rm=OurXADataSource, xar=OurXADataSource, flags=TMNOFLAGS)>
####<Feb 7, 2006 12:04:46 PM EST> <Debug> <JTAXA> <machine-name> <managed_server_2> <[ACTIVE] ExecuteThread: '46' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-0ED82BD605F5F462EB9B> <> <1139331886688> <000000> <Resource 'OurXADataSource' setTransactionTimeout(120) not called. callSetTransactionTimeout=false, supportsSetTransactionTimeout=true>
####<Feb 7, 2006 12:04:46 PM EST> <Debug> <JTAXA> <machine-name> <managed_server_2> <[ACTIVE] ExecuteThread: '46' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1139331886688> <000000> <startResourceUse, Number of active requests:3, last alive time:32 ms ago.>
####<Feb 7, 2006 12:04:46 PM EST> <Debug> <JTAXA> <machine-name> <managed_server_2> <[ACTIVE] ExecuteThread: '46' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-0ED82BD605F5F462EB9B> <> <1139331886688> <000000> <BEA1-0ED82BD605F5F462EB9B: null: XA.start DONE (rm=OurXADataSource, xar=OurXADataSource>
####<Feb 7, 2006 12:04:46 PM EST> <Debug> <JTAXA> <machine-name> <managed_server_2> <[ACTIVE] ExecuteThread: '46' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-0ED82BD605F5F462EB9B> <> <1139331886688> <000000> <endResourceUse, Number of active requests:0>
####<Feb 7, 2006 12:04:48 PM EST> <Debug> <JTAXA> <machine-name> <managed_server_2> <[ACTIVE] ExecuteThread: '46' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1139331888391> <000000> <BEA1-0ED82BD605F5F462EB9B: null: XA.end(rm=OurXADataSource, xar=OurXADataSource, flags=TMFAIL)>
####<Feb 7, 2006 12:04:48 PM EST> <Debug> <JTAXA> <machine-name> <managed_server_2> <[ACTIVE] ExecuteThread: '46' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1139331888391> <000000> <startResourceUse, Number of active requests:1, last alive time:0 ms ago.>
####<Feb 7, 2006 12:04:48 PM EST> <Debug> <JTAXA> <machine-name> <managed_server_2> <[ACTIVE] ExecuteThread: '46' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-0ED82BD605F5F462EB9B> <> <1139331888391> <000000> <XA.end DONE (rm=OurXADataSource, xar=OurXADataSource>
####<Feb 7, 2006 12:04:48 PM EST> <Debug> <JTAXA> <machine-name> <managed_server_2> <[ACTIVE] ExecuteThread: '46' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-0ED82BD605F5F462EB9B> <> <1139331888391> <000000> <endResourceUse, Number of active requests:0>
####<Feb 7, 2006 12:04:48 PM EST> <Debug> <JTAXA> <machine-name> <managed_server_2> <[ACTIVE] ExecuteThread: '46' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1139331888391> <000000> <BEA1-0ED82BD605F5F462EB9B: null: XAResource[OurXADataSource].rollback()>
####<Feb 7, 2006 12:04:48 PM EST> <Debug> <JTAXA> <machine-name> <managed_server_2> <[ACTIVE] ExecuteThread: '46' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1139331888391> <000000> <startResourceUse, Number of active requests:1, last alive time:0 ms ago.>
####<Feb 7, 2006 12:04:48 PM EST> <Debug> <JTAXA> <machine-name> <managed_server_2> <[ACTIVE] ExecuteThread: '46' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-0ED82BD605F5F462EB9B> <> <1139331888391> <000000> <BEA1-0ED82BD605F5F462EB9B: null: XAResource[OurXADataSource].rollback: FAILED , error code: XA_OK, message: java.sql.SQLException: ROLLBACK:Status:0 msg:*** SQLJDBC_XA DTC_ERROR Context: xa_rollback, state=1, StatusCode:-4 (0xFFFFFFFC) ***
javax.transaction.xa.XAException: java.sql.SQLException: ROLLBACK:Status:0 msg:*** SQLJDBC_XA DTC_ERROR Context: xa_rollback, state=1, StatusCode:-4 (0xFFFFFFFC) ***
     at com.microsoft.sqlserver.jdbc.SQLServerXAResource.rollback(Ljavax.transaction.xa.Xid;)V(Unknown Source)
     at weblogic.jdbc.jta.DataSource.rollback(DataSource.java:1005)
     at weblogic.transaction.internal.XAServerResourceInfo.rollback(XAServerResourceInfo.java:1378)
     at weblogic.transaction.internal.XAServerResourceInfo.rollback(XAServerResourceInfo.java:727)
     at weblogic.transaction.internal.ServerSCInfo.startRollback(ServerSCInfo.java:740)
     at weblogic.transaction.internal.ServerTransactionImpl.localRollback(ServerTransactionImpl.java:2013)
     at weblogic.transaction.internal.ServerTransactionImpl.globalRollback(ServerTransactionImpl.java:2721)
     at weblogic.transaction.internal.ServerTransactionImpl.internalRollback(ServerTransactionImpl.java:392)
     at weblogic.transaction.internal.ServerTransactionImpl.rollback(ServerTransactionImpl.java:371)
     at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:485)
     at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:332)
     at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:289)
     at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:3824)
     at weblogic.jms.client.JMSSession.execute(JMSSession.java:3786)
     at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:4228)
     at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
>
####<Feb 7, 2006 12:04:48 PM EST> <Debug> <JTAXA> <machine-name> <managed_server_2> <[ACTIVE] ExecuteThread: '46' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-0ED82BD605F5F462EB9B> <> <1139331888391> <000000> <endResourceUse, Number of active requests:0>
####<Feb 7, 2006 12:04:48 PM EST> <Error> <JTA> <machine-name> <managed_server_2> <[ACTIVE] ExecuteThread: '46' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-0ED82BD605F5F462EB9B> <> <1139331888391> <BEA-110412> <Xid=BEA1-0ED82BD605F5F462EB9B(15099934),Status=Rolled back. [Reason=weblogic.transaction.internal.AppSetRollbackOnlyException],HeuristicErrorCode=XA_HEURHAZ,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=1,seconds left=60,activeThread=Thread[[ACTIVE] ExecuteThread: '46' for queue: 'weblogic.kernel.Default (self-tuning)',5,Pooled Threads],XAServerResourceInfo[WLStore_our_domain_our_filestore]=(ServerResourceInfo[WLStore_our_domain_our_filestore]=(state=new,assigned=none),xar=null,re-Registered = false),XAServerResourceInfo[OurXADataSource]=(ServerResourceInfo[OurXADataSource]=(state=rolledback,assigned=managed_server_2),xar=OurXADataSource,re-Registered = false),SCInfo[our_domain+managed_server_2]=(state=rolledback),SCInfo[our_domain+managed_server_1]=(state=rolledback),properties=({}),local properties=({weblogic.jdbc.jta.OurXADataSource=[ No XAConnection is attached to this TxInfo ]}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=managed_server_2+ouripaddress:8002+our_domain+t3+, XAResources={ThirdXADataSource, SecondXADataSource},NonXAResources={})],CoordinatorURL=managed_server_1+ouripaddress:8001+our_domain+t3+) completed heuristically: (OurXADataSource, HeuristicHazard, (javax.transaction.xa.XAException: java.sql.SQLException: ROLLBACK:Status:0 msg:*** SQLJDBC_XA DTC_ERROR Context: xa_rollback, state=1, StatusCode:-4 (0xFFFFFFFC) ***)) >
####<Feb 7, 2006 12:04:48 PM EST> <Notice> <EJB> <machine-name> <managed_server_2> <[ACTIVE] ExecuteThread: '46' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1139331888453> <BEA-010017> <Exception occurred during rollback of transaction Xid=BEA1-0ED82BD605F5F462EB9B(15099934),Status=Rolled back. [Reason=weblogic.transaction.internal.AppSetRollbackOnlyException],HeuristicErrorCode=XA_HEURHAZ,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=1,seconds left=60,XAServerResourceInfo[WLStore_our_domain_our_filestore]=(ServerResourceInfo[WLStore_our_domain_our_filestore]=(state=new,assigned=none),xar=null,re-Registered = false),XAServerResourceInfo[OurXADataSource]=(ServerResourceInfo[OurXADataSource]=(state=rolledback,assigned=managed_server_2),xar=OurXADataSource,re-Registered = false),SCInfo[our_domain+managed_server_2]=(state=rolledback),SCInfo[our_domain+managed_server_1]=(state=rolledback),properties=({}),local properties=({weblogic.jdbc.jta.OurXADataSource=[ No XAConnection is attached to this TxInfo ]}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=managed_server_2+ouripaddress:8002+our_domain+t3+, XAResources={ThirdXADataSource, SecondXADataSource},NonXAResources={})],CoordinatorURL=managed_server_1+ouripaddress:8001+our_domain+t3+): javax.transaction.SystemException: Heuristic hazard: (OurXADataSource, HeuristicHazard, (javax.transaction.xa.XAException: java.sql.SQLException: ROLLBACK:Status:0 msg:*** SQLJDBC_XA DTC_ERROR Context: xa_rollback, state=1, StatusCode:-4 (0xFFFFFFFC) ***))
     at weblogic.transaction.internal.ServerTransactionImpl.internalRollback(ServerTransactionImpl.java:405)
     at weblogic.transaction.internal.ServerTransactionImpl.rollback(ServerTransactionImpl.java:371)
     at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:485)
     at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:332)
     at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:289)
     at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:3824)
     at weblogic.jms.client.JMSSession.execute(JMSSession.java:3786)
     at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:4228)
     at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
.>
####<Feb 7, 2006 12:04:48 PM EST> <Info> <EJB> <machine-name> <managed_server_2> <[ACTIVE] ExecuteThread: '46' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1139331888516> <BEA-010213> <Message-Driven EJB: OurMDB's transaction was rolledback. The transaction details are: Xid=BEA1-0ED82BD605F5F462EB9B(15099934),Status=Rolled back. [Reason=weblogic.transaction.internal.AppSetRollbackOnlyException],HeuristicErrorCode=XA_HEURHAZ,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=1,seconds left=60,XAServerResourceInfo[WLStore_our_domain_our_filestore]=(ServerResourceInfo[WLStore_our_domain_our_filestore]=(state=new,assigned=none),xar=null,re-Registered = false),XAServerResourceInfo[OurXADataSource]=(ServerResourceInfo[OurXADataSource]=(state=rolledback,assigned=managed_server_2),xar=OurXADataSource,re-Registered = false),SCInfo[our_domain+managed_server_2]=(state=rolledback),SCInfo[our_domain+managed_server_1]=(state=rolledback),properties=({}),local properties=({weblogic.jdbc.jta.OurXADataSource=[ No XAConnection is attached to this TxInfo ]}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=managed_server_2+ouripaddress:8002+our_domain+t3+, XAResources={ThirdXADataSource, SecondXADataSource},NonXAResources={})],CoordinatorURL=managed_server_1+ouripaddress:8001+our_domain+t3+).>
####<Feb 7, 2006 12:04:48 PM EST> <Error> <JDBC> <machine-name> <managed_server_2> <[ACTIVE] ExecuteThread: '46' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-0EEC2BD605F5F462EB9B> <> <1139331888594> <BEA-001112> <Test "select count(*) from DUAL" set up for pool "OurXADataSource" failed with exception: "com.microsoft.sqlserver.jdbc.SQLServerException: Connection is Closed".>
####<Feb 7, 2006 12:04:48 PM EST> <Info> <JDBC> <machine-name> <managed_server_2> <[ACTIVE] ExecuteThread: '46' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-0EEC2BD605F5F462EB9B> <> <1139331888594> <BEA-001128> <Connection for pool "OurXADataSource" closed.>
####<Feb 7, 2006 12:04:48 PM EST> <Debug> <JTAXA> <machine-name> <managed_server_2> <[ACTIVE] ExecuteThread: '46' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-0EEC2BD605F5F462EB9B> <> <1139331888594> <000000> <java.lang.Exception: DEBUG: unregister
     at weblogic.transaction.internal.TxDebug.debugStack(TxDebug.java:60)
     at weblogic.transaction.internal.XAResourceDescriptor.unregister(XAResourceDescriptor.java:764)
     at weblogic.transaction.internal.ResourceDescriptor.unregister(ResourceDescriptor.java:335)
     at weblogic.transaction.internal.ResourceDescriptor.unregister(ResourceDescriptor.java:297)
     at weblogic.transaction.internal.ServerTransactionManagerImpl.unregisterResource(ServerTransactionManagerImpl.java:684)
     at weblogic.jdbc.common.internal.XAConnectionEnvFactory.refreshResource(XAConnectionEnvFactory.java:222)
     at weblogic.jdbc.common.internal.XAConnectionEnvFactory.refreshResource(XAConnectionEnvFactory.java:173)
     at weblogic.common.resourcepool.ResourcePoolImpl.refreshResource(ResourcePoolImpl.java:1554)
     at weblogic.common.resourcepool.ResourcePoolImpl.checkResource(ResourcePoolImpl.java:1462)
     at weblogic.common.resourcepool.ResourcePoolImpl.checkAndReturnResource(ResourcePoolImpl.java:1373)
     at weblogic.common.resourcepool.ResourcePoolImpl.checkAndReturnResource(ResourcePoolImpl.java:1363)
     at weblogic.common.resourcepool.ResourcePoolImpl.reserveResourceInternal(ResourcePoolImpl.java:323)
     at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:295)
     at weblogic.jdbc.common.internal.ConnectionPool.reserve(ConnectionPool.java:457)
     at weblogic.jdbc.common.internal.ConnectionPool.reserve(ConnectionPool.java:346)
     at weblogic.jdbc.common.internal.ConnectionPoolManager.reserve(ConnectionPoolManager.java:83)
     at weblogic.jdbc.jta.DataSource.getXAConnectionFromPool(DataSource.java:1438)
     at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1256)
     at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:462)
     at weblogic.jdbc.jta.DataSource.connect(DataSource.java:392)
     at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:359)
     at ourpackage.OurDataSourceUtil.openConnection(OurDataSourceUtil.java:125)
     at ourpackage.OurMDB.onMessage(OurMDB.java:171)
     at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:426)
     at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:332)
     at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:289)
     at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:3824)
     at weblogic.jms.client.JMSSession.execute(JMSSession.java:3786)
     at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:4228)
     at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
>

Rollback a transaction

Similar Messages

Maybe you are looking for