Re: [Quickfixj-users] quickfix.ConfigError

[<AW...@FF...>]

That is correct. Today, I tried again, it went back to notmal. Hopefully, i=
t is our db problem, although I cannot figure it out.



----- Original Message -----
From: "Steve Bate" [st...@te...]
Sent: 03/08/2007 05:56 PM EST
To: qui...@li...
Subject: Re: [Quickfixj-users] quickfix.ConfigError



QuickFIX/J Documentation: http://www.quickfixj.org/documentation/
QuickFIX/J Support: http://www.quickfixj.org/support/
> Does anyone happen to know what went wrong with this one? We are very
> concerned about the reliability and stability of QF/J. Thanks.

Alvin,

I haven't seen this problem before. I don't see any reason at this
point to believe it's a QFJ bug. If I understand you previous message
correctly, you weren't seeing this problem and then one day it
started happening without any correlation to code changes? Is that
correct?

Steve


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3DDE=
VDEV
_______________________________________________
Quickfixj-users mailing list
Qui...@li...
https://lists.sourceforge.net/lists/listinfo/quickfixj-users


                                                                ***********=
********************************************************************
This e-mail message is intended solely for the use of the addressee.
The message may contain information that is privileged and=20
confidential.
Disclosure to anyone other than the intended recipient is prohibited.
If you are not the intended recipient, please do not disseminate,
distribute or copy this communication, by e-mail or otherwise. Instead,
please notify us immediately by return e-mail(including the original
message with your reply) and then delete and discard all copies of the
message. We have taken precautions to minimize the risk of  transmitting
software viruses but nevertheless advise you to carry out your own
virus checks on any attachment to this message.  We accept
no liability for any loss or damage caused by software viruses.
***************************************************************************=
****