orbitcpp-list

Re: [orbitcpp-list] running orbitcpp client and server programs from separate machines

[Bill L. <the...@ya...>]

Phil,

Thanks for your response.  

I am not sure that we are both talking about the same
problem, though, because the crash I referred to in my
previous message is completely reproducible--it
happens every time I try to run the sample on machines
A and C or B and C.  However, I will try the later
versions and let you know if that fixes the problem.

-Bill Lasley

--- Phil Dawes <ph...@or...>
wrote:
> Bill Lasley writes:
>  > Hi,
>  > 
>  > I installed ORBit-0.5.0-1, ORBit-devel-0.5.0-1, 
> orbitcpp-0.22-1, and
>  > orbitcpp-0.22-1 on three machines, all running
> RedHat 6.1.  As far as
> I
>  > can tell, all three machines have similar network
> configurations.
>  > 
>  > I built and ran the simple helloworld sample on
> various combinations
> of
>  > these machines (call them A, B, and C).
>  > 
>  > I perverted the sample slightly so that the
> programs could read and
>  > write IOR strings from an LDAP server on A.
>  > 
>  > Running server on A and client on A works.
>  > Running server on B and client on B works.
>  > Running server on C and client on C works.
>  > 
>  > Running server on A and client on B works.
>  > Running server on B and client on A works.
>  > 
>  > Running server on A and client on C causes the
> client to crash and
> dump
>  > core.
>  > Running server on C and client on A causes the
> client to crash and
> dump
>  > core.
>  > 
>  > I added code to trap exceptions in the client
> program, and it appears
> to
>  > be a system exception, minor code of 5, thrown
> when the client
> program
>  > calls the _narrow() function.
>  > 
>  > I can't figure out why the sample works for A and
> B but not for A and
>  > C.  I thought maybe C might have too low a limit
> on open file
>  > descriptors, but that was not the case (1024 for
> all machines).
>  > 
>  > Is there a particular setting that causes client
> crashes (untrapped
>  > exception, minor code 5) when the orbitcpp
> helloworld samples are run
> on
>  > two separate machines?
>  > 
>  > The ORBit source code looks like a steep learning
> curve, so I thought
>  > I would ask around before I go any further into
> the source, in case
>  > there is something very simple wrong here.   I am
> not very
> knowledgeable
>  > about CORBA in general, which is why I used the
> ldap server instead
> of
>  > the orbit name server.
>  > 
>  > If anybody has any suggestions, I am (like Ross
> Perot) all ears.
>  > 
> 
> Hi Bill,
> 
> There was a dodgy memory bug in that version, and it
> didn't get fixed
> (because I couldn't repeat it ;-) until version
> 0.25.1.
> I suggest you get ORBit-0.5.1 and orbitcpp-0.25.1
> (from
> ftp://orbitcpp.sourceforge.net/pub/orbitcpp)
> 
> Hope this helps,
> 
> Phil.
> 
> _______________________________________________
> orbitcpp-list mailing list
> orb...@li...
>
http://lists.sourceforge.net/mailman/listinfo/orbitcpp-list
> 
__________________________________________________
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
http://im.yahoo.com

Re: [orbitcpp-list] running orbitcpp client and server programs from separate machines

[Bill L. <the...@ya...>]

Phil,

I downloaded, built, and installed ORBit 0.5.1, and then I went to your site
and downloaded orbitcpp-0.25.1.  I ran ./configure, but the make reported
errors trying to build the test programs.  I removed the test directory from
the list of targets and was then able to complete the make and make install,
but when I try to run make on my app, I get the following error:

orbit-idl2cpp ../admanager.idl
Traceback (innermost last):
  File "/usr/local/bin/orbit-idl2cpp", line 11, in ?
    from orbit_idl2cpp.commonfile import CommonGenerator
ImportError: cannot import name CommonGenerator
make[2]: *** [admanager.hh] Error 1

If it makes any difference, I am running RedHat 6.1, which came with gcc
version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)

So here are my questions:

- Does the idl2cpp error above look familiar?  Is there an easy fix?  Sorry
to bug you with this, but I really don't know anything about python.

- Is there a devel version of orbitcpp 0.25.1 that I also need, or does your
tar file have everything required for development?


Thanks.

-Bill Lasley



--- Phil Dawes <ph...@or...> wrote:
> Bill Lasley writes:
>  > Hi,
>  > 
>  > I installed ORBit-0.5.0-1, ORBit-devel-0.5.0-1,  orbitcpp-0.22-1, and
>  > orbitcpp-0.22-1 on three machines, all running RedHat 6.1.  As far as
> I
>  > can tell, all three machines have similar network configurations.
>  > 
>  > I built and ran the simple helloworld sample on various combinations
> of
>  > these machines (call them A, B, and C).
>  > 
>  > I perverted the sample slightly so that the programs could read and
>  > write IOR strings from an LDAP server on A.
>  > 
>  > Running server on A and client on A works.
>  > Running server on B and client on B works.
>  > Running server on C and client on C works.
>  > 
>  > Running server on A and client on B works.
>  > Running server on B and client on A works.
>  > 
>  > Running server on A and client on C causes the client to crash and
> dump
>  > core.
>  > Running server on C and client on A causes the client to crash and
> dump
>  > core.
>  > 
>  > I added code to trap exceptions in the client program, and it appears
> to
>  > be a system exception, minor code of 5, thrown when the client
> program
>  > calls the _narrow() function.
>  > 
>  > I can't figure out why the sample works for A and B but not for A and
>  > C.  I thought maybe C might have too low a limit on open file
>  > descriptors, but that was not the case (1024 for all machines).
>  > 
>  > Is there a particular setting that causes client crashes (untrapped
>  > exception, minor code 5) when the orbitcpp helloworld samples are run
> on
>  > two separate machines?
>  > 
>  > The ORBit source code looks like a steep learning curve, so I thought
>  > I would ask around before I go any further into the source, in case
>  > there is something very simple wrong here.   I am not very
> knowledgeable
>  > about CORBA in general, which is why I used the ldap server instead
> of
>  > the orbit name server.
>  > 
>  > If anybody has any suggestions, I am (like Ross Perot) all ears.
>  > 
> 
> Hi Bill,
> 
> There was a dodgy memory bug in that version, and it didn't get fixed
> (because I couldn't repeat it ;-) until version 0.25.1.
> I suggest you get ORBit-0.5.1 and orbitcpp-0.25.1 (from
> ftp://orbitcpp.sourceforge.net/pub/orbitcpp)
> 
> Hope this helps,
> 
> Phil.
> 
> _______________________________________________
> orbitcpp-list mailing list
> orb...@li...
> http://lists.sourceforge.net/mailman/listinfo/orbitcpp-list
> 
__________________________________________________
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
http://im.yahoo.com

Re: [orbitcpp-list] running orbitcpp client and server programs from separate machines

[Phil D. <ph...@us...>]

Bill Lasley wrote:
> 
> Phil,
> 
> I downloaded, built, and installed ORBit 0.5.1, and then I went to your site
> and downloaded orbitcpp-0.25.1.  I ran ./configure, but the make reported
> errors trying to build the test programs.  I removed the test directory from
> the list of targets and was then able to complete the make and make install,
> but when I try to run make on my app, I get the following error:
> 
> orbit-idl2cpp ../admanager.idl
> Traceback (innermost last):
>   File "/usr/local/bin/orbit-idl2cpp", line 11, in ?
>     from orbit_idl2cpp.commonfile import CommonGenerator
> ImportError: cannot import name CommonGenerator
> make[2]: *** [admanager.hh] Error 1
> 
> If it makes any difference, I am running RedHat 6.1, which came with gcc
> version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)
> 
> So here are my questions:
> 
> - Does the idl2cpp error above look familiar?  Is there an easy fix?  Sorry
> to bug you with this, but I really don't know anything about python.
> 

I think it's a missing PYTHONPATH error - have you read README.PYTHON?

> - Is there a devel version of orbitcpp 0.25.1 that I also need, or does your
> tar file have everything required for development?
> 

The tar file should contain everything. BTW, If you haven't already, I
recommend you uninstall the redhat orbitcpp rpm before attempting to
build/install ORBit-C++.

Hope this helps,

Phil.