Quantcast

Version 1.6.2 - MessageCracker handler for FIX.5.0SP2

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

Version 1.6.2 - MessageCracker handler for FIX.5.0SP2

thannon
This post was updated on .
I am having trouble with handling FIX.5.0SP2 messages.  I have registered a handler in the following way (tried both with and without the @Handler annotation)...

@Handler
public void onMessage(quickfix.fix50sp2.BusinessMessageReject message, SessionID sessionID)
   throws FieldNotFound, UnsupportedMessageType, IncorrectTagValue
{
      // handler implementation
}

Following is the message conversation (length and checksums are not correct due to substitution of confidential data)

FIXT.1.1:US->THEM: 8=FIXT.1.1|9=80|35=A|34=1|49=US|52=20160419-20:23:18.122|56=THEM|98=0|108=30|141=Y|1137=9|10=078|
FIXT.1.1:US->THEM: 8=FIXT.1.1|9=80|35=A|34=1|49=THEM|52=20160419-20:23:18.635|56=US|98=0|108=30|141=Y|1137=9|10=087|
FIXT.1.1:US->THEM: 8=FIXT.1.1|9=55|35=0|34=2|49=THEM|52=20160419-20:23:48.812|56=US|10=192|
FIXT.1.1:US->THEM: 8=FIXT.1.1|9=55|35=0|34=2|49=US|52=20160419-20:23:48.804|56=THEM|10=193|
FIXT.1.1:US->THEM: 8=FIXT.1.1|9=199|35=W|34=3|49=US|52=20160419-20:23:53.776|56=THEM|22=1|48=549310VL1|167=NONE|460=11|1227=BOND|1500=FEED|268=1|269=1|270=100|423=1|271=9000|272=20160419|273=20:23:47.222|276=I|64=20160421|5637=2|10=210|
FIXT.1.1:US->THEM: 8=FIXT.1.1|9=101|35=j|34=3|49=THEM|52=20160419-20:23:53.820|56=US|45=3|372=W|380=0|58=ERROR_IN_UPDATE_OR_INSERT|10=179|
FIXT.1.1:US->THEM: 8=FIXT.1.1|9=100|35=j|34=4|49=US|52=20160419-20:23:53.812|56=THEM|45=3|58=Unsupported Message Type|372=j|380=3|10=068|

As one can see in the Logon messages, the DefaultApplVerID (1137=9) is FIX50SP2.  Yet QF/J is rejecting their BusinessMessageReject message with "Unsupported Message Type".

These are relevant log entries...

19 Apr 2016 20:23:17,223 INFO [NioProcessor-20] quickfix.mina.initiator.InitiatorIoHandler - MINA session created for FIXT.1.1:US->THEM: local=/10.0.2.232:52978, class org.apache.mina.transport.socket.nio.NioSocketSession, remote=theirhost:80
19 Apr 2016 20:23:18,629 INFO [NioProcessor-20] quickfix.mina.initiator.InitiatorIoHandler - Setting DefaultApplVerID (1137=9) from Logon
19 Apr 2016 20:23:53,811 ERROR [QF/J Session dispatcher: FIXT.1.1:US->THEM] quickfixj.errorEvent - FIXT.1.1:US->THEM: Rejecting invalid message: quickfix.UnsupportedMessageType: 8=FIXT.1.19=10135=j34=349=THEM52=20160419-20:23:53.82056=US45=358=ERROR_IN_UPDATE_OR_INSERT372=W380=010=179
19 Apr 2016 20:23:53,812 ERROR [QF/J Session dispatcher: FIXT.1.1:US->THEM] quickfixj.errorEvent - FIXT.1.1:US->THEM: Reject sent for Message 3: Unsupported Message Type


However, when I change the handler signature to...

public void onMessage(quickfix.fix50.BusinessMessageReject message, SessionID sessionID)

... this handler is invoked.

The session is defined as follows...

[session]
BeginString=FIXT.1.1
SenderCompID=US
TargetCompID=THEM
DefaultApplVerID=FIX.5.0SP2
ConnectionType=initiator
TimeZone=US/Eastern
StartTime=19:02:00
EndTime=17:58:00
AppDataDictionary=FIX50SP2.xml
SocketConnectPort=80
SocketConnectHost=theirhost
SocketUseSSL=N
ResetOnLogon=Y

