Issue 326 in glassdb: service vm needs better support for handling commit conflicts

Status: Accepted
Owner: [hidden email]
Labels: Type-Defect Priority-Medium GLASS-Server Version-1.0-beta.8.7

New issue 326 by [hidden email]: service vm needs better support for  
handling commit conflicts
http://code.google.com/p/glassdb/issues/detail?id=326

Johan was having trouble with an unresponsive service vm [1] and was able  
to discover that the issue was related to not handling commit conflicts  
correctly inside the service vm task block[2].

However, finding the problem was difficult because once you get commit  
conflicts, things do not get logged to the object log (without fancy  
footwork) ... also there needs to be some default error handling as well ...

[1]  
http://forum.world.st/seaside-fastcgi-gems-that-no-longer-accept-connections-td4204480.html
[2]  
http://forum.world.st/seaside-fastcgi-gems-that-no-longer-accept-connections-tp4204480p4243735.html

Comment #1 on issue 326 by [hidden email]: service vm needs better  
support for handling commit conflicts
http://code.google.com/p/glassdb/issues/detail?id=326

Johan,

Is this issue covered by Issue #355 or are they separate?

--
You received this message because this project is configured to send all  
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings