Caused by: java.sql.SQLTimeoutException: ORA-01013: user requested cancel of current operation

Many times we encounter this error and think that there might be some JPA issue or network issue. However, the error is pretty explicit in its nature, but still not clear to ring the bell very first time.
As the error says there is a timeout, and since Oracle is saying, we shall accept it.

Another clue is "user requested cancel of current operation". This means that the connection was closed by the application server not the database server, hence it can be safely concluded that application has configured timeouts on transactions at its end.

However, if you feel that this transaction should have been concluded within the application server limits, your doubt might be true.

This problem can arise in case there is a lock on the record being updated by JPA or lock on the table in which JPA is attempting to insert. The lock is most probably being held by some other application, and since application server configuration is on aggressive SLA, the transaction is waiting itself out.


 Exception : org.springframework.dao.QueryTimeoutException: could not execute statement; SQL [n/a]; nested exception is org.hibernate.QueryTimeoutException: could not execute statement  
 at org.springframework.orm.jpa.vendor.HibernateJpaDialect.convertHibernateAccessException(HibernateJpaDialect.java:265)  
  at org.springframework.orm.jpa.vendor.HibernateJpaDialect.translateExceptionIfPossible(HibernateJpaDialect.java:244)  
  at org.springframework.orm.jpa.JpaTransactionManager.doCommit(JpaTransactionManager.java:521)  
  at org.springframework.transaction.support.AbstractPlatformTransactionManager.processCommit(AbstractPlatformTransactionManager.java:761)  
  at org.springframework.transaction.support.AbstractPlatformTransactionManager.commit(AbstractPlatformTransactionManager.java:730)  
  at org.springframework.transaction.interceptor.TransactionAspectSupport.commitTransactionAfterReturning(TransactionAspectSupport.java:504)  
  at org.springframework.transaction.interceptor.TransactionAspectSupport.invokeWithinTransaction(TransactionAspectSupport.java:292)  
  at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:96)  
  at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)  
  at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:92)  
  at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)  
 Caused by: org.hibernate.QueryTimeoutException: could not execute statement  
  at org.hibernate.dialect.Oracle8iDialect$3.convert(Oracle8iDialect.java:532)  
  at org.hibernate.exception.internal.StandardSQLExceptionConverter.convert(StandardSQLExceptionConverter.java:42)  
  at org.hibernate.engine.jdbc.spi.SqlExceptionHelper.convert(SqlExceptionHelper.java:109)  
  at org.hibernate.engine.jdbc.spi.SqlExceptionHelper.convert(SqlExceptionHelper.java:95)  
  at org.hibernate.engine.jdbc.internal.ResultSetReturnImpl.executeUpdate(ResultSetReturnImpl.java:207)  
  at org.hibernate.persister.entity.AbstractEntityPersister.update(AbstractEntityPersister.java:3139)  
  at org.hibernate.persister.entity.AbstractEntityPersister.updateOrInsert(AbstractEntityPersister.java:3013)  
  at org.hibernate.persister.entity.AbstractEntityPersister.update(AbstractEntityPersister.java:3393)  
  at org.hibernate.action.internal.EntityUpdateAction.execute(EntityUpdateAction.java:145)  
  at org.hibernate.engine.spi.ActionQueue.executeActions(ActionQueue.java:582)  
  at org.hibernate.engine.spi.ActionQueue.executeActions(ActionQueue.java:456)  
  at org.hibernate.event.internal.AbstractFlushingEventListener.performExecutions(AbstractFlushingEventListener.java:337)  
  at org.hibernate.event.internal.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:39)  
  at org.hibernate.internal.SessionImpl.flush(SessionImpl.java:1282)  
  at org.hibernate.internal.SessionImpl.managedFlush(SessionImpl.java:465)  
  at org.hibernate.internal.SessionImpl.flushBeforeTransactionCompletion(SessionImpl.java:2963)  
  at org.hibernate.internal.SessionImpl.beforeTransactionCompletion(SessionImpl.java:2339)  
  at org.hibernate.engine.jdbc.internal.JdbcCoordinatorImpl.beforeTransactionCompletion(JdbcCoordinatorImpl.java:485)  
  at org.hibernate.resource.transaction.backend.jdbc.internal.JdbcResourceLocalTransactionCoordinatorImpl.beforeCompletionCallback(JdbcResourceLocalTransactionCoordinatorImpl.java:147)  
  at org.hibernate.resource.transaction.backend.jdbc.internal.JdbcResourceLocalTransactionCoordinatorImpl.access$100(JdbcResourceLocalTransactionCoordinatorImpl.java:38)  
  at org.hibernate.resource.transaction.backend.jdbc.internal.JdbcResourceLocalTransactionCoordinatorImpl$TransactionDriverControlImpl.commit(JdbcResourceLocalTransactionCoordinatorImpl.java:231)  
  at org.hibernate.engine.transaction.internal.TransactionImpl.commit(TransactionImpl.java:65)  
  at org.hibernate.jpa.internal.TransactionImpl.commit(TransactionImpl.java:61)  
  at org.springframework.orm.jpa.JpaTransactionManager.doCommit(JpaTransactionManager.java:517)  
  ... 127 more  
 Caused by: java.sql.SQLTimeoutException: ORA-01013: user requested cancel of current operation  
  at oracle.jdbc.driver.T4CTTIoer11.processError(T4CTTIoer11.java:494)  
  at oracle.jdbc.driver.T4CTTIoer11.processError(T4CTTIoer11.java:446)  
  at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:1054)  
  at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:623)  
  at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:252)  
  at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:612)  
  at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:226)  
  at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:59)  
  at oracle.jdbc.driver.T4CPreparedStatement.executeForRows(T4CPreparedStatement.java:910)  
  at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1119)  
  at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3780)  
  at oracle.jdbc.driver.T4CPreparedStatement.executeInternal(T4CPreparedStatement.java:1343)  
  at oracle.jdbc.driver.OraclePreparedStatement.executeLargeUpdate(OraclePreparedStatement.java:3865)  
  at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:3845)  
  at oracle.jdbc.driver.OraclePreparedStatementWrapper.executeUpdate(OraclePreparedStatementWrapper.java:1061)  
  at org.hibernate.engine.jdbc.internal.ResultSetReturnImpl.executeUpdate(ResultSetReturnImpl.java:204)  
  ... 146 more  
 Caused by: Error : 1013

