[omniORB] Server and client block in Thread Pool model -SOLVE D ???

[Serguei Kolos]

Thank you for the hint. You are right. This is exactly the case for me.
Does anybody can answer to the following questions:
1. If it is a bug then will be fixed in the upcoming release?
2. What is a minimum safe value for the ORBmaxServerThreadPerConnection 
? probably 2 ?
Cheers,
Sergei

Malge Nishant wrote:

>As per my knowledge if we use "ORBmaxServerThreadPerConnection  1", in some
>cases the connection is not set watchable properly. If the thread which was
>executing the upcall fails to set the Connection watchable then the
>Monitoring thread will never watch that connection and is left use less. 
>Please let your client and server run for some more time. ORB will close the
>IDLE connections after a while then your client and server should start
>working again... If they really do then above is the problem.
>
>
>Thankx
>Nishant
>-----Original Message-----
>From: Serguei Kolos [mailto:Serguei.Kolos at cern.ch]
>Sent: Tuesday, July 15, 2003 2:59 PM
>
>Thread Pool model. There is probably a bug somewhere in the omni library.
>
>
>_______________________________________________
>omniORB-list mailing list
>omniORB-list at omniorb-support.com
>http://www.omniorb-support.com/mailman/listinfo/omniorb-list
>  
>