Discussion Forums

FIX Technology   < Previous   Next >

Re: Class Cast Exceptions - FIXT.1.1 - ApplVerID=6
John Cameron / Cameron Edge <>
25 Jul 2011 8:34AM ET

The class cast that you refer to is a characteristic of the particular FIX implementation you are using - ie QuickFIX.

It does not reflect any limitation of the FIX protocol itself.

You would be best advised to post your question on the QuickFIX website.

> Hi,
>
> I work for a trade routing system where our client feeds to two different systems. One of these systems is on FIX.5.0 and the other FIX.4.4. I was under the impression that both message types could be fed on the same session as follows:
>
> TransportDataDictionary=FIXT11.xml
> AppDataDictionary=FIX44.xml
> AppDataDictionary.FIX.5.0=FIX50.xml
> BeginString=FIXT.1.1
> DefaultApplVerID=FIX.5.0
>
> On messages going to system A(FIX5.0) we set ApplVerID=7.
> On messages going to system B(FIX4.4) we set ApplVerID=6.
>
> However, when we feed messages down to system B we get the followig:
>
> java.lang.ClassCastException: quickfix.fix50.ExecutionReport cannot be cast to quickfix.fix44.Message
>
> Does anyone know if there is a solution for this, perhaps I have missed some config?
>
> Any advice would be greatly appreciated
>
> Regrads Phil

Class Cast Exceptions - FIXT.1.1 - ApplVerID=6
Philip Quinn / JP Morgan   22 Jul 2011 1:24PM ET

Re: Class Cast Exceptions - FIXT.1.1 - ApplVerID=6
Hanno Klein / Deutsche Börse   25 Jul 2011 7:32AM ET

Re: Class Cast Exceptions - FIXT.1.1 - ApplVerID=6
Philip Quinn / JP Morgan   25 Jul 2011 9:32AM ET

Re: Class Cast Exceptions - FIXT.1.1 - ApplVerID=6
John Cameron / Cameron Edge   25 Jul 2011 8:34AM ET