You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by GitBox <gi...@apache.org> on 2019/11/07 03:24:25 UTC
[GitHub] [pulsar] TC-oKozlov commented on issue #5206: TooLongFrameException
: Adjusted frame length exceeds 5253120: 369295620 - discarded => Error
while producing message with TLS on standalone setup
TC-oKozlov commented on issue #5206: TooLongFrameException : Adjusted frame length exceeds 5253120: 369295620 - discarded => Error while producing message with TLS on standalone setup
URL: https://github.com/apache/pulsar/issues/5206#issuecomment-550630916
We are having similar issue in our setup, however in our case we run Pulsar on Kubernetes and trying to have SSL terminate on the load balancer in-front of the Pulsar Proxy, so the client has to send msgs using "pulsar+ssl", but it's not encrypted behind the load balancer, so it's not clear whether proxy and broker should use standard broker port 6650, or TLS broker port 6651?
----------------------------------------------------------------
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:
users@infra.apache.org
With regards,
Apache Git Services