Re: connect in 0.11.0.0 warnings due to class not found exceptions

Good to hear! gson is used by org.reflections Cheers, Konstantine On Thu, Jul 6, 2017 at 10:03 PM, Koert Kuipers wrote: > i did not have log4j.logger.org.reflections=ERROR, because i didnt update > my log4j files yet. i will do this now. > > connect seems to start up fine.

Re: connect in 0.11.0.0 warnings due to class not found exceptions

i did not have log4j.logger.org.reflections=ERROR, because i didnt update my log4j files yet. i will do this now. connect seems to start up fine. i still wonder why its searching for gson. like... where does it get the idea for the start searching for gson? i dont use gson and neither does

Re: connect in 0.11.0.0 warnings due to class not found exceptions

Hi Koert, these warnings appear to be produced during the class scanning that Connect is performing when it's starting up. Connect is using org.reflections to discover plugins (Connectors, Transformations, Converters) in the various locations that it's configured to search for plugins. (such

connect in 0.11.0.0 warnings due to class not found exceptions

i just did a test upgrade to kafka 0.11.0.0 and i am seeing lots of ClassNotFoundException in the logs for connect-distributed upon startup, see below. is this expected? kind of curious why its looking for say gson while gson jar is not in libs folder. best, koert [2017-07-06 22:20:41,844] INFO