[QFJ-828] Messages Log Contains Another Session's Messages Created: 19/Feb/15  Updated: 20/Feb/15

Status: Open
Project: QuickFIX/J
Component/s: None
Affects Version/s: 1.5.3
Fix Version/s: None

Type: Bug Priority: Default
Reporter: Rupert Webb Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: QuickfixJ
Environment:

Linux Server


 Description   

I had two quick fix sessions configured: CLIENT and CLIENT2. Our CLIENT2 session connected while no one connected to the CLIENT session. You can see this from the event logs:

::::::::::::::
FIX.4.2-LIME-CLIENT2.event.log
::::::::::::::
20150219-08:20:41: Session FIX.4.2:LIME->CLIENT schedule is daily, 05:00:00-UTC - 00:59:00-UTC
20150219-08:20:41: Created session: FIX.4.2:LIME->CLIENT

::::::::::::::
FIX.4.2-LIME-CLIENT2.event.log
::::::::::::::
20150219-08:20:41: Session FIX.4.2:LIME->CLIENT2 schedule is daily, 05:00:00-UTC - 00:59:00-UTC
20150219-08:20:41: Created session: FIX.4.2:LIME->CLIENT2
20150219-12:03:04: Accepting session FIX.4.2:LIME->CLIENT2 from /10.22.75.167:52406
20150219-12:03:04: Acceptor heartbeat set to 45 seconds
20150219-12:03:04: Received logon
20150219-12:03:04: Responding to Logon request
20150219-12:03:04: Received ResendRequest FROM: 1 TO: infinity
...

However, all the messages in CLIENT2's message log begin appearing in CLIENT's messages log:

::::::::::::::
FIX.4.2-LIME-CLIENT.messages.log
::::::::::::::
8=FIX.4.2|9=103|35=A|34=1|49=CLIENT2|52=20150219-12:03:04.175|56=LIME|98=0|108=45|553=USER2|554=DROPCOPY|10=165|
8=FIX.4.2|9=71|35=A|34=5998|49=LIME|52=20150219-12:03:04.185|56=CLIENT2|98=0|108=45|10=117|
8=FIX.4.2|9=65|35=2|34=2|49=CLIENT2|52=20150219-12:03:04.697|56=LIME|7=1|16=0|10=032|

::::::::::::::
FIX.4.2-LIME-CLIENT2.messages.log
::::::::::::::
8=FIX.4.2|9=103|35=A|34=1|49=CLIENT2|52=20150219-12:03:04.175|56=LIME|98=0|108=45|553=USER2|554=DROPCOPY|10=165|
8=FIX.4.2|9=71|35=A|34=5998|49=LIME|52=20150219-12:03:04.185|56=CLIENT2|98=0|108=45|10=117|
8=FIX.4.2|9=65|35=2|34=2|49=CLIENT2|52=20150219-12:03:04.697|56=LIME|7=1|16=0|10=032|

This only begin happening today. Here is the configuration:
[DEFAULT]
ConnectionType=acceptor
ReconnectInterval=60
SenderCompID=LIME
FileStorePath=fixstore-[4]-2015-02-19/
FileLogPath=fixlogs-[4]-2015-02-19/
ValidateFieldsOutOfOrder=N
ValidateFieldsHaveValues=N
ValidateIncomingMessage=N
AllowUnknownMsgFields=Y
UseDataDictionary=Y
StartTime=05:00:00
EndTime=00:59:00
BeginString=FIX.4.2
SocketAcceptPort=9003
SocketReuseAddress=Y
ValidateUserDefinedFields=N
PersistMessages=Y
CheckLatency= Y

[SESSION]
TargetCompID=CLIENT2
CheckPassword=Y
Password=PASS

[SESSION]
TargetCompID=CLIENT
CheckPassword=Y
Password=PASS

 Comments   
Comment by Christoph John [ 20/Feb/15 ]

Hi, some questions:

  • can you reproduce the problem or did it appear only once?
  • did you change something in the session settings before the problem appeared?
  • how do you use the FileLog? Are you creating it on your own?
Comment by Rupert Webb [ 20/Feb/15 ]

It does not appear to be reproducible. We did have exceptionally high disk load when it happened.

We did not make any changes to the session settings

We are using the default FileLog without any modifications.

As additional piece of information, this is the code that we use to send FIX messages:
public synchronized boolean sendMessage(Message message) throws SessionNotFound

{ return Session.sendToTarget(message); }

We also have multiple threads call this function.

I'll see if I try to reproduce it

Generated at Sat Nov 23 01:00:33 UTC 2024 using JIRA 7.5.2#75007-sha1:9f5725bb824792b3230a5d8716f0c13e296a3cae.