GetObject of a singleton crash in multi-threading

[Cristiano Simionato]

In case of use GetObject for a singleton by a multi-threading access, sometime there is an exception while execute the instruction
"singletonsInCreation.Remove(name);" in Spring.Objects.Factory.Support.AbstractObjectFacto ry.AfterSingletonCreation because the Remove(string key) of the OrderedDictionary class call the RemoveAt(int index) with the index of the key, but two concurrent Remove could change the index generating an Index out of range inside the RemoveAt.

For now, I have resolved with a lock on singletonsInCreation inside the BeforeSingletonCreation and AfterSingletonCreation.

Bye, bye.
Cristiano.

[javajunky]

I also get this (well actually I believe that I see evidence of this occurring) in that I (intermittently) end up with errors from spring telling me that Objects are in creation, possibly caused by a cyclic reference.. however the beans involved don't seem to have any cyclic references, and the problem appears to be that they weren't correctly removed from the singletonsInCreation internal variable.

Since I am already extendind the WebApplicationContext, I am looking at overriding the method that returns the internal ObjectFactory and replacing the implementation with one that has a course-grain lock