Re: New Concurrent modification exception's after storm 0.10.0
So after spending another hour staring at the code, I've realized that we are indeed emitting instances of a List object that is re-used elsewhere in the bolt (doh!) I'm guessing something did change in the framework between 0.9.x and 0.10.x, but its definitely caught me doing something stupid :) Thanks! On Thu, Mar 3, 2016 at 1:01 PM, P. Taylor Goetzwrote: > Hi Stephen, > > Can you provide a stack trace that indicates where this is occurring? > > -Taylor > > > > On Mar 2, 2016, at 1:49 PM, Stephen Powis wrote: > > > > Hey! > > > > Did anything change between storm 0.9.5 and 0.10.0 regarding > ConcurrentModificationExceptions and how they are detected? We've had a > topology running for the last 6months or so and never saw this exception. > > > > After upgrading to Storm 0.10.x which didn't require any changes to our > topology/bolt/business logic, we're now seeing these intermittently and > have been struggling to see where we've gone wrong -- We don't seem to be > modifying values in the emitted tuples anywhere after emitting. > > > > Thanks! > > Stephen > >
Re: New Concurrent modification exception's after storm 0.10.0
Hi Stephen, Can you provide a stack trace that indicates where this is occurring? -Taylor > On Mar 2, 2016, at 1:49 PM, Stephen Powiswrote: > > Hey! > > Did anything change between storm 0.9.5 and 0.10.0 regarding > ConcurrentModificationExceptions and how they are detected? We've had a > topology running for the last 6months or so and never saw this exception. > > After upgrading to Storm 0.10.x which didn't require any changes to our > topology/bolt/business logic, we're now seeing these intermittently and have > been struggling to see where we've gone wrong -- We don't seem to be > modifying values in the emitted tuples anywhere after emitting. > > Thanks! > Stephen signature.asc Description: Message signed with OpenPGP using GPGMail
New Concurrent modification exception's after storm 0.10.0
Hey! Did anything change between storm 0.9.5 and 0.10.0 regarding ConcurrentModificationExceptions and how they are detected? We've had a topology running for the last 6months or so and never saw this exception. After upgrading to Storm 0.10.x which didn't require any changes to our topology/bolt/business logic, we're now seeing these intermittently and have been struggling to see where we've gone wrong -- We don't seem to be modifying values in the emitted tuples anywhere after emitting. Thanks! Stephen