Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NoSuchMethodError for org.apache.mesos.Protos$Value$Set.getItemList #33

Closed
oubiwann opened this issue Oct 6, 2016 · 6 comments
Closed
Milestone

Comments

@oubiwann
Copy link
Member

oubiwann commented Oct 6, 2016

This is a new one for me ... I'm not sure what has changed, but I wasn't getting this error last week :-/

(I might have still had an older jar file in my path, which would explain the sudden occurrence.)

When I kick off a new framework and the first resource offer is being processed, I get this error:

Exception in thread "Thread-7" java.lang.NoSuchMethodError: org.apache.mesos.Protos$Value$Set.getItemList()Lcom/google/protobuf/ProtocolStringList;
    at mesomatic.types$fn__819.invokeStatic(types.clj:596)
    at mesomatic.types$fn__819.invoke(types.clj:594)
    at clojure.lang.MultiFn.invoke(MultiFn.java:229)
    at mesomatic.types$fn__929.invokeStatic(types.clj:675)
    at mesomatic.types$fn__929.invoke(types.clj:667)
    at clojure.lang.MultiFn.invoke(MultiFn.java:229)
    at clojure.core$mapv$fn__6953.invoke(core.clj:6627)
    at clojure.core.protocols$iter_reduce.invokeStatic(protocols.clj:49)
    at clojure.core.protocols$fn__6742.invokeStatic(protocols.clj:75)
    at clojure.core.protocols$fn__6742.invoke(protocols.clj:75)
    at clojure.core.protocols$fn__6684$G__6679__6697.invoke(protocols.clj:13)
    at clojure.core$reduce.invokeStatic(core.clj:6545)
    at clojure.core$mapv.invokeStatic(core.clj:6618)
    at clojure.core$mapv.invoke(core.clj:6618)
    at mesomatic.types$fn__1298.invokeStatic(types.clj:1031)
    at mesomatic.types$fn__1298.invoke(types.clj:1024)
    at clojure.lang.MultiFn.invoke(MultiFn.java:229)
    at clojure.core$mapv$fn__6953.invoke(core.clj:6627)
    at clojure.core.protocols$iter_reduce.invokeStatic(protocols.clj:49)
    at clojure.core.protocols$fn__6742.invokeStatic(protocols.clj:75)
    at clojure.core.protocols$fn__6742.invoke(protocols.clj:75)
    at clojure.core.protocols$fn__6684$G__6679__6697.invoke(protocols.clj:13)
    at clojure.core$reduce.invokeStatic(core.clj:6545)
    at clojure.core$mapv.invokeStatic(core.clj:6618)
    at clojure.core$mapv.invoke(core.clj:6618)
    at mesomatic.scheduler$wrap_scheduler$reify__2859.resourceOffers(scheduler.clj:113)

Looking at mesomatic.types, this is the code that seems to be bombing out:

(defmethod pb->data Protos$Value$Set
  [^Protos$Value$Set value-set]
 (set (.getItemList value-set)))

And, indeed, when I look at the Protobuf docs, I don't see this method defined for ProtocolStringList:

I'm not sure if Protos$Value$Set is supposed to be a ProtocolStringList or not ...

@oubiwann
Copy link
Member Author

oubiwann commented Oct 6, 2016

I've actually been running mesomatic 1.0.1-r0 against 1.0.0, so I'm going to download and build a new 1.0.1 before I continue debugging (just in case).

@oubiwann
Copy link
Member Author

oubiwann commented Oct 7, 2016

A new build of 1.0.1 gives me the same error. Will dig into this more tomorrow ...

@oubiwann
Copy link
Member Author

oubiwann commented Oct 7, 2016

Last night while falling asleep, I had the thought that this bug might actually be due to an inadvertent change by a calling function ... one that might now be passing an invalid data type.

If that turns out to be the case, I'll just close this as "invalid" ;-)

@oubiwann
Copy link
Member Author

oubiwann commented Oct 7, 2016

Found an issue (#34, potentially related?) and will test this issue against that fix when it's in place.

@oubiwann
Copy link
Member Author

oubiwann commented Oct 7, 2016

Another issue which may affect this one: #35.

@oubiwann
Copy link
Member Author

oubiwann commented Oct 7, 2016

Sweet -- with fixes in place for the two issues found above, the error for this ticket goes away.

Closing as a symptom, not an actual issue.

@oubiwann oubiwann closed this as completed Oct 7, 2016
@oubiwann oubiwann added this to the 1.0.1 milestone Dec 20, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant