[omniORB-dev] OmniNames and IONA Orbix 3.3

Nimrod, David (Dave) nimrod at avaya.com
Fri May 16 20:08:12 BST 2003


Hi all:
I thought I was making some headway with this one, but I'm stumped again
Turns out the original code was generating IORs to the old spec. I made a change to call "genRef" (from genior.cc) and now I'm generating proper IOR's.
However, I still get an "Invalid Object Ref" exception in the code below. The ORB log only shows "Handling a GIOP LOCATE_REQUEST"

Any ideas? Any help would be greatly appreciated.

OmniNames Log:

omniORB: Server accepted connection from giop:tcp:135.8.116.17:3079
omniORB: AsyncInvoker: thread id = 2 has started. Total threads = 3
omniORB: Scavenger task execute.
omniORB: AsyncInvoker: thread id = 3 has started. Total threads = 3
omniORB: giopWorker task execute.
omniORB: Accepted connection from giop:tcp:135.8.116.17:3079 because of this rule: "* unix,ssl,tcp"
omniORB: inputMessage: from giop:tcp:135.8.116.17:3079 32 bytes
omniORB:
4749 4f50 0100 0103 1400 0000 0000 0000 GIOP............
0c00 0000 3ec3 d876 0000 10ea 0000 0001 ....>..v........
omniORB: Handling a GIOP LOCATE_REQUEST.
omniORB: sendChunk: to giop:tcp:135.8.116.17:3079 20 bytes
omniORB:
4749 4f50 0100 0104 0800 0000 0000 0000 GIOP............
0000 0000                               ....



My code:


	CORBA::Object_var aObjectVar;
	CosNaming::NamingContext_ptr aNewRootContext;
	try
	{
		aObjectVar = CORBA::Orbix.string_to_object(const_cast<char*>(narrow(aNameServiceIOR).c_str()));
		aNewRootContext = CosNaming::NamingContext::_narrow(aObjectVar);					<<<< This throws the exception.
		mNameServiceMap[aNameServiceIOR] = aNewRootContext;
	}
	catch (CORBA::SystemException const&sysEx)
	{
		ConsolePrintf(HighPriDbgException, "NameChronicler::addNameServiceIOR CORBA::SystemException exception handler throw ObjectDoesNotExist: %lu.\n", sysEx.minor());
		throw ObjectDoesNotExist(CANT_ADD_NAMESERVICE);
	}

My log:

IORGenerator::NameServiceIOR. sHostname = 'lznimrod-a2'
IORGenerator::MakeIOR. IRTypeId = 'omg.org/CosNaming/NamingContext'  sHostname = 'lznimrod-a2', port = 2809, sKeyseed = '0x3ec3d876000010ea00000001'
IORGenerator::MakeIOR. sResult = 'IOR:01000000200000006f6d672e6f72672f436f734e616d696e672f4e616d696e67436f6e7465787400010000000000000060000000010102000c0000006c7a6e696d726f642d613200f90a00000c0000003ec3d876000010ea000000010200000000000000080000000100000000545441010000001c00000001000000010001000100000001000105090101000100000009010100'
NameChronicler::addNameServiceIOR. aNameServiceIOR = 'IOR:01000000200000006f6d672e6f72672f436f734e616d696e672f4e616d696e67436f6e7465787400010000000000000060000000010102000c0000006c7a6e696d726f642d613200f90a00000c0000003ec3d876000010ea000000010200000000000000080000000100000000545441010000001c00000001000000010001000100000001000105090101000100000009010100'
First-chance exception in ConnectionServer.exe (KERNEL32.DLL): 0xE06D7363: Microsoft C++ Exception.
NameChronicler::addNameServiceIOR CORBA::SystemException exception handler throw ObjectDoesNotExist: 10101.


	______________________________________ 
	David Nimrod
	Avaya Inc. 
	Email: Nimrod at avaya.com <mailto:Nimrod at avaya.com> 

	______________________________________



-----Original Message-----
From: Nimrod, David (Dave) 
Sent: Monday, May 12, 2003 3:53 PM
To: 'Duncan Grisby'
Cc: omniorb-dev at omniorb-support.com
Subject: RE: [omniORB-dev] OmniNames and IONA Orbix 3.3 


Duncan:
Here's a debug dump.
As you can see I'm getting a [omniORB: throw OBJECT_NOT_EXIST from GIOP_S.cc:325 (NO,OBJECT_NOT_EXIST_NoMatch)] exception.
One funny thing about my setup is that the IOR is constructed directly from the nameservice string and NOT by doing resolve_initial_reference. Would that be a problem in OmniOrb 4.0.1?

Thanks, Dave Nimrod.


<<<OLD LOG DELETED>>>


-----Original Message-----
From: omniorb-dev-admin at omniorb-support.com [mailto:omniorb-dev-admin at omniorb-support.com]On Behalf Of Duncan Grisby
Sent: Wednesday, May 07, 2003 4:38 AM
To: Nimrod, David (Dave)
Cc: omniorb-dev at omniorb-support.com
Subject: Re: [omniORB-dev] OmniNames and IONA Orbix 3.3 


On Friday 2 May, "Nimrod, David (Dave)" wrote:

> I am migrating a product which was using Iona Orbix2.2c01 and
> OmniNames (OmniOrb 2.2.0) as its naming service.

Wow!  Talk about prehistoric technology...

> I migrated to Iona Orbix 3.3.4 and OmniOrb 4.0.1
> Everything compiles fine, but the "resolve" method return an exception.

What exception?  Run omniORB with -ORBtraceLevel 10. That should help
you see what's going on.

Cheers,

Duncan.

-- 
 -- Duncan Grisby         --
  -- duncan at grisby.org     --
   -- http://www.grisby.org --





More information about the omniORB-dev mailing list