Quantcast

Logon issue from trading platform to quickfixj

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Logon issue from trading platform to quickfixj

Jans99
QuickFIX/J Documentation: http://www.quickfixj.org/documentation/
QuickFIX/J Support: http://www.quickfixj.org/support/



Hello,
please see the details below, any advice would be very much appreciated.


From: Basu, Anish <[hidden email]>;
To: <[hidden email]>;
Subject: ps
Sent: Thu, Jun 23, 2016 12:43:08 AM

Hello 
I am having difficult in sending FIX messages from a Trading Platform to acceptor in QUICKFIXJ

As per the logs, i can see

1. Successfully called onCreate for sessionId ---->>>: FIX.4.2:MBT->FIXCLIENT2
2. MINA session created
3. After that, lots of - Unknown session ID during logon and
4. Finally as because logon is not successful, my 35=D messages are not getting accepted, and i could see the below message
    Ignoring non-logon message before session establishment


My acceptor config file is like this:

[DEFAULT]
SocketConnectHost=127.0.0.1
SocketAcceptPort=11111
SocketReuseAddress=Y
FileLogPath=log
FileStorePath=c:\fixfiles
DataDictionary=C:\code\workspace\FIXServer\FIX42.xml
BeginString=FIX.4.2

[SESSION]
SenderCompID=MBT
TargetCompID=FIXCLIENT2
ConnectionType=acceptor
StartTime=00:00:00
EndTime=00:00:00

I don't have any config for initiator.
My understanding is that as because the Trading Platform is creating and sending FIX messages over a TCP port (in my case its 11111 [sample]), so the acceptor will read from the same port and will call the fromApp() method to process order request.

Sorry i am getting confused, so please advice.

