Endless stacktrace in log4j when using TransportClient

NoNodeAvailableException and endless stacktrace in log4j when using TransportClient

Is there any changes to this as I am still seeing these recursive log trace which is causing StackOverFlow error.

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.