ConcurrentModificationException

n72 · Post by **n72** » 31 Oct 2010, 23:52

As you can see from the log, they are happening quite often. The body of all my handleRequests are wrapped in a try... catch block which logs anything that gets to the catch. So, I'm quite sure I'd see Exceptions of this type in they were happening in my extension code. So, do you have any idea what this could be? The game play as far as I can tell is unaffected. Is there any way I can get more informative errors with stack traces? Thanks

Exception in ExtensionHandler: java.util.ConcurrentModificationException
2010/10/31 18:00:40.537 - [ WARNING ] [id: 29] (ExtensionHandler.processEvent): Exception in ExtensionHandler: java.util.ConcurrentModificationException
2010/10/31 18:00:40.538 - [ WARNING ] [id: 23] (ExtensionHandler.processEvent): Exception in ExtensionHandler: java.util.ConcurrentModificationException
2010/10/31 18:00:40.537 - [ WARNING ] [id: 36] (ExtensionHandler.processEvent): Exception in ExtensionHandler: java.util.ConcurrentModificationException
2010/10/31 18:00:40.726 - [ WARNING ] [id: 36] (ExtensionHandler.processEvent): Exception in ExtensionHandler: java.util.ConcurrentModificationException
2010/10/31 18:00:40.819 - [ WARNING ] [id: 30] (ExtensionHandler.processEvent): Exception in ExtensionHandler: java.util.ConcurrentModificationException
2010/10/31 18:00:40.918 - [ WARNING ] [id: 23] (ExtensionHandler.processEvent): Exception in ExtensionHandler: java.util.ConcurrentModificationException
2010/10/31 18:00:41.006 - [ WARNING ] [id: 29] (ExtensionHandler.processEvent): Exception in ExtensionHandler: java.util.ConcurrentModificationException
2010/10/31 18:00:41.006 - [ WARNING ] [id: 23] (ExtensionHandler.processEvent): Exception in ExtensionHandler: java.util.ConcurrentModificationException

BigFIsh · Post by **BigFIsh** » 01 Nov 2010, 02:36

See http://forums.smartfoxserver.com/viewtopic.php?t=1603

n72 · Post by **n72** » 01 Nov 2010, 05:06

We're already using ConcurrentHashMap. Moreover, if this were happening in the extension code we created, we would see this logged, since everything is wrapped in a try... catch at the top level which logs everything that gets to it. It looks to me like this is happening somewhere in the SFS core, since it's getting logged by SFS.

I'd just like to know if there's some way we can get more info on the problem so we can track it down.

Post by **Lapo** » 02 Nov 2010, 07:55

Please get in touch with us directly via email. We'll send you some debugging tools. Please include a reference to this thread in the email.