Menu

#2 Fix message parsing problem due to use of | (pipe)

open-accepted
None
5
2006-08-01
2006-07-27
Steve B.
No

Hi,

I ran into StringIndexOutOfBounds exceptions on line
157 of LogMessage.java which caused the FIX messages
to not be parsed.

I tracked it down to the use of | to replace all
instances of the SOH FIX delimiter...my FIX messages
had pipes as part of the data which broke parsing.

As a hack I set DEFAULT_LOG_MESSAGE_DELIMETER to
SOH_DELIMETER which fixed the parsing problem.

Steve

Discussion

  • Brian Coyner

    Brian Coyner - 2006-07-30
    • assigned_to: nobody --> coyner_b
     
  • Brian Coyner

    Brian Coyner - 2006-08-01
    • status: open --> open-accepted
     
  • Brian Coyner

    Brian Coyner - 2006-08-01

    Logged In: YES
    user_id=513857

    Please provide an example message string.

     
  • Steve B.

    Steve B. - 2006-08-01

    Logged In: YES
    user_id=1562396

    Tag 48 will cause a parsing problem if you replace all SOHs
    with |.

    8=FIX.4.29=23835=d49=AAAAAAAAAAA56=BBBBBB34=7452=20060
    710-
    16:00:43320=ALL322=ABABABABABAB_CFZL070700000F323=4393=1
    44655=CFZL070700000F48=BO|200707167=FUT200=200707205=13
    207=eCBOT107=SOYBEAN OIL : Jul
    0715=USD16451=016452=0.0116454=110=077

     

Log in to post a comment.

MongoDB Logo MongoDB