forked from fcrepo4-labs/fcrepo-api-x
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
The jetty producer has fundamental flaws and is incapable of streaming
http requests to endpoints; it relies on an easily-exceeded 2MB buffer. The http4 component supports streaming out of the box, but Exchanges that originate from http requests automatically close streams when their lifecycle ends. This means that certain Camel constructs that terminate exchanges (e.g. recipientList, enrich, etc) must be avoided. This is an undocumented gotcha in Camel. Resolves fcrepo4-labs#76 Squashed commit of the following: commit f2c7250bb1545be7aeb171d504340d2af7795482 Author: Aaron Birkland <[email protected]> Date: Sat Nov 12 23:28:40 2016 -0500 Refactor intercept routes for streaming Http-based exchanges in streaming mode automatically close their connections after theexchange is done. As the "loop" and "enhance" nodes result in the termination of exchanges, the ssubsequent closing of the stream results in "attempt to read from closed stream" exceptions commit be18a35d271d6fe2d7640c57eb168257bb1cc53d Author: Aaron Birkland <[email protected]> Date: Thu Nov 10 19:24:16 2016 -0500 Complete conversion to http4 commit c665825763bd060681e3fd5222d22d6daab74a9b Author: Aaron Birkland <[email protected]> Date: Thu Nov 10 16:34:51 2016 -0500 checkstyle commit 5023908 Author: Elliot Metsger <[email protected]> Date: Wed Nov 9 11:36:26 2016 -0500 Work around limitations with buffering in the jetty component by using http4 instead. This problem manifests itself when API-X proxies the retrieval of large (>2MiB) resources from Fedora. (fcrepo4-labs#77) - Use http4 component instead of jetty in the 'execute-intercept' route - Includes IT demonstrating the issue whe the jetty component is used
- Loading branch information
Showing
12 changed files
with
508 additions
and
55 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.