Below are the entries from the log.
--------------------------------------------
Jun 23, 2016 9:27:35 AM quickfix.SessionSchedule <init>
??: [FIX.4.2:MBT->FIXCLIENT2] daily, 00:00:00-UTC - 00:00:00-UTC
<20160623-00:27:35, FIX.4.2:MBT->FIXCLIENT2, event> (Session FIX.4.2:MBT->FIXCLIENT2 schedule is daily, 00:00:00-UTC - 00:00:00-UTC)
<20160623-00:27:35, FIX.4.2:MBT->FIXCLIENT2, event> (Session state is not current; resetting FIX.4.2:MBT->FIXCLIENT2)
<20160623-00:27:35, FIX.4.2:MBT->FIXCLIENT2, event> (Created session: FIX.4.2:MBT->FIXCLIENT2)
Successfully called onCreate for sessionId ---->>>: FIX.4.2:MBT->FIXCLIENT2
Jun 23, 2016 9:27:35 AM quickfix.mina.SessionConnector startSessionTimer
??: SessionTimer started
Jun 23, 2016 9:27:35 AM quickfix.mina.NetworkingOptions logOption
??: Socket option: SocketReuseAddress=true
Jun 23, 2016 9:27:35 AM quickfix.mina.NetworkingOptions logOption
??: Socket option: SocketTcpNoDelay=true
Jun 23, 2016 9:27:35 AM quickfix.mina.NetworkingOptions logOption
??: Socket option: SocketSynchronousWrites=false
Jun 23, 2016 9:27:35 AM quickfix.mina.NetworkingOptions logOption
??: Socket option: SocketSynchronousWriteTimeout=30000
Jun 23, 2016 9:27:35 AM quickfix.mina.acceptor.AbstractSocketAcceptor startAcceptingConnections
??: Listening for connections at 0.0.0.0/0.0.0.0:11111 for session(s) [FIX.4.2:MBT->FIXCLIENT2]
type #quit to quit
Jun 23, 2016 9:27:39 AM quickfix.mina.acceptor.AcceptorIoHandler sessionCreated
??: MINA session created: /127.0.0.1:18573
Jun 23, 2016 9:27:39 AM quickfix.mina.acceptor.AcceptorIoHandler sessionCreated
??: MINA session created: /127.0.0.1:18574
<20160623-00:27:39, FIX.4.2:MBT->FIXCLIENT2, incoming> (8=FIX.4.2 9=68 35=A 98=0 108=15 49=FIXCLIENT2 56=MBT 34=5 52=20160623-00:27:39 10=034 )
Jun 23, 2016 9:27:39 AM quickfix.mina.acceptor.AcceptorIoHandler processMessage
??: Unknown session ID during logon: FIX.4.2:->FIXCLIENT2 cannot be found in session list [FIX.4.2:MBT->FIXCLIENT2] (connecting from /127.0.0.1:18574 to /127.0.0.1:11111)
<20160623-00:27:39, FIX.4.2:MBT->FIXCLIENT2, incoming> (8=FIX.4.2 9=68 35=A 98=0 108=15 49=FIXCLIENT2 56=MBT 34=7 52=20160623-00:27:39 10=036 )
Jun 23, 2016 9:27:39 AM quickfix.mina.acceptor.AcceptorIoHandler processMessage
??: Unknown session ID during logon: FIX.4.2:->FIXCLIENT2 cannot be found in session list [FIX.4.2:MBT->FIXCLIENT2] (connecting from /127.0.0.1:18573 to /127.0.0.1:11111)
Jun 23, 2016 9:27:41 AM quickfix.mina.acceptor.AcceptorIoHandler sessionCreated
??: MINA session created: /127.0.0.1:18579
<20160623-00:27:41, FIX.4.2:MBT->FIXCLIENT2, incoming> (8=FIX.4.2 9=68 35=A 98=0 108=15 49=FIXCLIENT2 56=MBT 34=1 52=20160623-00:27:41 10=023 )
Jun 23, 2016 9:27:41 AM quickfix.mina.acceptor.AcceptorIoHandler processMessage
??: Unknown session ID during logon: FIX.4.2:->FIXCLIENT2 cannot be found in session list [FIX.4.2:MBT->FIXCLIENT2] (connecting from /127.0.0.1:18579 to /127.0.0.1:11111)
<20160623-00:27:41, FIX.4.2:MBT->FIXCLIENT2, incoming> (8=FIX.4.2 9=182 35=D 11=2049 21=1 526=GLT2049 10080=111 100=T 55=1111 128=BROKER 54=1 40=1 38=100 544=2 10000=4097 10001=150-1004719 58=3878929539 49=FIXCLIENT2 56=MBT 34=2 52=20160623-00:27:41 10=040 )
Jun 23, 2016 9:27:41 AM quickfix.mina.acceptor.AcceptorIoHandler processMessage
??: Ignoring non-logon message before session establishment: 8=FIX.4.2 9=65 35=D 128=BROKER 11=2049 21=1 55=1111 100=T 526=GLT2049 10080=111 10=207
Jun 23, 2016 9:27:45 AM quickfix.mina.acceptor.AcceptorIoHandler sessionCreated
??: MINA session created: /127.0.0.1:18580
Jun 23, 2016 9:27:45 AM quickfix.mina.acceptor.AcceptorIoHandler sessionCreated
??: MINA session created: /127.0.0.1:18582
Jun 23, 2016 9:27:45 AM quickfix.mina.acceptor.AcceptorIoHandler sessionCreated
??: MINA session created: /127.0.0.1:18583
<20160623-00:27:45, FIX.4.2:MBT->FIXCLIENT2, incoming> (8=FIX.4.2 9=68 35=A 98=0 108=15 49=FIXCLIENT2 56=MBT 34=3 52=20160623-00:27:45 10=029 )
Jun 23, 2016 9:27:45 AM quickfix.mina.acceptor.AcceptorIoHandler processMessage
??: Unknown session ID during logon: FIX.4.2:->FIXCLIENT2 cannot be found in session list [FIX.4.2:MBT->FIXCLIENT2] (connecting from /127.0.0.1:18580 to /127.0.0.1:11111)
<20160623-00:27:45, FIX.4.2:MBT->FIXCLIENT2, incoming> (8=FIX.4.2 9=68 35=A 98=0 108=15 49=FIXCLIENT2 56=MBT 34=6 52=20160623-00:27:45 10=032 )
Jun 23, 2016 9:27:45 AM quickfix.mina.acceptor.AcceptorIoHandler processMessage
??: Unknown session ID during logon: FIX.4.2:->FIXCLIENT2 cannot be found in session list [FIX.4.2:MBT->FIXCLIENT2] (connecting from /127.0.0.1:18582 to /127.0.0.1:11111)
<20160623-00:27:45, FIX.4.2:MBT->FIXCLIENT2, incoming> (8=FIX.4.2 9=68 35=A 98=0 108=15 49=FIXCLIENT2 56=MBT 34=7 52=20160623-00:27:45 10=033 )
Jun 23, 2016 9:27:45 AM quickfix.mina.acceptor.AcceptorIoHandler processMessage
??: Unknown session ID during logon: FIX.4.2:->FIXCLIENT2 cannot be found in session list [FIX.4.2:MBT->FIXCLIENT2] (connecting from /127.0.0.1:18583 to /127.0.0.1:11111)
<20160623-00:27:46, FIX.4.2:MBT->FIXCLIENT2, incoming> (8=FIX.4.2 9=56 35=1 49=FIXCLIENT2 56=MBT 34=4 52=20160623-00:27:46 10=240 )
Jun 23, 2016 9:27:46 AM quickfix.mina.acceptor.AcceptorIoHandler processMessage
??: Ignoring non-logon message before session establishment: 8=FIX.4.2 9=56 35=1 34=4 49=FIXCLIENT2 52=20160623-00:27:46 56=MBT 10=240
Jun 23, 2016 9:27:47 AM quickfix.mina.acceptor.AcceptorIoHandler sessionCreated
??: MINA session created: /127.0.0.1:18586
<20160623-00:27:47, FIX.4.2:MBT->FIXCLIENT2, incoming> (8=FIX.4.2 9=68 35=A 98=0 108=15 49=FIXCLIENT2 56=MBT 34=1 52=20160623-00:27:47 10=029 )
Jun 23, 2016 9:27:47 AM quickfix.mina.acceptor.AcceptorIoHandler processMessage
??: Unknown session ID during logon: FIX.4.2:->FIXCLIENT2 cannot be found in session list [FIX.4.2:MBT->FIXCLIENT2] (connecting from /127.0.0.1:18586 to /127.0.0.1:11111)
<20160623-00:27:47, FIX.4.2:MBT->FIXCLIENT2, incoming> (8=FIX.4.2 9=182 35=D 11=2305 21=1 526=GLT2305 10080=111 100=T 55=1111 128=BROKER 54=1 40=1 38=100 544=2 10000=4609 10001=150-1004719 58=3520953624 49=FIXCLIENT2 56=MBT 34=2 52=20160623-00:27:47 10=011 )
Jun 23, 2016 9:27:47 AM quickfix.mina.acceptor.AcceptorIoHandler processMessage
??: Ignoring non-logon message before session establishment: 8=FIX.4.2 9=65 35=D 128=BROKER 11=2305 21=1 55=1111 100=T 526=GLT2305 10080=111 10=197
Jun 23, 2016 9:27:47 AM quickfix.mina.acceptor.AcceptorIoHandler sessionCreated
??: MINA session created: /127.0.0.1:18587
Jun 23, 2016 9:27:47 AM quickfix.mina.acceptor.AcceptorIoHandler sessionCreated
??: MINA session created: /127.0.0.1:18588
<20160623-00:27:47, FIX.4.2:MBT->FIXCLIENT2, incoming> (8=FIX.4.2 9=68 35=A 98=0 108=15 49=FIXCLIENT2 56=MBT 34=6 52=20160623-00:27:47 10=034 )
Jun 23, 2016 9:27:47 AM quickfix.mina.acceptor.AcceptorIoHandler processMessage
??: Unknown session ID during logon: FIX.4.2:->FIXCLIENT2 cannot be found in session list [FIX.4.2:MBT->FIXCLIENT2] (connecting from /127.0.0.1:18587 to /127.0.0.1:11111)
<20160623-00:27:47, FIX.4.2:MBT->FIXCLIENT2, incoming> (8=FIX.4.2 9=68 35=A 98=0 108=15 49=FIXCLIENT2 56=MBT 34=5 52=20160623-00:27:47 10=033 )
Jun 23, 2016 9:27:47 AM quickfix.mina.acceptor.AcceptorIoHandler processMessage
??: Unknown session ID during logon: FIX.4.2:->FIXCLIENT2 cannot be found in session list [FIX.4.2:MBT->FIXCLIENT2] (connecting from /127.0.0.1:18588 to /127.0.0.1:11111)
--------------------------------------------------

