[omniORB] eg3_impl in Echo example does not work well

[Emmanuel Saint-Loubert]

Hello,

I suspect this might a problem of set-up with the OmniORB.cfg file

When you start OmniNames for the first time you need to set up the omniORB.cfg  file
(see the on-line doc on how to do that at
http://www.orl.co.uk/omniORB/doc/omniNames/node3.html#SECTION00030000000000000000)

This is because the eg3_impl program makes a call to :

    resolve_initial_references("NameService")

    this call actually will return the IOR of the root context of the Naming Service
as found in the omniORB.cfg. This is why it is important to set-up the omniORB.cfg
file with the correct IOR (as printed out the *first* time you run the
NamingService). For example:

Also it is best to set-up the 2 environment variable which control where the
omniORB.cfg file is located and where the NamingService "log" all the naming service
entries

    setenv OMNIORB_CONFIG                  /home/saintlou/omniORB.cfg
    setenv OMNINAMES_LOGDIR            /home/saintlou/names

Finally, please note that you should use the "-start" option only the *first* time
you invoke OmniORB. If you want to re-initialize your NamingService you will need to
clear the log files first (ie delete the content of the directory located  under
$OMNINAMES_LOGDIR)

Best regards,

-- Emmanuel R. Saint-Loubert         saintlou@tumbleweed.com
   Tumbleweed Software Corp.       http://www.tumbleweed.com
   2010 Broadway                            Tel 650-569-3676
   Redwood City, CA 94063                   Fax 650-369-7197


Kazuyuki Imada wrote:

> Hi,
>
> I built echo example with gcc 2.7.2 on Solaris.
> But it does not work well and wrote core.
>
> First I started omniNames:
>
> % omniNames -start 2057
>
> Tue Aug 18 13:23:41 1998:
>
> Starting omniNames for the first time.
> Wrote initial log file.
> Read log file successfully.
> Root context is
> IOR:001989a70000002849444c3a6f6d672e6f72672f436f734e616d696e672f
> 4e616d696e67436f6e746578743a312e3000000000010000000000000028000100000000000c3137
>
> 322e32372e362e373400080900000000000c35d901cd48a2d8eb00000001
> Checkpointing Phase 1: Prepare.
> Checkpointing Phase 2: Commit.
> Checkpointing completed.
>
> ------------------------------------------------
> Next I run eg3_impl (with GDB):
>
> % gdb eg3_impl
> GDB is free software and you are welcome to distribute copies of it
>  under certain conditions; type "show copying" to see the conditions.
> There is absolutely no warranty for GDB; type "show warranty" for
> details.
> GDB 4.15.3 (sparc-sun-solaris2.5),
> Copyright 1996 Free Software Foundation, Inc...
> (gdb) r
> Starting program:
> /export/home/imada/omniORB_2.5.0/src/examples/echo/eg3_impl
>
> Program received signal SIGABRT, Aborted.
> 0xef5e0edc in __sigprocmask ()
> (gdb) bt
> #0  0xef5e0edc in __sigprocmask ()
> #1  0xef5d9b70 in __bounceself ()
> #2  0xef5d4f6c in cond_timedwait ()
> #3  0xef5e0e34 in _sleep ()
> #4  0x138e88 in abort ()
> #5  0x161754 in __default_terminate ()
> #6  0x1617ac in terminate ()
> (gdb)
>
> It looks omniNames works well, but eg3_impl is clashed.
>
> Let me know what I should do for this problem.
>
> Any comments or helps would be apreciated.
>
> - Kazu
>
> ---
> Kazuyuki Imada
> Canon Sales Co., Inc.
> Solution SE Dept.
>
> Phone: +81 (3) 5232-8334
> Fax  : +81 (3) 5443-0316
> Email: imada@solmi.canon-sales.co.jp