davideuler / gss

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

jboss org.hibernate errors?? #112

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
Running jboss server / or two standalone instances for gss service, and every 
now and then errors like attached in log start appearing.
What might be causing them? Is this org.hibernate problem or postgresql 
database problem? How can it be resolved?

Jboss server(s) are running on centos 5 64bit servers.

Caused by: org.hibernate.StaleObjectStateException: Row was updated or deleted 
by another transaction (or unsaved-value mapping was incorrect): 
[org.gss_project.gss.server.domain.Folder#2392]

and 

01 Feb 2012 10:27:15,008 pool-25-thread-1 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@5925bfa
javax.persistence.OptimisticLockException

Regards,
Nikola

Original issue reported on code.google.com by ngara...@gmail.com on 1 Feb 2012 at 9:37

Attachments:

GoogleCodeExporter commented 8 years ago
Normally, you don't need to worry about those. It happens often (especially 
during multiple requests from the webdav client) that two threads try to modify 
the same folder/file. This causes those exceptions. We catch them and retry the 
transaction (Colliding again is of extremely low probability but even then we 
retry again).

Original comment by chstath on 1 Feb 2012 at 10:03

GoogleCodeExporter commented 8 years ago
Well, I am trying to upload around 20k files total over 200GB using bitkinex 
webdav client and I get lots of http 500/503 errors during uploads and slow 
performance. Thats why I was asking if "org.hibernate" has anything to do with 
that...

Original comment by ngara...@gmail.com on 1 Feb 2012 at 10:14

GoogleCodeExporter commented 8 years ago
Webdav clients tend to flood the server with multiple requests. HTTP 500 is 
returned by the web server (not gss) probably because jboss instance(s) are 
busy.

Original comment by chstath on 1 Feb 2012 at 10:24