chstath / gss

Automatically exported from code.google.com/p/gss
Other
0 stars 0 forks source link

resthandler errors #115

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
Today I got this error in logs:

03 Feb 2012 08:38:49,007 ajp-0.0.0.0-8109-11 ERROR () 
[org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/pithos].[RESTH
andler]] Servlet.service() for servlet RESTHandler threw exception
javax.ejb.EJBTransactionRolledbackException: Transaction rolled back

What is the cause and how I can fix it?
There is server log attached with more errors attached

Original issue reported on code.google.com by ngara...@gmail.com on 3 Feb 2012 at 7:45

Attachments:

GoogleCodeExporter commented 9 years ago
Even more:

03 Feb 2012 11:17:30,775 ajp-0.0.0.0-8109-9 ERROR () 
[org.gss_project.gss.server.webdav.milton.GssOtherUserResource] Unable to get 
user files
javax.ejb.EJBTransactionRolledbackException: Transaction rolled back

Caused by: javax.transaction.RollbackException: 
[com.arjuna.ats.internal.jta.transaction.arjunacore.commitwhenaborted] 
[com.arjuna.ats.internal.jta.transaction.arjunacore.commitwhenaborted] Could 
not commit transaction.
        at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commitAndDisassociate(TransactionImple.java:1435)
        at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.commit(BaseTransaction.java:137)
        at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:75)
        at org.jboss.aspects.tx.TxPolicy.endTransaction(TxPolicy.java:170)

03 Feb 2012 11:17:42,665 ajp-0.0.0.0-8109-3 WARN  () 
[com.arjuna.ats.arjuna.logging.arjLoggerI18N] 
[com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator_2] 
TwoPhaseCoordinator.beforeCompletion - failed for 
com.arjuna.ats.internal.jta.resources.arjunacore.SynchronizationImple@645956c2
javax.persistence.OptimisticLockException

Original comment by ngara...@gmail.com on 3 Feb 2012 at 11:21

GoogleCodeExporter commented 9 years ago
As I mentioned in issue 112, there are times when two threads try to modify the 
same resource (folder or file) directly or indirectly (e.g. one thread modifies 
a file and the other modifies the containing folder) causing 
OptimisticLockExceptions by hibernate which in turn cause the transaction to 
rollback. Gss catches the exceptions and retries the transaction. Therefore, 
there is nothing to be fixed. Probably, we shouldn't log them anyway.

Original comment by chstath on 7 Feb 2012 at 9:02