Re: [Quickfixj-users] JDBC log problems

[Steve B. <st...@te...>]

Jeff, 

The exception is being thrown from the MySQL JDBC driver. Apparently
there was an attempt to bind a prepared statement parameter to null.
The most likely way for this to happen is if some property of the
session ID is null. The properties are initialized to an empty string
but they could be explicitly initialized to through the constructors.

Are you creating any session IDs explicitly? For example, are you
creating session settings programmatically? Some databases, specifically
Oracle, interpret empty strings as nulls. At least in the past, MySQL
handles empty strings correctly. I doubt that is your problem because
you'd see the exception on every message.

Hope this helps,

Steve
 
> -----Original Message-----
> From: qui...@li... [mailto:quickfixj-
> use...@li...] On Behalf Of Jeff Schwartz
> Sent: Tuesday, September 11, 2007 9:42 AM
> To: qui...@li...
> Subject: [Quickfixj-users] JDBC log problems
> 
> QuickFIX/J Documentation: http://www.quickfixj.org/documentation/
> QuickFIX/J Support: http://www.quickfixj.org/support/
> My application is hanging for 5-15 seconds at various times because of a
> SQL error using the JDBC log.
> Has anyone else seen this?  Is the File based log sturdier?
> 
> Thanks,
> Jeff
> Sep 11, 2007 9:31:17 AM org.apache.commons.logging.impl.SLF4JLog warn
> WARNING: #0002 was active for 12859 milliseconds and has been removed
> automatica
> ly. The Thread responsible was named 'Thread-4', but the last SQL it
> performed i
> s unknown because the trace property is not enabled.
> Sep 11, 2007 9:31:17 AM cqig.fixit.FixItApplication send
> INFO: null
> java.lang.NullPointerException
>         at
> com.mysql.jdbc.ServerPreparedStatement.executeInternal(ServerPrepared
> Statement.java:673)
>         at
> com.mysql.jdbc.PreparedStatement.execute(PreparedStatement.java:770)