[JAVA-1632] IllegalArgumentException: response too long: 1701078386 Created: 26/Jan/15 Updated: 19/Oct/16 Resolved: 15/Oct/15 |
|
| Status: | Closed |
| Project: | Java Driver |
| Component/s: | Connection Management |
| Affects Version/s: | 2.12.2 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Critical - P2 |
| Reporter: | Martin W. Kirst | Assignee: | Jeffrey Yemin |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | connection, crash, driver | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
mongo-java-driver v2.12.2 |
||
| Issue Links: |
|
||||||||
| Description |
|
Hi, we're using MongoDB in our financial application with an estimated data size of 130GB. On a daily basis we're observing strange Exceptions (see stacktrace below). The code is pretty simple though. Theres a (Http-)Controller, which accepts a single JSON document and saves it to MongoDB. Each document owns about 30 fields. The actual write operation is done via SpringData's CrudRepository. The strange thing is the number - which seams to be a string! I blindly guess that the MongoDB driver parses the wrong buffer and goes crazy afterwards. Can anyone confirm this?
|
| Comments |
| Comment by Ross Lawley [ 17/Feb/15 ] |
|
Thanks martin_w_kirst closing this ticket and marking fixed. |
| Comment by Martin W. Kirst [ 16/Feb/15 ] |
|
Hi, after updating to 2.12.5 this issue didn't occur anymore. Thanks for your support. Regards |
| Comment by Jeffrey Yemin [ 26/Jan/15 ] |
|
Thanks Martin, please let us know the results. |
| Comment by Martin W. Kirst [ 26/Jan/15 ] |
|
@Jeff Yemin I've read the comments on Indeed, there are multiple connections to mongodb at the same time (in our case). I will update to 2.12.5. |
| Comment by Martin W. Kirst [ 26/Jan/15 ] |
|
Hi, thanks for the quick response. I've scanned the MongoDB log file, but couldn't find any access on the used collection within this timeframe. Regarding Multi-Threading, I've checked the sources but didn't find any ConnectionPool or similar stuff, which may lead to MultiThreading. |
| Comment by Jeffrey Yemin [ 26/Jan/15 ] |
|
Also, please check the description of |
| Comment by Ross Lawley [ 26/Jan/15 ] |
|
Hi martin_w_kirst, Thanks for the bug report - to help understand the cause better I have a couple of questions: Are you seeing anything posted in the MongoDB server logs that could correspond to these errors? |
| Comment by Martin W. Kirst [ 26/Jan/15 ] |
|
I'v forgot to mention, we're using: |