[QFJ-421] Session responder lock is too restrictive Created: 20/Mar/09 Updated: 15/Nov/12 Resolved: 20/May/11 |
|
| Status: | Closed |
| Project: | QuickFIX/J |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 1.5.1 |
| Type: | Bug | Priority: | Default |
| Reporter: | Steve Bate | Assignee: | Eric Deshayes |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||||||||||||||
| Description |
|
The Session responder lock uses an interned String which is effectively a class-level lock. This can be made less restrictive by creating a new object instance for each Session. |
| Comments |
| Comment by Andre Mermegas [ 26/May/10 ] |
|
this patch was undone in svn between 926 and 928 by ld1979 , I see, may i suggest simply making the mutex an object instead, this is a lighter and better lock object than String. private final Object responderSync = new Object(); |
| Comment by Steve Bate [ 28/Apr/11 ] |
|
This fix was reverted in Rev #928. |
| Comment by Eric Deshayes [ 29/Apr/11 ] |
|
Fix reapplied in Rev#1026 |