[omniORB] omniORB4.0 and orblink
baileyk@schneider.com
baileyk@schneider.com
Mon Feb 3 15:55:02 2003
You could try to adjust the GIOP/IIOP configuration of the omniORB process.
First, try to set omniORB to use GIOP 1.0 rather than the default 1.2.
Then you could try to set the "lcdMode" parameter to 1. If these don't
help, then see if you can get a trace from both processes ( traceLevel 40
for the omniOrb side ). Post the results. You could post the results of a
catior on an orblink IOR too (or the IOR itself). Then maybe someone on
the list will be able to see what's going on.
Kendall
Christian Au <au@ira.uka.de>
Sent by: To: omniorb-list@omniorb-support.com
omniorb-list-admin@omniorb-s cc:
upport.com Fax to:
Subject: [omniORB] omniORB4.0 and orblink
02/03/2003 08:50 AM
Hi everyone,
i have a problem when communicating between c++ objects, using omniORB4.0,
and lisp objects, using orblink. calling a c++ function
from lisp is no problem, but it's not possible to call a lisp-function
from a c++ object!
the poa-dispatcher of orblink recieves an empty message, which leads to an
error in lisp.
everything is going fine when i use mico instaed of omniorb for c++
(nevertheless i want to stick to omniORB if possible!), so it seems to be
a problem of
omniorb!?
has anyone encoutered the same problem or knows what could be the reason
for this error?
Thanks,
Christian
_______________________________________________
omniORB-list mailing list
omniORB-list@omniorb-support.com
http://www.omniorb-support.com/mailman/listinfo/omniorb-list