It is Initiator. Only one session. Version is quickfix-1.9.4. OS is Windows Server 2003
SP1.
The reason we use JConsole to monitor QF is that we updated from Java
1.5.0_02 to 1.5.0_04 and then the FIX engine crash once or twice every day
(sometimes when session is up and sometime session is down). I do not know
if the crash has anything to do with threading growth. We did not have
the crash when we used Java 1.5.0_02, but I do not know what about
threading growth issue under 1.5.0_02. I also am not sure if the crash is
related to java itself or to QF.
Thanks!
Oren Miller <or...@qu...>
07/21/2005 11:53 AM
To: Alvin Wang <AW...@FF...>
cc: qui...@li..., quickfix-users list
<qui...@li...>
bcc:
Subject: Re: threading growth issue?
Please give more details on your configuration.
ThreadedSocketAcceptor? Initiator? Number of sessions... version of
QF... operating system...
--oren
On Jul 21, 2005, at 2:39 PM, Alvin Wang wrote:
>
> Hi,
>
> I configure my QF(Java/JNI) engine something like:
> StartTime=08:00:00
> EndTime=23:55:00
>
> I use JConsole (java 1.5.04) to monitor the QF engine's JVM. Before
> the endtime, there were less than 20 threads running. After that,
> the # of threads kept climbing progressively to about 2000 until
> StartTime. After QF re-create the session, the # of thread stopped
> growing.
>
> Can anyone explain to me what is going on here? It looks very
> disturbing.
>
> Thanks
> Alvin
> **********************************************************************
> 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.
> **********************************************************************
|
