I am working with the "ordermatch" and "tradeclient" sample =
applications. I have changed the samples to log the messages that are =
sent/received for each of the 4 events in both apps (from/to Admin/App).
When I start both of them initially, they connect with each other and =
work correctly. However, if I disconnect the client and remove its =
sequence numbers and message files and then try to reconnect it takes a =
long time for the Logon to occur. =20
The client starts sending logon requests (MsgType=3DA) to the server =
with a sequence number starting at 1 and incrementing with each attempt. =
The server keeps dropping the connection until a message with the =
expected sequence number has been received. The client will also drop =
the socket once the server drops it. This causes Logoff events in both =
the client and server to fire.
Then, in the "block"/"onTimeout" loop of the initiator, the client will =
try to re-establish the connection after 30 events. Once the connection =
is re-established, the client will send a logon with the next sequence =
number.
During this process, there are no Application level events that are =
fired (toAdmin, fromAdmin) on the server, except the Logout event. The =
events on the client are the "toAdmin" for the logon request =
(MsgType=3DA) and a "Logout" event. =20
> Is there a way to have the client initiate the conversation with a =
logon that resets the sequence numbers? I believe that this would be =
the preferred course of action if the recovery files are not found.
> Is there another way to speed up this logon or to have more control of =
the process from the application?
Any help is much appreciated.
Thanks,
Sean Castette
----------------------------
GetCo
(312) 242-4605
|
