[CAMEL-14424] camel-salesforce - HTTP responses over 4 MB fail

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.0.0
• Fix Version/s: 3.1.0, 3.0.2
• Component/s: camel-salesforce
• Estimated Complexity: Unknown
• Assignee: Unassigned
• Reporter: Jeremy Ross
• Created: 22/Jan/20 14:57
• Updated: 23/Jan/20 05:30
• Resolved: 23/Jan/20 05:29

Description

It appears that any HTTP response from salesforce over 4 MB fails. Responses over 4 MB will be quite common when dealing with file attachments. Pull request to follow.

 

Stacktrace: org.apache.camel.component.salesforce.api.SalesforceException: Unexpected error {200:OK} executing {GET:https://emuedu.my.salesforce.com/services/data/v45.0/sobjects/ContentVersion/0682E00000XXXXXXXX/VersionData}
  at org.apache.camel.component.salesforce.internal.client.AbstractClientBase$1.onComplete(AbstractClientBase.java:201)
  at org.eclipse.jetty.client.ResponseNotifier.notifyComplete(ResponseNotifier.java:196)
  at org.eclipse.jetty.client.ResponseNotifier.notifyComplete(ResponseNotifier.java:188)
  at org.eclipse.jetty.client.HttpReceiver.terminateResponse(HttpReceiver.java:441)
  at org.eclipse.jetty.client.HttpReceiver.terminateResponse(HttpReceiver.java:421)
  at org.eclipse.jetty.client.HttpReceiver.responseContent(HttpReceiver.java:347)
  at org.eclipse.jetty.client.http.HttpReceiverOverHTTP.content(HttpReceiverOverHTTP.java:283)
  at org.eclipse.jetty.http.HttpParser.parseContent(HttpParser.java:1788)
  at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:1518)
  at org.eclipse.jetty.client.http.HttpReceiverOverHTTP.parse(HttpReceiverOverHTTP.java:172)
  at org.eclipse.jetty.client.http.HttpReceiverOverHTTP.process(HttpReceiverOverHTTP.java:135)
  at org.eclipse.jetty.client.http.HttpReceiverOverHTTP.receive(HttpReceiverOverHTTP.java:73)
  at org.eclipse.jetty.client.http.HttpChannelOverHTTP.receive(HttpChannelOverHTTP.java:133)
  at org.eclipse.jetty.client.http.HttpConnectionOverHTTP.onFillable(HttpConnectionOverHTTP.java:155)
  at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:305)
  at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:103)
  at org.eclipse.jetty.io.ssl.SslConnection$DecryptedEndPoint.onFillable(SslConnection.java:427)
  at org.eclipse.jetty.io.ssl.SslConnection.onFillable(SslConnection.java:321)
  at org.eclipse.jetty.io.ssl.SslConnection$2.succeeded(SslConnection.java:159)
  at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:103)
  at org.eclipse.jetty.io.ChannelEndPoint$2.run(ChannelEndPoint.java:117)
  at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.runTask(EatWhatYouKill.java:333)
  at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.doProduce(EatWhatYouKill.java:310)
  at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.tryProduce(EatWhatYouKill.java:168)
  at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.run(EatWhatYouKill.java:126)
  at org.eclipse.jetty.util.thread.ReservedThreadExecutor$ReservedThread.run(ReservedThreadExecutor.java:366)
  at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:781)
  at org.eclipse.jetty.util.thread.QueuedThreadPool$Runner.run(QueuedThreadPool.java:917)
  at java.base/java.lang.Thread.run(Thread.java:834)
Caused by: java.lang.IllegalArgumentException: Buffering capacity 4194304 exceeded
  at org.eclipse.jetty.client.util.BufferingResponseListener.onContent(BufferingResponseListener.java:124)
  at org.eclipse.jetty.client.api.Response$Listener$Adapter.onContent(Response.java:248)
  at org.eclipse.jetty.client.ResponseNotifier.notifyContent(ResponseNotifier.java:133)
  at org.eclipse.jetty.client.ResponseNotifier.notifyContent(ResponseNotifier.java:125)
  at org.eclipse.jetty.client.HttpReceiver.responseContent(HttpReceiver.java:337)
  ... 23 more

Issue Links

• links to: GitHub Pull Request #3505