Warning and Error Messages During File Processing

Files are passing through the iWay Integration Solution for FIX, but the following warnings and errors are observed in the log file:

ERROR (W.Inbound-Channel.1) Exception when running pre-
emitters: com.epam.fixml.converter.FIXMLConverterException: Unexpected
root element detected: emitStatus. [line=1, col=57]
ERROR (W.Inbound-Channel.1) Cannot emit reply to FIXEmit,
deadLetter=deadletter\2012-03-26T11_27_08.861Z-.XDFIXEmit: XD[FAIL]
cause: 0 subcause: 0 message:Exception when running pre-emitters
WARN (console) com.ibi.config.ConfigurationException: Listener
type "fix" is undefined WARN (bootstrap) MRThread:senderId-targetId:
[CommonsLog - warn()] - Sequence reset was sent in response to resend
request because resent process encountered invalid message in message
store. Cause: java.io.IOException: Not supported

Workaround:

It is OK to occasionally see errors from the FIX Engine or the server. When they get out of sync, they must reset themselves. Error messages are printed in the log when this occurs. If they really become out of sync, you must delete the logs folders and restart all components. However, this error indicates that the FIXML sent to the FIX preemitter was invalid.

The Sequence Reset parameter is part of the B2Bits configuration. According to the documentation, this parameter is used to automatically resolve a sequence gap problem (for example, when there is a sequence reset every day). The following are supported values for the Sequence Reset parameter:

The Reconnect Interval is the interval that the provider will use between attempts to start a B2Bits session. When the provider starts and the server is down, B2Bits will generate an error and will not create the session. The provider will then wait for this interval before trying to create the session again. Once the session is created, this parameter is irrelevant, and B2Bits takes full control.


iWay Software