Why does the signature with quickfix.fix50 work and not the expected quickfix.fix50sp2?
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Version 1.6.2 - MessageCracker handler for FIX.5.0SP2

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


Hi,

do you know if this also occurs with QFJ 1.6.1 or 1.6.0?
Are you using the DefaultMessageFactory or do you have a custom factory? If not, maybe try to use a
custom factory.
Dumb question: I assume you have the 5.0SP2 classes in your classpath? Otherwise the
DefaultMessageFactory cannot discover the 5.0SP2 message factory.

Regards,
Chris.


On 20/04/16 04:53, thannon wrote:

> QuickFIX/J Documentation: http://www.quickfixj.org/documentation/
> QuickFIX/J Support: http://www.quickfixj.org/support/
>
>
> I am having trouble with handling FIX.5.0SP2 messages.  I have registered a
> handler in the following way (tried both with and without the @Handler
> annotation)...
>
> @Handler
> public void onMessage(quickfix.fix50sp2.BusinessMessageReject message,
> SessionID sessionID)
>     throws FieldNotFound, UnsupportedMessageType, IncorrectTagValue
> {
>        // handler implementation
> }
>
> Following is the message conversation (length and checksums are not correct
> due to substitution of confidential data)
>
> FIXT.1.1:US->THEM:
> 8=FIXT.1.1|9=80|35=A|34=1|49=US|52=20160419-20:23:18.122|56=THEM|98=0|108=30|141=Y|1137=9|10=078|
> FIXT.1.1:US->THEM:
> 8=FIXT.1.1|9=80|35=A|34=1|49=THEM|52=20160419-20:23:18.635|56=US|98=0|108=30|141=Y|1137=9|10=087|
> FIXT.1.1:US->THEM:
> 8=FIXT.1.1|9=55|35=0|34=2|49=THEM|52=20160419-20:23:48.812|56=US|10=192|
> FIXT.1.1:US->THEM:
> 8=FIXT.1.1|9=55|35=0|34=2|49=US|52=20160419-20:23:48.804|56=THEM|10=193|
> FIXT.1.1:US->THEM:
> 8=FIXT.1.1|9=199|35=W|34=3|49=US|52=20160419-20:23:53.776|56=THEM|22=1|48=549310VL1|167=NONE|460=11|1227=BOND|1500=FEED|268=1|269=1|270=100|423=1|271=9000|272=20160419|273=20:23:47.222|276=I|64=20160421|5637=2|10=210|
> FIXT.1.1:US->THEM:
> 8=FIXT.1.1|9=101|35=j|34=3|49=THEM|52=20160419-20:23:53.820|56=US|45=3|372=W|380=0|58=ERROR_IN_UPDATE_OR_INSERT|10=179|
> FIXT.1.1:US->THEM:
> 8=FIXT.1.1|9=100|35=j|34=4|49=US|52=20160419-20:23:53.812|56=THEM|45=3|58=Unsupported
> Message Type|372=j|380=3|10=068|
>
> As one can see in the Logon messages, the DefaultApplVerID (1137=9) is
> FIX50SP2.  Yet QF/J is rejecting our BusinessMessageReject message with
> "Unsupported Message Type".
>
> These are relevant log entries...
>
> 19 Apr 2016 20:23:17,223 INFO [NioProcessor-20]
> quickfix.mina.initiator.InitiatorIoHandler - MINA session created for
> FIXT.1.1:US->THEM: local=/10.0.2.232:52978, class
> org.apache.mina.transport.socket.nio.NioSocketSession, remote=theirhost:80
> 19 Apr 2016 20:23:18,629 INFO [NioProcessor-20]
> quickfix.mina.initiator.InitiatorIoHandler - Setting DefaultApplVerID
> (1137=9) from Logon
> 19 Apr 2016 20:23:53,811 ERROR [QF/J Session dispatcher: FIXT.1.1:US->THEM]
> quickfixj.errorEvent - FIXT.1.1:US->THEM: Rejecting invalid message:
> quickfix.UnsupportedMessageType:
> 8=FIXT.1.19=10135=j34=349=THEM52=20160419-20:23:53.82056=US45=358=ERROR_IN_UPDATE_OR_INSERT372=W380=010=179
> 19 Apr 2016 20:23:53,812 ERROR [QF/J Session dispatcher: FIXT.1.1:US->THEM]
> quickfixj.errorEvent - FIXT.1.1:US->THEM: Reject sent for Message 3:
> Unsupported Message Type
>
>
> However, when I change the handler signature to...
>
> public void onMessage(quickfix.fix50.BusinessMessageReject message,
> SessionID sessionID)
>
> ... this handler is invoked.
>
> The session is defined as follows...
>
> [session]
> BeginString=FIXT.1.1
> SenderCompID=US
> TargetCompID=THEM
> DefaultApplVerID=FIX.5.0SP2
> ConnectionType=initiator
> TimeZone=US/Eastern
> StartTime=19:02:00
> EndTime=17:58:00
> AppDataDictionary=FIX50SP2.xml
> SocketConnectPort=80
> SocketConnectHost=theirhost
> SocketUseSSL=N
> ResetOnLogon=Y
>
> Why does the signature with quickfix.fix50 work and not the expected
> quickfix.fix50sp2?
>
>
>
> --
> View this message in context: http://quickfix-j.364392.n2.nabble.com/Version-1-6-2-MessageCracker-handler-for-FIX-5-0SP2-tp7579464.html
> Sent from the QuickFIX/J mailing list archive at Nabble.com.
>
> ------------------------------------------------------------------------------
> Find and fix application performance issues faster with Applications Manager
> Applications Manager provides deep performance insights into multiple tiers of
> your business applications. It resolves application problems quickly and
> reduces your MTTR. Get your free trial!
> https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
> _______________________________________________
> Quickfixj-users mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/quickfixj-users

