SetAutoCommit(false) is still committing

Hello, I am calling a CallableStatement on an Oracle DB using JDBC connectivity by doing the following:
Connection conn = DatabaseConnectionUtil.getConnection();
try {
logger.debug("Turning off auto commit");
conn.setAutoCommit(false);
catch (SQLException sqle) {
logger.error("Failed to set autocommit to false on Connection object");
logger.error(sqle);
qo.prepareCallableStatement(conn, proc);
qo.executeStatement();
conn.close();
Notice I am issuing no commits anywhere because I am just trying to test this out. However, my transactions are being committed somehow. There are no commits issued in my called package either. Is there some other setting I need to check? Is a commit done when I issue conn.close()?

Nothing to do with setAutoCommit.
Oracle (and some other databases) will commit on connection close; this and the contrary behaviour (rollback) are both permitted by the JDBC standard.
You can see this in SQL*Plus too. Do an insert/update/delete, then use the "EXIT" or "DISCONNECT" commands to normally terminate your session. Connect again and you will see the changes have been committed. However, Oracle will roll back if the connection is "broken", either in SQL*Plus or in JDBC.

Similar Messages

JDBC connection.setAutoCommit(false) commits after each update????

The problem is on AUTO COMMIT of JDBC connection.
What I did was:
conn.setAutoCommit(false);
conn.executeUpdate( mySQLStatement );
conn.rollback();
The expected result to the database table
should be: NOTHING UPDATED.
But what actually happened was: the updates
went into the database.
So the setAutoCommit(false) didn't work
as expected.
BTW, I am using Oracle 8.1.7 and the Oracle
thin JDBC driver.
Any help or hint will be appreciated.
Thanks.
Chenglin

Chenglin,
I ran the below java class on our SUN [sparc] Solaris 7 computer with J2SE 1.4.2_02, Oracle 8i (8.1.7.4) database and the "classes12.zip" file that comes with the database distribution. I checked the column value -- using SQL*Plus -- before and after running the java class, and the value was the same.
import java.sql.Connection;
import java.sql.DriverManager;
import java.sql.Statement;
public class JdbcTes2 {
public static void main(String[] args) {
    final String SQL = "update "              +
                          "TABLE "            +
                       "set "                 +
                          "COLUMN = 'Value' " +
                       "where "               +
                          "PRIMARY_KEY = 'key'";
    Connection dbConn = null;
    Statement stmt = null;
    String line = null;
    String url = "???";
    try {
      Class.forName("oracle.jdbc.driver.OracleDriver");
      dbConn = DriverManager.getConnection(url);
      dbConn.setAutoCommit(false);
      stmt = dbConn.createStatement();
      stmt.executeUpdate(SQL);
      dbConn.rollback();
    catch (Exception x) {
      System.err.println("Exception caught: " + x);
      x.printStackTrace();
    finally {
      if (stmt != null) {
        try {
          stmt.close();
        catch (Exception x) {
          System.err.println("Failed to close statement.");
          x.printStackTrace();
      if (dbConn != null) {
        try {
          dbConn.close();
        catch (Exception x) {
          System.err.println("Failed to close DB connection.");
          x.printStackTrace();
}Good Luck,
Avi.

Oracle 8i setAutoCommit(false) is ignored

When getting a Connection object from the Oracle 8i driver manager, I call conn.setAutoCommit(false). That should mean that if I don't explicitly call conn.commit() at the end of my INSERT/DELETE/UPDATE and before conn.close(), then the default behaviour should be for changes to be rolled back - right ? It certainly works that way with DB2.
However, I realised yesterday that I'd been forgetting to put the call to conn.commit() in my code. Regardless of this, data was still being committed. I'm confused...
I've heard tell that it is possible for an Oracle database instance to exhibit behaviour whereby data is automatically committed when a connection is closed and that, in effect, this overrides any call to setAutoCommit(false) from JDBC. I've put this question to my DBA, but am still awaiting a reply.
In the meantime, does any Oracle JDBC guru out there know why this might be happening ? I'm not messing around with transaction isolation levels.

I also found this particularly interesting (again from the Oracle JDBC manual), and probably still on the topic.
Close the Result Set and Statement Objects
You must explicitly close the ResultSet and Statement objects after you finish using them. This applies to all ResultSet and Statement objects you create when using the Oracle JDBC drivers. The drivers do not have finalizer methods; cleanup routines are performed by the close() method of the ResultSet and Statement classes. If you do not explicitly close your ResultSet and Statement objects, serious memory leaks could occur. You could also run out of cursors in the database. Closing a result set or statement releases the corresponding cursor in the database.
For example, if your ResultSet object is rset and your Statement object is stmt, close the result set and statement with these lines:
rset.close();
stmt.close();
When you close a Statement object that a given Connection object creates, the connection itself remains open.
------------------------------------------------------------------------Note:
Typically, you should put close() statements in a finally clause.

Perform transaction in creator [SetAutocommit(false) and commit()]

Hi,
I've finished one application with the Sun Java Studio Creator 2 but I've 2 technicals problems. One problem is about manage transactions.
In a validate button, I've to perform update with 2 tables for example (orders and orders_details).
My code:
ordersDataProvider.getCachedRowSet().acceptChanges();
orders_detailsDataProvider.getCachedRowSet().acceptChanges();
It works but when I've an error in the 'orders_detailsDataProvider.getCachedRowSet().acceptChanges();', the orders's changes into the database are not rollback.
I try the following:
try{
Context ctx=new InitialContext();
DataSource ds=(DataSource)ctx.lookup("java:comp/env/jdbc/moduleachat");
//Get a connection
conn=ds.getConnection();
/* Begin the transaction */
conn.setAutoCommit(false);
//update orders
ordersDataProvider.getCachedRowSet().acceptChanges();
//update order details
orders_detailsDataProvider.getCachedRowSet().acceptChanges();
/* Commit transaction */
conn.commit();
return "confirmPage";
}catch(Exception ex){
log(ex.getMessage(), ex);
//Rollback transaction
try{
conn.rollback();
}catch(SQLException esql){
log(esql.getMessage(), esql);
return null;
it doesn't work. When errors occurs in the orders_details's update, the orders's update is not still rollback. it seems like the connection I get is not in the same context of orders and orders details rowset context.
Can anyboby gives me a solution. It very important for a professional application

I don't understand why nobody has solutions about my problems.
To creator team:
Tell us if it's a bug or not. I've try with 'acceptchanges(Connection conn)' but it doesn't work.
Yesterday i've searched for many hours solutions on internet and I've found that others guys have the same problem and in the CachedRowSet implementation there is a property called 'COMMIT_ON_ACCEPT_CHANGE'. This property is final and set to true. i don't see where we can set it to false. So every time we call acceptchanges(connection), even if connection is in setAutoCommit ( false ), the acceptchanges commit all changes directly. Is it a bug or not? I hope no because manage transactions must be one feature of Java Studio Creator's CachedRowSet.
Thanks

Need information regarding setAutoCommit(false) in oracle otd

Hi All,
I need to insert data to two oracle tables. If data insertion to both tables are success then connection should commit else it should not commit.
Hence for this i set
1) oracleOtd.setAutoCommit(false);
The i inserted value to first table. During insertion to second table it
gave exception for me.
But when i checked database the data has been inserted to database
even though there is an exception.
I believe this oracleOtd.setAutoCommit(false) doesn't have any effect.
Please leet me know if i need to do some additional settings.
Regards
Venkatesh.S

I use this same function (using JavaCAPS 5.1.1) and, admittedly, the opportunity to "test" this hasn't come up.
However, consider putting a rollback call in your catch-block.
oracleOtd.rollback();Dave

Delete parked document still committed budget

Dear SAP-ers,
I do budget active checking with BCS, the problem is when i do deleted Parked Document using FBV0, the budget still committed. For display this, i am using the standard report painter 4FM (Budget Usage).
Anyone can help me ?
Thanks
Regard's
Silvy

HI,
Please refer the note 100409.
Reg
Madhu M

Error on setAutoCommit(false)

Hi. I'm trying to do a update in my Java Web aplication, but when I get my connection and
try to do a setAutoCommit(false) in it, I get a exception whith the message: ORA-01722: invalid number exception. The problem is this don't happens in my database, only in the database of the network where i deploy my aplication.
Maybe is a difference between the configuration of this two databases?

Hi. I'm trying to do a update in my Java Web aplication, but when I get my connection and
try to do a setAutoCommit(false) in it, I get a exception whith the message: ORA-01722: invalid number exception. The problem is this don't happens in my database, only in the database of the network where i deploy my aplication.
Maybe is a difference between the configuration of this two databases?

SetAutoCommit(false) fails

I am trying to set AutoCommit to 'false'
in a method and I get this error mesage:
[Microsoft][ODBC Microsoft Access Driver]Attribute cannot be set now
The message is very uninformative and frustrating.
Has anybody encountered this before?

This not a servlet. not EJB, just some proxy class
for convenient database access.
I am writing a method that takes a collection of SQL queries
(Strings) and executes them as a single transaction:
public String executeTransaction(Collection update_queries) throws SQLException
if (update_queries == null)
throw new SIException("null update queries collection passed to DBProxy.executeTransaction!");
synchronized(_proxy_lock)
String result = null;
Statement update_stmnt = null;
try
//Enter transaction mode
_connection.setAutoCommit(false);
update_stmnt = _connection.createStatement();
At the end of the method I would like to return to AutoCommit mode.
I'd be very grateful if you could help.
Maybe I should switch to another database provider, like PostgreSQL?

User Mapping to R/3 - admin.pwdprotection=false but still pwd field appears

 
Hello All, 
I am doing SSO using user mapping to R/3 system from Portal as the ids are different for Portal and R/3. 
I can access a transaction iview from R/3 successfully using user mapping(in SSO) but the problem is everytime a user changes his R/3 password, the mapped password is to be changed in Portal.Otherwise, unable to access transaction iview. 
1) I have changed the property ume.usermapping.admin.pwdprotection=false in configtool but still in User Admin > User mapping for system access , the password field is populated and while accessing the R/3, the password is being verified. I have seen in another system where the password field is not being asked after modifying the property to false, only id field is present. From the end user, under Personalize > User Profile > User Mapping for system, no systems are present as expected for mapping. Logon method in system is uidpw and mapping type is "Admin". 
Versions - Portal is NW7.0 SP18 and ECC is .0 EhP3. 
anybody faced the same problem? Is there a note to fix it? 
2)Also, in the User Admin > User mapping for system access , in the dropdown I can see the system aliases I have created in systems but not in System admin> sys config > Ume config > under User Mapping , I do not find any reference system. 
After first restart it was not there, after some time it has come, later it was coming as configured but invalid beside the system in braces in dropdown like abc(configured but invalid). Once I unselected, now it is no more available in dropdown. 
3) I have used diagtool to identify the problem. In the ticket, how do I see the mapped user? 
I am seeing only the following details.From the log - 
The created ticket is: 
[ [Ticket [initialized] 
Ticket Version = 0 
Ticket Codepage = (Encoding=1100) 
User = 121444 
Issuing System ID = EPD ( Portal name) 
Issuing System Client = 000 
Creation Time = 200905150649 
Valid Time = 8 h 0 min 
Signature (length=261 bytes) 
InfoUnit id=32, name=portal_user, content=portal:121444, length=16 
InfoUnit id=136, name=authscheme, content=basicauthentication, length=19 
InfoUnit id=1, length=9 
InfoUnit id=2, length=3 
InfoUnit id=3, length=3 
InfoUnit id=4, length=12 
InfoUnit id=5, length=4 
InfoUnit id=10, length=9 
]. 
Authentication stack: [ticket]. 
 
Does this have an entry for mapped user of target R/3 system also? 
If I am not finding the userid/pwd in ticket, how is SSO working? based on user mapping only? 
Thanks, 
Isvarya 

Thanks Anja for the quick response.
My primary objective is to use SSO with logon tickets to backend which is independent of user passwords.
regarding 1)
From the link -
http://help.sap.com/saphelp_nw70/helpdata/EN/f8/3b514ca29011d5bdeb006094191908/frameset.htm
Features
● Either users or administrators can perform user mapping.
¡ Users must always enter a password to validate their mapped user ID.
This password is not stored, but is used to confirm that the user is entering a user ID with which he or she has access to the ABAP-based system.
○ Administrators can enter a password to validate their entries.
The UME property ume.usermapping.admin.pwdprotection defines whether or not the administrator must enter a password. By default the administrator must enter one.
is also in the same lines.
But as per the SAP library link, I do not find a reference system because of problem 2 in the initial post.
Also, I have a screenshot of user admin where the password field itself is not present. If you can share your email id, I will send the scrnshot without pwd and mine with password.
2)I have seen this note. But, none of the 3 cases mentioned are applicable to me..user mapping is working just fine..Only reference system is not populated.
3) Becuase of 1, I was expecting to see mapped id alone or mapped id along with system name in logon tickets.
Thanks for the response.

Button.enabled = false (but still clickable?!)

Hello Dear Forum,
Got a button (imported png defined as a button in the library).
The button is dragged onto the stage, given an instance name "btn".
Clicking the button fires an eventListener which is doing all the right things, except...
btn.enabled = false;
...only changes the cursor from a pointing finger to an arrow. What?! It is still clickable.
My intention is to disable the button so it cannot be clicked. But it can still be clicked. Not good.
QUESTION: How do I disable a button and prevent it from being clicked?
Thanks for your support,
///johan
REASON: I am temporarily disabling the button so that it cannot be clicked multiple times while loading other stuff. Makes sense.

To disable the button (a homegrown SimpleButton) use its mouseEnabled property. I think enabled only applies to Button components in AS3.

Startmode=false but still not auto-deploy

Hi,
I'm running Weblogic 7.0 SP2 on Solaris 9. I have set startmode=false in startWebLogic.sh
but my applications are still not auto-deploy. My programmers have tried to modified
a class without restarting the server, but the change does not take effect. They
have tried on Windows platform and it auto-deploy. But it doesn't in Solaris platform.
Is there some configurations that I missed? Please help. Tks.

Location of JSP file -> /appl/bea/ngccs/mydomain/applications/DefaultWebApp/ngccs/test/test.jsp
Location of class file -> /appl/bea/ngccs/mydomain/applications/DefaultWebApp/WEB-INF/classes/test/test.class
I have set the startmode= and startmode=false which is in development mode.
I then access from IE to point the URL to access test.jsp and the test.class.
Then I modified test.class and uploaded again to the same class location and access
from IE again. This time the changes is not displayed, the old class was being
loaded instead of the new one.
How to use the weblogic.Deployer, wldeploy, or the console to deploy?
Rob Woollen <[email protected]> wrote:
Richard wrote:
What sort of info do you need? The server is 24X7 production but runningWeblogic
in development because we have program updates once in few days anddon't want
to restart the Weblogic each time. I have read the startmode=falsefor auto deploy
so I tried to use it. The server is running on a single Weblogic instanceonly.
As I said in my last post, the applications directory and auto-polling
is for single-server development environments only. If you're in a
production environmentm especially a 24x7 environment, you don't want
this option. I don't even believe we support it for production.
If you want to change the application while the server is running, use
weblogic.Deployer, wldeploy, or the console.
Can you explain to me exactly what type of application change you are
doing?
-- Rob
Rob Woollen <[email protected]> wrote:
First off, let me make it clear that the applications directory is
meant
for single-server development environments only. Once you move past
that into production or testing scenarios, use weblogic.Deployer, the
console, or the wldeploy ant task to deploy.
I'd need more info to diagnose your issue. Does making the exact same
change to the application work in your Windows environment?
-- Rob
Richard wrote:
Hi,
I'm running Weblogic 7.0 SP2 on Solaris 9. I have set startmode=falsein startWebLogic.sh
but my applications are still not auto-deploy. My programmers havetried to modified
a class without restarting the server, but the change does not takeeffect. They
have tried on Windows platform and it auto-deploy. But it doesn't
in
Solaris platform.
Is there some configurations that I missed? Please help. Tks.

Although browser.sessionstore.resume_from_crash = false, it still is restoring session and even session which where password protected! how to solve

In the config browser.sessionstore.resume_from_crash is set to false, However when restarting FF all sessions can be restored by pressing the button session restore on the home page.
'''It restores also password protected sessions without asking for any password! This is unacceptible!'''

See:
* http://kb.mozillazine.org/Browser.sessionstore.privacy_level
* http://kb.mozillazine.org/Session_Restore

Help me to update the table

hi all
i have a table. In my code i am doing like this
got connection and every thing need to update.
-> setAutoCommit(false)
-> updating here
-> commiting here
-> setAutoCommit(true)
->
->
-> again updating here
can i do this way

No reason why not...
Most people stick with autocommit either ON or OFF, all the time for everything, but you can certainly switch back and forth as you propose.
In general, almost all professional JDBC programming using real databases will be done with autocommit off, though there are certainly plausible exceptions and special cases.

How to setAutoCommit to false in JPA2 transactions?

I am very sorry for the multiple posting I issued, I apologized and but it didn't work apparently.
In the rolling back from a partially failed transaction acting on several entities, gimbal2 suggested turning the autoCommit off (maybe something like setAutoCommit(false)). Any idea how one does this in JPA 2 + Eclipselink + Glassfish 3.1?
Many thanks.

Your DAO layer should not really get so complicated that you can't post a SSCE that demonstrates the problem, especially if you are using JPA. You are probably already manually doing too much that should be left to JPA with the right relationships and cascade types set. I really think you should use this as a warning that there is something wrong and consider simplying things before your DAO gets too complicated for any changes to be made to it. An exception always causes the current transaction to be marked for rollback as long as it's not an application exception. Either
1.) You are using open session in view
2.) You are calling other methods that are running in their own transaction different from the calling transaction.
3.) You are manually forcing commits at some points in your code.
It is extremely unlikely that there is a bug in your container's JTA implementation that is causing this.Many thanks for your time.
To your points above.
1) Sorry, would you be more specific to what you mean?
2) I was, but then I eliminated all long-distance calls and made them all local! You will see below.
3) Yes I do, but no flushing; otherwise how would I persist?
Very well then, here is an pseude-SSCE that causes the failures I am talking about, do excuse me for being verbose (academia-inherited).
I have the following entities for a conference management system we are building. I have:
- Participant, any new user will become a participant in the system
- Referee, the new user could then assume the roles of a referee, author, attendee... or a combo
// supper class for sharing code
@MappedSuperclass
public abstract class ParentEntity implements Serializable {
 @Id
 @GeneratedValue(strategy = GenerationType.IDENTITY)
 private Integer id;
 // other objects, setters, getters...
// a participant in the system could assume several roles, a key-per-role however
@Entity
public class ZparticipantRole implements Serializable {
 @Id
 private Integer id;
@Entity
public class Participant extends ParentEntity {
 @OneToMany
 private List<ZparticipantRole> zparticipantRoles = new ArrayList<ZparticipantRole>();
 // other objects, setters, getters...
@Entity
public class Referee extends ParentEntity {
 @OneToOne
 private Participant participant = new Participant();
 // other objects, setters, getters...
Here is how persistence.xml looks, running on GF 3.1, NB 7, JPA 2, Eclipselink impl.
<?xml version="1.0" encoding="UTF-8"?>
<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="default" transaction-type="JTA">
 <jta-data-source>mysql_mecms</jta-data-source>
 <exclude-unlisted-classes>false</exclude-unlisted-classes>
 <validation-mode>NONE</validation-mode>
 <properties>
 </properties>
</persistence-unit>
</persistence>
// managed bean that fetches data from the frontend to dispatch for transaction management
@ManagedBean
@ViewScoped
public class EventRegRefereeController implements Serializable {
 @EJB
 private JPAManager jpaManager;
 // other data, setters and getters
 // method called from JSF page
 public void regAsRef() {
 boolean statusOk = true;
 try {
 // participant is already persisted, but referee is new
 jpaManager.createReferee(referee, participant);
 } catch (Exception e) {
 statusOk = false;
 // life goes on...
@Stateless
public class JPAManager implements Serializable {
 @PersistenceContext(unitName = "default")
 private EntityManager em;
 final int AUTHOR_ROLE = 1;
 final int REFEREE_ROLE = 2;
 public void createReferee(Referee referee, Participant participant) {
 referee.setParticipant(participant);
 em.persist(referee);
 ZparticipantRole refereeRole = em.getReference(ZparticipantRole.class, REFEREE_ROLE);
 participant.getZparticipantRoles().add(refereeRole);
 em.merge(participant);
 // other methods...
}So all the necessary ingredients are above. Here is what happens, and I will use code-style to preserve indentation.
1. Database empty, a new user comes so they would be registered as a participant, call them p1 with id=1
2. p1 comes back to register as referee,
 2.1 participant is fetched using "em.find()",
 2.2 new referee is created
 2.3 jpaManager is called on them (jpaManager.createReferee(referee, participant);)
 Since referee is brand new, all goes ok, call them r1 with id=1
3. There is a table called participant_zparticipantrole and it has the following entry: (Participant_ID, zparticipantRoles_ID) = (1, 2)
4. Suppose now that we execute a bad piece of code... what's better than Step 2.3 above? That is, the SAME referee on the SAME participant (just bear with me... I know that's bad and avoidable), here is what happens:
 4.1 The same referee arrives to the createReferee method, but, because the key-generation is IDENTITY, the old (id=1) is neglected and a new id=2 for the referee is created and persisted. So far, we deserve it
 4.2 The this piece is executed: participant.getZparticipantRoles().add(refereeRole)... see it? This is bad, we are putting the same record ((Participant_ID, zparticipantRoles_ID) = (1, 2)) in the same table! And it fails, rightly so.
 4.3 An exception is thrown, something like this:
Exception [EclipseLink-4002] (Eclipse Persistence Services - 2.2.0.v20110202-r8913): org.eclipse.persistence.exceptions.DatabaseException
Internal Exception: com.mysql.jdbc.exceptions.jdbc4.MySQLIntegrityConstraintViolationException: Duplicate entry '1-2' for key 1
Error Code: 1062
Call: INSERT INTO PARTICIPANT_ZPARTICIPANTROLE (zparticipantRoles_ID, Participant_ID) VALUES (?, ?)
and this statement appears in the exception:
Caused by: javax.transaction.RollbackException: Transaction marked for rollback.
...Yet, the new record inserted for the referee is never rolled back! My referee table has two entries with id=1 and id=2. This is where I was expecting a rollback. That got us worried, suppose there is a piece of a faulty logic lurking somewhere that would give way sometime due to some failure, our database is... smudged!
So?

XY Graph-Setting Y-Scale visible to False still Shows Corresponding Y scale Max and Min

Hi Guys,
I use XY graph to display the data with 3 Y-scales.
When I set any Y scale Visiblity property to False,its still display the Y scale Max and Min range Lines in plot area of the Graph and making cross line or extra parralel line with other visible scales.
Attached the screen shot for ref.
And I know the cross line may be due to different Y scales range setting.But XY graph should not display the invisible Y scales and its property as well.
please provide your suggestions to avoid that.
Solved!
Go to Solution.

The scales and the lines associated with those scales are separate properties. I have never tried it, and right now I am not at a computer, but there should be properties for setting the grid line colors. Set them to transparent.
Mike...
Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion
"... after all, He's not a tame lion..."
Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

SetAutoCommit(false) is still committing

Similar Messages

Maybe you are looking for