Thank you very much,
Regards
Anish


------------------------------------------------------------------------------
Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San
Francisco, CA to explore cutting-edge tech and listen to tech luminaries
present their vision of the future. This family event has something for
everyone, including kids. Get more information and register today.
http://sdm.link/attshape
_______________________________________________
Quickfixj-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/quickfixj-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Logon issue from trading platform to quickfixj

Christoph John
QuickFIX/J Documentation: http://www.quickfixj.org/documentation/
QuickFIX/J Support: http://www.quickfixj.org/support/



Hi,

the incoming messages look wrong. Sender/TargetCompID should be part of the header but they are listed after tags 98 and 108 on the Logon message. The incoming NewOrderSingle messages looks even worse.
Do you assemble these messages yourself? Normally, QuickFIX/J will deal with the needed header tags. Or don't you control the other side of the connection?

Regards,
Chris.


On 23/06/16 02:48, ANISH BASU wrote:
Hello,
please see the details below, any advice would be very much appreciated.


From: Basu, Anish [hidden email];
To: [hidden email];
Subject: ps
Sent: Thu, Jun 23, 2016 12:43:08 AM

Hello 
I am having difficult in sending FIX messages from a Trading Platform to acceptor in QUICKFIXJ

As per the logs, i can see

1. Successfully called onCreate for sessionId ---->>>: FIX.4.2:MBT->FIXCLIENT2
2. MINA session created
3. After that, lots of - Unknown session ID during logon and
4. Finally as because logon is not successful, my 35=D messages are not getting accepted, and i could see the below message
    Ignoring non-logon message before session establishment