--
Christoph John
Development & Support
Direct: +49 241 557080-28
Mailto:[hidden email]
       


http://www.macd.com <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

------------------------------------------------------------------------------
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
_______________________________________________
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: Version 1.6.2 - MessageCracker handler for FIX.5.0SP2

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


Hmm, quickly checked: it seems that the fix50sp*.MessageFactory is not in the core module (but 4.0
to 5.0 are). The sp* factories are only in the specific message module (or in the all module).
How is your classpath looking?

On 20/04/16 09:36, Christoph John wrote:

> Hi,
>
> do you know if this also occurs with QFJ 1.6.1 or 1.6.0?
> Are you using the DefaultMessageFactory or do you have a custom factory? If not, maybe try to use
> a custom factory.
> Dumb question: I assume you have the 5.0SP2 classes in your classpath? Otherwise the
> DefaultMessageFactory cannot discover the 5.0SP2 message factory.
>
> Regards,
> Chris.
>
>
> On 20/04/16 04:53, thannon wrote:
>> QuickFIX/J Documentation: http://www.quickfixj.org/documentation/
>> QuickFIX/J Support: http://www.quickfixj.org/support/
>>
>>
>> I am having trouble with handling FIX.5.0SP2 messages.  I have registered a
>> handler in the following way (tried both with and without the @Handler
>> annotation)...
>>
>> @Handler
>> public void onMessage(quickfix.fix50sp2.BusinessMessageReject message,
>> SessionID sessionID)
>>     throws FieldNotFound, UnsupportedMessageType, IncorrectTagValue
>> {
>>        // handler implementation
>> }
>>
>> Following is the message conversation (length and checksums are not correct
>> due to substitution of confidential data)
>>
>> FIXT.1.1:US->THEM:
>> 8=FIXT.1.1|9=80|35=A|34=1|49=US|52=20160419-20:23:18.122|56=THEM|98=0|108=30|141=Y|1137=9|10=078|
>> FIXT.1.1:US->THEM:
>> 8=FIXT.1.1|9=80|35=A|34=1|49=THEM|52=20160419-20:23:18.635|56=US|98=0|108=30|141=Y|1137=9|10=087|
>> FIXT.1.1:US->THEM:
>> 8=FIXT.1.1|9=55|35=0|34=2|49=THEM|52=20160419-20:23:48.812|56=US|10=192|
>> FIXT.1.1:US->THEM:
>> 8=FIXT.1.1|9=55|35=0|34=2|49=US|52=20160419-20:23:48.804|56=THEM|10=193|
>> FIXT.1.1:US->THEM:
>> 8=FIXT.1.1|9=199|35=W|34=3|49=US|52=20160419-20:23:53.776|56=THEM|22=1|48=549310VL1|167=NONE|460=11|1227=BOND|1500=FEED|268=1|269=1|270=100|423=1|271=9000|272=20160419|273=20:23:47.222|276=I|64=20160421|5637=2|10=210|
>>
>> FIXT.1.1:US->THEM:
>> 8=FIXT.1.1|9=101|35=j|34=3|49=THEM|52=20160419-20:23:53.820|56=US|45=3|372=W|380=0|58=ERROR_IN_UPDATE_OR_INSERT|10=179|
>>
>> FIXT.1.1:US->THEM:
>> 8=FIXT.1.1|9=100|35=j|34=4|49=US|52=20160419-20:23:53.812|56=THEM|45=3|58=Unsupported
>> Message Type|372=j|380=3|10=068|
>>
>> As one can see in the Logon messages, the DefaultApplVerID (1137=9) is
>> FIX50SP2.  Yet QF/J is rejecting our BusinessMessageReject message with
>> "Unsupported Message Type".
>>
>> These are relevant log entries...
>>
>> 19 Apr 2016 20:23:17,223 INFO [NioProcessor-20]
>> quickfix.mina.initiator.InitiatorIoHandler - MINA session created for
>> FIXT.1.1:US->THEM: local=/10.0.2.232:52978, class
>> org.apache.mina.transport.socket.nio.NioSocketSession, remote=theirhost:80
>> 19 Apr 2016 20:23:18,629 INFO [NioProcessor-20]
>> quickfix.mina.initiator.InitiatorIoHandler - Setting DefaultApplVerID
>> (1137=9) from Logon
>> 19 Apr 2016 20:23:53,811 ERROR [QF/J Session dispatcher: FIXT.1.1:US->THEM]
>> quickfixj.errorEvent - FIXT.1.1:US->THEM: Rejecting invalid message:
>> quickfix.UnsupportedMessageType:
>> 8=FIXT.1.19=10135=j34=349=THEM52=20160419-20:23:53.82056=US45=358=ERROR_IN_UPDATE_OR_INSERT372=W380=010=179
>>
>> 19 Apr 2016 20:23:53,812 ERROR [QF/J Session dispatcher: FIXT.1.1:US->THEM]
>> quickfixj.errorEvent - FIXT.1.1:US->THEM: Reject sent for Message 3:
>> Unsupported Message Type
>>
>>
>> However, when I change the handler signature to...
>>
>> public void onMessage(quickfix.fix50.BusinessMessageReject message,
>> SessionID sessionID)
>>
>> ... this handler is invoked.
>>
>> The session is defined as follows...
>>
>> [session]
>> BeginString=FIXT.1.1
>> SenderCompID=US
>> TargetCompID=THEM
>> DefaultApplVerID=FIX.5.0SP2
>> ConnectionType=initiator
>> TimeZone=US/Eastern
>> StartTime=19:02:00
>> EndTime=17:58:00
>> AppDataDictionary=FIX50SP2.xml
>> SocketConnectPort=80
>> SocketConnectHost=theirhost
>> SocketUseSSL=N
>> ResetOnLogon=Y
>>
>> Why does the signature with quickfix.fix50 work and not the expected
>> quickfix.fix50sp2?
>>
>>
>>
>> --
>> View this message in context:
>> http://quickfix-j.364392.n2.nabble.com/Version-1-6-2-MessageCracker-handler-for-FIX-5-0SP2-tp7579464.html
>> Sent from the QuickFIX/J mailing list archive at Nabble.com.
>>
>> ------------------------------------------------------------------------------
>> Find and fix application performance issues faster with Applications Manager
>> Applications Manager provides deep performance insights into multiple tiers of
>> your business applications. It resolves application problems quickly and
>> reduces your MTTR. Get your free trial!
>> https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
>> _______________________________________________
>> Quickfixj-users mailing list
>> [hidden email]
>> https://lists.sourceforge.net/lists/listinfo/quickfixj-users
>

