cuzyoucant commented on issue #7960: URL: https://github.com/apache/pulsar/issues/7960#issuecomment-685684259
After some more debugging we found some additional information about the bug. We got it to run in the standalone after disabling TLS connections in the config. It would be quite the hassle to disable all TLS connections in the kubernetes cluster so i can't say if disabling TLS would get it to work in kubernetes. After some digging in the sourcecode i found the part where it is checked if TLS is enabled in the config and depending on that, some other code is executed. With some extra exception handling i am pretty sure the uncaught exception is comming from there. In the file ServiceChannelInitializer.java beginning in line 87 to 116.  If TLS is not enabled with the broker, this part is skipped and the proxy works. If it is enabled this part throws and Exception with message "null" somewhere which is never caught. I hope this helps to identify the problem. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