My acceptor config file is like this:

[DEFAULT]
SocketConnectHost=127.0.0.1
SocketAcceptPort=11111
SocketReuseAddress=Y
FileLogPath=log
FileStorePath=c:\fixfiles
DataDictionary=C:\code\workspace\FIXServer\FIX42.xml
BeginString=FIX.4.2

[SESSION]
SenderCompID=MBT
TargetCompID=FIXCLIENT2
ConnectionType=acceptor
StartTime=00:00:00
EndTime=00:00:00

I don't have any config for initiator.
My understanding is that as because the Trading Platform is creating and sending FIX messages over a TCP port (in my case its 11111 [sample]), so the acceptor will read from the same port and will call the fromApp() method to process order request.

Sorry i am getting confused, so please advice.

Below are the entries from the log.
--------------------------------------------
Jun 23, 2016 9:27:35 AM quickfix.SessionSchedule <init>
??: [FIX.4.2:MBT->FIXCLIENT2] daily, 00:00:00-UTC - 00:00:00-UTC
<20160623-00:27:35, FIX.4.2:MBT->FIXCLIENT2, event> (Session FIX.4.2:MBT->FIXCLIENT2 schedule is daily, 00:00:00-UTC - 00:00:00-UTC)
<20160623-00:27:35, FIX.4.2:MBT->FIXCLIENT2, event> (Session state is not current; resetting FIX.4.2:MBT->FIXCLIENT2)
<20160623-00:27:35, FIX.4.2:MBT->FIXCLIENT2, event> (Created session: FIX.4.2:MBT->FIXCLIENT2)
Successfully called onCreate for sessionId ---->>>: FIX.4.2:MBT->FIXCLIENT2
Jun 23, 2016 9:27:35 AM quickfix.mina.SessionConnector startSessionTimer
??: SessionTimer started
Jun 23, 2016 9:27:35 AM quickfix.mina.NetworkingOptions logOption
??: Socket option: SocketReuseAddress=true
Jun 23, 2016 9:27:35 AM quickfix.mina.NetworkingOptions logOption
??: Socket option: SocketTcpNoDelay=true
Jun 23, 2016 9:27:35 AM quickfix.mina.NetworkingOptions logOption
??: Socket option: SocketSynchronousWrites=false
Jun 23, 2016 9:27:35 AM quickfix.mina.NetworkingOptions logOption
??: Socket option: SocketSynchronousWriteTimeout=30000
Jun 23, 2016 9:27:35 AM quickfix.mina.acceptor.AbstractSocketAcceptor startAcceptingConnections
??: Listening for connections at 0.0.0.0/0.0.0.0:11111 for session(s) [FIX.4.2:MBT->FIXCLIENT2]
type #quit to quit
Jun 23, 2016 9:27:39 AM quickfix.mina.acceptor.AcceptorIoHandler sessionCreated
??: MINA session created: /127.0.0.1:18573
Jun 23, 2016 9:27:39 AM quickfix.mina.acceptor.AcceptorIoHandler sessionCreated
??: MINA session created: /127.0.0.1:18574
<20160623-00:27:39, FIX.4.2:MBT->FIXCLIENT2, incoming> (8=FIX.4.2 9=68 35=A 98=0 108=15 49=FIXCLIENT2 56=MBT 34=5 52=20160623-00:27:39 10=034 )
Jun 23, 2016 9:27:39 AM quickfix.mina.acceptor.AcceptorIoHandler processMessage
??: Unknown session ID during logon: FIX.4.2:->FIXCLIENT2 cannot be found in session list [FIX.4.2:MBT->FIXCLIENT2] (connecting from /127.0.0.1:18574 to /127.0.0.1:11111)
<20160623-00:27:39, FIX.4.2:MBT->FIXCLIENT2, incoming> (8=FIX.4.2 9=68 35=A 98=0 108=15 49=FIXCLIENT2 56=MBT 34=7 52=20160623-00:27:39 10=036 )
Jun 23, 2016 9:27:39 AM quickfix.mina.acceptor.AcceptorIoHandler processMessage
??: Unknown session ID during logon: FIX.4.2:->FIXCLIENT2 cannot be found in session list [FIX.4.2:MBT->FIXCLIENT2] (connecting from /127.0.0.1:18573 to /127.0.0.1:11111)
Jun 23, 2016 9:27:41 AM quickfix.mina.acceptor.AcceptorIoHandler sessionCreated
??: MINA session created: /127.0.0.1:18579
<20160623-00:27:41, FIX.4.2:MBT->FIXCLIENT2, incoming> (8=FIX.4.2 9=68 35=A 98=0 108=15 49=FIXCLIENT2 56=MBT 34=1 52=20160623-00:27:41 10=023 )
Jun 23, 2016 9:27:41 AM quickfix.mina.acceptor.AcceptorIoHandler processMessage
??: Unknown session ID during logon: FIX.4.2:->FIXCLIENT2 cannot be found in session list [FIX.4.2:MBT->FIXCLIENT2] (connecting from /127.0.0.1:18579 to /127.0.0.1:11111)
<20160623-00:27:41, FIX.4.2:MBT->FIXCLIENT2, incoming> (8=FIX.4.2 9=182 35=D 11=2049 21=1 526=GLT2049 10080=111 100=T 55=1111 128=BROKER 54=1 40=1 38=100 544=2 10000=4097 10001=150-1004719 58=3878929539 49=FIXCLIENT2 56=MBT 34=2 52=20160623-00:27:41 10=040 )
Jun 23, 2016 9:27:41 AM quickfix.mina.acceptor.AcceptorIoHandler processMessage
??: Ignoring non-logon message before session establishment: 8=FIX.4.2 9=65 35=D 128=BROKER 11=2049 21=1 55=1111 100=T 526=GLT2049 10080=111 10=207
Jun 23, 2016 9:27:45 AM quickfix.mina.acceptor.AcceptorIoHandler sessionCreated
??: MINA session created: /127.0.0.1:18580
Jun 23, 2016 9:27:45 AM quickfix.mina.acceptor.AcceptorIoHandler sessionCreated
??: MINA session created: /127.0.0.1:18582
Jun 23, 2016 9:27:45 AM quickfix.mina.acceptor.AcceptorIoHandler sessionCreated
??: MINA session created: /127.0.0.1:18583
<20160623-00:27:45, FIX.4.2:MBT->FIXCLIENT2, incoming> (8=FIX.4.2 9=68 35=A 98=0 108=15 49=FIXCLIENT2 56=MBT 34=3 52=20160623-00:27:45 10=029 )
Jun 23, 2016 9:27:45 AM quickfix.mina.acceptor.AcceptorIoHandler processMessage
??: Unknown session ID during logon: FIX.4.2:->FIXCLIENT2 cannot be found in session list [FIX.4.2:MBT->FIXCLIENT2] (connecting from /127.0.0.1:18580 to /127.0.0.1:11111)
<20160623-00:27:45, FIX.4.2:MBT->FIXCLIENT2, incoming> (8=FIX.4.2 9=68 35=A 98=0 108=15 49=FIXCLIENT2 56=MBT 34=6 52=20160623-00:27:45 10=032 )
Jun 23, 2016 9:27:45 AM quickfix.mina.acceptor.AcceptorIoHandler processMessage


