Skip to content

Error: 1228 - error during validation of incoming VPackObject index table is out of bounds #82

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

Closed
laihuei-n4 opened this issue Dec 8, 2016 · 9 comments
Assignees
Labels
Milestone

Comments

@laihuei-n4
Copy link

Hi, I was using arangodb-java-driver 4.1.3 to create vertexes in ArangoDB with the method: com.arangodb.ArangoCollection.insertDocuments(Collection values).

In some cases, it worked well but sometimes it throws the exception below:

...
Caused by: com.arangodb.ArangoDBException: Response: 400, Error: 1228 - error during validation of incoming VPackObject index table is out of bounds
at com.arangodb.internal.velocystream.Communication.checkError(Communication.java:104)
at com.arangodb.internal.velocystream.CommunicationSync.execute(CommunicationSync.java:122)
at com.arangodb.internal.velocystream.CommunicationSync.execute(CommunicationSync.java:42)
at com.arangodb.internal.ArangoExecutorSync.execute(ArangoExecutorSync.java:58)
at com.arangodb.ArangoCollection.insertDocuments(ArangoCollection.java:115)
...

The class I used for objects to store contains one field of long type. If I change the type to String, it works fine. Any idea?

@mvollmary
Copy link

Hi, can you please post one of the failing objects here?

Thanks & Best
Mark

@laihuei-n4
Copy link
Author

I am not sure which objects causing the failure. Each time, the method insertDocuments is invoked for one chunk of 100 objects. Each object in ArangoDB UI looks like below. If I change long1 type from long to String, it works without the exception.

map1		{2}
list1		[4]
    string1	:	string-foo
    long1	:	71733115603202

@mvollmary
Copy link

Ok, thanks. I think the problem not only belongs to the long. As I see your objects contains additional fields. Can you post the Java code of your POJO and maybe a snippet of the initialization with some data?

Thanks

@laihuei-n4
Copy link
Author

The exceptions are observed again even without data of long type. I am doing some testing to figure it out.

@miguel-porto
Copy link
Contributor

I've got the very same issue with updateDocument:
arangodb/arangodb#2226

@mvollmary
Copy link

It could be that this bug is already fixed in the actual 4.1.4-SNAPSHOT. Maybe you both can test it with your cases. Please let me know if this works. If it fixes the issue I will release a new version of the driver as soon as possible.

To get the snapshot with maven add the staging repository of oss.sonatype.org to your pom.xml:

<repositories>
  <repository>
    <id>arangodb-snapshots</id>
    <url>https://oss.sonatype.org/content/groups/staging</url>
  </repository>
</repositories>

Thanks & Best
Mark

@laihuei-n4
Copy link
Author

After replacing 4.1.3 with 4.1.4-SNAPSHOT version, the issue doesn't exist in my test case. I have no idea what the root cause is and if this issue is fixed completely. Will continue observing. Thanks!

@miguel-porto
Copy link
Contributor

I confirm: fixed with this version! ;-)

@mvollmary mvollmary added the bug label Dec 19, 2016
@mvollmary mvollmary added this to the 4.1.4 milestone Dec 19, 2016
@mvollmary mvollmary self-assigned this Dec 19, 2016
@mvollmary
Copy link

Ok, Thanks. I released version 4.1.4 with the fix.

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

No branches or pull requests

3 participants