--
Christoph John
Development & Support
Direct: +49 241 557080-28
Mailto:[hidden email]
       


http://www.macd.com <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

------------------------------------------------------------------------------
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
_______________________________________________
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: Version 1.6.2 - MessageCracker handler for FIX.5.0SP2

thannon
In reply to this post by Christoph John
Hi Chris,

I do not know if this occurs in previous 1.6.x versions.  I am using the DefaultMessageFactory; I've never used a custom factory so I will have to research how to do so.

I do have the 5.0SP2 classes in classpath via the quickfix-messages-fix50sp2-1.6.2.jar

-Tommy

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


Hi,

do you know if this also occurs with QFJ 1.6.1 or 1.6.0?
Are you using the DefaultMessageFactory or do you have a custom factory? If not, maybe try to use a
custom factory.
Dumb question: I assume you have the 5.0SP2 classes in your classpath? Otherwise the
DefaultMessageFactory cannot discover the 5.0SP2 message factory.

Regards,
Chris.


On 20/04/16 04:53, thannon wrote:
> QuickFIX/J Documentation: http://www.quickfixj.org/documentation/
> QuickFIX/J Support: http://www.quickfixj.org/support/
>
>
> I am having trouble with handling FIX.5.0SP2 messages.  I have registered a
> handler in the following way (tried both with and without the @Handler
> annotation)...
>
> @Handler
> public void onMessage(quickfix.fix50sp2.BusinessMessageReject message,
> SessionID sessionID)
>     throws FieldNotFound, UnsupportedMessageType, IncorrectTagValue
> {
>        // handler implementation
> }
>
> Following is the message conversation (length and checksums are not correct
> due to substitution of confidential data)
>
> FIXT.1.1:US->THEM:
> 8=FIXT.1.1|9=80|35=A|34=1|49=US|52=20160419-20:23:18.122|56=THEM|98=0|108=30|141=Y|1137=9|10=078|
> FIXT.1.1:US->THEM:
> 8=FIXT.1.1|9=80|35=A|34=1|49=THEM|52=20160419-20:23:18.635|56=US|98=0|108=30|141=Y|1137=9|10=087|
> FIXT.1.1:US->THEM:
> 8=FIXT.1.1|9=55|35=0|34=2|49=THEM|52=20160419-20:23:48.812|56=US|10=192|
> FIXT.1.1:US->THEM:
> 8=FIXT.1.1|9=55|35=0|34=2|49=US|52=20160419-20:23:48.804|56=THEM|10=193|
> FIXT.1.1:US->THEM:
> 8=FIXT.1.1|9=199|35=W|34=3|49=US|52=20160419-20:23:53.776|56=THEM|22=1|48=549310VL1|167=NONE|460=11|1227=BOND|1500=FEED|268=1|269=1|270=100|423=1|271=9000|272=20160419|273=20:23:47.222|276=I|64=20160421|5637=2|10=210|
> FIXT.1.1:US->THEM:
> 8=FIXT.1.1|9=101|35=j|34=3|49=THEM|52=20160419-20:23:53.820|56=US|45=3|372=W|380=0|58=ERROR_IN_UPDATE_OR_INSERT|10=179|
> FIXT.1.1:US->THEM:
> 8=FIXT.1.1|9=100|35=j|34=4|49=US|52=20160419-20:23:53.812|56=THEM|45=3|58=Unsupported
> Message Type|372=j|380=3|10=068|
>
> As one can see in the Logon messages, the DefaultApplVerID (1137=9) is
> FIX50SP2.  Yet QF/J is rejecting our BusinessMessageReject message with
> "Unsupported Message Type".
>
> These are relevant log entries...
>
> 19 Apr 2016 20:23:17,223 INFO [NioProcessor-20]
> quickfix.mina.initiator.InitiatorIoHandler - MINA session created for
> FIXT.1.1:US->THEM: local=/10.0.2.232:52978, class
> org.apache.mina.transport.socket.nio.NioSocketSession, remote=theirhost:80
> 19 Apr 2016 20:23:18,629 INFO [NioProcessor-20]
> quickfix.mina.initiator.InitiatorIoHandler - Setting DefaultApplVerID
> (1137=9) from Logon
> 19 Apr 2016 20:23:53,811 ERROR [QF/J Session dispatcher: FIXT.1.1:US->THEM]
> quickfixj.errorEvent - FIXT.1.1:US->THEM: Rejecting invalid message:
> quickfix.UnsupportedMessageType:
> 8=FIXT.1.19=10135=j34=349=THEM52=20160419-20:23:53.82056=US45=358=ERROR_IN_UPDATE_OR_INSERT372=W380=010=179
> 19 Apr 2016 20:23:53,812 ERROR [QF/J Session dispatcher: FIXT.1.1:US->THEM]
> quickfixj.errorEvent - FIXT.1.1:US->THEM: Reject sent for Message 3:
> Unsupported Message Type
>
>
> However, when I change the handler signature to...
>
> public void onMessage(quickfix.fix50.BusinessMessageReject message,
> SessionID sessionID)
>
> ... this handler is invoked.
>
> The session is defined as follows...
>
> [session]
> BeginString=FIXT.1.1
> SenderCompID=US
> TargetCompID=THEM
> DefaultApplVerID=FIX.5.0SP2
> ConnectionType=initiator
> TimeZone=US/Eastern
> StartTime=19:02:00
> EndTime=17:58:00
> AppDataDictionary=FIX50SP2.xml
> SocketConnectPort=80
> SocketConnectHost=theirhost
> SocketUseSSL=N
> ResetOnLogon=Y
>
> Why does the signature with quickfix.fix50 work and not the expected
> quickfix.fix50sp2?
>
>
>
> --
> View this message in context: http://quickfix-j.364392.n2.nabble.com/Version-1-6-2-MessageCracker-handler-for-FIX-5-0SP2-tp7579464.html
> Sent from the QuickFIX/J mailing list archive at Nabble.com.
>
> ------------------------------------------------------------------------------
> Find and fix application performance issues faster with Applications Manager
> Applications Manager provides deep performance insights into multiple tiers of
> your business applications. It resolves application problems quickly and
> reduces your MTTR. Get your free trial!
> https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
> _______________________________________________
> Quickfixj-users mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/quickfixj-users