--
Christoph John
Development & Support
Direct: +49 241 557080-28
Mailto:Christoph.John@...



http://www.macd.com


MACD GmbH
Oppenhoffallee 103
D-52066 Aachen
Tel: +49 241 557080-0 | Fax: +49 241 557080-10
 Amtsgericht Aachen: HRB 8151
Ust.-Id: DE 813021663

Geschäftsführer: George Macdonald


take care of the environment - print only if necessary

------------------------------------------------------------------------------
Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San
Francisco, CA to explore cutting-edge tech and listen to tech luminaries
present their vision of the future. This family event has something for
everyone, including kids. Get more information and register today.
http://sdm.link/attshape
_______________________________________________
Quickfixj-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/quickfixj-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Logon issue from trading platform to quickfixj

Jans99
QuickFIX/J Documentation: http://www.quickfixj.org/documentation/
QuickFIX/J Support: http://www.quickfixj.org/support/



Hello Chris,
Thank you.
To be honest, i don't have any control on the incoming FIX messages thats being send by the platform.
But, finally the session issue seems to be resolved, and in the next layer i am facing multiple logons/connection and Msgseqno too high error.

I will post the log soon.
Very much appreciate your mail.

Thanks and Regards
Anish


From: Christoph John <[hidden email]>;
To: ANISH BASU <[hidden email]>; <[hidden email]>;
Subject: Re: Logon issue from trading platform to quickfixj
Sent: Thu, Jun 23, 2016 5:55:25 AM

