Re: [Quickfixj-users] jdbc logging

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

No worries, Toli!=20=20

Thank you so much for the time you spent on that reply...the minute I
have a free...uh...minute, I will batten down the hatches and get behind
what's going on here.  I have a sneaking suspicion the Proxool libraries
are the culprit in conjunction with Oracle....hopefully I'll be able to
tell you soon.

This definitely was not working with 1.0.3...and I migrated to 1.1.0 in
the hopes that it was fixed.  I have been meaning to install mysql on my
machine and attempt to connect to that and see what happens...this email
is the kick in the butt I needed.

Thanks again for all your help and detailed reply...much appreciated
beyond belief!

Rob



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: Wednesday, May 02, 2007 2:37 PM
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,

When i said that the JdbcLog was "fixed", I meant that it stopped
going into the recursive death spiral of printing stacktraces, so that
you get this instead:
> JdbcLog cannot log SQLException due to recursive log errors!

Truth be told, i'm at a loss what your problem may be. i'm not seeing
anything useful in the log. I saw that kind of exception when the QFJ
engine couldn't make the connection to the database: it was either not
running, the tables were not present, the user/password was incorrect,
it didn't have perms to write, etc. In that case, the underlying
proxool cashing code would go crazy, trying to keep creating
connections. But it doesn't look like that's the case with you.

I haven't tried QFJ with Oracle - we don't have it in-house, we use
MySQL.
I can't remember if you said that it worked for you with 1.0.3, or if
it was the other problem (app exiting w/out an explicit wait() call).

There are 3 approaches i can suggest:
1. Try something other than Oracle - maybe MySQL. it's fairly easy to
setup, and you can see if it's an Oracle or a general Jdbc problem you
have.

2. The error comes from Proxool - which is a transparent JDBC pooling
framework. If you feel comfortable modifying QFJ, you can check out
the source and try to disable Proxool altogether, but changing the
quickfix.JdbcUtil.getDataSource() function not create a Proxool pool.
Perhaps that'll give you a better error that somehow gets masked by
Proxool.

3. Another thing i may suggest for debugging is for you to download
our Marketcetera OMS and configure it to point to your Oracle database
and see if you get the same problem.
If you don't, then you can perhaps isolate the problem to your app
setup. Otherwise, we are much more likely seeing a bug in QFJ itself,
and then I can work on getting an Oracle setup and trying to reproduce
your setup.
http://trac.marketcetera.org/trac.fcgi/wiki/Marketcetera/OMSInstallation
I'd be happy to walk you through the Marketcetera setup to save you
time if you want. Just let me know.

I realize that all of these suggestions are a lot of work and may be
asking too much. If you can isolate the error to QuickfixJ. then you
can post the SQL create scripts for Oracle database, and we'll try to
reproduce the problem locally.

--=20
Toli Kuznets
http://www.marketcetera.com: Open-Source Trading Platform
download.run.trade.

------------------------------------------------------------------------
-
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.