I have a site running an version of the UserApp, 3.6 On of the UserApp
servers starting throwing this error every 5 minutes:

------

Error persisting activity state, scheduling activity for retry.
com.novell.soa.af.impl.activity.ActivityPersistenc eException: Activity
Id [Activity1]: Error persisting activity state.
at
com.novell.soa.af.impl.activity.UserActivity.notif yArrive(UserActivity.java:378)
at
com.novell.soa.af.impl.activity.RunnableActivity.r un(RunnableActivity.java:50)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run Task(ThreadPoolExecutor.java:650)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:675)
at java.lang.Thread.run(Thread.java:595)
Caused by: com.novell.soa.persist.PersistenceException:
org.hibernate.exception.ConstraintViolationExcepti on: Could not execute
JDBC batch update
at
com.novell.soa.persist.HibernateUtil.commit(Hibern ateUtil.java:149)
at
com.novell.soa.af.impl.activity.UserActivity.notif yArrive(UserActivity.java:370)
.... 4 more
Caused by: org.hibernate.exception.ConstraintViolationExcepti on: Could
not execute JDBC batch update
at
org.hibernate.exception.SQLStateConverter.convert( SQLStateConverter.java:71)
at
org.hibernate.exception.JDBCExceptionHelper.conver t(JDBCExceptionHelper.java:43)
at
org.hibernate.jdbc.AbstractBatcher.executeBatch(Ab stractBatcher.java:253)
at
org.hibernate.jdbc.AbstractBatcher.prepareStatemen t(AbstractBatcher.java:92)
at
org.hibernate.jdbc.AbstractBatcher.prepareStatemen t(AbstractBatcher.java:87)
at
org.hibernate.jdbc.AbstractBatcher.prepareBatchSta tement(AbstractBatcher.java:222)
at
org.hibernate.persister.entity.AbstractEntityPersi ster.insert(AbstractEntityPersister.java:2224)
at
org.hibernate.persister.entity.AbstractEntityPersi ster.insert(AbstractEntityPersister.java:2660)
at
org.hibernate.action.EntityInsertAction.execute(En tityInsertAction.java:52)
at
org.hibernate.engine.ActionQueue.execute(ActionQue ue.java:248)
at
org.hibernate.engine.ActionQueue.executeActions(Ac tionQueue.java:232)
at
org.hibernate.engine.ActionQueue.executeActions(Ac tionQueue.java:139)
at
org.hibernate.event.def.AbstractFlushingEventListe ner.performExecutions(AbstractFlushingEventListene r.java:298)
at
org.hibernate.event.def.DefaultFlushEventListener. onFlush(DefaultFlushEventListener.java:27)
at org.hibernate.impl.SessionImpl.flush(SessionImpl.j ava:1000)
at
org.hibernate.impl.SessionImpl.managedFlush(Sessio nImpl.java:338)
at
org.hibernate.transaction.JDBCTransaction.commit(J DBCTransaction.java:106)
at
com.novell.soa.persist.HibernateUtil.commit(Hibern ateUtil.java:147)
.... 5 more
Caused by: java.sql.BatchUpdateException: ORA-00001: unique constraint
(IDMUSER.AFACTIVITYTIMERTASKS_PK) violated

at
oracle.jdbc.driver.DatabaseError.throwBatchUpdateE xception(DatabaseError.java:343)
at
oracle.jdbc.driver.OraclePreparedStatement.execute Batch(OraclePreparedStatement.java:10768)
at
org.jboss.resource.adapter.jdbc.WrappedStatement.e xecuteBatch(WrappedStatement.java:519)
at
org.hibernate.jdbc.BatchingBatcher.doExecuteBatch( BatchingBatcher.java:48)
at
org.hibernate.jdbc.AbstractBatcher.executeBatch(Ab stractBatcher.java:246)
.... 20 more

----

I figured out which workflow it was that was causing this by using the
RequestID. I tried to terminate the workflow in iManager, but I still
get this error every 5 minutes.

I found an entry with this RequestID in the AFACTIVITYTIMERTASKS table
in the DB. I was thinking about removing that entry to see if that
fixes it, but I wasn't sure if that would fix it or if it would cause
even more harm.

Has anyone see this before and would it be safe to remove that line from
the AFACTIVITYTIMERTASKS table? Would it even fix this problem? Would
it cause mass havoc?

Thanks.

Matt


--
matt
------------------------------------------------------------------------
matt's Profile: https://forums.netiq.com/member.php?userid=183
View this thread: https://forums.netiq.com/showthread.php?t=46202