This exception is related to the pack200 -m option, which alters class file timestamps.
Do clojure class loaders depend on class file timestamps? On Monday, December 8, 2014 9:15:57 AM UTC-8, Brian Craft wrote: > > Assuming this is something to do with class loaders going wrong, how would > I approach finding the code paths involved? Could I identify where the > class is being loaded; set breakpoints at those places to get the stack > traces? Something else? > > In my case it seems to be triggered by a type hint on a function argument > that is a record. > > On Sunday, December 7, 2014 11:46:01 AM UTC-8, Brian Craft wrote: >> >> Not sure if I followed the non-interactive case. Is it just >> 1) deftype or defrecord in one file >> 2) import the class in a different file >> 3) AOT compile (e.g. uberjar)? >> >> On Saturday, December 6, 2014 11:07:36 PM UTC-8, Ambrose >> Bonnaire-Sergeant wrote: >>> >>> Perhaps this issue is biting you >>> http://dev.clojure.org/jira/browse/CLJ-979 >>> >>> Thanks, >>> Ambrose >>> >>> On Sat, Dec 6, 2014 at 5:22 PM, Brian Craft <craft...@gmail.com> wrote: >>> >>>> Yes, I know. ;) In this case it's happening with an uberjar, not with >>>> the repl. I do "java -jar myapp.jar", and later, while it is processing >>>> data, get this exception. No repl involved. >>>> >>>> >>>> On Saturday, December 6, 2014 2:02:01 PM UTC-8, juan.facorro wrote: >>>>> >>>>> Hi Brian, >>>>> >>>>> This problem usually happens when working on the REPL and you redefine >>>>> a record or type (derecord and deftype), but there are still some >>>>> existing >>>>> instances lying around, that belong to the previous definition of that >>>>> same >>>>> type. >>>>> >>>>> See this thread for more information: https://groups. >>>>> google.com/forum/#!msg/clojure/N2ivUM8bvB8/xgiFVtsXKnkJ >>>>> >>>>> Cheers, >>>>> >>>>> Juan >>>>> >>>>> On Saturday, December 6, 2014 5:55:23 PM UTC-3, Brian Craft wrote: >>>>>> >>>>>> I'm experimenting with jwrapper, and am getting runtime exceptions >>>>>> like this, due to some jar manipulation that it's doing. I know one of >>>>>> the >>>>>> steps is pack200, however running pack200 manually doesn't create these >>>>>> issues. >>>>>> >>>>>> Anyone have suggestions for debugging this? I've seen this type of >>>>>> error countless times in clojure, but only when reloading interactively. >>>>>> This is the first time I've see it when running an uberjar. >>>>>> >>>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups "Clojure" group. >>>> To post to this group, send email to clo...@googlegroups.com >>>> Note that posts from new members are moderated - please be patient with >>>> your first post. >>>> To unsubscribe from this group, send email to >>>> clojure+u...@googlegroups.com >>>> For more options, visit this group at >>>> http://groups.google.com/group/clojure?hl=en >>>> --- >>>> You received this message because you are subscribed to the Google >>>> Groups "Clojure" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to clojure+u...@googlegroups.com. >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> >>> -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
