| Anonymous | Login | Signup for a new account | 11-04-2025 10:47 PST |
| Main | My View | View Issues | Change Log | Docs |
| Viewing Issue Advanced Details [ Jump to Notes ] | [ View Simple ] [ Issue History ] [ Print ] | ||||||||
| ID | Category | Severity | Reproducibility | Date Submitted | Last Update | ||||
| 0002997 | [Hessian] | minor | always | 10-08-08 11:57 | 10-14-08 15:05 | ||||
| Reporter | emil | View Status | public | ||||||
| Assigned To | |||||||||
| Priority | normal | Resolution | fixed | Platform | |||||
| Status | closed | OS | |||||||
| Projection | none | OS Version | |||||||
| ETA | none | Fixed in Version | 3.2.1 | Product Version | 3.2.1 | ||||
| Product Build | |||||||||
| Summary | 0002997: Multiple outstanding requests with Hessian Flex fail | ||||||||
| Description |
(Rep. by Leonid Geller) Specifically, if I send request A(x), and while it is being processed on the +server side, send request A(y) (same operation, different parameters), I will +get back successful response to A(y), while response to A(x) will fail with +trace output: "Unknown stream completed: ..." message (line 162 in HessianOperation.as) Looks like a classic "collision on a key" error, where the second request +overrides the metadata of the first; however looking through the Hessian code, +I could not spot the error. Perhaps it has to do with using URLStream instance +as key to storing the tokens?... |
||||||||
| Steps To Reproduce | |||||||||
| Additional Information | |||||||||
| Attached Files | |||||||||
|
|
|||||||||
| Mantis 1.0.0rc3[^]
Copyright © 2000 - 2005 Mantis Group
28 total queries executed. 25 unique queries executed. |