[QFJ-134] Stack overflow when JdbcLog fails to log a message Created: 07/Feb/07  Updated: 12/Apr/07  Resolved: 11/Feb/07

Status: Closed
Project: QuickFIX/J
Component/s: Engine
Affects Version/s: 1.0.5
Fix Version/s: 1.1.0

Type: Bug Priority: Default
Reporter: Toli Kuznets Assignee: Steve Bate
Resolution: Fixed Votes: 0
Labels: None

Attachments: Text File jdbc-oomErrorSessionLookupNPE.patch     Text File out.txt    
Issue Links:
Relates
relates to QFJ-133 Return of bug 89 - session lookup cau... Closed

 Description   

This is a continuation of bug 133 - just breaking out the recursive stack overflow error.

See the (bottom of) attached log - if the JdbcLog fails to insert a message, we end up calling the JdbcLog.insert() recursively until we get a stack overflow.
I think this is b/c of Proxool - it keeps trying to get a connection and log something.

Patch is attached to the bug 133 and here as well.



 Comments   
Comment by Toli Kuznets [ 07/Feb/07 ]

See the bottom of the file for the stack trace that deals with proxool-caused stack overflow

Comment by Toli Kuznets [ 07/Feb/07 ]

patch for both bug 133 and this one

Generated at Tue Oct 28 01:47:50 UTC 2025 using JIRA 7.5.2#75007-sha1:9f5725bb824792b3230a5d8716f0c13e296a3cae.