Re: [Quickfixj-users] jdbc logging

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

J=F6rg,

We are using an Oracle 10.2.0.3 in RAC configuration on a RedHat Enterprise=
 Linux 4 with update 4 server.  I'm using the latest ojdbc.jar file to come=
 with this Oracle installation to connect to this system from my Windows XP=
 Professional box running the class directly from my Eclipse 3.2 IDE.

To further illustrate my conundrum...I tested individual sessions I have se=
t up with various vendors...all of my initial testing of the JDBC logging/s=
toring had, thus far, been with Neovest, whose development connection I've =
been testing with for a few weeks now has been very dependable and trouble-=
free...turns out, the day I started testing QuickFIX/j's JDBC logging, Neov=
est's test connection was acting up and has been for a few days now...my en=
gine would send a logon request and they would immediately reply with a log=
out message and the engine would logout...in the midst of all of this, entr=
ies would be inserted into the Oracle tables via the logging, but I would c=
ontinue to get the recursive errors.=20=20

I switched to mySQL and attempted to connect to the bad connection with Neo=
vest and the engine would attempt to login, get the logout response and log=
 off and then retry again in 30 seconds...no recursive errors and all conne=
ction/session creation attempts were logged to mySQL.  Seemed the oracle im=
plementation of the proxool libraries didn't like the fact that the connect=
ion was sending an incorrect response to my logon request I guess.

At any rate, I changed my test session to connect to FutureTrade and I have=
 now been successfully able to connect to Oracle using JDBC logging/store w=
ithout any recursive errors!  A little disconcerting that a problematic con=
nection results in a recursive connection error but hopefully, in productio=
n over our dedicated lines we are getting installed, the connections to our=
 vendors will be mostly trouble-free *na=EFve fingers crossed*...I guess we=
'll just have to watch this.

I'll keep you posted as I continue to monitor this.  Also to answer your lo=
gging/store question, my config file has the jdbcurl, driver, username and =
password and my initiator is successfully using both the JdbcLogFactory and=
 JdbcStoreFactory utilities connected to Oracle now with my valid test conn=
ection to FutureTrade...still trouble with the invalid Neovest connection.

Thanks so much for your patience and help with all of this...

Gratefully,
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:quickfixj-users=
-bo...@li...] On Behalf Of Joerg Thoennes
Sent: Thursday, May 03, 2007 7:10 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/
Hi Robert,

just to recollect:

JdbcLogging with QF/J 1.1.0 to Oracle does not work.

But does the JdbcStoreFactory work?

Which Oracle version do you use and which version of the Oracle JDBC driver?

Steve, shall we open a JIRA issue for this? The thread is getting really lo=
ng now...

Thanks, J=F6rg

On 05/02/07 20:49, Robert Brueckmann wrote:
> QuickFIX/J Documentation: http://www.quickfixj.org/documentation/
> QuickFIX/J Support: http://www.quickfixj.org/support/
> No worries, Toli!=20=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.
>=20
> 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.
>=20
> Thanks again for all your help and detailed reply...much appreciated
> beyond belief!
>=20
> Rob
>=20
>=20
>=20
> Merlin Securities - #1 Prime Broker North America, #1 Prime Broker Single=
 Strategy Funds, #1 Prime Broker Funds Under $100M - Global Custodian 2007
>=20
>=20
> 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
>=20
> QuickFIX/J Documentation: http://www.quickfixj.org/documentation/
> QuickFIX/J Support: http://www.quickfixj.org/support/
> Robert,
>=20
> 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!
>=20
> 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.
>=20
> 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).
>=20
> 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.
>=20
> 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.
>=20
> 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.
>=20
> 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


--=20
Joerg Thoennes
http://www.macd.com                 Tel.: +49 (0)241 44597-24
Macdonald Associates GmbH           Gesch=E4ftsf=FChrer: Roger Macdonald
Lothringer Str. 52, D-52070 Aachen  Amtsgericht Aachen, HRB 8151, Ust.-Id D=
E813021663

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