[Quickfix-developers] Re: [Quickfix-users] threading growth issue?

[Brian E. <azz...@ya...>]

Alvin -

This sounds like it might be related to the between sessions socket
creation bug that was fixed in 10.0.0.

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

I don't know enough about the JNI implementation, but if the thread
spawned during the creation of the socket didn't get killed when the
socket was closed, it could cause the behavior you're describing.

You might want to try 1.10.2 and see if the problem remains.

- Brian Erst
Thynk Software, Inc.

--- Alvin Wang <AW...@FF...> 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.
>
**********************************************************************
> 
>