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/03/15 18:01:25 UTC
[GitHub] [pulsar] tcbuzor opened a new issue #3832:
io.netty.handler.codec.TooLongFrameException: Adjusted frame length exceeds
5242880: 369295620 - discarded
tcbuzor opened a new issue #3832: io.netty.handler.codec.TooLongFrameException: Adjusted frame length exceeds 5242880: 369295620 - discarded
URL: https://github.com/apache/pulsar/issues/3832
**Describe the bug**
I installed Apache pulsar 2.3.0 and set up TLS by following the steps described in https://pulsar.apache.org/docs/en/security-tls-transport/
When I use the client in the pulsar distribution, I get the TooLonFrameException
11:36:56.866 [pulsar-io-49-3] INFO org.apache.bookkeeper.mledger.impl.ManagedCursorImpl - [public/functions/persistent/coordinate-participants] Rewind from 120:0 to 120:0
11:37:01.309 [pulsar-io-49-4] INFO org.apache.pulsar.broker.service.ServerCnx - New connection from /10.107.48.30:43
11:37:01.329 [pulsar-io-49-4] WARN org.apache.pulsar.broker.service.ServerCnx - [IP Address:43754] Got exception TooLongFrameException : Adjusted frame length exceeds 5242880: 369295620 - discarded
io.netty.handler.codec.TooLongFrameException: Adjusted frame length exceeds 5242880: 369295620 - discarded
at io.netty.handler.codec.LengthFieldBasedFrameDecoder.fail(LengthFieldBasedFrameDecoder.java:522) ~[io.netty-netty-all-4.1.32.Final.jar:4.1.32.Final]
11:37:01.334 [pulsar-io-49-4] INFO org.apache.pulsar.broker.service.ServerCnx - Closed connection from /10.107.48.30:43754
**To Reproduce**
Steps to reproduce the behavior:
1. Download the Apache pulsar binary from https://pulsar.apache.org/en/download/
Current version (Stable) 2.3.0
2. Unzip the binary and follow the steps for setting up TLS with self signed certificate
3. launch pulsar in standalone mode - ./pulsar standalone
4. start pulsar consumer ./pulsar-client -n 0 -s "TEST" TEST_TOPIC
**Expected behavior**
I expect the consumer to start listening for messages on TEST_TOPIC and the producer should be able to send messages to the TEST_TOPIC
**Screenshots**
If applicable, add screenshots to help explain your problem.
**Desktop (please complete the following information):**
- OS: Red Hat Enterprise Linux 7
**Additional context**
Add any other context about the problem here.
----------------------------------------------------------------
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