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?

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.

  • 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.

  • 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.

  • 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

  • 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

  • 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?

  • Disk utility false "failed" disk errors

    Hello, I'm really hoping someone can help me solve this problem.
    I have an iMac (see specs below) connected via Thunderbolt to a LaCie 2big RAID drive (with two 3TB internal Seagate drives set up as mirrored RAID slices). Both the iMac and the LaCie drive were purchased brand new in 2012 and worked flawlessly until April 2014. In April, one of the LaCie's two internal drives failed and could not be rescued using Apple's Disk Utility. Since the LaCie unit was still under warranty, LaCie replaced the affected internal drive at no cost. Since then however, Apple's Disk Utility has been giving me a "failed" disk warning on the same internal drive about once a month. The first time, LaCie simply directed me to reformat the drive and the problem went away. But the same problem has appeared roughly every month since then.
    I sent the entire unit back to LaCie for diagnosis and they told me that the drive is perfectly fine. In other words, it's a software failure, not a hardware failure. I was told that Disk Utility was giving me false errors, possibly caused by the iMac going into sleep mode and not ejecting the disk properly. They said they've seen it before, but Apple has not yet released a patch for it. Since receiving the drive back from LaCie, I've changed the iMac's energy saver settings to prevent it from going to sleep after any inactivity. However, the same drive failed again this morning.
    The only solution LaCie has given me is to wait for Apple to release a patch and in the meantime, reformat my drive whenever the "failed" warning appears to clear the problem. However, I have more than 2TB of data on this drive and the process of backing it up, reformatting the disk and copying all of my data back again typically takes more than 20 hours. I simply cannot afford to keep doing this every month. LaCie seems to have washed their hands of this and pointed their finger at Apple's Disk Utility. My questions is, has anyone else had similar problems? And if so, what is the solution?
    Hardware Specs:
    27-inch iMac, Mid 2011 (3.1 Ghz Intel Core i5, 12 GB RAM)
    LaCie 2big 6TB Thunderbolt RAID disk (set up as two 3TB mirrored RAID slices)
    Thanks,
    Mike.

    Permissions you can ignore on 10.5 and 10.6:
    http://support.apple.com/kb/TS1448?viewlocale=en_US
    Using 'should be -rw-r--r-- , they are lrw-r--r--' as an example, you will see the that the permissions are not changed, but the | indicates a different location. This is because an update to Leopard changed the location of a number of system components.
    As long as you see, "Permissions Repair Complete" when it's finished... you're done.

  • ScreenUpdating=False fails to prevent screen updating, and causes bizarre behaviour

    I have recently installed Office 2013 (MSO Standard 2013) on my (Win 7 Professional) computer.  During a brief transitional period, Office 2003 will remain on my computer.
    I had been looking forward to running the many Excel VBA applications on Excel 2013, but am not only disappointed, but alarmed.  We are significantly dependent on over 50 business applications running in Excel VBA (many of which are complex,
    and many of which I have developed), but we now find that seemingly one difference alone (though we may yet discover more) is rendering many of them virtually unusable.  That difference is the behaviour of the Application.ScreenUpdating method.
    In Excel 2003, the ScreenUpdating method behaved intuitively, predictably and reliably.  It basically does what it says - all screen updating, except for the status bar, is frozen.  To allow users to peek at any updates, one would simply
    set ScreenUpdating=True and at the appropriate point freeze updating with ScreenUpdating=False.  Now, in Excel 2013, we are instead finding behaviour which has to be described as bizarre, counterintuitive and destructive.  Essentially, what is happening
    is that whenever another worksheet is activated, ScreenUpdating=False does not prevent screen updating - and for good measure, there are a number of other unpleasant side-effects.  I have spent many long hours searching through hundreds of forum posts
    and testing workarounds - all without success.  I have seen many posts complaining about ScreenUpdating in Excel 2013, but not a single implementable solution.  Yes, I've seen the advice about replacing Select or Activate methods with objects, but
    this workaround would not only be extremely costly and impractical in our case (it would require reworking tens of thousands of lines of code and would probably take many person months of unjustifiable work), it almost certainly wouldn't work.  (You'll
    have to take my word on that.)  And all because ScreenUpdating=False doesn't really prevent screen updating any more!  I cannot accept that ScreenUpdating is working properly in Excel 2013, nor that its functionality is in any way acceptable.
    The problems are best illustrated with a simple example.  I created this example to verify that the flickering was unrelated to the complexity of the business applications I referred to above.  In this example, there is a "master"
    workbook named "ScreenUpdatingTest.xls".  This contains a single button on its only worksheet, and this button executes macro "TestScreenUpdating".  This macro turns screen updating off, then sequentially opens workbook AAA.xls,
    workbook BBB.xls and workbook CCC.xls with a 3 second interval between each workbook being opened.  After 3 more seconds, it activates workbook ScreenUpdatingTest.xls and then turns screen updating on.  Along the way, it reports these actions in
    the status bar.  One would expect that this would result in AAA, BBB and CCC being opened in the background, with the user seeing no changes on the screen apart from the status bar and the workbooks appearing in the task bar.  This is precisely what
    happens in Excel 2003.
    By contrast, Excel 2013 seems to do absolutely nothing for about 12 seconds (even the task bar and the status bar remains unchanged), then, AAA, BBB and CCC can be seen to open (in maximized windows) in rapid succession.  The only message I see in the
    status bar is the last one, "Switched back to ScreenUpdatingTest.xls."  Even more bizarrely, that there is a call to Msgbox "Hi" just before the Application.ScreenUpdating=True at the end of the subroutine - and this should be unrelated
    to which workbook the focus end up with, right?  Wrong!  If Msgbox "Hi" is commented out, the focus ends up with CCC.xls - in other words, Workbooks(ThisWorkbook.Name).Activate seems to be ignored.  But if Msgbox "Hi" is
    uncommented, the focus ends up with ScreenUpdatingTest.xls!  This is crazy, isn't it?
    Sub TestScreenUpdating()
    Application.ScreenUpdating = False
    Application.Wait Now() + TimeValue("00:00:03")
    Workbooks.Open ThisWorkbook.Path & "\AAA.xls"
    Windows("AAA.xls").Activate
    Application.StatusBar = "AAA.xls has been opened."
    'Excel 2003:
    ' I see workbook ScreenUpdatingTest.xls on the screen with no flickering.
    ' AAA.xls is open in the task bar.
    ' The message that AAA.xls has been opened appears in the status bar.
    'Excel 2013:
    ' I see workbook ScreenUpdatingTest.xls on the screen with no flickering.
    ' AAA.xls is >>>NOT<<< open in the task bar
    ' >>>NO<<< message that AAA.xls has been opened appears in the status bar.
    Application.Wait Now() + TimeValue("00:00:03")
    Workbooks.Open ThisWorkbook.Path & "\BBB.xls"
    Windows("BBB.xls").Activate
    Application.StatusBar = "BBB.xls has been opened."
    'Excel 2003:
    ' I see workbook ScreenUpdatingTest.xls on the screen with no flickering.
    ' AAA.xls and BBB.xls are open in the task bar.
    ' The message that BBB.xls has been opened appears in the status bar.
    'Excel 2013:
    ' I see workbook ScreenUpdatingTest.xls on the screen with no flickering.
    ' AAA.xls and BBB.xls are >>>NOT<<< open in the task bar.
    ' >>>NO<<< message that BBB.xls has been opened appears in the status bar.
    Application.Wait Now() + TimeValue("00:00:03")
    Workbooks.Open ThisWorkbook.Path & "\CCC.xls"
    Windows("CCC.xls").Activate
    Application.StatusBar = "CCC.xls has been opened."
    'Excel 2003:
    ' I see workbook ScreenUpdatingTest.xls on the screen with no flickering.
    ' AAA.xls, BBB.xls and CCC.xls are open in the task bar.
    ' The message that CCC.xls has been opened appears in the status bar.
    'Excel 2013:
    ' I see workbook ScreenUpdatingTest.xls on the screen with no flickering.
    ' AAA.xls, BBB.xls and CCC.xls are >>>NOT<<< open in the task bar.
    ' >>>NO<<< message that CCC.xls has been opened appears in the status bar.
    Application.Wait Now() + TimeValue("00:00:03")
    Workbooks(ThisWorkbook.Name).Activate
    Application.StatusBar = "Switched back to ScreenUpdatingTest.xls."
    MsgBox "Hi"
    Application.ScreenUpdating = True
    'Excel 2003:
    ' I see workbook ScreenUpdatingTest.xls on the screen with no flickering.
    ' AAA.xls, BBB.xls and CCC.xls are open in the task bar.
    ' The message that we have switched back to ScreenUpdatingTest.xls appears in the status bar.
    'Excel 2013:
    ' Workbooks AAA.xls, BBB.xls and CCC.xls appear in rapid succession.
    ' When execution ends:
    ' If Msgbox "Hi" is commented out, the focus is with CCC.xls.
    ' If Msgbox "Hi" is uncommented, the focus is with ScreenUpdatingTest.xls.
    ' AAA.xls, BBB.xls and CCC.xls are >>>NOT<<< open in the task bar.
    ' The message that we have switched back to ScreenUpdatingTest.xls appears in the status bar.
    End Sub
    Surely it is reasonable to expect that such functionality should remain consistent from one version to the next!  Our applications in Excel 2003 had a professional, elegant user interface, and they behaved predictably, intuitively and robustly. 
    With Excel 2013, this is utterly trashed, with flickering, unpredictable behaviour (who knows what will get the focus?) and inefficiency (things are so much slower when the screen updates).  With Office 2003 going out of support, vast numbers of people
    in my company will be moving to Excel 2013 as Excel 2003 is decommissioned.  I imagine the same will be happening in many other companies.  We now find ourselves on the cusp of being dealt us a devastating blow due to ONE DYSFUNCTIONAL METHOD, and
    we are desperate for a solution.  A solution would either have to restore the former Excel 2003 functionality of ScreenUpdating, or it would have to introduce a new method which really does turn screen updating on or off without exception.
    Please, HELP!
    -Peter

    Thanks for the input, Jim.
    I don't think the Single Document Interface is contributing to the problem.  Since installing Office 2013, Excel 2003 has also inherited a Single Document Interface - yet while it behaves like a charm, Excel 2013 behaves ineptly.
    Whatever the reasons for the problem, the fact is that this functionality is now broken - one might even say catastrophically broken - and some sort of resolution is essential.  It would be madness to allow something like this to have such a severe
    impact on business operations.
    My call for help is still out there, as loud as ever!  BTW, I can send my example files, zipped, to anyone who might like to look at them.
    Peter
    Sydney, Australia

  • 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?

  • Reconnect policy with MySQL failing because of autoCommit error

    This related to this issue, but I didn't see any responses to it: Reconnecting a dead connection from a UnitOfWork commit - Autocommit error
    I'm testing with MySQL 4.1 and I have a reconnect policy that does the following (I believe this is a pretty standard approach):
    session.setExceptionHandler( new ExceptionHandler() {
    public Object handleException(RuntimeException exception) {
         if (exception instanceof DatabaseException) {          
    dbex.getAccessor().reestablishConnection(dbex.getSession());
    However, when it reestablishes the connection (and I have traced this and can verify that this code is executing and a reconnect is performed), I get the following error for any updates:
    Internal Exception: java.sql.SQLException: Can't call rollback when autocommit=trueError Code: 0
    at oracle.toplink.exceptions.DatabaseException.sqlException(DatabaseException.java:277)
    at oracle.toplink.internal.databaseaccess.DatabaseAccessor.basicRollbackTransaction(DatabaseAccessor.java:1090)
    at oracle.toplink.internal.databaseaccess.DatasourceAccessor.rollbackTransaction(DatasourceAccessor.java:486)
    at oracle.toplink.internal.databaseaccess.DatabaseAccessor.rollbackTransaction(DatabaseAccessor.java:1075)
    at oracle.toplink.publicinterface.Session.basicRollbackTransaction(Session.java:377)
    I only have this problem with the MySQL JDBC drivers. I can continue to read normally, but I can't perform any transactions.
    This isn't so much of a question about MySQL specifically, but rather a question about how reestablishConnection() connects to the database differently from my initial login using DatabaseLogin. Obviously, I don't have this error connecting normally. I only get it after a reconnect is applied.
    Specific questions are: Is there another handler I can add to ensure JDBC Connections returned by ServerSession are always setAutoCommit(false)? Am I reestablishing the JDBC connections incorrectly?
    Nate

    Nate,
    This does appear to be MySQL JDBC specific but is most likely related to a general issue.
    When the connection drops and you receive the notification through the exception handler I would typically recommend looking at the session in us (isUnitOfWork) or the query type (isWriteObjectQuery) to see if the operation that failed was involved in a transaction (UnitOfWork commit).
    In these transaction cases you need to do more then just re-connect and retry. You need to ensure after reconnection that an application exception is raised so the UnitOfWork operation(s) can be retried completely. I would simply add to this case to ensure that the JDBC connection is put back in a state where it can be managed properly.
    There is no special operation or any case I know of where any special auto-commit needs to be set on a connection after it has dropped and before it is re-connected.
    Doug

  • Failed to RowUpdate to 2 different tables simultaneously

    Hi there,
    I am trying to update two different tables from each other after some calculation (this is related to inventory cost calculation) while I am using a 3rd table to drive the loop. Unfortunately, the following exception is occured..
    Place 2o: transactionQty....>>>>:353975.0 onHandQty:844259.0
    Rolled Back
    java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]Row update failed.
    at com.microsoft.jdbc.base.BaseExceptions.createException(Unknown Source)
    at com.microsoft.jdbc.base.BaseExceptions.getException(Unknown Source)
    at com.microsoft.jdbc.base.BaseImplUpdatableResultSet.executeStatement(Unknown Source)
    at com.microsoft.jdbc.base.BaseImplUpdatableResultSet.updateRow(Unknown Source)
    at com.microsoft.jdbc.base.BaseResultSet.updateRow(Unknown Source)
    at updateInventoryCostData(InteIc.java:915)
    I can e-mail you the java file if any one want to help me.
    Can any one help me?
    Regards,
    Mortoza
    [email protected]

    Also, here is an example of handling transactions
    I believe this link may help:
    http://www.webservertalk.com/archive135-2005-3-934206.html
    public ArrayList myFunction(){
    Connection conn=null;
    PreparedStatement pstmt1= null;
    ResultSet resultSet=null;
    ArrayList list1;
    try{
    list1=new ArrayList();
    conn= dataSource.getConnection();
    conn.setAutoCommit(false);
    pstmt1= conn.prepareStatement();
    resultSet= pstmt1.executeUpdate();
    while(resultSet.next()){
    arrayList.add(resultSet.getString("lastName");
    conn.commit();
    return arrayList;
    } catch (SqlException e){
    if(conn!=null)
    conn.rollback();
    e.printStackTrace();
    } finally {
    if(conn!=null)
    conn.setAutoCommit(true);//must ensure this is done first because
    //following lines might throw an error
    if(rsultSet!=null)
    resultSet.close();
    if(pstmt1!=null)
    pstmt1.close();
    if(conn!=null)
    conn.close();
    }

  • GNOME Fails to start - Polkit? Main.js? - Receive 'Oops' message.

    Been using Arch for years but this is my first problem surprisingly so posting it in this Newbies section.
    I have MATE, KDE, and FLUXBOX working fine as desktop environments for years. Thought I would give GNOME a try and no matter what I've tried I cannot get it working. All I get is a sad face with an 'OOPS' message on screen. Although I am prompted to enter my WiFi password presumably from NetworkManager. None of the errors listed below turn up much on Google so I thought I'd turn to the community. Any help getting GNOME working correctly would be very much appreciated.
    -- Logs begin at Mon 2014-06-09 18:04:18 BST. --
    Jan 19 14:26:50 glow lightdm[1574]: pam_unix(lightdm-greeter:session): session opened for user lightdm by (uid=0)
    Jan 19 14:26:50 glow systemd-logind[432]: New session c4 of user lightdm.
    Jan 19 14:26:50 glow org.a11y.Bus[1582]: Activating service name='org.a11y.atspi.Registry'
    Jan 19 14:26:50 glow org.a11y.Bus[1582]: Successfully activated service 'org.a11y.atspi.Registry'
    Jan 19 14:26:50 glow org.a11y.atspi.Registry[1588]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
    Jan 19 14:26:50 glow systemd-logind[432]: Removed session c1.
    Jan 19 14:26:51 glow NetworkManager[422]: <warn> Could not get scan request result: Scan request rejected
    Jan 19 14:26:59 glow login[1524]: pam_unix(login:session): session opened for user cellardoor by LOGIN(uid=0)
    Jan 19 14:26:59 glow systemd-logind[432]: New session c5 of user cellardoor.
    Jan 19 14:26:59 glow login[1524]: LOGIN ON tty3 BY cellardoor
    Jan 19 14:27:16 glow org.a11y.Bus[1718]: Activating service name='org.a11y.atspi.Registry'
    Jan 19 14:27:16 glow org.a11y.Bus[1718]: Successfully activated service 'org.a11y.atspi.Registry'
    Jan 19 14:27:16 glow org.a11y.atspi.Registry[1725]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
    Jan 19 14:27:16 glow gnome-keyring-daemon[1735]: couldn't access control socket: /run/user/1000/keyring/control: No such file or directory
    Jan 19 14:27:16 glow gnome-session[1714]: ** Message: couldn't access control socket: /run/user/1000/keyring/control: No such file or directory
    Jan 19 14:27:16 glow gnome-session[1714]: SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
    Jan 19 14:27:16 glow gnome-session[1714]: GPG_AGENT_INFO=/run/user/1000/keyring/gpg:0:1
    Jan 19 14:27:16 glow gnome-session[1714]: SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
    Jan 19 14:27:16 glow rtkit-daemon[833]: Successfully made thread 1753 of process 1753 (/usr/bin/pulseaudio) owned by '1000' high priority at nice level -11.
    Jan 19 14:27:16 glow rtkit-daemon[833]: Supervising 2 threads of 2 processes of 1 users.
    Jan 19 14:27:16 glow pulseaudio[1753]: Daemon already running.
    Jan 19 14:27:16 glow dbus[425]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service'
    Jan 19 14:27:16 glow dbus[425]: [system] Successfully activated service 'org.freedesktop.hostname1'
    Jan 19 14:27:16 glow dbus[425]: [system] Activating via systemd: service name='org.freedesktop.locale1' unit='dbus-org.freedesktop.locale1.service'
    Jan 19 14:27:16 glow dbus[425]: [system] Successfully activated service 'org.freedesktop.locale1'
    Jan 19 14:27:16 glow gnome-session[1714]: (gnome-shell:1773): Gjs-WARNING **: JS ERROR: Error: Requiring Polkit, version none: Typelib file for namespace 'Polkit' (any version) not found
    Jan 19 14:27:16 glow gnome-session[1714]: @resource:///org/gnome/shell/ui/endSessionDialog.js:28
    Jan 19 14:27:16 glow gnome-session[1714]: @resource:///org/gnome/shell/ui/main.js:15
    Jan 19 14:27:16 glow gnome-session[1714]: @<main>:1
    Jan 19 14:27:16 glow gnome-session[1714]: ** Message: Execution of main.js threw exception: JS_EvaluateScript() failed
    Jan 19 14:27:16 glow gnome-session[1714]: gnome-session[1714]: WARNING: App 'gnome-shell.desktop' exited with code 1
    Jan 19 14:27:16 glow gnome-session[1714]: WARNING: App 'gnome-shell.desktop' exited with code 1
    Jan 19 14:27:17 glow gnome-session[1714]: (gnome-shell:1790): Gjs-WARNING **: JS ERROR: Error: Requiring Polkit, version none: Typelib file for namespace 'Polkit' (any version) not found
    Jan 19 14:27:17 glow gnome-session[1714]: @resource:///org/gnome/shell/ui/endSessionDialog.js:28
    Jan 19 14:27:17 glow gnome-session[1714]: @resource:///org/gnome/shell/ui/main.js:15
    Jan 19 14:27:17 glow gnome-session[1714]: @<main>:1
    Jan 19 14:27:17 glow gnome-session[1714]: ** Message: Execution of main.js threw exception: JS_EvaluateScript() failed
    Jan 19 14:27:17 glow gnome-session[1714]: WARNING: App 'gnome-shell.desktop' exited with code 1
    Jan 19 14:27:17 glow gnome-session[1714]: WARNING: App 'gnome-shell.desktop' respawning too quickly
    Jan 19 14:27:17 glow gnome-session[1714]: gnome-session[1714]: WARNING: App 'gnome-shell.desktop' exited with code 1
    Jan 19 14:27:17 glow gnome-session[1714]: gnome-session[1714]: WARNING: App 'gnome-shell.desktop' respawning too quickly
    Jan 19 14:27:17 glow gnome-session[1714]: Unrecoverable failure in required component gnome-shell.desktop
    Jan 19 14:27:17 glow fingerprint-polkit-agent[1806]: Got "debug" argument.
    Jan 19 14:27:17 glow fingerprint-polkit-agent[1806]: started.
    Jan 19 14:27:17 glow gnome-session[1714]: (uint32 1,)
    Jan 19 14:27:17 glow gnome-session[1714]: Entering running state
    Jan 19 14:27:17 glow gnome-session[1714]: Failed to play sound: File or data not found
    Jan 19 14:27:17 glow gnome-session[1714]: New PolkitAgentListener 0xb637a0
    Jan 19 14:27:17 glow gnome-session[1714]: Adding new listener PolkitQt1::Agent::Listener(0x7fff29d587e0) for 0xb637a0
    Jan 19 14:27:17 glow org.gnome.zeitgeist.Engine[1718]: ** (zeitgeist-datahub:1857): WARNING **: zeitgeist-datahub.vala:226: Unable to get name "org.gnome.zeitgeist.datahub" on the bus!
    Jan 19 14:27:17 glow polkitd[433]: Registered Authentication Agent for unix-session:c5 (system bus name :1.90 [/usr/lib/fingerprint-gui/fingerprint-polkit-agent -d], object path /fingerprintgui/PolicyKit1/AuthenticationAgent, locale en_GB.UTF-8)
    Jan 19 14:27:17 glow fingerprint-polkit-agent[1806]: Listener "/fingerprintgui/PolicyKit1/AuthenticationAgent" registered.
    Jan 19 14:27:17 glow NetworkManager[422]: <info> Auto-activating connection 'The Promised LAN'.
    Jan 19 14:27:17 glow NetworkManager[422]: <info> Activation (wlp3s0) starting connection 'The Promised LAN'
    Jan 19 14:27:17 glow NetworkManager[422]: <info> Activation (wlp3s0) Stage 1 of 5 (Device Prepare) scheduled...
    Jan 19 14:27:17 glow NetworkManager[422]: <info> Activation (wlp3s0) Stage 1 of 5 (Device Prepare) started...
    Jan 19 14:27:17 glow NetworkManager[422]: <info> (wlp3s0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
    Jan 19 14:27:17 glow NetworkManager[422]: <info> Activation (wlp3s0) Stage 2 of 5 (Device Configure) scheduled...
    Jan 19 14:27:17 glow NetworkManager[422]: <info> Activation (wlp3s0) Stage 1 of 5 (Device Prepare) complete.
    Jan 19 14:27:17 glow NetworkManager[422]: <info> Activation (wlp3s0) Stage 2 of 5 (Device Configure) starting...
    Jan 19 14:27:17 glow NetworkManager[422]: <info> (wlp3s0): device state change: prepare -> config (reason 'none') [40 50 0]
    Jan 19 14:27:17 glow NetworkManager[422]: <info> Activation (wlp3s0/wireless): access point 'The Promised LAN' has security, but secrets are required.
    Jan 19 14:27:17 glow NetworkManager[422]: <info> (wlp3s0): device state change: config -> need-auth (reason 'none') [50 60 0]
    Jan 19 14:27:17 glow NetworkManager[422]: <info> Activation (wlp3s0) Stage 2 of 5 (Device Configure) complete.
    Jan 19 14:27:17 glow org.freedesktop.thumbnails.Cache1[1718]: (tumblerd:1887): tumbler-WARNING **: Failed to load plugin "tumbler-raw-thumbnailer.so": libopenrawgnome.so.1: cannot open shared object file: No such file or directory
    Jan 19 14:27:17 glow org.freedesktop.thumbnails.Cache1[1718]: (tumblerd:1887): tumbler-WARNING **: Failed to load plugin "tumbler-ffmpeg-thumbnailer.so": libffmpegthumbnailer.so.4: cannot open shared object file: No such file or directory
    Jan 19 14:27:17 glow gnome-session[1714]: Traceback (most recent call last):
    Jan 19 14:27:17 glow gnome-session[1714]: File "<frozen importlib._bootstrap>", line 2158, in _find_spec
    Jan 19 14:27:17 glow gnome-session[1714]: AttributeError: 'DynamicImporter' object has no attribute 'find_spec'
    Jan 19 14:27:17 glow gnome-session[1714]: During handling of the above exception, another exception occurred:
    Jan 19 14:27:17 glow gnome-session[1714]: Traceback (most recent call last):
    Jan 19 14:27:17 glow gnome-session[1714]: File "/usr/share/system-config-printer/applet.py", line 45, in <module>
    Jan 19 14:27:17 glow gnome-session[1714]: from gi.repository import Notify
    Jan 19 14:27:17 glow gnome-session[1714]: File "/usr/lib/python3.4/site-packages/gi/importer.py", line 53, in find_module
    Jan 19 14:27:17 glow gnome-session[1714]: 'introspection typelib not found' % namespace)
    Jan 19 14:27:17 glow gnome-session[1714]: ImportError: cannot import name Notify, introspection typelib not found
    Jan 19 14:27:17 glow gnome-session[1714]: (nm-applet:1810): libnm-glib-CRITICAL **: nm_secret_agent_register: assertion 'priv->registered == FALSE' failed
    Jan 19 14:27:17 glow gnome-session[1714]: nm-applet-Message: No keyring secrets found for The Promised LAN/802-11-wireless-security; asking user.
    Jan 19 14:27:17 glow gnome-session[1714]: (gnome-settings-daemon:1742): GLib-GIO-CRITICAL **: g_dbus_proxy_call_internal: assertion 'G_IS_DBUS_PROXY (proxy)' failed
    Jan 19 14:27:17 glow gnome-session[1714]: (gnome-settings-daemon:1742): GLib-GIO-CRITICAL **: g_dbus_proxy_call_internal: assertion 'G_IS_DBUS_PROXY (proxy)' failed
    Jan 19 14:27:17 glow gnome-session[1714]: (tracker-extract:1813): Tracker-WARNING **: Call to gst_discoverer_discover_uri() failed: GStreamer encountered a general stream error.
    Jan 19 14:27:17 glow gnome-session[1714]: (tracker-extract:1813): Tracker-WARNING **: Task for 'file:///home/cellardoor/test.webm' finished with error: Could not get any metadata for uri:'file:///home/cellardoor/test.webm' and mime:'video/webm'
    Jan 19 14:27:17 glow gnome-session[1714]: (tracker-extract:1813): Tracker-WARNING **: Failed to open file: No OLE2 signature
    Jan 19 14:27:17 glow gnome-session[1714]: (tracker-extract:1813): Tracker-WARNING **: Task for 'file:///home/cellardoor/samsungkeyforserver.pub' finished with error: Could not get any metadata for uri:'file:///home/cellardoor/samsungkeyforserver.pub' and mime:'application/vnd.ms-publisher'
    Jan 19 14:27:18 glow org.gnome.OnlineAccounts[1718]: goa-daemon-Message: goa-daemon version 3.14.2 starting
    Jan 19 14:27:18 glow org.freedesktop.thumbnails.Thumbnailer1[1718]: (tumblerd:1909): tumbler-WARNING **: Failed to load plugin "tumbler-raw-thumbnailer.so": libopenrawgnome.so.1: cannot open shared object file: No such file or directory
    Jan 19 14:27:18 glow org.freedesktop.thumbnails.Thumbnailer1[1718]: (tumblerd:1909): tumbler-WARNING **: Failed to load plugin "tumbler-ffmpeg-thumbnailer.so": libffmpegthumbnailer.so.4: cannot open shared object file: No such file or directory
    Jan 19 14:27:18 glow gnome-session[1714]: (tracker-extract:1813): Tracker-WARNING **: Couldn't create PopplerDocument from uri:'file:///home/cellardoor/Documents/Holiday/certificate_flight_plus_2_a.pdf', PDF document is damaged
    Jan 19 14:27:18 glow gnome-session[1714]: (tracker-extract:1813): Tracker-WARNING **: Task for 'file:///home/cellardoor/Documents/Holiday/certificate_flight_plus_2_a.pdf' finished with error: Could not get any metadata for uri:'file:///home/cellardoor/Documents/Holiday/certificate_flight_plus_2_a.pdf' and mime:'application/pdf'
    Jan 19 14:27:18 glow gnome-session[1714]: (tracker-extract:1813): Tracker-WARNING **: Call to gst_discoverer_discover_uri() failed: Your GStreamer installation is missing a plug-in.
    Jan 19 14:27:18 glow gnome-session[1714]: (tracker-extract:1813): Tracker-WARNING **: Task for 'file:///home/cellardoor/Documents/Java/Assignment3/evidence%20of%20testing%20and%20results%20not%20as%20expected.xcf' finished with error: Could not get any metadata for uri:'file:///home/cellardoor/Documents/Java/Assignment3/evidence%20of%20testing%20and%20results%20not%20as%20expected.xcf' and mime:'image/x-xcf'
    Jan 19 14:27:18 glow gnome-session[1714]: Destroying listener
    Jan 19 14:27:18 glow gnome-session[1714]: Removing listener PolkitQt1::Agent::Listener(0x7fff29d587e0)
    Jan 19 14:27:18 glow polkitd[433]: Unregistered Authentication Agent for unix-session:c5 (system bus name :1.90, object path /fingerprintgui/PolicyKit1/AuthenticationAgent, locale en_GB.UTF-8)
    Jan 19 14:27:18 glow gnome-session[1714]: Received signal:1->'Hangup'
    Jan 19 14:27:18 glow gnome-session[1714]: Received signal:1->'Hangup'
    Jan 19 14:27:18 glow gnome-session[1714]: Received signal:1->'Hangup'
    Jan 19 14:27:18 glow NetworkManager[422]: <warn> No agents were available for this request.
    Jan 19 14:27:18 glow NetworkManager[422]: <info> (wlp3s0): device state change: need-auth -> failed (reason 'no-secrets') [60 120 7]
    Jan 19 14:27:18 glow NetworkManager[422]: <warn> Activation (wlp3s0) failed for connection 'The Promised LAN'
    Jan 19 14:27:18 glow NetworkManager[422]: <info> (wlp3s0): device state change: failed -> disconnected (reason 'none') [120 30 0]
    Jan 19 14:27:18 glow NetworkManager[422]: <info> (wlp3s0): deactivating device (reason 'none') [0]
    Jan 19 14:27:18 glow NetworkManager[422]: <info> Auto-activating connection 'Security'.
    Jan 19 14:27:18 glow NetworkManager[422]: <info> Activation (wlp3s0) starting connection 'Security'
    Jan 19 14:27:18 glow NetworkManager[422]: <info> Activation (wlp3s0) Stage 1 of 5 (Device Prepare) scheduled...
    Jan 19 14:27:18 glow NetworkManager[422]: <info> Activation (wlp3s0) Stage 1 of 5 (Device Prepare) started...
    Jan 19 14:27:18 glow NetworkManager[422]: <info> (wlp3s0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
    Jan 19 14:27:18 glow NetworkManager[422]: <info> Activation (wlp3s0) Stage 2 of 5 (Device Configure) scheduled...
    Jan 19 14:27:18 glow gnome-session[1714]: Received signal:1->'Hangup'
    Jan 19 14:27:18 glow NetworkManager[422]: <info> Activation (wlp3s0) Stage 1 of 5 (Device Prepare) complete.
    Jan 19 14:27:18 glow NetworkManager[422]: <info> Activation (wlp3s0) Stage 2 of 5 (Device Configure) starting...
    Jan 19 14:27:18 glow NetworkManager[422]: <info> (wlp3s0): device state change: prepare -> config (reason 'none') [40 50 0]
    Jan 19 14:27:18 glow NetworkManager[422]: <info> Activation (wlp3s0/wireless): access point 'Security' has security, but secrets are required.
    Jan 19 14:27:18 glow NetworkManager[422]: <info> (wlp3s0): device state change: config -> need-auth (reason 'none') [50 60 0]
    Jan 19 14:27:18 glow NetworkManager[422]: <info> Activation (wlp3s0) Stage 2 of 5 (Device Configure) complete.
    Jan 19 14:27:18 glow NetworkManager[422]: <warn> No agents were available for this request.
    Jan 19 14:27:18 glow NetworkManager[422]: <info> (wlp3s0): device state change: need-auth -> failed (reason 'no-secrets') [60 120 7]
    Jan 19 14:27:18 glow NetworkManager[422]: <warn> Activation (wlp3s0) failed for connection 'Security'
    Jan 19 14:27:18 glow NetworkManager[422]: <info> (wlp3s0): device state change: failed -> disconnected (reason 'none') [120 30 0]
    Jan 19 14:27:18 glow NetworkManager[422]: <info> (wlp3s0): deactivating device (reason 'none') [0]
    Jan 19 14:27:18 glow kernel: tracker-miner-f[1827]: segfault at 130000017a ip 00007f14f57cbdbe sp 00007ffff6a89330 error 4 in libgio-2.0.so.0.4200.1[7f14f5779000+16f000]
    Jan 19 14:27:18 glow org.freedesktop.thumbnails.Cache1[1718]: (tumblerd:1887): GVFS-RemoteVolumeMonitor-WARNING **: Owner of volume monitor org.gtk.Private.UDisks2VolumeMonitor disconnected from the bus; removing drives/volumes/mounts
    Jan 19 14:27:18 glow org.freedesktop.thumbnails.Cache1[1718]: (tumblerd:1887): GVFS-RemoteVolumeMonitor-WARNING **: Owner of volume monitor org.gtk.Private.MTPVolumeMonitor disconnected from the bus; removing drives/volumes/mounts
    Jan 19 14:27:18 glow NetworkManager[422]: <warn> Could not get scan request result: Scan request rejected
    Jan 19 14:27:18 glow org.a11y.Bus[1718]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
    Jan 19 14:27:18 glow gnome-session[1714]: g_dbus_connection_real_closed: Remote peer vanished with error: Error receiving message: Connection reset by peer (g-io-error-quark, 0). Exiting.
    Jan 19 14:27:18 glow gnome-session[1714]: Received signal:15->'Terminated'
    Jan 19 14:27:18 glow org.gtk.vfs.Daemon[1718]: A connection to the bus can't be made
    Jan 19 14:27:18 glow org.gtk.vfs.Daemon[1718]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
    Jan 19 14:27:18 glow org.freedesktop.Tracker1[1718]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
    Jan 19 14:27:18 glow org.gtk.vfs.Daemon[1718]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
    Jan 19 14:27:18 glow org.gnome.OnlineAccounts[1718]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
    Jan 19 14:27:18 glow org.gtk.Private.UDisks2VolumeMonitor[1718]: g_dbus_connection_real_closed: Remote peer vanished with error: Error receiving message: Connection reset by peer (g-io-error-quark, 0). Exiting.
    Jan 19 14:27:18 glow org.gtk.Private.MTPVolumeMonitor[1718]: g_dbus_connection_real_closed: Remote peer vanished with error: Error receiving message: Connection reset by peer (g-io-error-quark, 0). Exiting.
    Jan 19 14:27:18 glow org.gnome.evolution.dataserver.Sources3[1718]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
    Jan 19 14:27:18 glow org.gnome.zeitgeist.Engine[1718]: g_dbus_connection_real_closed: Remote peer vanished with error: Error receiving message: Connection reset by peer (g-io-error-quark, 0). Exiting.
    Jan 19 14:27:18 glow org.freedesktop.Tracker1[1718]: Received signal:15->'Terminated'
    Jan 19 14:27:18 glow org.freedesktop.Tracker1[1718]: OK
    Jan 19 14:27:18 glow ca.desrt.dconf[1718]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
    Jan 19 14:27:18 glow gnome-session[1714]: g_dbus_connection_real_closed: Remote peer vanished with error: Error receiving message: Connection reset by peer (g-io-error-quark, 0). Exiting.
    Jan 19 14:27:18 glow org.gnome.zeitgeist.Engine[1718]: [14:27:18.337568 WARNING] zeitgeist-daemon.vala:449: The connection is closed
    Jan 19 14:27:18 glow gnome-session[1714]: Received signal:15->'Terminated'
    Jan 19 14:27:18 glow gnome-session[1714]: OK
    Jan 19 14:27:18 glow org.freedesktop.Telepathy.AccountManager[1718]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
    Jan 19 14:27:18 glow org.gnome.evolution.dataserver.Calendar4[1718]: Could not connect: Connection refused
    Jan 19 14:27:18 glow org.freedesktop.thumbnails.Thumbnailer1[1718]: Error creating proxy: The connection is closed (g-io-error-quark, 18)
    Jan 19 14:27:18 glow org.freedesktop.thumbnails.Thumbnailer1[1718]: (tumblerd:1909): GLib-GIO-CRITICAL **: Error while sending AddMatch() message: The connection is closed
    Jan 19 14:27:18 glow org.freedesktop.thumbnails.Thumbnailer1[1718]: Error creating proxy: Error calling StartServiceByName for org.gtk.Private.MTPVolumeMonitor: The connection is closed (g-io-error-quark, 18)
    Jan 19 14:27:18 glow org.freedesktop.thumbnails.Thumbnailer1[1718]: (tumblerd:1909): GLib-GIO-CRITICAL **: Error while sending AddMatch() message: The connection is closed
    Jan 19 14:27:18 glow org.freedesktop.thumbnails.Thumbnailer1[1718]: (tumblerd:1909): GLib-GIO-CRITICAL **: Error while sending AddMatch() message: The connection is closed
    Jan 19 14:27:18 glow org.freedesktop.thumbnails.Thumbnailer1[1718]: Error creating proxy: Error calling StartServiceByName for org.gtk.vfs.Daemon: The connection is closed (g-io-error-quark, 18)
    Jan 19 14:27:18 glow gnome-session[1714]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
    Jan 19 14:27:18 glow gnome-session[1714]: Received signal:15->'Terminated'
    Jan 19 14:27:18 glow org.freedesktop.thumbnails.Thumbnailer1[1718]: (tumblerd:1909): tumblerd-WARNING **: Failed to start the thumbnail cache service: Another thumbnail cache service is already running
    Jan 19 14:27:18 glow gnome-session[1714]: OK
    Jan 19 14:27:18 glow systemd-coredump[1943]: Process 1827 (tracker-miner-f) of user 1000 dumped core.
    Thank you!
    Moderator edit:  Added code tags
    Last edited by ewaller (2015-01-19 15:57:10)

    Please use code tags when posting logs. From
    Jan 19 14:27:16 glow gnome-session[1714]: ** Message: couldn't access control socket: /run/user/1000/keyring/control: No such file or directory
    Jan 19 14:27:16 glow gnome-session[1714]: (gnome-shell:1773): Gjs-WARNING **: JS ERROR: Error: Requiring Polkit, version none: Typelib file for namespace 'Polkit' (any version) not found
    it seems you're missing dependencies, or they're not started for some reason. Try running GNOME via GDM, installing latter should pull in the full kitchen sink. If you want more hints, google for "gjs polkit not found".
    Last edited by Alad (2015-01-19 15:38:09)

  • AppV5 Office 2013 (Visio) couldn't get published (failed configuration in folder ProgramData\App-V 0x7D401F30-0x5)

    Environment:
    Server: AppV 5 SP1 Pub and Mgmt server (no Hotfixes applied)
    Client: Windows 7 SP1 x64 with AppV 5.0 SP2 client (tried RTM and with HF5)
    Created a Visio 2013 package with ODT (latest version). Only Visio, no other products added. Used the PACKAGEGUID to specify a custom PackageGUID.
    Configuration.xml;
    <Configuration>
    <Add SourcePath="C:\Temp\" OfficeClientEdition="32" >
    <Product ID="VisioStdVolume">
    <Language ID="en-us" />
    <Language ID="nl-nl" />
    <Language ID="fr-fr" />
    </Product>
    </Add>
    <Display Level="None" AcceptEULA="TRUE" />
    <Logging Name="VisioStd2013Setup.txt" Path="%temp%" />
    <Property Name="AUTOACTIVATE" Value="1" />
    <Property Name="PACKAGEGUID" Value="0123e69c-b152-4c70-b178-41be0d2b7d1b" />
    </Configuration>
    Adding and Publishing locally with Powershell works like expected. But using the App-V 5.0 Mgmt/Publishing server it fails on all clients.
    Package is published to computers.
    Domain Computers have READ permission on the AppV Content share.
    Previously Office 2013 packages could be published without any errors.
    AppV logs:
    Event ID: 19104:
    Part or all packages publish failed.
    published: 0
    failed: 1
    Please check the error events of 'Configure/Publish Package' before this message for the details of the failure.
    Event ID: 1008
    Package {0123e69c-b152-4c70-b178-41be0d2b7d1b} version {5197e402-1206-4940-bd96-a0597e7d4b1f} failed configuration in folder 'C:\ProgramData\App-V\0123E69C-B152-4C70-B178-41BE0D2B7D1B\5197E402-1206-4940-BD96-A0597E7D4B1F' with error 0x7D401F30-0x5.
    Event ID: 4001
    The App-V client failed to create a process for machine script event AddPackage with command line: '"C:\ProgramData\App-V\0123E69C-B152-4C70-B178-41BE0D2B7D1B\5197E402-1206-4940-BD96-A0597E7D4B1F\Root\..\Scripts\Integrator.exe" /I /Msi /License /AppV PackageGUID=0123e69c-b152-4c70-b178-41be0d2b7d1b PackageRoot="C:\ProgramData\App-V\0123E69C-B152-4C70-B178-41BE0D2B7D1B\5197E402-1206-4940-BD96-A0597E7D4B1F\Root" MsiName=SPPRedist.msi,SPPRedist64.msi PidKey=FN8TT-7WMH6-2D4X9-M337T-2342K,YC7DK-G2NP3-2QQC3-J6H88-GVGXT,C2FG9-N6J68-H8BTJ-BW3QX-RM3B3 PRIDName=VisioStdVolume'. Windows error: Access is denied.. The path must be a Windows application (.exe file).
    Analytic and Debugs logs aren’t very helpful (Client-Publishing):
    No package published.
    Published: false
    Failed: 0
    So, Access denied (0x5) on Integrator.exe in ProgramData? As we have AppLocker in place, checked the AppLocker logs. But no trace in there.
    Other AppV5 applications does work
    Tested on two different App-V 5 Pub Servers (5.0 SP1 and SP1 with HF4), same behaviour.
    Tested on three Win7 SP1 x64 clients, same behaviour.
    EnablePackageScripts (client config) is enabled on all clients.
    Issue was
    reported before on the forums, but Domain Users and Domain Computers have already READ permissions to the AppV Content Share (NTFS permissions) where the .appv file is stored.
    Added (as a test) Domain Computers and Everyone Full Control to c:\ProgramData\App-V, doesn’t solve it.
    Cannot use ProcMon, because the Publish event occurs before user login.
    I’m out of ideas. Someone that could assist me please?

    The above fix was a lucky shot.
    This solved it (hopefully) for good;
    http://www.the-d-spot.org/wordpress/2014/11/05/appv5-office-2013-package-cannot-be-published-access-is-denied-on-integrator-exe/

  • BUG: implied .executeBatch() failing with new drivers?

    Our application uses batching with SQLJ and is experiencing an issue with the latest driver versions and Java 1.5. It used to work fine when issuing a few INSERT statements with a specified execution context and then letting the SQLJ COMMIT execute the pending statements in the batch when the transaction was finished. With the new drivers, the SQLJ COMMIT is successful but it doesn't write any of the pending batches to database as it is supposed to (per the Oracle Database SQLJ Developer's Guide and Reference).
    In a small testcase I prepared (see the next message for the code), it shows a new batch was created for the first statement (NEW_BATCH_COUNT returned). It also shows subsequent statements are added to the existing batch (ADD_BATCH_COUNT returned). The COUNT() statements show the data never makes it to the database and the table contents were verified in the database after program completion.
    Java: 1.5.0_10
    Oracle Database: Oracle9i Enterprise Edition Release 9.2.0.1.0 - 64bit Production
    Oracle JDBC Driver: 10.2.0.2.0
    translator.jar: JPublisher 10g Release 10.2
    runtime12.jar: JPublisher 10g Release 10.2
    Can anyone please confirm this is a bug?
    Thanks much

    //---------- C O D E ---------------------------------
    package com.sqljtest;
    import java.sql.*;
    import java.util.*;
    import sqlj.runtime.ref.*;
    import sqlj.runtime.*;
    import oracle.sqlj.runtime.*;
    public class Sqljtest extends java.lang.Object {
    public static void main(String[] args) {
    Connection con = null;
    DefaultContext connContext = null;
    ExecutionContext ec = null;
    try {
    String driver = "oracle.jdbc.OracleDriver";
    String url = "jdbc:oracle:thin:@127.0.0.1:1521:mysid";
    String user = "scott";
    String password = "tiger";
    DriverManager.registerDriver(new oracle.jdbc.OracleDriver());
    con = DriverManager.getConnection(url, user, password);
    con.setAutoCommit(false);
    connContext = Oracle.getConnection(con);
    connContext.getConnection().setAutoCommit(false);
    ec = new ExecutionContext();
    ec.setBatching(true);
    Vector collection = new Vector();
    collection.add("one");
    collection.add("two");
    collection.add("three");
    collection.add("four");
    collection.add("five");
    int rowCount, updateCount;
    #sql [connContext] { SELECT COUNT(1) INTO :rowCount FROM sqljtest };
    System.out.println("before rowCount:" + rowCount);
    for (int i = 0; i < collection.size(); i++) {
    #sql [connContext, ec] {
    INSERT INTO sqljtest blah VALUES (: ((String)collection.get(i)) )
    updateCount = ec.getUpdateCount();
    System.out.println("INSERT (" collection.get(i) "): " + updateCount);
    #sql [connContext] { SELECT COUNT(1) INTO :rowCount FROM sqljtest };
    System.out.println("after inserts rowCount:" + rowCount);
    #sql [connContext] {COMMIT};
    #sql [connContext] { SELECT COUNT(1) INTO :rowCount FROM sqljtest };
    System.out.println("after sqlj commit rowCount:" + rowCount);
    } catch (Exception e) {
    System.err.println("Exception e: " + e.toString());
    } finally {
    try {
    if (connContext != null && !connContext.isClosed()) {
    connContext.close(ConnectionContext.CLOSE_CONNECTION);// .CLOSE_CONNECTION
    if (con != null) {
    con.close();
    } catch (Exception e) {
    System.err.println("Exception while closing connections: " + e.toString());
    //---------- O U T P U T -----------------------------
    run SQLJ Test:
    [SQLJ Test] before rowCount:0
    [SQLJ Test] INSERT (one): -3
    [SQLJ Test] INSERT (two): -4
    [SQLJ Test] INSERT (three): -4
    [SQLJ Test] INSERT (four): -4
    [SQLJ Test] INSERT (five): -4
    [SQLJ Test] after inserts rowCount:0
    [SQLJ Test] after sqlj commit rowCount:0

Maybe you are looking for