[omniORB-dev] ThreadPoll model problems

[Serguei Kolos]

Hello

I'm using omniORB 4.0.2 with gcc 32. Everything works fine for the 
ThreadPerConnection model.
When I switched to the ThreadPool model I have found several problems:

1. It seems that with the ThreadPool I can't set 
maxServerThreadPerConnection to 1.
    This simply doesn't work - the client, which is trying to connect to 
the server, which
    has this settings, just hangs.
    My question is - is this known issue or it is not an issue or this 
is a bug or what is it?

2. My server hangs during the ORB shutdown. It never hangs if I'm using 
the ThreadPerConnection
    model and always hangs with the ThreadPool. The trace attached.
    Does somebody have a clue to this?

omniORB: Scavenger reduce idle count for strand 0x8066f78 to 34
omniORB: Scan for idle connections done (1077536154,714237000).
23/2/04 12:35:58 :: [::main] signal 2 has been received - exiting ... 
omniORB: State root/ipc/partition<initial> (active) -> dea
ctivating
omniORB: POA(ipc/partition) etherealising object 
root/ipc/partition<initial> (deactivating).
 id: IDL:ipc/partition:1.0
omniORB: State root/ipc/partition<initial> (deactivating) -> etherealising
omniORB: Removing root/ipc/partition<initial> (etherealising) from 
object table
omniORB: RefCountServantBase has zero ref count -- deleted.
done
omniORB: Object table entry root/ipc/partition<initial> (dead) deleted.
omniORB: ObjRef(IDL:ipc/partition:1.0) -- deleted.
omniORB: Preparing to shutdown ORB.
omniORB: Destroying POA(RootPOA).
omniORB: Destroying POA(ipc/partition).
omniORB: Deactivating all POA(ipc/partition)'s objects.
omniORB: Waiting for requests to complete on POA(ipc/partition).
omniORB: Requests on POA(ipc/partition) completed.
omniORB: Etherealising POA(ipc/partition)'s objects.
omniORB: Destruction of POA(ipc/partition) complete.
omniORB: Deactivating all POA(RootPOA)'s objects.
omniORB: Waiting for requests to complete on POA(RootPOA).
omniORB: Requests on POA(RootPOA) completed.
omniORB: Etherealising POA(RootPOA)'s objects.
omniORB: giopServer waits for completion of rendezvousers and workers
omniORB: AsyncInvoker: thread id = 3 has exited. Total threads = 3
omniORB: Scan for idle connections (1077536159,716158000)
omniORB: Scavenger reduce idle count for strand 0x8066f78 to 33
omniORB: Scan for idle connections done (1077536159,716158000).
omniORB: Scan for idle connections (1077536164,720051000)
omniORB: Scavenger reduce idle count for strand 0x8066f78 to 32
omniORB: Scan for idle connections done (1077536164,720051000).
omniORB: AsyncInvoker: thread id = 1 has exited. Total threads = 2
omniORB: Scan for idle connections (1077536169,722022000)
omniORB: Scavenger reduce idle count for strand 0x8066f78 to 31
omniORB: Scan for idle connections done (1077536169,722022000).
omniORB: Scan for idle connections (1077536174,723966000)
omniORB: Scavenger reduce idle count for strand 0x8066f78 to 30
omniORB: Scan for idle connections done (1077536174,723966000).
omniORB: Scan for idle connections (1077536179,725935000)
omniORB: Scavenger reduce idle count for strand 0x8066f78 to 29
omniORB: Stopping serving incoming endpoints.
...
omniORB: Scavenger reduce idle count for strand 0x8066f78 to 1
omniORB: Scan for idle connections done (1077536319,780618000).
omniORB: Scan for idle connections (1077536324,782560000)
omniORB: Scavenger reduce idle count for strand 0x8066f78 to 0
omniORB: Scavenger close connection from giop:tcp:137.138.90.234:2742
omniORB: Scan for idle connections done (1077536324,782560000).
omniORB: Scan for idle connections (1077536329,784570000)
omniORB: Scan for idle connections done (1077536329,784570000).
omniORB: Scan for idle connections (1077536334,786448000)
omniORB: Scan for idle connections done (1077536334,786448000).
omniORB: Scan for idle connections (1077536339,788412000)
omniORB: Scan for idle connections done (1077536339,788412000).
omniORB: Scan for idle connections (1077536344,790376000)
omniORB: Scan for idle connections done (1077536344,790376000).
...