Hey Sascha,
It looks like something is failing when Guice is starting up, but the actual failure is being masked by another Guice failure to generate the appropriate error message which is why the stack trace looks so obscure. There's a similar issue mentioned
here which is happening in the same version of Guice we're using (4.0 beta).
It's likely that Guice is failing because of a bad configuration-based binding somewhere. If you post your common.runtime.properties and runtime.properties for the middle manager, we can see if there's any hints in there as to what is going on. Alternatively (or additionally), it might be worthwhile trying out the the Kafka indexing service tutorial (
http://imply.io/docs/latest/tutorial-kafka-indexing-service.html) which has fairly conservative configurations which might help to rule out other potential causes.
If both of those options don't pan out, there's an open PR to update to Guice 4.1 which will hopefully fix the Guice error so the real exception is visible:
https://github.com/druid-io/druid/pull/3222. Last resort might be generating a build from master with Guice 4.1 and see if that helps clarify what's going on.