--
Christoph John
Development & Support
Direct: +49 241 557080-28
Mailto:[hidden email]
       


http://www.macd.com <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

------------------------------------------------------------------------------
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
_______________________________________________
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: Version 1.6.2 - MessageCracker handler for FIX.5.0SP2

thannon
In reply to this post by Christoph John
Classpath includes (among other modules) the following:

quickfixj-messages-fix50-1.6.2.jar
quickfixj-core-1.6.2.jar
quickfixj-messages-fix44-1.6.2.jar
quickfixj-messages-fix50sp2-1.6.2.jar
quickfixj-messages-fixt11-1.6.2.jar

Would changing the order help?  If so, what order?

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


Hmm, quickly checked: it seems that the fix50sp*.MessageFactory is not in the core module (but 4.0
to 5.0 are). The sp* factories are only in the specific message module (or in the all module).
How is your classpath looking?

On 20/04/16 09:36, Christoph John wrote:
> Hi,
>
> do you know if this also occurs with QFJ 1.6.1 or 1.6.0?
> Are you using the DefaultMessageFactory or do you have a custom factory? If not, maybe try to use
> a custom factory.
> Dumb question: I assume you have the 5.0SP2 classes in your classpath? Otherwise the
> DefaultMessageFactory cannot discover the 5.0SP2 message factory.
>
> Regards,
> Chris.
>
>
> On 20/04/16 04:53, thannon wrote:
>> QuickFIX/J Documentation: http://www.quickfixj.org/documentation/
>> QuickFIX/J Support: http://www.quickfixj.org/support/
>>
>>
>> I am having trouble with handling FIX.5.0SP2 messages.  I have registered a
>> handler in the following way (tried both with and without the @Handler
>> annotation)...
>>
>> @Handler
>> public void onMessage(quickfix.fix50sp2.BusinessMessageReject message,
>> SessionID sessionID)
>>     throws FieldNotFound, UnsupportedMessageType, IncorrectTagValue
>> {
>>        // handler implementation
>> }
>>
>> Following is the message conversation (length and checksums are not correct
>> due to substitution of confidential data)
>>
>> FIXT.1.1:US->THEM:
>> 8=FIXT.1.1|9=80|35=A|34=1|49=US|52=20160419-20:23:18.122|56=THEM|98=0|108=30|141=Y|1137=9|10=078|
>> FIXT.1.1:US->THEM:
>> 8=FIXT.1.1|9=80|35=A|34=1|49=THEM|52=20160419-20:23:18.635|56=US|98=0|108=30|141=Y|1137=9|10=087|
>> FIXT.1.1:US->THEM:
>> 8=FIXT.1.1|9=55|35=0|34=2|49=THEM|52=20160419-20:23:48.812|56=US|10=192|
>> FIXT.1.1:US->THEM:
>> 8=FIXT.1.1|9=55|35=0|34=2|49=US|52=20160419-20:23:48.804|56=THEM|10=193|
>> FIXT.1.1:US->THEM:
>> 8=FIXT.1.1|9=199|35=W|34=3|49=US|52=20160419-20:23:53.776|56=THEM|22=1|48=549310VL1|167=NONE|460=11|1227=BOND|1500=FEED|268=1|269=1|270=100|423=1|271=9000|272=20160419|273=20:23:47.222|276=I|64=20160421|5637=2|10=210|
>>
>> FIXT.1.1:US->THEM:
>> 8=FIXT.1.1|9=101|35=j|34=3|49=THEM|52=20160419-20:23:53.820|56=US|45=3|372=W|380=0|58=ERROR_IN_UPDATE_OR_INSERT|10=179|
>>
>> FIXT.1.1:US->THEM:
>> 8=FIXT.1.1|9=100|35=j|34=4|49=US|52=20160419-20:23:53.812|56=THEM|45=3|58=Unsupported
>> Message Type|372=j|380=3|10=068|
>>
>> As one can see in the Logon messages, the DefaultApplVerID (1137=9) is
>> FIX50SP2.  Yet QF/J is rejecting our BusinessMessageReject message with
>> "Unsupported Message Type".
>>
>> These are relevant log entries...
>>
>> 19 Apr 2016 20:23:17,223 INFO [NioProcessor-20]
>> quickfix.mina.initiator.InitiatorIoHandler - MINA session created for
>> FIXT.1.1:US->THEM: local=/10.0.2.232:52978, class
>> org.apache.mina.transport.socket.nio.NioSocketSession, remote=theirhost:80
>> 19 Apr 2016 20:23:18,629 INFO [NioProcessor-20]
>> quickfix.mina.initiator.InitiatorIoHandler - Setting DefaultApplVerID
>> (1137=9) from Logon
>> 19 Apr 2016 20:23:53,811 ERROR [QF/J Session dispatcher: FIXT.1.1:US->THEM]
>> quickfixj.errorEvent - FIXT.1.1:US->THEM: Rejecting invalid message:
>> quickfix.UnsupportedMessageType:
>> 8=FIXT.1.19=10135=j34=349=THEM52=20160419-20:23:53.82056=US45=358=ERROR_IN_UPDATE_OR_INSERT372=W380=010=179
>>
>> 19 Apr 2016 20:23:53,812 ERROR [QF/J Session dispatcher: FIXT.1.1:US->THEM]
>> quickfixj.errorEvent - FIXT.1.1:US->THEM: Reject sent for Message 3:
>> Unsupported Message Type
>>
>>
>> However, when I change the handler signature to...
>>
>> public void onMessage(quickfix.fix50.BusinessMessageReject message,
>> SessionID sessionID)
>>
>> ... this handler is invoked.
>>
>> The session is defined as follows...
>>
>> [session]
>> BeginString=FIXT.1.1
>> SenderCompID=US
>> TargetCompID=THEM
>> DefaultApplVerID=FIX.5.0SP2
>> ConnectionType=initiator
>> TimeZone=US/Eastern
>> StartTime=19:02:00
>> EndTime=17:58:00
>> AppDataDictionary=FIX50SP2.xml
>> SocketConnectPort=80
>> SocketConnectHost=theirhost
>> SocketUseSSL=N
>> ResetOnLogon=Y
>>
>> Why does the signature with quickfix.fix50 work and not the expected
>> quickfix.fix50sp2?
>>
>>
>>
>> --
>> View this message in context:
>> http://quickfix-j.364392.n2.nabble.com/Version-1-6-2-MessageCracker-handler-for-FIX-5-0SP2-tp7579464.html
>> Sent from the QuickFIX/J mailing list archive at Nabble.com.
>>
>> ------------------------------------------------------------------------------
>> Find and fix application performance issues faster with Applications Manager
>> Applications Manager provides deep performance insights into multiple tiers of
>> your business applications. It resolves application problems quickly and
>> reduces your MTTR. Get your free trial!
>> https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
>> _______________________________________________
>> Quickfixj-users mailing list
>> [hidden email]
>> https://lists.sourceforge.net/lists/listinfo/quickfixj-users
>

