Summary: | IllegalArgumentException thrown by PerMessageDeflate sendMessagePart() | ||
---|---|---|---|
Product: | Tomcat 8 | Reporter: | email.wtam |
Component: | WebSocket | Assignee: | Tomcat Developers Mailing List <dev> |
Status: | RESOLVED FIXED | ||
Severity: | critical | ||
Priority: | P2 | ||
Version: | 8.5.20 | ||
Target Milestone: | ---- | ||
Hardware: | PC | ||
OS: | All |
Description
email.wtam
2017-09-05 13:29:23 UTC
From the stack trace, this appears to be a duplicate of bug 59635. Are you sure compressedPayload.limit() is zero? 1, 2 and 3 are also possibilities. What is really needed here is a test case. Can you provide the String that was being sent at the time? I'll take another look at the code but a reliable test case would make this a lot simpler. I've managed to reproduce this. It is triggered by a zero length message after a non-zero length message when the compression context is retained between messages. I'm starting to think about a fix. Fixed in: - trunk for 9.0.0.M27 onwards - 8.5.x for 8.5.21 onwards - 8.0.x for 8.0.47 onwards - 7.0.x for 7.0.82 onwards |