🚀 go-pugleaf

sonyantony@hotmail.com (Sony Antony) wrote in message news:<3eb007f1.0112191107.79f369e7@posting.google.com>...
> Hi :
> I was investigating an incompatibility issue between visibroker and
> Orbix 2000. I found out that there is an extra service context being
> sent out with the request ( visibroker client ) that resulted in a
> MARSHAL exception from teh orbix server.


> What does the corba standard says about the service contexts. Can an
> ORB send any number of service contexts along with the requests. Or in
> other words is Service Context an optional 'exta' piece of info. 

I still dont know teh answer for the above. If anybody could please
help...


> 
> Thanks
> --sony
> The details of the situation.

The actual problem that prompted me to post this mail has been solved.
By trial & error, I found out that this doesn t happen if I force the
evenchannel to be created as a GIOP 1.2 object reference, using
policies:iiop:server_version_policy = "1.1";

in the 'event' configuration scope.




> Symptom :  A MARSHAL exception is thrown by the IONA event channel
> server ( itevent ) when visibroker client makes the call
> CosEventChannelAdmin::EventChannel::for_suppliers().
> Platforms : IONA Orbix 1.2.3 on Solaris 8 ( Java ) => server 
> Visibroker 4.5 ( java ) on Solaris 8 => client
> 
> 
> Here is the actual GIOP request ( captured using giop_snoop at the
> Orbix 2000 server end ). Notice the extra service context.
> ---------------------------------------------------
> 13:2:59 [Conn:3] In: (first for binding) [Request] GIOP v1.2 MsgLen:
> 164
> 
> Endian: big ReqId: 0 (two-way)
> 
> Target Address (0: KeyAddr) 
> 
> ObjKey (len 109) ':>.21.nucleusIIT_EventNamedRoot.IT_Event::EventChannelFactory.IT_NotificationActivator..IT_EventNamedRootxEC1'
> 
> Looks like an Orbix2000 Indirect Persistent key
> 
> Operation (len 14) 'for_suppliers' 
> 
> No. of Service Contexts: 1
> 
> Tag: 1447645955 (* unknown)
> 
> GIOP Hdr (len 12): [47][49][4f][50][01][02][00][00][00][00][00][a4]
> 
> Msg Hdr (len 160):
[00][00][00][00][01][00][00][00][00][00][00][00][00][00][00][6d][3a][3e][02][32][31][07][6e][75][63][6c][65][75][73][49][49][54][5f][45][76][65][6e][74][4e][61][6d][65][64][52][6f][6f][74][00][49][54][5f][45][76][65][6e][74][3a][3a][45][76][65][6e][74][43][68][61][6e][6e][65][6c][46][61][63][74][6f][72][79][00][49][54][5f][4e][6f][74][69][66][69][63][61][74][69][6f][6e][41][63][
> 4][69][76][61][74][6f][72][00][15][49][54][5f][45][76][65][6e][74][4e][61][6d][65][64][52][6f][6f][74][78][45][43][31][00][00][00][00][00][00][0e][66][6f][72][5f][73][75][70][70][6c][69][65][72][73][00][00][00][00][00][00][01][56][49][53][03][00][00][00][00]
> 
> Msg Body (len 4): [00][00][00][00]
> 
> [---- end of message ----] 
> 
> ---------------------------------------------------
> 
> Here is the exact same request sent from an IONA client, *with no
> exception*. Notice the absense of any service contexts.
> 
> -----------------------------------------------------
> 
> 13:13:19 [Conn:7] In: [Request] GIOP v1.2 MsgLen: 152 
> 
> Endian: big ReqId: 4 (two-way)
> 
> Target Address (0: KeyAddr) 
> 
> ObjKey (len 109) ':>.21.nucleusIIT_EventNamedRoot.IT_Event::EventChannelFactory.IT_NotificationActivator..IT_EventNamedRootxEC2'
> 
> Looks like an Orbix2000 Indirect Persistent key
> 
> Operation (len 14) 'for_suppliers' 
> 
> No. of Service Contexts: 0
> 
> GIOP Hdr (len 12): [47][49][4f][50][01][02][00][00][00][00][00][98]
> 
> Msg Hdr (len 152):
[00][00][00][04][03][00][00][00][00][00][00][00][00][00][00][6d][3a][3e][02][32][31][07][6e][75][63][6c][65][75][73][49][49][54][5f][45][76][65][6e][74][4e][61][6d][65][64][52][6f][6f][74][00][49][54][5f][45][76][65][6e][74][3a][3a][45][76][65][6e][74][43][68][61][6e][6e][65][6c][46][61][63][74][6f][72][79][00][49][54][5f][4e][6f][74][69][66][69][63][61][74][69][6f][6e][41][63][
> 4][69][76][61][74][6f][72][00][15][49][54][5f][45][76][65][6e][74][4e][61][6d][65][64][52][6f][6f][74][78][45][43][32][00][00][00][00][00][00][0e][66][6f][72][5f][73][75][70][70][6c][69][65][72][73][00][00][00][00][00][00][00]
> 
> [---- end of message ----] 
> 
> -----------------------------------------------
> 
> 1. Is there any way to configure visibroker to turn off this "extra"
> being sent.
> 
> 2. Is there any way to configure Orbix 2000 to ignore this "extra".
> 
> 
> --sony