--
Christoph John
Development & Support
Direct: +49 241 557080-28
Mailto:[hidden email]
       


http://www.macd.com <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

------------------------------------------------------------------------------
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
_______________________________________________
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: Version 1.6.2 - MessageCracker handler for FIX.5.0SP2

thannon
In reply to this post by thannon
I managed to get it to work by doing the following (as described in this post http://quickfix-j.364392.n2.nabble.com/Receive-FIX-5-0SP2-messages-td7578954.html) ...

final DefaultMessageFactory defaultMessageFactory = new DefaultMessageFactory();
defaultMessageFactory.addFactory(FixVersions.FIX50, quickfix.fix50sp2.MessageFactory.class);

I looked at the DefaultMessageFactory source code and found the following comment in create(...) method...

            // The default message factory assumes that only FIX 5.0 will be
            // used with FIXT 1.1 sessions. A more flexible approach will require
            // an extension to the QF JNI API. Until then, you will need a custom
            // message factory if you want to use application messages prior to
            // FIX 5.0 with a FIXT 1.1 session.
            //
            // TODO: how do we support 50/50SP1/50SP2 concurrently?
            //
            // If you need to determine admin message category based on a data
            // dictionary, then use a custom message factory and don't use the
            // static method used below.

So, does my current approach result in being able to only handle FIX50SP2 messages instead of FIX50?

- Tommy
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Version 1.6.2 - MessageCracker handler for FIX.5.0SP2

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


Hi,

totally forgot about that one. I should have created a JIRA issue for this back then. ;) I now have
created one: http://www.quickfixj.org/jira/browse/QFJ-888
However, this will only be done for 1.7 since it will break compatibility to 1.6.x. The workaround
is either to use a custom message factory or to re-add your needed message factory as you did.

