Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No response due to the file size over the default MaxBufferLength of PipeStream #1045

Closed
starMagic opened this issue Nov 15, 2022 · 1 comment · Fixed by #1399
Closed

No response due to the file size over the default MaxBufferLength of PipeStream #1045

starMagic opened this issue Nov 15, 2022 · 1 comment · Fixed by #1399

Comments

@starMagic
Copy link

The default MaxBufferLength of PipeStream is _maxBufferLength = 200 * 1024 * 1024
The issue occurs when there is a file in linux, whose sizes are over the default MaxBufferLength.
Steps:

  1. Given a JsonData1.txt, whose sizes are 210MB ( > 200MB), and a JsonData2.txt, whose sizes are 190MB (< 200MB)
  2. Copy both JsonData1.txt and JsonData2.txt into /test/ in your linux.
  3. Test the JsonData by attached test.zip file.
  4. Config commandtext= "cat /test/JsonData1.txt" in app.config, and config other items.
  5. Run it, then you will get a time out issue. Actually, it should spend about 17s, if you change _maxBufferLength = 300 * 1024 * 1024
  6. Config commandtext= "cat /test/JsonData2.txt" in app.config.
  7. Run it, then you will get an available timespan.

Test.zip

@starMagic
Copy link
Author

Hi guys, any comment's here?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant