Thursday, May 13, 2010
Wednesday, May 5, 2010
Such a rare incident occured recently when we detected an optimistic lock exception in one of the WebServices under very specific caller scenarios on one of our integration test environment.
However, the developer could not reproduce the error on his workstation and although he was already running a newer version of the code, he was actually right.
It turned out the problem occurred on a clustered environment only where several containers and nodes are running in parallel. Lesson learnt: It doesn't need to be the programmer who broke a piece of software. Sometimes other influences lead the software to behave different. Here it was the environment in which the software was running.