java.sql.SQLIntegrityConstraintViolationException: The statement was aborted because it would have caused a duplicate key value in a unique or primary key constraint or unique index identified by 'SQL140616082752550' defined on 'PERSISTENTMESSAGE'. 2014-06-16 08:44:08,571 - [INFO] - from application in Thread-14 [Pipeline 2 Engine console output] Error Code: 20000 2014-06-16 08:44:08,571 - [INFO] - from application in Thread-14 [Pipeline 2 Engine console output] Call: INSERT INTO PERSISTENTMESSAGE (jobId, sequence, col, file, LEVEL, line, text, throwable, timestamp) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?) 2014-06-16 08:44:08,571 - [INFO] - from application in Thread-14 [Pipeline 2 Engine console output] bind => [9 parameters bound] 2014-06-16 08:44:08,571 - [INFO] - from application in Thread-14 [Pipeline 2 Engine console output] Query: InsertObjectQuery(org.daisy.pipeline.persistence.messaging.PersistentMessage@3c401d45) 2014-06-16 08:44:08,571 - [INFO] - from application in Thread-14

Google Groups | Greg Kearney | 2 years ago
  1. 0

    Trying, really trying to get Pipeline 2 to work

    Google Groups | 2 years ago | Greg Kearney
    java.sql.SQLIntegrityConstraintViolationException: The statement was aborted because it would have caused a duplicate key value in a unique or primary key constraint or unique index identified by 'SQL140616082752550' defined on 'PERSISTENTMESSAGE'. 2014-06-16 08:44:08,571 - [INFO] - from application in Thread-14 [Pipeline 2 Engine console output] Error Code: 20000 2014-06-16 08:44:08,571 - [INFO] - from application in Thread-14 [Pipeline 2 Engine console output] Call: INSERT INTO PERSISTENTMESSAGE (jobId, sequence, col, file, LEVEL, line, text, throwable, timestamp) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?) 2014-06-16 08:44:08,571 - [INFO] - from application in Thread-14 [Pipeline 2 Engine console output] bind => [9 parameters bound] 2014-06-16 08:44:08,571 - [INFO] - from application in Thread-14 [Pipeline 2 Engine console output] Query: InsertObjectQuery(org.daisy.pipeline.persistence.messaging.PersistentMessage@3c401d45) 2014-06-16 08:44:08,571 - [INFO] - from application in Thread-14
  2. 0

    When a flush method is issued right after a remove method in a one-to-many relationship causes a SQLIntegrityConstraintViolationException.

    Eclipse Bugzilla | 5 years ago | wwong
    java.sql.SQLIntegrityConstraintViolationException: Column 'NODEGROUPID' cannot accept a NULL value. Error Code: 20000 Call: UPDATE node SET nodeGroupID = ? WHERE (nodeID = ?) bind => [null, 105] Query: DeleteObjectQuery(Node[nodeId=105,nodes={[]},nodeGroupId=Nodegroup[nodes={[]},nodeGroupName=nodeGroupName_5,comment=comment_5,creatorId=5,creationTime=Tue May 08 16:13:59 EDT 2012,type=5,flags=5,nodeGroupId=97],proxyNodeId=persistence.jpa.entities.Node@557e5cbd,nodeName=nodeName_3,nodeAddress=nodeAddress_3,userName=userName_3,password=password_3,comment=comment_3,creatorId=3,creationTime=Tue May 08 16:16:49 EDT 2012,type=3,flags=3,features=3,hostId=hostId_3,policies={[]}])
  3. 0

    Trying, really trying to get Pipeline 2 to work

    Google Groups | 2 years ago | Greg Kearney
    java.sql.SQLIntegrityConstraintViolationException: The statement was aborted because it would have caused a duplicate key value in a unique or primary key constraint or unique index identified by 'SQL140616082752550' defined on 'PERSISTENTMESSAGE'. 2014-06-16 08:44:08,718 - [INFO] - from application in Thread-14
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    Trying, really trying to get Pipeline 2 to work

    Google Groups | 2 years ago | Greg Kearney
    java.sql.SQLIntegrityConstraintViolationException: The statement was aborted because it would have caused a duplicate key value in a unique or primary key constraint or unique index identified by 'SQL140616082752550' defined on 'PERSISTENTMESSAGE'. 2014-06-16 08:44:08,718 - [INFO] - from application in Thread-14
  6. 0

    Trying, really trying to get Pipeline 2 to work

    Google Groups | 2 years ago | Greg Kearney
    java.sql.SQLIntegrityConstraintViolationException: The statement was aborted because it would have caused a duplicate key value in a unique or primary key constraint or unique index identified by 'SQL140616082752550' defined on 'PERSISTENTMESSAGE'. 2014-06-16 08:44:08,718 - [INFO] - from application in Thread-14

    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. java.sql.SQLIntegrityConstraintViolationException

      The statement was aborted because it would have caused a duplicate key value in a unique or primary key constraint or unique index identified by 'SQL140616082752550' defined on 'PERSISTENTMESSAGE'. 2014-06-16 08:44:08,571 - [INFO] - from application in Thread-14 [Pipeline 2 Engine console output] Error Code: 20000 2014-06-16 08:44:08,571 - [INFO] - from application in Thread-14 [Pipeline 2 Engine console output] Call: INSERT INTO PERSISTENTMESSAGE (jobId, sequence, col, file, LEVEL, line, text, throwable, timestamp) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?) 2014-06-16 08:44:08,571 - [INFO] - from application in Thread-14 [Pipeline 2 Engine console output] bind => [9 parameters bound] 2014-06-16 08:44:08,571 - [INFO] - from application in Thread-14 [Pipeline 2 Engine console output] Query: InsertObjectQuery(org.daisy.pipeline.persistence.messaging.PersistentMessage@3c401d45) 2014-06-16 08:44:08,571 - [INFO] - from application in Thread-14

      at org.eclipse.persistence.exceptions.DatabaseException.sqlException()
    2. EclipseLink (non-OSGi)
      DatabaseException.sqlException
      1. org.eclipse.persistence.exceptions.DatabaseException.sqlException(DatabaseException.java:324)
      1 frame