sonyantony@hotmail.com (Sony Antony) wrote in message news:<3eb007f1.0112191107.79f369e7@posting.google.com>...
> Hi :
> I was investigating an incompatibility issue between visibroker and
> Orbix 2000. I found out that there is an extra service context being
> sent out with the request ( visibroker client ) that resulted in a
> MARSHAL exception from teh orbix server.


> What does the corba standard says about the service contexts. Can an
> ORB send any number of service contexts along with the requests. Or in
> other words is Service Context an optional 'exta' piece of info. 

I still dont know teh answer for the above. If anybody could please
help...


> 
> Thanks
> --sony
> The details of the situation.

The actual problem that prompted me to post this mail has been solved.
By trial & error, I found out that this doesn t happen if I force the
evenchannel to be created as a GIOP 1.2 object reference, using
policies:iiop:server_version_policy = "1.1";

in the 'event' configuration scope.




> Symptom :  A MARSHAL exception is thrown by the IONA event channel
> server ( itevent ) when visibroker client makes the call
> CosEventChannelAdmin::EventChannel::for_suppliers().
> Platforms : IONA Orbix 1.2.3 on Solaris 8 ( Java ) => server 
> Visibroker 4.5 ( java ) on Solaris 8 => client
> 
> 
> Here is the actual GIOP request ( captured using giop_snoop at the
> Orbix 2000 server end ). Notice the extra service context.
> ---------------------------------------------------
> 13:2:59 [Conn:3] In: (first for binding) [Request] GIOP v1.2 MsgLen:
> 164
> 
> Endian: big ReqId: 0 (two-way)
> 
> Target Address (0: KeyAddr) 
> 
> ObjKey (len 109) ':>.21.nucleusIIT_EventNamedRoot.IT_Event::EventChannelFactory.IT_NotificationActivator..IT_EventNamedRootxEC1'
> 
> Looks like an Orbix2000 Indirect Persistent key
> 
> Operation (len 14) 'for_suppliers' 
> 
> No. of Service Contexts: 1
> 
> Tag: 1447645955 (* unknown)
> 
> GIOP Hdr (len 12): [47][49][4f][50][01][02][00][00][00][00][00][a4]
> 
> Msg Hdr (len 160):
[00][00][00][00][01][00][00][00][00][00][00][00][00][00][00][6d][3a][3e][02][32][31][07][6e][75][63][6c][65][75][73][49][49][54][5f][45][76][65][6e][74][4e][61][6d][65][64][52][6f][6f][74][00][49][54][5f][45][76][65][6e][74][3a][3a][45][76][65][6e][74][43][68][61][6e][6e][65][6c][46][61][63][74][6f][72][79][00][49][54][5f][4e][6f][74][69][66][69][63][61][74][69][6f][6e][41][63][
> 4][69][76][61][74][6f][72][00][15][49][54][5f][45][76][65][6e][74][4e][61][6d][65][64][52][6f][6f][74][78][45][43][31][00][00][00][00][00][00][0e][66][6f][72][5f][73][75][70][70][6c][69][65][72][73][00][00][00][00][00][00][01][56][49][53][03][00][00][00][00]
> 
> Msg Body (len 4): [00][00][00][00]
> 
> [---- end of message ----] 
> 
> ---------------------------------------------------
> 
> Here is the exact same request sent from an IONA client, *with no
> exception*. Notice the absense of any service contexts.
> 
> -----------------------------------------------------
> 
> 13:13:19 [Conn:7] In: [Request] GIOP v1.2 MsgLen: 152 
> 
> Endian: big ReqId: 4 (two-way)
> 
> Target Address (0: KeyAddr) 
> 
> ObjKey (len 109) ':>.21.nucleusIIT_EventNamedRoot.IT_Event::EventChannelFactory.IT_NotificationActivator..IT_EventNamedRootxEC2'
> 
> Looks like an Orbix2000 Indirect Persistent key
> 
> Operation (len 14) 'for_suppliers' 
> 
> No. of Service Contexts: 0
> 
> GIOP Hdr (len 12): [47][49][4f][50][01][02][00][00][00][00][00][98]
> 
> Msg Hdr (len 152):
[00][00][00][04][03][00][00][00][00][00][00][00][00][00][00][6d][3a][3e][02][32][31][07][6e][75][63][6c][65][75][73][49][49][54][5f][45][76][65][6e][74][4e][61][6d][65][64][52][6f][6f][74][00][49][54][5f][45][76][65][6e][74][3a][3a][45][76][65][6e][74][43][68][61][6e][6e][65][6c][46][61][63][74][6f][72][79][00][49][54][5f][4e][6f][74][69][66][69][63][61][74][69][6f][6e][41][63][
> 4][69][76][61][74][6f][72][00][15][49][54][5f][45][76][65][6e][74][4e][61][6d][65][64][52][6f][6f][74][78][45][43][32][00][00][00][00][00][00][0e][66][6f][72][5f][73][75][70][70][6c][69][65][72][73][00][00][00][00][00][00][00]
> 
> [---- end of message ----] 
> 
> -----------------------------------------------
> 
> 1. Is there any way to configure visibroker to turn off this "extra"
> being sent.
> 
> 2. Is there any way to configure Orbix 2000 to ignore this "extra".
> 
> 
> --sony

