[Quickfix-developers] Re: threading growth issue? also possible crash issues....

[Oren M. <or...@qu...>]

Please attach the relevant portion of your log files.

--oren
  ----- Original Message -----=20
  From: Alvin Wang=20
  To: Joerg Thoennes=20
  Cc: Oren Miller ; qui...@li... ; =
qui...@li...=20
  Sent: Wednesday, July 27, 2005 9:48 AM
  Subject: Re: threading growth issue? also possible crash issues....



  I upgraded to QF 1.10.2  (Java/JNI). The crash issue got worse, 4-5 =
times per day.=20

  Another issue with 1.10, when the counterparty (acceptor) sends logon =
message with wrong seq number, the toAdmin method is not called.=20
  In addition, it seems the onLogout method is called instead, and then =
another logon message is sent out from QF to the counterparty. As the =
result, it becomes a deadlock. Is there a better way to handle this?=20

  Thanks=20
  Alvin=20




       Joerg Thoennes <Joe...@ma...>=20
        Sent by: qui...@li...=20
        07/21/2005 02:23 PM=20

              =20
                To:        Alvin Wang <AW...@FF...>=20
                cc:        Oren Miller <or...@qu...>, =
qui...@li..., quickfix-users list =
<qui...@li...>=20
                bcc:        =20
                Subject:        [Quickfix-developers] Re: =
[Quickfix-users] Re: threading growth issue?=20



  QuickFIX Documentation: =
http://www.quickfixengine.org/quickfix/doc/html/index.html
  QuickFIX FAQ: =
http://www.quickfixengine.org/wikifix/index.php?QuickFixFAQ
  QuickFIX Support: http://www.quickfixengine.org/services.html

  Alvin Wang wrote:
  > It is Initiator. Only one session. Version is quickfix-1.9.4. OS is =
Windows Server 2003=20
  > SP1.
  >=20
  > The reason we use JConsole to monitor QF is that we updated from =
Java=20
  > 1.5.0_02 to 1.5.0_04 and then the FIX engine crash once or twice =
every day=20
  > (sometimes when session is up and sometime session is down). I do =
not know=20
  > if the crash has anything to do with threading growth.  We did not =
have=20
  > the crash when we used Java 1.5.0_02, but I do not know what about=20
  > threading growth issue under 1.5.0_02.  I also am not sure if the =
crash is=20
  > related to java itself or to QF.=20

  Maybe this sections from the 1.10.0 release notes is relevant, since =
the # of threads=20
  climbs until StartTime:

  > Initiator will no longer initiate socket connections outside of the =
session
  > time.  Previously it would connect and immediately close connection =
during
  > every retry interval.

  Oren, perhaps you can give more details what you have changed here.

  Cheers, J=F6rg

  --=20
  Joerg Thoennes
                                 http://macd.com
  Tel.: +49 (0)241 44597-24      Macdonald Associates GmbH
  Fax : +49 (0)241 44597-10      Lothringer Str. 52, D-52070 Aachen


  -------------------------------------------------------
  SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
  from IBM. Find simple to follow Roadmaps, straightforward articles,
  informative Webcasts and more! Get everything you need to get up to
  speed, fast. =
http://ads.osdn.com/?ad_id=3D7477&alloc_id=3D16492&op=3Dclick
  _______________________________________________
  Quickfix-developers mailing list
  Qui...@li...
  https://lists.sourceforge.net/lists/listinfo/quickfix-developers


  ********************************************************************** =
This e-mail message is intended solely for the use of the addressee. The =
message may contain information that is privileged and 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. =
**********************************************************************