Buffering capacity 1048576 exceeded

See original GitHub issue

When we subscribe platform events from SFDC using EMP connector, sometimes we receive the below error message, does anyone know what is the root cause of error “Buffering capacity 1048576 exceeded”? 2019-08-16 11:53:07,078 WARN [c.i.s.e.lib.EmpConnector] [ HttpClient@153c6041-935910] EMP connector received error message: {failure={exception=java.lang.IllegalArgumentException: Buffering capacity 1048576 exceeded, message={clientId=jr1mvw84q01iegfw6mtlig4fqfm, channel=/meta/connect, id=16376, connectionType=long-polling}, connectionType=long-polling}, channel=/meta/connect, id=16376, successful=false}, will stop and restore the connection.

Issue Analytics

State:
Created 4 years ago
Reactions:4
Comments:6 (1 by maintainers)

Top GitHub Comments

1reaction

edmondopcommented, Jul 20, 2021

@pmeister we figured out on our side that messages are lost by the buffer if you do not provide enough space. It is buffering the streamingAPI messages and this is producing lost notifications if you resubscribe with replayId = -2 and you have a lot of messages in the retention window

0reactions

Ziauddin135commented, Mar 2, 2022

@lmcalpin ,

Can you please help how to set maxMessageSize Map against longPollingTrabsportOptions in properties file?

Thanks

Top Results From Across the Web

java - Buffering capacity 2097152 exceeded from jetty when ...

Buffering capacity 2097152 exceeded from jetty when response is large. Save this question. Show activity on this post. My guess is that this...

Re: [jetty-users] java.lang.IllegalArgumentException - Eclipse

IllegalArgumentException : Buffering capacity exceeded; Next by Date: Re: [jetty-users] how to disable automatic gzip decompression in jetty ...

camel-salesforce - HTTP responses over 4 MB fail

IllegalArgumentException : Buffering capacity 4194304 exceeded at org.eclipse.jetty.client.util.BufferingResponseListener.

Query cannot be completed because the parameter array ...

SingleStoreDB v7.8. ERROR 1956 ER_PARAMETER_CAPACITY_EXCEEDED: Query cannot be completed because the parameter array capacity of 1048576 was exceeded.

Error that the max streaming memory limit has been exceeded

Mule Runtime could not allocate byte buffer because the runtime automatically makes sure that no more than half of the available heap memory ......