If you are running topology with debug true, I guess there would be the command used to launch the workers in supervisor.log. Check it, it may contain the clue to the wrong classpath. You can try running the that command directly from console to further debug the issue.
On Tue, Aug 26, 2014 at 9:00 AM, Jason Kania <jason.ka...@ymail.com> wrote: > Thanks for the response. > > I checked and didn't see any errors in the nimbus log. It is hard to tell > exactly, but it seems that the classes being used vary over time and are > one or more versions behind the current ones. To me it makes sense that it > is something sneaking into the classpath, but as of yet, I do not know how. > > ------------------------------ > *From:* Vikas Agarwal <vi...@infoobjects.com> > *To:* user@storm.incubator.apache.org; Jason Kania <jason.ka...@ymail.com> > > *Sent:* Monday, August 25, 2014 10:57:19 PM > > *Subject:* Re: Preventing storm from caching classes > > You can check if kill operation is dumping any error in nimbus.log. It > might be the case that it is unable to delete the jar somehow. Further, are > you always seeing the immediate previous version of your classes on > deployment of new one OR it is quite old version of the same? In later > case, it might be due to some previous jar being present in storm lib or > somewhere else from where it is coming into the classpath. > > > > > On Mon, Aug 25, 2014 at 11:45 PM, Jason Kania <jason.ka...@ymail.com> > wrote: > > I am killing the topology. I can even kill storm and the result remains > the same once storm is relaunched. > > Jason > > ------------------------------ > *From:* Vikas Agarwal <vi...@infoobjects.com> > *To:* user@storm.incubator.apache.org; Jason Kania <jason.ka...@ymail.com> > > *Sent:* Monday, August 25, 2014 12:02:25 PM > > *Subject:* Re: Preventing storm from caching classes > > 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 > > > > > > -- > 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 > > > -- 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