Hi,

the incoming messages look wrong. Sender/TargetCompID should be part of the header but they are listed after tags 98 and 108 on the Logon message. The incoming NewOrderSingle messages looks even worse.
Do you assemble these messages yourself? Normally, QuickFIX/J will deal with the needed header tags. Or don't you control the other side of the connection?

Regards,
Chris.


On 23/06/16 02:48, ANISH BASU wrote:
Hello,
please see the details below, any advice would be very much appreciated.


From: Basu, Anish <a rel="nofollow" shape="rect" class="moz-txt-link-rfc2396E" ymailto="mailto:anish_basu@monex.co.jp" target="_blank" href="javascript:return"><anish_basu@...>;
To: <a rel="nofollow" shape="rect" class="moz-txt-link-rfc2396E" ymailto="mailto:anishbas@yahoo.com" target="_blank" href="javascript:return"><a rel="nofollow" shape="rect" class="moz-txt-link-rfc2396E" ymailto="mailto:anishbas@yahoo.com" target="_blank" href="javascript:return"><anishbas@...>;
Subject: ps
Sent: Thu, Jun 23, 2016 12:43:08 AM

Hello 
I am having difficult in sending FIX messages from a Trading Platform to acceptor in QUICKFIXJ

As per the logs, i can see

1. Successfully called onCreate for sessionId ---->>>: FIX.4.2:MBT->FIXCLIENT2
2. MINA session created
3. After that, lots of - Unknown session ID during logon and
4. Finally as because logon is not successful, my 35=D messages are not getting accepted, and i could see the below message
    Ignoring non-logon message before session establishment


