Just wondering if anyone else has experienced something similar in production, under load, using Cocoon 2.1.4.
We're finding that every once in a while a sax event stream seems to get corrupted. A user may end up with the XML from another user's session, or the wrong snippet of XML from their own session. Other times we get a Stack Overflow exception out of the XML parser, but again, it is infrequent and we have had trouble replicating the problem. Seems to be a concurrency issue from the smell of the symptoms. We're not sure if it's in Cocoon, Avalon, Caching or somewhere else. We're trying to set up replicable test environment, but as of yet have not succeeded. Anyone else seen anything like this? Thanks for any/all help that might point me in the right direction. Andrzej Jan Taramina Chaeron Corporation: Enterprise System Solutions http://www.chaeron.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
