| Register | FAQ | Calendar | Search | Today's Posts | Mark Forums Read |
|
#1
| |||
| |||
| In article <406ad19e$1@news.fhg.de>, Axel F <fix@iff.fhg.de> wrote: >> It is very easy to confirm that omniORB only listens on the port you >> tell it. For example, run eg2_impl with -ORBendPoint giop:tcp::12345 >> then run netstat -a -o (on a recent Windows version). You'll see that >> the eg2_impl process is only listening on port 12345. > >Its the same: the ports 10001 to 10010 and the port 12345. Ok, the >port 10000 is reserved for the nameservice (this is configured for >the old version in the registry at SOFTWARE\ORL\omniORB\2.0). Could >it be a configuration problem with my old omniORB version? The old configuration shouldn't affect it. Please send a trace from traceLevel 25. Also include the exact command you are running, with all its command line arguments. Cheers, Duncan. -- -- Duncan Grisby -- -- duncan@grisby.org -- -- http://www.grisby.org -- |
|
#2
| |||
| |||
| Thank you for your help. I have found the ORBendPoint entries in my registry. I have removed all entries and now it works with my command line parameters. Ciao, Axel |
![]() |
| Thread Tools | |
| Display Modes | |
In an effort to better serve ads to our visitors, cookies are used on objectmix.com. For more information, check out our Privacy Policy.