That sounds like a very odd issue, as each storm worker runs within an independent JVM. Are you putting all your classes in a single jar file (that you upload to storm)? Is there any chance your build system is not including the newest versions? Can you open the jar file and verify that the correct versions are there?
--Tom On Mon, Aug 25, 2014 at 10:02 AM, Vikas Agarwal <vi...@infoobjects.com> wrote: > Are you killing the topology before uploading new one? > > > On Mon, Aug 25, 2014 at 9:26 PM, Jason Kania <jason.ka...@ymail.com> > wrote: > >> Hello, >> >> I would like to know if anybody knows how to prevent Storm from caching a >> previous version of the classes making up a topology. I am hitting problems >> where Storm is running old versions of my classes instead of the ones in >> the currently supplied jar file. I am having to include version numbers in >> the names of my classes to get the desired code to run. >> >> Thanks, >> >> Jason >> > > > > -- > Regards, > Vikas Agarwal > 91 – 9928301411 > > InfoObjects, Inc. > Execution Matters > http://www.infoobjects.com > 2041 Mission College Boulevard, #280 > Santa Clara, CA 95054 > +1 (408) 988-2000 Work > +1 (408) 716-2726 Fax > >