========= WAS CANCELLED BY =======:
Path: news.sol.net!spool0-nwblwi.newsops.execpc.com!newsfeeds.sol.net!newspump.sol.net!newsfeed.direct.ca!look.ca!newshub2.rdc1.sfba.home.com!news.home.com!sjc1.nntp.concentric.net!newsfeed.concentric.net!newsfeed.ozemail.com.au!ozemail.com.au!not-for-mail
Message-ID: <cancel.3eb007f1.0112260011.3196c804@posting.google.com>
Control: cancel <3eb007f1.0112260011.3196c804@posting.google.com>
Subject: cmsg cancel <3eb007f1.0112260011.3196c804@posting.google.com>
From: sonyantony@hotmail.com (Sony Antony)
Newsgroups: comp.lang.java.corba
X-No-Archive: yes
Lines: 2
NNTP-Posting-Host: wonenara.ozemail.com.au
X-Trace: ozemail.com.au 1009706287 203.108.164.177 (Sun, 30 Dec 2001 20:58:07 EST)
NNTP-Posting-Date: Sun, 30 Dec 2001 20:58:07 EST
Organization: OzEmail Ltd, Australia
Distribution: world
Date: Sun, 30 Dec 2001 09:33:33 GMT

This message was cancelled from within Mozilla.

Hi Sony,

> What does the corba standard says about the service contexts.

Why don't you just read the spec and find out the answer for yourself?!

> Can an ORB send any number of service contexts along with the
> requests. 

Yes.

> Or in other words is Service Context an optional 'exta' piece of
> info.

In general, yes, though it's specifically required to implement
certain CORBA features, such as the OTS and client propagated
priorities in Real-time CORBA.  Again, reading the CORBA spec is best
way to learn the answers to questions like these...

Take care,

        Doug
-- 
Dr. Douglas C. Schmidt, Associate Professor  TEL: (949) 824-1901
Dept of Electrical & Computer Engineering    FAX: (949) 824-2321
616E Engineering Tower                       WEB: www.ece.uci.edu/~schmidt/
University of California, Irvine, 92697-2625 NET: schmidt@uci.edu