|
Viewing Issue Advanced Details
[ Jump to Notes ]
|
[ View Simple ]
[ Issue History ]
[ Print ]
|
|
ID |
Category |
Severity |
Reproducibility |
Date Submitted |
Last Update |
|
0006168 |
[Resin] |
major |
random |
06-26-18 15:02 |
08-03-18 15:29 |
|
|
Reporter |
mikeb01 |
View Status |
public |
|
|
Assigned To |
ferg |
|
Priority |
normal |
Resolution |
fixed |
Platform |
|
|
Status |
closed |
|
OS |
|
|
Projection |
none |
|
OS Version |
|
|
ETA |
none |
Fixed in Version |
4.0.58 |
Product Version |
4.0.57 |
| |
Product Build |
|
|
|
Summary |
0006168: AsyncServlet Wake-up occasionally looses events |
|
Description |
We use the AsyncServlet specification to implement a streaming style HTTP connection. The with the streaming connection we do not close the connection after each request nor do we time out. With the streaming connection we notice that occasionally that a call to AsyncContext.dispatch() will fail to redispatch the associated servlet. This results in the streaming servlet failing send messages that it should.
This only happens very occasionally. We have an acceptance test run that lasts 25 minutes and runs over Note: 0000070 instances of Resin. The loss of events may happen 1 in every 10 or so runs. |
|
Steps To Reproduce |
|
|
Additional Information |
|
|
|
Attached Files |
|
|
|
Relationships 
