Exception in client when cosmosDb response headerSize > 8192 about azure-cosmosdb-java HOT 5 CLOSED

Hi @owennewo thank you for reporting this here.
I wonder if you captured the response header and what hits the header limit in your case.
Is it the continuation token in header response which hits the limit?

from azure-cosmosdb-java.

yes - its the continuation header response.

• response_header.txt - contains the contents of AppendableCharSequence seq variable at the point the exception was thrown (HttpObjectDecoder.java:839)
• stack.txt - is the exceptions stack
• sample.txt - provides a summary of the java I'm invoking

The query is hitting a partitioned cosmosdb. I'm not providing a partition key, instead I've set enableCrossPartitionQuery=true. I'm guessing these types of queries can have large continuation tokens!

from azure-cosmosdb-java.

@owennewo the fix is as you suggested, we should set higher header size limit.

Are you interested in sending a Pull Request?

We will merge your contribution to our source code if you do so. :-)

from azure-cosmosdb-java.

@moderakh - there is a pull request but its failed due to travice / CI

Caused by: java.lang.IllegalArgumentException: Empty key
[ERROR] at javax.crypto.spec.SecretKeySpec.<init>(SecretKeySpec.java:96)

I've manually tested the code.

from azure-cosmosdb-java.

@owennewo please ignore the failure that's fine. The reason the travis build is failing for you is for public PRs Travis (due to security reasons) doesn't resolve secret key for integration tests. We will look into that later.

Thanks for reporting the header issue, and your contribution 👍

from azure-cosmosdb-java.