>Mark,
>Your server could create a custom POA with SINGLE_THREAD_MODEL specified for
its
>threading policy. There is also a command line parameter I see called
>"-ORBThreadPerConnection" that might do what you need.
>Rob
Thanks for you help - however, I tried this and got confusing results. When
I created my own POA with SINGLE_THREAD_MODEL, I still got the same behavior as
before (messages out of sequence). So I tried the ORBThreadPerConnection
argument, and the results look better (less out of sequence) - but still out of
sequence.
What I don't understand, is if I create my own POA with a single thread, and
I use the "-ORBThreadPerConnection 1" argument in the debugger, I still get 5
threads. As far as I can tell these threads are...
1. CORBA::ORB::run
2. MICOMT::Thread::ThreadWrapper (for MICO::IIOPServer)
3. MICOMT::Thread::ThreadWrapper (for MICO::GIOPConnReader -
SelectDispatcher)
4. MICOMT::Thread::ThreadWrapper (for MICO::GIOPConnReader -
SelectDispatcher)
5. MICOMT::Thread::ThreadWrapper (for MICO::GIOPConnReader - TCPTransport).
I'm trying to understand how these work together. My server shouldn't care
if it's single or multi-thread (right now it's single). My client creates it's
own corba instance (so that the server can call back to the client whenever).
This client isn't doing anything else other than orb->run. I do have other
clients that are a gui and have to have multi-thread - but I'm trying to get
the simplest case to work first.
Thanks for any help - I've been wracking my brain for a few months and I'm
stumped.
Mark
---------------------------------
It's here! Your new message!
Get new email alerts with the free Yahoo! Toolbar.
_______________________________________________
Mico-devel mailing list
Mico-devel@mico.org
http://www.mico.org/mailman/listinfo/mico-devel
