[QFJ-180] acceptor and initiator on localhost; fromAdmin() callback is not activated Created: 21/May/07 Updated: 07/Jun/07 Resolved: 07/Jun/07 |
|
| Status: | Closed |
| Project: | QuickFIX/J |
| Component/s: | Engine |
| Affects Version/s: | 1.1.0 |
| Fix Version/s: | None |
| Type: | Other | Priority: | Default |
| Reporter: | Thomas Hügel | Assignee: | Steve Bate |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Description |
|
Hello, i tested my fixengine by creating an acceptor and an initiator session on the same machine. the initiator is configured to login to the acceptor session. They had different sequence numbers, so the logout() callback from initiator session is getting called. But the fromAdmin() callback is never activated. That´s confusing, because when initiating a session to an remote fix engine this works, I use to catch the fromAdmin() callback and reset the sequencenumbers by reading the remote message sequencenumber; internally it does not work. Why ?. Regards |
| Comments |
| Comment by Steve Bate [ 25/May/07 ] |
|
I don't know of any reason why this would behave differently if the initiator and acceptor are on the same machine, or even in the same JVM. I assume the automatic logout is caused by the incoming sequence number being too low. The doTargetTooLow() method in the Session generates the logout. The logout is sent using the sendRaw() method which performs the callback. Is there any possibility you are seeing a thread deadlock? You could look at a thread dump to find out. Java 6 will automatically identify deadlocks in the thread dump. |