Cheers,
Chris.


On 20/04/16 21:07, thannon wrote:

> QuickFIX/J Documentation: http://www.quickfixj.org/documentation/
> QuickFIX/J Support: http://www.quickfixj.org/support/
>
>
> I managed to get it to work by doing the following (as described in this post
> http://quickfix-j.364392.n2.nabble.com/Receive-FIX-5-0SP2-messages-td7578954.html)
> ...
>
> final DefaultMessageFactory defaultMessageFactory = new
> DefaultMessageFactory();
> defaultMessageFactory.addFactory(FixVersions.FIX50,
> quickfix.fix50sp2.MessageFactory.class);
>
> I looked at the DefaultMessageFactory source code and found the following
> comment in create(...) method...
>
>              // The default message factory assumes that only FIX 5.0 will be
>              // used with FIXT 1.1 sessions. A more flexible approach will
> require
>              // an extension to the QF JNI API. Until then, you will need a
> custom
>              // message factory if you want to use application messages prior
> to
>              // FIX 5.0 with a FIXT 1.1 session.
>              //
>              // TODO: how do we support 50/50SP1/50SP2 concurrently?
>              //
>              // If you need to determine admin message category based on a
> data
>              // dictionary, then use a custom message factory and don't use
> the
>              // static method used below.
>
> So, does my current approach result in being able to only handle FIX50SP2
> messages instead of FIX50?
>
> - Tommy
>
>
>
> --
> View this message in context: http://quickfix-j.364392.n2.nabble.com/Version-1-6-2-MessageCracker-handler-for-FIX-5-0SP2-tp7579464p7579469.html
> Sent from the QuickFIX/J mailing list archive at Nabble.com.
>
> ------------------------------------------------------------------------------
> Find and fix application performance issues faster with Applications Manager
> Applications Manager provides deep performance insights into multiple tiers of
> your business applications. It resolves application problems quickly and
> reduces your MTTR. Get your free trial!
> https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
> _______________________________________________
> Quickfixj-users mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/quickfixj-users

--
Christoph John
Development & Support
Direct: +49 241 557080-28
Mailto:[hidden email]
       


http://www.macd.com <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

------------------------------------------------------------------------------
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
_______________________________________________
Quickfixj-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/quickfixj-users
Loading...