Comments

Post a Comment

Popular posts from this blog

pandas dataframe add missing date from range in a multi-dimensional structure with duplicate index

This solution demonstrates how to fill in the missing dates in a given range in a multi-index pandas dataframe. The complexity is added by the presence of duplicate dates in the given data, where the date is considered as an index. In case you try to reindex a data frame with duplicate indexes, you will get the following error. ValueError : cannot reindex from a duplicate axis To resolve this situation and to achieve the end goal of refitting dataset with missing indexes, following pseudo code can be used. Read multidimensional data into pandas dataframe (dataset), with date column as an index (only one index). Transform dataframe index created above into datetime index type Create a new dataframe (d) with the required date range, and value of other records as null Append 'd' into 'dataset' Set index of 'dataset' to include more column to create a multi-level index Reindex to 'dataset', and fill the desired value. The example python co
Read more

utility to extract date from text with java

Image
A date pattern recognition algorithm to not only identify date pattern but also fetches probable date in Java date format. This algorithm is very fast and lightweight. The processing time is linear and all dates are identified in a single pass. Algorithm resolves date using tree traverse mechanism. Tree data structures are custom created to build supported date, time and month patterns. Following Trees are used (Note: ^ sign denotes complete pattern) DATE PATTERN TREE Month Pattern Tree (Jan and January both are valid, identified using ^ sign) Time pattern (Identified as suffix to Date, $ sign indicates SPACE character) Tree structures are used in the following algorithm.  Date Part Identification algorithm flowchart Time part identification algorithm flowchart These flow charts are self-explanatory in most part. --> sign is used to denote next match in respective tree structures. The algorithm also acknowledges multipl
Read more