[omniORB] automatic generating thread at every omniORB related functions

[zhang ji]

Hi Duncan,

With tracelevel 25 I got below message:
"
...
omniORB: tcpSocketMTfactory Rendezvouser: block on
accept()
omniORB: tcpSocketMTfactory Rendezvouser: unblock from
accept()
omniORB: tcpSocketMTfactory Rendezvouser: accept new
strand.
omniORB: tcpSocketMTfactory Worker: start.
omniORB: throw omniConnectionBroken (minor 9) from
tcpSocketMTfactory.cc:1060
omniORB: tcpSocketMTfactory Worker: #### Connection
closed.
omniORB: tcpSocketMTfactory Worker: exit.
omniORB: tcpSocketMTfactory Worker: start.
omniORB: throw omniConnectionBroken (minor 9) from
tcpSocketMTfactory.cc:1060
omniORB: tcpSocketMTfactory Rendezvouser: block on
accept()
omniORB: tcpSocketMTfactory Rendezvouser: unblock from
accept()
omniORB: tcpSocketMTfactory Rendezvouser: accept new
strand.
omniORB: tcpSocketStrand::~Strand() close socket no. 0
omniORB: tcpSocketMTfactory Worker: #### Connection
closed.
omniORB: tcpSocketMTfactory Worker: start.
...
"

Thanks,
Shifeng

--- Duncan Grisby <duncan@grisby.org> wrote:
> On Wednesday 18 September, zhang ji wrote:
> 
> > I build one dynamical library libTest.so with
> which
> > one omniORB server links. 
> > By debugging the running of the omniORB server, I
> > found each omniORB related function call in the
> > omniORB server would generate a new thread,
> > espercially when the orb_run()  processed, there
> will
> > generate a lot of threads.
> 
> What does this libTest.so do?  It sounds like the
> problem must be with
> that. Can you get a trace from omniORB with trace
> level 25?
> 
> Cheers,
> 
> Duncan.
> 
> -- 
>  -- Duncan Grisby         --
>   -- duncan@grisby.org     --
>    -- http://www.grisby.org --


__________________________________________________
Do you Yahoo!?
New DSL Internet Access from SBC & Yahoo!
http://sbc.yahoo.com