[QFJ-432] Trace reason when session gets disconnected Created: 10/Apr/09 Updated: 15/Nov/12 Resolved: 25/Jan/10 |
|
| Status: | Closed |
| Project: | QuickFIX/J |
| Component/s: | Engine |
| Affects Version/s: | 1.4.0 |
| Fix Version/s: | 1.5.0 |
| Type: | Improvement | Priority: | Default |
| Reporter: | Paul-Henri Giraud | Assignee: | Unassigned |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Description |
|
When a session is disconnected (Session.disconnect()), we just get a "<session> disconnected" trace. In some case, the disconnection is a normal behavior (e.g. after a logout), in some other it is not (e.g. socket failure). It is therefore difficult to troubleshot FIX connectors with this lack of information. |
| Comments |
| Comment by Steve Bate [ 25/Jan/10 ] |
|
SVN #928 |