[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| Title: | ObjectBroker Development - BEA Systems' CORBA |
| Notice: | See note 2 for kit locations; note 4 for training |
| Moderator: | RECV::GUMBEL d |
|
| Created: | Thu Dec 27 1990 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 2482 |
| Total number of notes: | 13057 |
I am having problem connecting a V2.6 client with a V2.5a
server. I was running V2.5b-08 on my Windows NT client and was
having no problems connecting. I upgraded my Windows NT client
to V2.6 and regenerated, recompiled, and relinked my client code.
I am now getting the error :
CORBA_NO_IMPLEMENT = OBB_INV_HOSTNOTFND <e>, A host node could not be
found to execute the request.
-OBB_REG_KEYNOTFND <e>, Could not find key 'Implementations\Definitions\
7a2579cd8f56.02.10.19.c0.45.00.00.00'
I ran the system administrator and did an obbmsho on the server
node and I can see the above implementation running.
Any help would be greatly appreciated!
Craig
======================================================================
Client trace
*** Load Network implementation MicrosoftTCP
FamilyName<5> <TCPIP>
ImagePath<24> <%OBB_ROOT\lib\trnwsk.dll>
LibraryName: C:\win32app\obroker\lib\trnwsk.dll
--- WM_CREATE message
--- WinSock implementation Microsoft Windows Sockets Version 1.1.
--- Min Version: 1.1
--- Max Version: 1.1
--- Max Sockets: 32767
--- Max Datagram: 65527
**** Server Instance Selection
*** Load Agent implementation OrbV12
FamilyName<3> <OBB>
ImagePath<26> <%OBB_ROOT\lib\obbagncl.dll>
LibraryName: C:\win32app\obroker\lib\obbagncl.dll
OBB__TrnWsckBindWellKnown
--- Connecting to rckbnd
--- Port: 62
--- Attempting connect on socket: 276
--- Connect failed: 10061
--- Transport Error: Connect was forcefully rejected.
OBB__TrnWsckBindWellKnown
--- Connecting to hps126.mro.dec.com
--- Port: 62
--- Attempting connect on socket: 300
--- Setting nonblocking socket : 300
--- Set asynch socket
--- Socket: 300
--- Message: WSA_READ
--- SocketSetAsynch - Successful
Obtaining Security Key for Client ID 7b13acabdf60.02.10.1e.70.65.00.00.00
Impl ID 65e448ecbd2c.0c.7e.0b.00.00.00.00.00
List of server supported sec. types isn't known yet. Trying client sec types in turn
Number of client supported security types: 1
Trying each of the sectypes from above list
*** Load Authentication implementation Trusted
FamilyName<3> <TRS>
ImagePath<26> <%OBB_ROOT\lib\obbsectr.dll>
LibraryName: C:\win32app\obroker\lib\obbsectr.dll
Trying to get security key using Trusted package
Successfully obtained key/esatablished context using security package Trusted
In Marshall Args - # args:11
Arg #:0
In Marshall ObjRef
In Marshall Args - # args:1
Arg #:0
End Marshall Args Successfully. # Args:1
Ending Marshall ObjRef Successfully
Arg #:1
Arg #:2
Arg #:3
In Marshall Args - # args:13
Arg #:0
Arg #:1
Arg #:2
Arg #:3
Arg #:4
Arg #:5
Arg #:6
In Marshall Args - # args:1
Arg #:0
Arg Name: MicrosoftTCP
type:38
valflags:0
argflags:0
Marshalling a string of length:6
End Marshall Args Successfully. # Args:1
Arg #:7
Arg #:8
Arg #:9
Arg #:10
Arg #:11
Arg #:12
End Marshall Args Successfully. # Args:13
Arg #:4
In Marshall Args - # args:0
End Marshall Args Successfully. # Args:0
Arg #:5
Arg #:6
Arg #:7
Arg #:8
Arg #:9
Arg #:10
End Marshall Args Successfully. # Args:11
Signing messsage from Client ID 7b13acabdf60.02.10.1e.70.65.00.00.00
to Impl ID 65e448ecbd2c.0c.7e.0b.00.00.00.00.00
Using Trusted Security package to sign message.
Status of signing message: OBB_SUCCESS (s), Successful completion.
*** Request Sent: Synchronous Invoke.
*** Method: 65e448f20f7c.0c.7e.0b.00.00.00.00.00.
** * MethodServerClass: 65e448ecbd2c.0c.7e.0b.00.00.00.00.00
*** Marshalled Buffer: 564
*** Allocated Buffer : 1888
OBB__TrnWsckSar
--- SAR: Sending message on socket 300
--- Sending on socket 300
--- Socket send buffer size is 8192
--- Sending data on socket - send len is 564
--- Number of bytes actually written 564
--- SAR: Waiting for message on socket 300
--- SAR: Receiving message on socket 300
--- Receiving on socket 300
--- Receiving Header on socket - len is 20
--- Received data - retval is 20
--- Received the transport header
*** In SocketRecvBuf ***--- Receiving data - remaining is 324
--- ioctlsocket buffer available for recv() is 324
--- Recv returned 324
*** Transport Status: OBB_SUCCESS (s), Successful completion.
Trying to verify message from client UUID 7b13acabdf60.02.10.1e.70.65.00.00.00
Using Trusted security package to verify signed message
Stauts of verifying signed message: OBB_SUCCESS (s), Successful completion.
In Unmarshall Args - # Args:3
Arg #:0
Type:21
In Unmarshall Args - # Args:0
End Unmarshall Args Successfully - # Args :0
Arg #:1
Type:23
In Unmarshall Args - # Args:0
Arg #:0
In Unmarshall Args - # Args:0
End Unmarshall Args Successfully - # Args :0
Arg #:1
In Unmarshall Args - # Args:0
End Unmarshall Args Successfully - # Args :0
Arg #:2
In Unmarshall Args - # Args:0
Arg #:0
type:9
valflags:0
argflags:0
name is KEYNAME
Dtype length:0
Type:9
End Unmarshall Args Successfully - # Args :0
End Unmarshall Args Successfully - # Args :0
Arg #:2
Type:11
End Unmarshall Args Successfully - # Args :3
*** Operation Status: OBB_INV_METHODFAIL (e), Method execution failed.
OBB__TrnWsckFreeHandle
--- Closing socket: 300
OBB__TrnWsckBindWellKnown
--- Connecting to rckbnd
--- Port: 62
--- Attempting connect on socket: 188
--- Connect failed: 10061
--- Transport Error: Connect was forcefully rejected.
OBB__TrnWsckBindWellKnown
--- Connecting to hps126.mro.dec.com
--- Port: 62
--- Attempting connect on socket: 216
--- Setting nonblocking socket : 216
--- Set asynch socket
--- Socket: 216
--- Message: WSA_READ
--- SocketSetAsynch - Successful
Obtaining Security Key for Client ID 7b13acabdf60.02.10.1e.70.65.00.00.00
Impl ID 65e448ecbd2c.0c.7e.0b.00.00.00.00.00
List of server supported sec. types isn't known yet. Trying client sec types in turn
Number of client supported security types: 1
Trying each of the sectypes from above list
Trying to get security key using Trusted package
Successfully obtained key/esatablished context using security package Trusted
In Marshall Args - # args:11
Arg #:0
In Marshall ObjRef
In Marshall Args - # args:1
Arg #:0
End Marshall Args Successfully. # Args:1
Ending Marshall ObjRef Successfully
Arg #:1
Arg #:2
Arg #:3
In Marshall Args - # args:8
Arg #:0
Arg #:1
Arg #:2
Arg #:3
Arg #:4
In Marshall ObjRef
In Marshall Args - # args:7
Arg #:0
Arg #:1
Arg #:2
Arg #:3
Arg #:4
Arg #:5
Arg #:6
End Marshall Args Successfully. # Args:7
In Marshall Args - # args:10
Arg #:0
Arg #:1
Arg #:2
Arg #:3
Arg #:4
Arg #:5
Arg #:6
Arg #:7
Arg #:8
Arg #:9
End Marshall Args Successfully. # Args:10
Ending Marshall ObjRef Successfully
Arg #:5
Arg #:6
Arg #:7
End Marshall Args Successfully. # Args:8
Arg #:4
In Marshall Args - # args:0
End Marshall Args Successfully. # Args:0
Arg #:5
Arg #:6
Arg #:7
Arg #:8
Arg #:9
Arg #:10
End Marshall Args Successfully. # Args:11
Signing messsage from Client ID 7b13acabdf60.02.10.1e.70.65.00.00.00
to Impl ID 65e448ecbd2c.0c.7e.0b.00.00.00.00.00
Using Trusted Security package to sign message.
Status of signing message: OBB_SUCCESS (s), Successful completion.
*** Request Sent: Synchronous Invoke.
*** Method: 65e448eeadd4.0c.7e.0b.00.00.00.00.00.
** * MethodServerClass: 65e448ecbd2c.0c.7e.0b.00.00.00.00.00
*** Marshalled Buffer: 628
*** Allocated Buffer : 1955
OBB__TrnWsckSar
--- SAR: Sending message on socket 216
--- Sending on socket 216
--- Socket send buffer size is 8192
--- Sending data on socket - send len is 628
--- Number of bytes actually written 628
--- SAR: Waiting for message on socket 216
--- SAR: Receiving message on socket 216
--- Receiving on socket 216
--- Receiving Header on socket - len is 20
--- Received data - retval is 20
--- Received the transport header
*** In SocketRecvBuf ***--- Receiving data - remaining is 280
--- ioctlsocket buffer available for recv() is 280
--- Recv returned 280
*** Transport Status: OBB_SUCCESS (s), Successful completion.
Trying to verify message from client UUID 7b13acabdf60.02.10.1e.70.65.00.00.00
Using Trusted security package to verify signed message
Stauts of verifying signed message: OBB_SUCCESS (s), Successful completion.
In Unmarshall Args - # Args:3
Arg #:0
Type:21
In Unmarshall Args - # Args:0
End Unmarshall Args Successfully - # Args :0
Arg #:1
Type:23
In Unmarshall Args - # Args:0
Arg #:0
In Unmarshall Args - # Args:0
End Unmarshall Args Successfully - # Args :0
Arg #:1
In Unmarshall Args - # Args:0
Arg #:0
type:9
valflags:0
argflags:0
name is KEYNAME
Dtype length:0
Type:9
End Unmarshall Args Successfully - # Args :0
End Unmarshall Args Successfully - # Args :0
Arg #:2
Type:11
End Unmarshall Args Successfully - # Args :3
*** Operation Status: OBB_INV_METHODFAIL (e), Method execution failed.
OBB__TrnWsckFreeHandle
--- Closing socket: 216
======================================================================
IDL file
module OP
{
// Some constants used in the example (Note that putting them here
// eliminates the need for a separate user-written header file to share
// this information between client and server sources)
const short MAXLINELEN = 512;
const short BFALSE = 0;
const short BTRUE = 1;
const string STR_OBJ_FILNAM = "OPIO.DAT";
// An enumerated list of application-specific errors, accompanied by
// explanatory text strings.
enum ERR_TYPES {ErrOfferNonex, // no such Offer
ErrPriceNonex, // no such Price
ErrProductNonex}; // no such Product
// everything we need to know about an Offer...
struct OfferData {
string OfferNo;
string ShipDate;
string CountryCode;
string ServerStatus;
string ServerMessage;
string Currency;
string CLP_Price;
string MLP_Price;
string IBP_Price;
string STD_Price;
string Segment1;
string Segment2;
string OEM1;
string OEM2;
string EndUser;
string Extra1;
string Extra2;
string Extra3;
};
// everything we need to know about a Price...
struct PriceData {
string OfferNo;
string ShipDate;
string CountryCode;
string ServerStatus;
string ServerMessage;
string Currency;
string CLP_Price;
string MLP_Price;
string IBP_Price;
string STD_Price;
string Price_Extra1;
string Price_Extra2;
string Price_Extra3;
};
// everything we need to know about a Product...
struct ProductData {
string OfferNo;
string ShipDate;
string CountryCode;
string ServerStatus;
string ServerMessage;
string Segment1;
string Segment2;
string OEM1;
string OEM2;
string EndUser;
string DEP_Code;
string PID_Code;
string Product_Extra1;
string Product_Extra2;
string Product_Extra3;
};
exception UserExcep {
ERR_TYPES Reason;
};
// The Offer interface, with one operation
interface Offer {
void Get (in string OfferNo,
in string ShipDate,
in string CountryCode,
out string ServerStatus,
out string ServerMessage,
out string Currency,
out string CLP_Price,
out string MLP_Price,
out string IBP_Price,
out string STD_Price,
out string Segment1,
out string Segment2,
out string OEM1,
out string OEM2,
out string EndUser,
out string Extra1,
out string Extra2,
out string Extra3)
raises (UserExcep);
}; //end of interface Offer
interface Price {
void Get (in string OfferNo,
in string ShipDate,
in string CountryCode,
out string ServerStatus,
out string ServerMessage,
out string Currency,
out string CLP_Price,
out string MLP_Price,
out string IBP_Price,
out string STD_Price,
out string Price_Extra1,
out string Price_Extra2,
out string Price_Extra3)
raises (UserExcep);
}; //end of interface Price
interface Product {
void Get (in string OfferNo,
in string ShipDate,
in string CountryCode,
out string ServerStatus,
out string ServerMessage,
out string Segment1,
out string Segment2,
out string OEM1,
out string OEM2,
out string EndUser,
out string DEP_Code,
out string PID_Code,
out string Product_Extra1,
out string Product_Extra2,
out string Product_Extra3)
raises (UserExcep);
}; //end of interface Product
}; //end of module OP
#pragma repository_id( "OP::MAXLINELEN", "7a2579cd8f4d.02.10.19.c0.45.00.00.00")
#pragma repository_id( "OP::BFALSE", "7a2579cd8f4e.02.10.19.c0.45.00.00.00")
#pragma repository_id( "OP::BTRUE", "7a2579cd8f4f.02.10.19.c0.45.00.00.00")
#pragma repository_id( "OP::STR_OBJ_FILNAM", "7a2579cd8f50.02.10.19.c0.45.00.00.00")
#pragma repository_id( "OP::ERR_TYPES", "7a2579cd8f51.02.10.19.c0.45.00.00.00")
#pragma repository_id( "OP::OfferData", "7a2579cd8f52.02.10.19.c0.45.00.00.00")
#pragma repository_id( "OP::PriceData", "7a2579cd8f53.02.10.19.c0.45.00.00.00")
#pragma repository_id( "OP::ProductData", "7a2579cd8f54.02.10.19.c0.45.00.00.00")
#pragma repository_id( "OP::UserExcep", "7a2579cd8f55.02.10.19.c0.45.00.00.00")
#pragma interface_id( "OP::Offer", "7a2579cd8f56.02.10.19.c0.45.00.00.00")
#pragma operation_id( "OP::Offer::Get", "7a2579cd8f57.02.10.19.c0.45.00.00.00", 1)
#pragma interface_id( "OP::Price", "7a2579cd8f58.02.10.19.c0.45.00.00.00")
#pragma operation_id( "OP::Price::Get", "7a2579cd8f59.02.10.19.c0.45.00.00.00", 1)
#pragma interface_id( "OP::Product", "7a2579cd8f5a.02.10.19.c0.45.00.00.00")
#pragma operation_id( "OP::Product::Get", "7a2579cd8f5b.02.10.19.c0.45.00.00.00", 1)
======================================================================
IML File
// *******************************************************************
// Created Mon Feb 24 19:02:29 1997 by OBB V2.6-08 (COMPILE/GENERATE)
// *******************************************************************
//
// OBB Default IML file
// ---------------------
//
// Use this file as a base for your additional IML definitions.
//
implementation OfferImpl
{
activation_type ( program );
activation_string ( "<tba> - command to run implementation" );
implementation_identifier ( "7a2579cd8f56.02.10.19.c0.45.00.00.00" );
registration_attribute string ImplementationName = "OfferImpl";
method_dispatcher_routine OfferImpl__dispatch ();
registration_routine OfferImpl__register ();
deactivate_impl_routine OfferImpl__notify ();
Get ( )
implements ( OP::Offer::Get )
invoke_builtin ( "OfferImpl_Get" )
;
};
implementation PriceImpl
{
activation_type ( program );
activation_string ( "<tba> - command to run implementation" );
implementation_identifier ( "7a2579cd8f58.02.10.19.c0.45.00.00.00" );
registration_attribute string ImplementationName = "PriceImpl";
method_dispatcher_routine PriceImpl__dispatch ();
registration_routine PriceImpl__register ();
deactivate_impl_routine PriceImpl__notify ();
Get ( )
implements ( OP::Price::Get )
invoke_builtin ( "PriceImpl_Get" )
;
};
implementation ProductImpl
{
activation_type ( program );
activation_string ( "<tba> - command to run implementation" );
implementation_identifier ( "7a2579cd8f5a.02.10.19.c0.45.00.00.00" );
registration_attribute string ImplementationName = "ProductImpl";
method_dispatcher_routine ProductImpl__dispatch ();
registration_routine ProductImpl__register ();
deactivate_impl_routine ProductImpl__notify ();
Get ( )
implements ( OP::Product::Get )
invoke_builtin ( "ProductImpl_Get" )
;
};
======================================================================
MML File
// *******************************************************************
// Created Mon Feb 24 19:05:58 1997 by OBB V2.6-08 (COMPILE/GENERATE)
// *******************************************************************
//
// OBB Default MML file
// ---------------------
//
method_map OfferMap interface OP::Offer
{
Get :
{
default :
select_implementation
by_name (OfferImpl)
by_identifier ( "7a2579cd8f56.02.10.19.c0.45.00.00.00" )
;
};
};
method_map PriceMap interface OP::Price
{
Get :
{
default :
select_implementation
by_name (PriceImpl)
by_identifier ( "7a2579cd8f58.02.10.19.c0.45.00.00.00" )
;
};
};
method_map ProductMap interface OP::Product
{
Get :
{
default :
select_implementation
by_name (ProductImpl)
by_identifier ( "7a2579cd8f5a.02.10.19.c0.45.00.00.00" )
;
};
};
======================================================================
opio.dat
DEC::~00001597cbf607a7c920000021019c04500000000000cd79257a568f0000021019c0450000000000100000cd79257a568f0000021019c04500000002010000180~hps126.mro.dec.com~~~|
DEC::~00001597cbf607a9eb60000021019c04500000000000cd79257a588f0000021019c0450000000000100000cd79257a588f0000021019c04500000002010000180~hps126.mro.dec.com~~~|
DEC::~00001597cbf607ad8d60000021019c04500000000000cd79257a5a8f0000021019c0450000000000100000cd79257a5a8f0000021019c04500000002010000180~hps126.mro.dec.com~~~|
| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 2444.1 | | RECV::SLAVIN | | Tue Feb 25 1997 11:42 | 3 |
| I am not sure this is the problem, but V2.5a uses only "old style"
object references. If you regenerated on V2.6 and created "new style"
object references, then the V2.5a system will not understand them.
|
| 2444.2 | Same object references... | ALLVAX::BRUSSEAU | | Tue Feb 25 1997 12:05 | 5 |
| I did not regenerate the object strings when I upgraded the client to
V2.6. These are the V2.5a object references that were working when
I was running a V2.5b-08 client. My understanding is that if this
clent/server configuration was working when the client was V2.5b-08,
it should work equally as well when the client gets upgraded to V2.6.
|
| 2444.3 | | SEND::SLAVIN | | Tue Feb 25 1997 14:31 | 6 |
|
have you
- tried using the network tester to see if the connections between the
client and server are running correctly
- do you have the proxies set up corrrectly
|
| 2444.4 | Network test OK | ALLVAX::BRUSSEAU | | Tue Feb 25 1997 15:07 | 4 |
| I just completed a network test between the client and server (I had
done this when the client was V2.5b-08, but did not retest when I
upgraded). The test completed successfully (so I assume the proxies
are OK as well - I see my client listed in the server's proxy list).7
|
| 2444.5 | object reference and show server output | RECV::VLATAS | WARNING: Do not swallow the battery door | Wed Feb 26 1997 09:09 | 9 |
|
Can you post the object reference that the client is using in
a stringified form, and the output from the show server.
The agent on the server machine is not selecting the server, and it
is not finding the implementation registered (so it can't start it).
Thanks
Tony
|
| 2444.6 | object references and show server output | ALLVAX::BRUSSEAU | | Wed Feb 26 1997 09:43 | 51 |
|
Here is the requested info. Thanks for the help!
Stringified Objects
DEC::~00001597cbf607a7c920000021019c04500000000000cd79257a568f0000021019c0450000000000100000cd79257a568f0000021019c04500000002010000180~hps126.mro.dec.com~~~|
DEC::~00001597cbf607a9eb60000021019c04500000000000cd79257a588f0000021019c0450000000000100000cd79257a588f0000021019c04500000002010000180~hps126.mro.dec.com~~~|
DEC::~00001597cbf607ad8d60000021019c04500000000000cd79257a5a8f0000021019c0450000000000100000cd79257a5a8f0000021019c04500000002010000180~hps126.mro.dec.com~~~|
obbmsho -n output
Implementation Servers on node hps126.mro.dec.com.
Implementation Name Username Status
------------------------------------------ ------------ ------
OfferImpl penney Executing
Inst UUID: 7b11277971d6.02.10.19.c0.45.00.00.00 Pid: 0001E2C8
Impl UUID: 76d2c006e942.0c.c0.1f.00.00.00.00.00
Registered at: Mon Feb 24 07:40:48 1997
Server has no attributes
OfferImpl penney Executing
Inst UUID: 7b1127944362.02.10.19.c0.45.00.00.00 Pid: 0001A4C9
Impl UUID: 7a2579cd8f56.02.10.19.c0.45.00.00.00
Registered at: Mon Feb 24 07:40:55 1997
Server has no attributes
PriceImpl penney Executing
Inst UUID: 7b112795c062.02.10.19.c0.45.00.00.00 Pid: 0001A4C9
Impl UUID: 7a2579cd8f58.02.10.19.c0.45.00.00.00
Registered at: Mon Feb 24 07:40:56 1997
Server has no attributes
ProductImpl penney Executing
Inst UUID: 7b112795e196.02.10.19.c0.45.00.00.00 Pid: 0001A4C9
Impl UUID: 7a2579cd8f5a.02.10.19.c0.45.00.00.00
Registered at: Mon Feb 24 07:40:57 1997
Server has no attributes
OBB_CMD_NUMMSRVSFND (i), 4 servers found.
|
| 2444.7 | | SEND::SLAVIN | | Wed Feb 26 1997 15:20 | 3 |
| You should consider at least moving to ObjectBroker V2.5b. This has
the best ACA bits with it with the most bugs fixed. Then you can use
the new object bindings everywhere.
|
| 2444.8 | Win 95 version of Object Broker V2.5b-08? | ALLVAX::BRUSSEAU | | Wed Feb 26 1997 18:13 | 11 |
| There is one client in our configuration that must stay at V2.5a due to
other products on their system (namely DEC EDI - why this is a
constraint on DEC EDI I don't know).
Is there a V2.5b-08 kit that will run under Windows 95? As I mentioned
earlier, this was running under NT using V2.5b-08 of Object Broker. I
upgraded to V2.6 because I did not find a Windows 95 kit at V2.5b-08.
If I can go back to the 2.5b version on both NT and Win95, I consider
this a victory!
Thanks again to all who have helped...
|
| 2444.9 | | RECV::SLAVIN | | Thu Feb 27 1997 11:17 | 4 |
| > Is there a V2.5b-08 kit that will run under Windows 95?
I think that Windows-95 was first supported in ObjectBroker V2.6.
|
| 2444.10 | | RECV::SLAVIN | | Thu Feb 27 1997 11:19 | 8 |
| > There is one client in our configuration that must stay at V2.5a due to
> other products on their system (namely DEC EDI - why this is a
> constraint on DEC EDI I don't know).
I believe that DEC EDI now supports OBB V2.7. Your best course would
be to upgrade to the most recent version of ObjectBroker that you can,
since V2.5a is not supported anymore.
|
| 2444.11 | | VAXCPU::michaud | Jeff Michaud - ObjectBroker | Thu Feb 27 1997 23:52 | 8 |
| > I just completed a network test between the client and server ....
> The test completed successfully (so I assume the proxies
> are OK as well .....
The Network Tester bypasses the ORB and goes straight to OBB's
transport layer, so proxy information is neither sent, nor
checked. Ie. a success using the Network Tester does not test
that your proxies are ok.
|
| 2444.12 | Can you show/stop the server from the V2.6 machine? | RECV::VLATAS | WARNING: Do not swallow the battery door | Fri Feb 28 1997 07:02 | 22 |
| re .6:
The impl ids in the stringified object references matched the impl
ids from the show server output. The one exception was that you had
another server running with an "OfferImpl" which had a different impl
ID. The agent matches based on impl id, so that should not be a
problem (it should find the server with the impl id that matched).
The interface IDs in the object references matched the interface IDs in
the IDL, that doesn't appear to be the problem.
What platform is the V2.5A server running on?
Was the show server done from the V2.6 client side, or the V2.5A server
side? If the show server was done from teh V2.5A machine locally, do
the show server from the V2.6 machine and post that output. Also, try
to stop the server from the V2.6 client machine, see if it can do that.
If this were a proxy problem, I would expect a "CLIENT NOT AUTHORIZED"
failure to be returned.
Tony
|
| 2444.13 | DEC/EDI V2.1D supports ObjectBroker V2.6, V2.7, ... | METSYS::THOMPSON | | Tue Mar 04 1997 07:45 | 8 |
|
DEC/EDI V2.1D does now support OBB V2.6 and later.
As does DEC/EDI V3.1A on UNIX.
If you are using DECnet/OSI as a transport, note 2408.18 is very
important. TCP/IP works just fine.
Mark
|
| 2444.14 | Running under V2.7 | ALLVAX::BRUSSEAU | | Fri Mar 14 1997 14:33 | 8 |
| We ended up doing an upgrade to V2.7 on both the client and the server
and things are working just fine. I don't know what the problem was,
but thankfully, we are up and running. Thanks to all who helped!
Craig
FYI - I'm not sure what the client running DEC/EDI did in order
for this upgrade to happen...
|