Re: [Quickfixj-users] jdbc logging

[Robert B. <rbr...@me...>]

Toli,

Thanks...that explains why I can't get jdbc logging to work in
1.0.3...but my code which simply logs to the FileStoreFactory works
perfectly in 1.0.3 but all I do is update the libraries in the classpath
to the libraries from the 1.1.0 release and this is what the screen
shows:

<20070430-15:58:45, FIX.4.2:MERL_DROP->NEOV, event> (Session
FIX.4.2:MERL_DROP->NEOV schedule is daily, 10:30:00 UTC - 23:00:00 UTC)
<20070430-15:58:45, FIX.4.2:MERL_DROP->NEOV, event> (Created session:
FIX.4.2:MERL_DROP->NEOV)
<20070430-15:58:45, FIX.4.2:MERL_DROP->NEOV, event> (Valid order types:
[2])

Then the engine stops.  I have try/catches with everything being printed
to the log...nothing...no exception is being thrown, nothing at all.
I'm at a loss.  Revert the libraries back to 1.0.3 and it fires
up...heartbeats run like clockwork and the incoming FIX messages get
stored in the database.

I'm going to start removing lines of code bit by bit and see if there's
something in my initialization of my application to gain access to the
queue that's causing this to break in 1.1.0...but you would think that
some sort of exception would be thrown...NOTHING happens...the engine
code just stops.  No message, nothing.

Bizarre.

robert l. brueckmann
vice president
merlin securities
712 fifth avenue
new york, ny 10019
p: 212.822.4821
f: 212.822.4820



Merlin Securities - #1 Prime Broker North America, #1 Prime Broker Single S=
trategy Funds, #1 Prime Broker Funds Under $100M - Global Custodian 2007


From: qui...@li...
[mailto:qui...@li...] On Behalf Of Toli
Kuznets
Sent: Monday, April 30, 2007 11:58 AM
To: qui...@li...
Subject: Re: [Quickfixj-users] jdbc logging

QuickFIX/J Documentation: http://www.quickfixj.org/documentation/
QuickFIX/J Support: http://www.quickfixj.org/support/
Robert,

I believe i know what the problem may be. in QFJ 1.1.0 we fixed a bug
where an error connecting to the Jdbc store caused teh JdbcLog to go
into an infinite recursion and print out the log below:
> java.sql.SQLException: We are already in the process of making 1
connections and the number of simultaneous builds has been throttled to
0

essentially, it catch an exception making the first db entry, then
would try to log the exception, and never stop. you get the idea.

> I'm still baffled though why my FileStoreFactory code (no JDBC
logging) will not work with the 1.1.0 libraries though...

in that case, you are not dealing with JdbcLog so everything worked
fine - your system worked correctly and the above situation didn't
happen.

If you look at the output of QFJ 1.1, you should see somewhere a line
saying something about encountering a "write to Jdbc" failure and
quitting the JdbcLog.

Still not sure why your app will quit completely in case of a JdbcLog
failure - it should just not log, but the app itself should keep
working.

So see if your database is setup correctly, make sure you can log on
to it with the credentials supplied in the SessionSettings, etc.

Also, if you can, try to run it in the debugger and trap all
Errors/Exceptions, maybe for some reason JdbcLog throws some error
that kills your entire app?

------------------------------------------------------------------------
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Quickfixj-users mailing list
Qui...@li...
https://lists.sourceforge.net/lists/listinfo/quickfixj-users
=20

--------------------------------------------------------

This message contains information from Merlin Securities, LLC, or from one =
of its affiliates, that may be confidential and privileged. If you are not =
an intended recipient, please refrain from any disclosure, copying, distrib=
ution or use of this information and note that such actions are prohibited.=
 If you have received this transmission in error, please notify the sender =
immediately by telephone or by replying to this transmission.
=20
Merlin Securities, LLC is a registered broker-dealer. Services offered thro=
ugh Merlin Securities, LLC are not insured by the FDIC or any other Federal=
 Government Agency, are not deposits of or guaranteed by Merlin Securities,=
 LLC and may lose value. Nothing in this communication shall constitute a s=
olicitation or recommendation to buy or sell a particular security.