[ 
https://issues.apache.org/jira/browse/OOZIE-971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13443789#comment-13443789
 ] 

Hadoop QA commented on OOZIE-971:
---------------------------------

Testing JIRA OOZIE-971

Cleaning local svn workspace

{code}
----------------------------

+1 PATCH_APPLIES
   CLEAN cleaned target directories
-1 RAW_PATCH_ANALYSIS
    +1 the patch does not introduce any @author tags
    +1 the patch does not introduce any tabs
    +1 the patch does not introduce any trailing spaces
    +1 the patch does not introduce any line longer than 132
    -1 the patch does not add/modify any testcase
+1 RAT
    +1 the patch does not seem to introduce new RAT warnings
+1 JAVADOC
    +1 the patch does not seem to introduce new Javadoc warnings
+1 COMPILE
    +1 HEAD compiles
    +1 patch compiles
    +1 the patch does not seem to introduce new javac warnings
+1 BACKWARDS_COMPATIBILITY
    +1 the patch does not change any JPA Entity/Colum/Basic/Lob/Transient 
annotations
    +1 the patch does not modify JPA files
+1 TESTS
   Tests run: 901
   Tests failures: 0
   Tests errors: 1
+1 DISTRO
    +1 distro tarball builds with the patch 

----------------------------
{code}

The full output of the test-patch run is available at

   https://builds.apache.org/job/oozie-trunk-precommit-build/67/
                
> TestRecoveryService failing very often in pre-commit builds
> -----------------------------------------------------------
>
>                 Key: OOZIE-971
>                 URL: https://issues.apache.org/jira/browse/OOZIE-971
>             Project: Oozie
>          Issue Type: Bug
>    Affects Versions: 3.3.0, trunk
>            Reporter: Virag Kothari
>            Assignee: Mona Chitnis
>             Fix For: 3.3.0, trunk
>
>         Attachments: OOZIE-971.patch, OOZIE-971v2.patch
>
>
> The SuspendX Command in 'testCoordActionRecoveryServiceForSuspended' fails 
> with the JPA error 'This may mean that you deleted the instance in a separate 
> transaction, but this context still has a cached version.'
> The below exception thrown in almost every pre-commit build from last couple 
> of days 
> {code}
> 04:11:13,322 ERROR SuspendXCommand:536 - USER[test] GROUP[-] TOKEN[testToken] 
> APP[testApp] JOB[0000002-120827041103168-oozie-jenk-W] ACTION[-] XException, 
> org.apache.oozie.command.CommandException: E0603: SQL error in operation 
> [<openjpa-2.1.0-r422266:1071316 nonfatal store error> 
> org.apache.openjpa.persistence.EntityNotFoundException: The instance of type 
> "class org.apache.oozie.WorkflowJobBean" with oid 
> "0000000-120827035717784-oozie-jenk-W" no longer exists in the data store.  
> This may mean that you deleted the instance in a separate transaction, but 
> this context still has a cached version.
> FailedObject: 
> org.apache.oozie.WorkflowJobBean-0000000-120827035717784-oozie-jenk-W], {1}
>       at 
> org.apache.oozie.command.wf.SuspendXCommand.execute(SuspendXCommand.java:73)
>       at 
> org.apache.oozie.command.wf.SuspendXCommand.execute(SuspendXCommand.java:45)
>       at org.apache.oozie.command.XCommand.call(XCommand.java:277)
>       at 
> org.apache.oozie.command.XCommand.executeInterrupts(XCommand.java:344)
>       at org.apache.oozie.command.XCommand.call(XCommand.java:260)
>       at 
> org.apache.oozie.service.CallableQueueService$CallableWrapper.run(CallableQueueService.java:175)
>       at 
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
>       at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>       at java.lang.Thread.run(Thread.java:662)
> Caused by: org.apache.oozie.executor.jpa.JPAExecutorException: E0603: SQL 
> error in operation [<openjpa-2.1.0-r422266:1071316 nonfatal store error> 
> org.apache.openjpa.persistence.EntityNotFoundException: The instance of type 
> "class org.apache.oozie.WorkflowJobBean" with oid 
> "0000000-120827035717784-oozie-jenk-W" no longer exists in the data store.  
> This may mean that you deleted the instance in a separate transaction, but 
> this context still has a cached version.
> FailedObject: 
> org.apache.oozie.WorkflowJobBean-0000000-120827035717784-oozie-jenk-W], {1}
>       at 
> org.apache.oozie.executor.jpa.BulkUpdateInsertJPAExecutor.execute(BulkUpdateInsertJPAExecutor.java:98)
>       at 
> org.apache.oozie.executor.jpa.BulkUpdateInsertJPAExecutor.execute(BulkUpdateInsertJPAExecutor.java:32)
>       at org.apache.oozie.service.JPAService.execute(JPAService.java:211)
>       at 
> org.apache.oozie.command.wf.SuspendXCommand.execute(SuspendXCommand.java:66)
>       ... 8 more
> Caused by: <openjpa-2.1.0-r422266:1071316 nonfatal store error> 
> org.apache.openjpa.persistence.EntityNotFoundException: The instance of type 
> "class org.apache.oozie.WorkflowJobBean" with oid 
> "0000000-120827035717784-oozie-jenk-W" no longer exists in the data store.  
> This may mean that you deleted the instance in a separate transaction, but 
> this context still has a cached version.
> FailedObject: 
> org.apache.oozie.WorkflowJobBean-0000000-120827035717784-oozie-jenk-W
>       at 
> org.apache.openjpa.kernel.StateManagerImpl.loadFields(StateManagerImpl.java:3062)
>       at 
> org.apache.openjpa.kernel.DetachedStateManager.attach(DetachedStateManager.java:163)
>       at 
> org.apache.openjpa.kernel.AttachManager.attach(AttachManager.java:251)
>       at 
> org.apache.openjpa.kernel.AttachManager.attach(AttachManager.java:104)
>       at org.apache.openjpa.kernel.BrokerImpl.attach(BrokerImpl.java:3429)
>       at 
> org.apache.openjpa.kernel.DelegatingBroker.attach(DelegatingBroker.java:1206)
>       at 
> org.apache.openjpa.persistence.EntityManagerImpl.merge(EntityManagerImpl.java:869)
>       at 
> org.apache.oozie.executor.jpa.BulkUpdateInsertJPAExecutor.execute(BulkUpdateInsertJPAExecutor.java:92)
>       ... 11 more
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to