[QFJ-701] Restart FIX engine occur I/O exception Created: 04/Sep/12 Updated: 04/Sep/12 Resolved: 04/Sep/12 |
|
Status: | Closed |
Project: | QuickFIX/J |
Component/s: | Engine |
Affects Version/s: | 1.4.0 |
Fix Version/s: | None |
Type: | Other | Priority: | Default |
Reporter: | Li,Wei | Assignee: | Unassigned |
Resolution: | Not a bug | Votes: | 0 |
Labels: | logon | ||
Environment: |
Windows 2003 Server |
Issue Links: |
|
Description |
Recently when our system was restarted, occasionally occur I/O exception, the following: quickfix.ConfigError: error during session initialization I check .session file in store directory, find that it is an empty file. And as long as this file is empty, start FIX engine must occur this I/O exception. I compare quickfixj1.4.0 and quickfixj1.5.2, find the code was strengthened, increased 'sessionTimeFile.length() > 0', by this way when .session file is an empty file, will execute storeSessionTimeStamp(), program will be correctly executed. This handle whether it is in order to avoid .session empty file lead to I/O exception. So what science would generate a empty .session file? --quickfixj1.5.2 catch (final Exception e) { throw new IOException(e.getMessage()); }finally { sessionTimeInput.close(); }} else { storeSessionTimeStamp(); }} |
Comments |
Comment by Christoph John [ 04/Sep/12 ] |
I don't really understand the intention of this issue. Is it just the question under which circumstances an empty session file would be generated? I don't know exactly but we also faced this issue when one of our process crashed on startup. I guess this is due to the method FileStore.storeSessionTimeStamp() which creates the file and closes it (regardless of whether a timestamp could be stored or not). |
Comment by Christoph John [ 04/Sep/12 ] |
If you still have questions, please ask on the mailing list: http://quickfixj.org/support/ Thank you. |