[omniORB] Troubles with incoming connections when using versi on4.0.4 with MSDev

[Sébastien Bouchex]

Fred,
 
Apparently, I just saw that this problem has been fixed on August 17th
(according to the CVS update.log file). I'm building the latest snapshot to
check if the problem is fixed.
 
Seb

  _____  

From: Frederic Prin [mailto:frederic.prin at silvaco.com] 
Sent: Wednesday, September 08, 2004 2:57 PM
To: 'Sébastien Bouchex'; omniorb-list at omniorb-support.com
Subject: RE: [omniORB] Troubles with incoming connections when using
version4.0.4 with MSDev


Hi,
 
I think it is one of the major windows specific bug that appears with the
4.0.4 omniORB version.
Have a look at the attached mail from the omniORB mailling list.
(you can search for all Re: message on this topic from the mailing list...
there are some interresting ones!)
 
HIH
 
Fred
 
 

-----Original Message-----
From: omniorb-list-bounces at omniorb-support.com
[mailto:omniorb-list-bounces at omniorb-support.com] On Behalf Of Sébastien
Bouchex
Sent: mercredi 8 septembre 2004 14:16
To: 'omniorb-list at omniorb-support.com'
Subject: [omniORB] Troubles with incoming connections when using
version4.0.4 with MSDev


Hello,
 
We have some troubles with the latest version (4.0.4) of OmniOrb when
launched withinh the the MS Dev app : Connections are never accepted.
 
Here is what we are using to reproduce the problem :
- The test is done with the anyExample sample code provided in the ofifcial
package. The binary is anyExample_impl.exe built with the regular makefile.
- We are using the OmniOrb dll coming from the official package.
- We are using Visual C++ 2002.
- OmniOrb tracing has been enable with traceLevel = 25
 
To test the connection, I simply telnet to the port displayed in the log of
the the sample app. I know that it's not the right client but that's not
important.
 
- When the binary is launched from a command prompt, everything is fine. The
log shows that there is an incoming connection, so something like that :
omniORB: Server accepted connection from giop:tcp:192.168.0.1:2904
omniORB: AsyncInvoker: thread id = 2 has started. Total threads = 3
omniORB: AsyncInvoker: thread id = 3 has started. Total threads = 3
omniORB: Scavenger task execute.
omniORB: giopWorker task execute.
omniORB: Accepted connection from giop:tcp:10.1.12.118:2904 because of this
rule: "* unix,ssl,tcp"
 
- When the same binary is launched from Visual C++ 2002, the log does not
show anything and the connection hangs.
 
I have attached the log to this message.
 
Thanks
Seb
 
Sébastien BOUCHEX BELLOMIE - Senior Software Engineer 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.omniorb-support.com/pipermail/omniorb-list/attachments/20040908/2f1d01ce/attachment.htm