[jacorb-developer] Re: [omniORB] Problem with communication b etween JacORB and OmniORB

[Wilson Jimmy - jiwils]

I use JacORB 1.3.30 in conjunction with omniORBpy 1.4.  omniORBpy works fine
as the client to a JacORB server. 

Are you talking about a bug/fix in JacORB 1.4 (post beta 4), or a bug in the
beta of the omniORB 4 release?

Jimmy
-- 
James "Jimmy" Wilson
Software Developer, Acxiom Corporation

-----Original Message-----
From: Steve Osselton [mailto:steve@prismtechnologies.com]
Sent: Wednesday, May 01, 2002 2:34 AM
To: shamus@tdcadsl.dk
Cc: omniorb-list@omniorb.org;
jacorb-developer@lists.spline.inf.fu-berlin.de
Subject: Re: [jacorb-developer] Re: [omniORB] Problem with communication
between JacORB and OmniORB


I think this is a known bug that has been fixed (sadly post beta 4).
OmniORB initially sends a GIOP LocateRequest prior to the actual
request. As part of the GIOP 1.2 updates this functionality had been
lost.

Cheers Steve.

bjorn rohde jensen wrote:
> Hi Vibhu,
> 
>  I did not experience any problems last i had JacORB and omniORB
> talk to each other, but that was a while ago. Have you tried to
> run a network sniffer to see, what the orbs are saying to each
> other, and have you examined traces from both omniORB and JacORB?
> 
> Yours sincerely,
> 
> Bjorn
> 
> Vibhu Rishi wrote:
> 
>>Hi,
>>I am running JacORB as the server and OmniORB as client. When i Try to
>>send a request from the omni client, it never reaches the JacORB server.
>>using gdb i could go till the stub code of omniORB, where it hangs at
>>the _invoke method.
>>
>>The interface as defined in my IDL file is :
>>
>>void run(in long funPtr,
>>                 in Key objKey,
>>                 in Reason r,
>>                 in TrapKey tKey,
>>                 in long clientID);
>>
>>(note Key, Reason, Trap etc are my own data structures).
>>
>>This works with an omniORB Client and OmniORB Server, but not when the
>>server is JacORB.
>>
>>Has anyone else encountered this problem before ?
>>
>>regards
>>vibhu..
>>
>>  ------------------------------------------------------------------------
>>                           Name: Wipro_Disclaimer.txt
>>   Wipro_Disclaimer.txt    Type: Plain Text (text/plain)
>>                       Encoding: 7bit
> 
> _______________________________________________
> jacorb-developer maillist  -
jacorb-developer@lists.spline.inf.fu-berlin.de
> http://lists.spline.inf.fu-berlin.de/mailman/listinfo/jacorb-developer
> 
> 



_______________________________________________
jacorb-developer maillist  -  jacorb-developer@lists.spline.inf.fu-berlin.de
http://lists.spline.inf.fu-berlin.de/mailman/listinfo/jacorb-developer


********************************************************************

The information contained in this communication is
confidential, is intended only for the use of the recipient
named above, and may be legally privileged.
If the reader of this message is not the intended
recipient, you are hereby notified that any dissemination, 
distribution, or copying of this communication is strictly
prohibited.
If you have received this communication in error,
please re-send this communication to the sender and
delete the original message or any copy of it from your
computer system. Thank You.