Yee, Well then... turn off JRebel and attempt to reproduce the bug... if you can't then it isn't Stripes. Right?
I know its tempting to keep JRebel engaged all the time and I recall the time I hit a bug in JRebel and thought it was one in Stripes... it took me a long time to consider simply turning off JRebel... but if you already suspect JRebel then flip it off and attempt to reproduce. --Nikolaos Yee wrote: > Hi Nokolaos, > > The bug has already been reported to JRebel. Stripes plugin for JRebel was > created by third party, so it could take a while for it to be fixed. > > My concern here is to ascertain whether ConcurrentModificationException error > is > a bug in Stripes - or caused by the bug in JRebel. > > Cheers, > Yee > > > > > ------------------------------------------------------------------------------ > The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: > Pinpoint memory and threading errors before they happen. > Find and fix more than 250 security defects in the development cycle. > Locate bottlenecks in serial and parallel code that limit performance. > http://p.sf.net/sfu/intel-dev2devfeb > _______________________________________________ > Stripes-users mailing list > Stripes-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/stripes-users > > ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ Stripes-users mailing list Stripes-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/stripes-users