My acceptor config file is like this:

[DEFAULT]
SocketConnectHost=127.0.0.1
SocketAcceptPort=11111
SocketReuseAddress=Y
FileLogPath=log
FileStorePath=c:\fixfiles
DataDictionary=C:\code\workspace\FIXServer\FIX42.xml
BeginString=FIX.4.2

[SESSION]
SenderCompID=MBT
TargetCompID=FIXCLIENT2
ConnectionType=acceptor
StartTime=00:00:00
EndTime=00:00:00

I don't have any config for initiator.
My understanding is that as because the Trading Platform is creating and sending FIX messages over a TCP port (in my case its 11111 [sample]), so the acceptor will read from the same port and will call the fromApp() method to process order request.

Sorry i am getting confused, so please advice.

Below are the entries from the log.
--------------------------------------------
Jun 23, 2016 9:27:35 AM quickfix.SessionSchedule <init>
??: [FIX.4.2:MBT->FIXCLIENT2] daily, 00:00:00-UTC - 00:00:00-UTC
<20160623-00:27:35, FIX.4.2:MBT->FIXCLIENT2, event> (Session FIX.4.2:MBT->FIXCLIENT2 schedule is daily, 00:00:00-UTC - 00:00:00-UTC)
<20160623-00:27:35, FIX.4.2:MBT->FIXCLIENT2, event> (Session state is not current; resetting FIX.4.2:MBT->FIXCLIENT2)
<20160623-00:27:35, FIX.4.2:MBT->FIXCLIENT2, event> (Created session: FIX.4.2:MBT->FIXCLIENT2)
Successfully called onCreate for sessionId ---->>>: FIX.4.2:MBT->FIXCLIENT2
Jun 23, 2016 9:27:35 AM quickfix.mina.SessionConnector startSessionTimer
??: SessionTimer started
Jun 23, 2016 9:27:35 AM quickfix.mina.NetworkingOptions logOption
??: Socket option: SocketReuseAddress=true
Jun 23, 2016 9:27:35 AM quickfix.mina.NetworkingOptions logOption
??: Socket option: SocketTcpNoDelay=true
Jun 23, 2016 9:27:35 AM quickfix.mina.NetworkingOptions logOption
??: Socket option: SocketSynchronousWrites=false
Jun 23, 2016 9:27:35 AM quickfix.mina.NetworkingOptions logOption
??: Socket option: SocketSynchronousWriteTimeout=30000
Jun 23, 2016 9:27:35 AM quickfix.mina.acceptor.AbstractSocketAcceptor startAcceptingConnections
??: Listening for connections at 0.0.0.0/0.0.0.0:11111 for session(s) [FIX.4.2:MBT->FIXCLIENT2]
type #quit to quit
Jun 23, 2016 9:27:39 AM quickfix.mina.acceptor.AcceptorIoHandler sessionCreated
??: MINA session created: /127.0.0.1:18573
Jun 23, 2016 9:27:39 AM quickfix.mina.acceptor.AcceptorIoHandler sessionCreated
??: MINA session created: /127.0.0.1:18574
<20160623-00:27:39, FIX.4.2:MBT->FIXCLIENT2, incoming> (8=FIX.4.2 9=68 35=A 98=0 108=15 49=FIXCLIENT2 56=MBT 34=5 52=20160623-00:27:39 10=034 )
Jun 23, 2016 9:27:39 AM quickfix.mina.acceptor.AcceptorIoHandler processMessage
??: Unknown session ID during logon: FIX.4.2:->FIXCLIENT2 cannot be found in session list [FIX.4.2:MBT->FIXCLIENT2] (connecting from /127.0.0.1:18574 to /127.0.0.1:11111)
<20160623-00:27:39, FIX.4.2:MBT->FIXCLIENT2, incoming> (8=FIX.4.2 9=68 35=A 98=0 108=15 49=FIXCLIENT2 56=MBT 34=7 52=20160623-00:27:39 10=036 )
Jun 23, 2016 9:27:39 AM quickfix.mina.acceptor.AcceptorIoHandler processMessage
??: Unknown session ID during logon: FIX.4.2:->FIXCLIENT2 cannot be found in session list [FIX.4.2:MBT->FIXCLIENT2] (connecting from /127.0.0.1:18573 to /127.0.0.1:11111)
Jun 23, 2016 9:27:41 AM quickfix.mina.acceptor.AcceptorIoHandler sessionCreated
??: MINA session created: /127.0.0.1:18579
<20160623-00:27:41, FIX.4.2:MBT->FIXCLIENT2, incoming> (8=FIX.4.2 9=68 35=A 98=0 108=15 49=FIXCLIENT2 56=MBT 34=1 52=20160623-00:27:41 10=023 )
Jun 23, 2016 9:27:41 AM quickfix.mina.acceptor.AcceptorIoHandler processMessage
??: Unknown session ID during logon: FIX.4.2:->FIXCLIENT2 cannot be found in session list [FIX.4.2:MBT->FIXCLIENT2] (connecting from /127.0.0.1:18579 to /127.0.0.1:11111)
<20160623-00:27:41, FIX.4.2:MBT->FIXCLIENT2, incoming> (8=FIX.4.2 9=182 35=D 11=2049 21=1 526=GLT2049 10080=111 100=T 55=1111 128=BROKER 54=1 40=1 38=100 544=2 10000=4097 10001=150-1004719 58=3878929539 49=FIXCLIENT2 56=MBT 34=2 52=20160623-00:27:41 10=040 )
Jun 23, 2016 9:27:41 AM quickfix.mina.acceptor.AcceptorIoHandler processMessage
??: Ignoring non-logon message before session establishment: 8=FIX.4.2 9=65 35=D 128=BROKER 11=2049 21=1 55=1111 100=T 526=GLT2049 10080=111 10=207
Jun 23, 2016 9:27:45 AM quickfix.mina.acceptor.AcceptorIoHandler sessionCreated
??: MINA session created: /127.0.0.1:18580
Jun 23, 2016 9:27:45 AM quickfix.mina.acceptor.AcceptorIoHandler sessionCreated
??: MINA session created: /127.0.0.1:18582
Jun 23, 2016 9:27:45 AM quickfix.mina.acceptor.AcceptorIoHandler sessionCreated
??: MINA session created: /127.0.0.1:18583
<20160623-00:27:45, FIX.4.2:MBT->FIXCLIENT2, incoming> (8=FIX.4.2 9=68 35=A 98=0 108=15 49=FIXCLIENT2 56=MBT 34=3 52=20160623-00:27:45 10=029 )
Jun 23, 2016 9:27:45 AM quickfix.mina.acceptor.AcceptorIoHandler processMessage
??: Unknown session ID during logon: FIX.4.2:->FIXCLIENT2 cannot be found in session list [FIX.4.2:MBT->FIXCLIENT2] (connecting from /127.0.0.1:18580 to /127.0.0.1:11111)
<20160623-00:27:45, FIX.4.2:MBT->FIXCLIENT2, incoming> (8=FIX.4.2 9=68 35=A 98=0 108=15 49=FIXCLIENT2 56=MBT 34=6 52=20160623-00:27:45 10=032 )
Jun 23, 2016 9:27:45 AM quickfix.mina.acceptor.AcceptorIoHandler processMessage


--

------------------------------------------------------------------------------
Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San
Francisco, CA to explore cutting-edge tech and listen to tech luminaries
present their vision of the future. This family event has something for
everyone, including kids. Get more information and register today.
http://sdm.link/attshape
_______________________________________________
Quickfixj-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/quickfixj-users
Loading...