[Quickfix-developers] QuickFix/J Disconnection error, termination questions, message crack
Brought to you by:
orenmnero
|
From: Andrew W. <awi...@ca...> - 2005-10-29 19:12:34
|
Item 1) After a successful connection and heartbeats established, a
initiator.stop(true) causes an exception. See short logs and messages
below. I can successfully Is this something to be concerned about? See the
logs below...
Item 2) If the initiator does not successfully establish a connection -
what I mean by this is that a logon is rejected because a seqnum is
incorrect, I cannot gracefully exit my application because it appears that
the underlying quickfix process does not respond to initiator.stop() and
gracefully terminate. I must force a System.exit() call to terminate. I am
only concerned that "something" in the quickfix application may fail to
cleanly shutdown and prevent subsequent reconnections.
Item 3) In the QuickFix documentation there appears to be a "crack" method
that is the "Best" implementation of interpretting FromAdmin messages. Does
the QuickFix/J lib have no equivalent at the moment?
I am using Sun's JDK 1.5.0_04 on Linux.
Thanks,
Andrew
<20051029-18:37:20, FIX.4.2:CLIENT->PROVIDER, outgoing>
(8=FIX.4.2~9=70~35=A~34=26~49=CLIENT~52=20051029-18:37:20.864~56=PROVIDER~98
=0~108=30~10=112~)
<20051029-18:37:20, FIX.4.2:CLIENT->PROVIDER, event> (Initiated logon
request)
<20051029-18:37:20, FIX.4.2:CLIENT->PROVIDER, incoming>
(8=FIX.4.2~9=77~35=A~49=PROVIDER~56=CLIENT~43=N~34=44~52=20051029-18:35:40~9
8=0~108=30~141=N~10=188~)
<20051029-18:37:20, FIX.4.2:CLIENT->PROVIDER, event> (Received logon
response)
<20051029-18:37:51, FIX.4.2:CLIENT->PROVIDER, incoming>
(8=FIX.4.2~9=59~35=0~49=PROVIDER~56=CLIENT~43=N~34=45~52=20051029-18:36:10~1
0=111~)
<20051029-18:37:51, FIX.4.2:CLIENT->PROVIDER, outgoing>
(8=FIX.4.2~9=58~35=0~34=27~49=CLIENT~52=20051029-18:37:51.321~56=PROVIDER~10
=069~)
Terminate requested
<20051029-18:37:58, FIX.4.2:CLIENT->PROVIDER, event> (Initiated logout
request)
<20051029-18:37:58, FIX.4.2:CLIENT->PROVIDER, outgoing>
(8=FIX.4.2~9=58~35=5~34=28~49=CLIENT~52=20051029-18:37:58.823~56=PROVIDER~10
=089~)
Exception in thread "Timer-0" java.lang.IllegalStateException: IoProcessor
is not started.
at
net.gleamynode.netty2.IoProcessor.ensureStarted(IoProcessor.java:303)
at
net.gleamynode.netty2.IoProcessor.notifyWriteRequest(IoProcessor.java:292)
at net.gleamynode.netty2.Session.write(Session.java:319)
at net.gleamynode.netty2.Session.write(Session.java:302)
at
quickfix.netty.AbstractSocketInitiator$SessionConnection$QuickFixSessionResp
onder.send(AbstractSocketInitiator.java:415)
at quickfix.Session.send(Session.java:1426)
at quickfix.Session.sendRaw(Session.java:1386)
at quickfix.Session.generateLogout(Session.java:749)
at quickfix.Session.generateLogout(Session.java:740)
at quickfix.Session.next(Session.java:1056)
at
quickfix.netty.AbstractSocketInitiator.processTimerEvent(AbstractSocketIniti
ator.java:210)
at quickfix.SocketInitiator.onTimerEvent(SocketInitiator.java:109)
at
quickfix.netty.AbstractSocketInitiator$SessionConnection.onTimerEvent(Abstra
ctSocketInitiator.java:322)
at
quickfix.netty.AbstractSocketInitiator$SessionTimerTask.run(AbstractSocketIn
itiator.java:150)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)
|