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.

Sign up for GitHub

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

Jump to bottom

IndexOutOfBoundsException in PackingIrodsOutputStream #200

Closed
dkocher opened this issue Oct 26, 2016 · 3 comments
Closed

IndexOutOfBoundsException in PackingIrodsOutputStream #200

dkocher opened this issue Oct 26, 2016 · 3 comments
Assignees
@michael-conway
Labels
bug
Milestone
4.1.10 release su...

Comments

@dkocher
Copy link
Contributor

dkocher commented Oct 26, 2016

With byteBufferSizeMax set to 32768.

java.lang.IndexOutOfBoundsException
    at java.io.ByteArrayOutputStream.write(ByteArrayOutputStream.java:151)
    at org.irods.jargon.core.pub.io.PackingIrodsOutputStream.write(PackingIrodsOutputStream.java:99)
@dkocher dkocher added this to the mx for iRODS 4.2 compatability milestone Nov 7, 2016
michael-conway pushed a commit that referenced this issue Nov 29, 2016
#200 setup for testing of issue
9a0939a
michael-conway pushed a commit that referenced this issue Dec 2, 2016
#200 added a unit test
864d663
@michael-conway
Copy link
Collaborator

added test...passes...will try changing other params. Set jargon props putBufferSize to 32768. Will verify that.

Is there a magic number on the input file size that triggers this?

michael-conway pushed a commit that referenced this issue Dec 2, 2016
#200 added a functional test
52f3e9b
@michael-conway
Copy link
Collaborator

able to reproduce...added a functional test with a lazy walk...

michael-conway pushed a commit that referenced this issue Dec 2, 2016
#200 test testWriteStreamBug200b reproduces with magic numbers
398ff14
michael-conway pushed a commit that referenced this issue Dec 2, 2016
#200 ignore failing for the benefit of CI while resolution..
262168b
michael-conway pushed a commit that referenced this issue Dec 2, 2016
#200 fix, need to do further testing
4b9347f
@michael-conway
Copy link
Collaborator

Will close for now here. Will do further testing under REST and WebDav, but the failing scenario and all of the functional tests now pass (lazy walk of file size and various buffer params).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@michael-conway michael-conway

Labels
bug
Projects
None yet
Milestone
4.1.10 release support
Development

No branches or pull requests
2 participants
@dkocher @michael-conway