AW: [omniORB] Multi-profile IOR

evgeni.rojkov at evgeni.rojkov at
Thu Sep 29 13:14:59 BST 2011

why do you need IORs for ?
could try "corbanames" like NameService=corbaname::customer_host:2809 with
I do not have problems accessing JacOrb NameService with omniORB clients
Regards, Evgeni


Von: Tatiana Lazareva [mailto:tatiana.alexandrovna.lazareva at] 
Gesendet: Donnerstag, 29. September 2011 11:32
An: Duncan Grisby
Cc: Rojkov, Evgeni; omniorb-list at
Betreff: Re: [omniORB] Multi-profile IOR

Hi Duncan,  
see inline please

2011/9/29 Duncan Grisby <duncan at>

	On Wed, 2011-09-28 at 17:24 +0400, Tatiana Lazareva wrote:
	> Yes, my client get TRANSIENT exception in multi-profile IOR case.
	> For example, when I use single IOR:
	> /omcvobs/simbsso3g/external/omniORB/solaris/build/bin/catior
	> Type ID: ""
	> Profiles:
	> 1. IIOP 1.2 fe80::203:baff:fe57:5e9d 2809 "NameService"
	>             TAG_ORB_TYPE omniORB
	I'm rather surprised by this -- that's a link-local IPv6 address, which
	won't work in most circumstances, and omniORB should not have published
	it in its IOR. How did you configure omniNames?
	[TL] I use the default cfg for v4.0 or later, but fro IPv6 support I use
omniORB 4.1.4.
	> the registration is successfully performed, but if I use dual IOR:
	> /omcvobs/simbsso3g/external/omniORB/solaris/build/bin/catior
	> Type ID: ""
	> Profiles:
	> 1. IIOP 1.2 15000 "StandardNS/NameServer-POA/_root"
	>             TAG_ORB_TYPE 0x4a414300
	This is a JacORB naming service.
	[TL] Yes, I know. Also, I know that server use jacORB and I have the
example of dual and single IOR from. But I have no access to customer server and
because of it I should generate my own IOR with my IP addresses. Unfortunately,
I can not find tool for multiple-profile IOR generation and because of it I
create my IOR using the customer IOR manually. Can you suggest me the ways to
generate multiple-profile IOR if you know? So, I use the naming service the same
as the customer use(JacORB). My server and client work successfully with my
single IOR, my catior understand both of these IORs (my single and dual IOR, and
customers' too). Moreover, my client (based on omniORB )must work with customer
server (base on jacORB). But, my client can not perform registration with dual
IOR. Also I debugged my code and understood that TRANSIENT exception is caught
during the "::CORBA::Object_ptr resolve(const ::CosNaming::Name& n);" function

	> 2. IIOP 1.2 fe80:000:0000:00:203:baff:fe57:5e9d 15000
	> "StandardNS/NameServer-POA/_root"
	It has two IIOP profiles in it, which is not the correct way to
	represent multiple IP addresses -- they should be in a single IIOP
	profile with a TAG_ALTERNATE_IIOP_ADDRESS entry. That may or may not be
	the problem.

	 [TL] The customer prefer use multiple-profile IOR. So my client must
work with IORs that I sent... 

	Please get a trace from your client with -ORBtraceLevel 25. That will
	show what's going on. 

	[TL] I use my own client implemented using th omniORB library. I can not
have logs that you need. May be you mean server logs? I can configure this
parameter for omniORB server and for dual IOR it does not receive anything. But
for single IOR (the registration is performed) and the server log look like


/opt/al/NEOS_TAT5/env/NEOS_BLU9.0-02.a/omniNames/bin /out

		Starting the omniNames CORBA name service...

		Setting the LD_LIBRARY_PATH environment variable...


		Setting the output directory for omniNames...

		Output directory for omniNames was set to /out

		Setting the config file for omniNames...

		Config file for omniNames was set to


		omniORB: Version: 4.1.4

		omniORB: Distribution date: Sun Jul 19 18:35:23 BST 2009 dgrisby

		omniORB: Skip link local address fe80::203:baff:fe57:5e9d on
interface bge0.

		omniORB: My addresses are: 



		omniORB: ::1

		omniORB: Maximum supported GIOP version is 1.2

		omniORB: Native char code sets: UTF-8 ISO-8859-1.

		omniORB: Transmission char code sets: UTF-8(1.2) UTF-8(1.1)
ISO-8859-1(1.2) ISO-8859-1(1.1) ISO-8859-1(1.0).

		omniORB: Native wide char code sets: UTF-16.

		omniORB: Transmission wide char code sets: UTF-16(1.2).

		omniORB: Information: the omniDynamic library is not linked.

		omniORB: Current configuration is as follows:

		omniORB:   DefaultInitRef (file) = 

		omniORB:   DefaultInitRef (args) = 

		omniORB:   InitRef = NameService=corbaname::

		omniORB:   abortOnInternalError = 0

		omniORB:   abortOnNativeException = 0

		omniORB:   acceptBiDirectionalGIOP = 0

		omniORB:   acceptMisalignedTcIndirections = 0

		omniORB:   bootstrapAgentHostname = 

		omniORB:   bootstrapAgentPort = 900

		omniORB:   clientCallTimeOutPeriod = 0

		omniORB:   clientConnectTimeOutPeriod = 0

		omniORB:   clientTransportRule = * unix,ssl,tcp

		omniORB:   configFile =

		omniORB:   connectionWatchImmediate = 0

		omniORB:   connectionWatchPeriod = 50000

		omniORB:   copyValuesInLocalCalls = 1

		omniORB:   diiThrowsSysExceptions = 0

		omniORB:   dumpConfiguration = 0

		omniORB:   endPoint = giop:tcp::2809

		omniORB:   endPointPublish = addr

		omniORB:   giopMaxMsgSize = 2097152

		omniORB:   giopTargetAddressMode = KeyAddr

		omniORB:   id = omniORB4

		omniORB:   idleThreadTimeout = 10

		omniORB:   immediateAddressSwitch = 0

		omniORB:   inConScanPeriod = 180

		omniORB:   lcdMode = 0

		omniORB:   maxGIOPConnectionPerServer = 5

		omniORB:   maxGIOPVersion = 1.2

		omniORB:   maxInterleavedCallsPerConnection = 5

		omniORB:   maxServerThreadPerConnection = 100

		omniORB:   maxServerThreadPoolSize = 100

		omniORB:   maxSocketRecv = 2147483647

		omniORB:   maxSocketSend = 2147483647

		omniORB:   nativeCharCodeSet = ISO-8859-1

		omniORB:   nativeWCharCodeSet = UTF-16

		omniORB:   objectTableSize = 0

		omniORB:   offerBiDirectionalGIOP = 0

		omniORB:   oneCallPerConnection = 1

		omniORB:   outConScanPeriod = 120

		omniORB:   poaHoldRequestTimeout = 0

		omniORB:   poaUniquePersistentSystemIds = 1

		omniORB:   principal = [Null]

		omniORB:   resetTimeOutOnRetries = 0

		omniORB:   scanGranularity = 5

		omniORB:   serverCallTimeOutPeriod = 0

		omniORB:   serverTransportRule = * unix,ssl,tcp

		omniORB:   socketSendBuffer = -1

		omniORB:   strictIIOP = 1

		omniORB:   supportBootstrapAgent = 0

		omniORB:   supportCurrent = 1

		omniORB:   supportPerThreadTimeOut = 0

		omniORB:   tcAliasExpand = 0

		omniORB:   threadPerConnectionLowerLimit = 9000

		omniORB:   threadPerConnectionPolicy = 1

		omniORB:   threadPerConnectionUpperLimit = 10000

		omniORB:   threadPoolWatchConnection = 1

		omniORB:   traceExceptions = 0

		omniORB:   traceFile = [stderr]

		omniORB:   traceInvocationReturns = 0

		omniORB:   traceInvocations = 0

		omniORB:   traceLevel = 25

		omniORB:   traceThreadId = 0

		omniORB:   traceTime = 0

		omniORB:   unixTransportDirectory = /tmp/omni-%u

		omniORB:   unixTransportPermission =  777

		omniORB:   useTypeCodeIndirections = 1

		omniORB:   validateUTF8 = 0

		omniORB:   verifyObjectExistsAndType = 1

		omniORB: Initialising incoming endpoints.

		omniORB: Instantiate endpoint 'giop:tcp::2809'

		omniORB: Bind to address :: port 2809.

		omniORB: Publish specification: 'addr'

		omniORB: Try to publish 'addr' for endpoint

		omniORB: Publish endpoint 'giop:tcp:'

		omniORB: Starting serving incoming endpoints.

		omniORB: AsyncInvoker: thread id = 1 has started. Total threads
= 1

		omniORB: giopRendezvouser task execute for

		Thu Sep 29 13:30:58 2011:

		Starting omniNames for the first time.

		omniORB: Creating ref to in process: root/<4e843ad2722c0001/0>

		 target id      :

		 most derived id: 

		omniORB: ObjRef() -- deleted.

		Wrote initial log file.

		omniORB: Persistent server identifier: 4e843ad2722c0001

		omniORB: Adding key<NameService> (activating) to object table.

		omniORB: State key<NameService> (activating) -> active

		Read log file successfully.

		omniORB: Creating ref to local: key<NameService>

		 target id      :

		 most derived id:

		Root context is

		Checkpointing Phase 1: Prepare.

		Checkpointing Phase 2: Commit.

		Checkpointing completed.

		omniORB: SocketCollection idle. Sleeping.

		omniORB: Server accepted connection from

		omniORB: AsyncInvoker: thread id = 2 has started. Total threads
= 2

		omniORB: Scavenger task execute.

		omniORB: AsyncInvoker: thread id = 3 has started. Total threads
= 3

		omniORB: giopWorker task execute.

		omniORB: Accepted connection from
giop:tcp:[::ffff:]:35984 because of this rule: "* unix,ssl,tcp"

		omniORB: inputMessage: from giop:tcp:[::ffff:]:35984
100 bytes

		omniORB: sendChunk: to giop:tcp:[::ffff:]:35984 25

		omniORB: inputMessage: from giop:tcp:[::ffff:]:35984 93

		omniORB: Creating ref to in process: root/<4e843ad2722c0001/1>

		 target id      :

		 most derived id:

		omniORB: Adding root/<4e843ad2722c0001/1> (activating) to object

		omniORB: State root/<4e843ad2722c0001/1> (activating) -> active

		omniORB: Creating ref to local: root/<4e843ad2722c0001/1>

		 target id      :

		 most derived id:

		omniORB: ObjRef( --

		omniORB: createLocalObjRef -- reusing reference from local ref

		omniORB: sendChunk: to giop:tcp:[::ffff:]:35984 204

		omniORB: Server accepted connection from

		omniORB: AsyncInvoker: thread id = 4 has started. Total threads
= 4

		omniORB: giopWorker task execute.

		omniORB: Accepted connection from
giop:tcp:[::ffff:]:35985 because of this rule: "* unix,ssl,tcp"

		omniORB: inputMessage: from
giop:tcp:[::ffff:]:35985 38 bytes

		omniORB: Handling a GIOP LOCATE_REQUEST.

		omniORB: sendChunk: to giop:tcp:[::ffff:]:35985 20

		omniORB: inputMessage: from
giop:tcp:[::ffff:]:35985 117 bytes

		omniORB: Receive codeset service context and set TCS to

		omniORB: Creating ref to in process: root/<4e843ad2722c0001/2>

		 target id      :

		 most derived id:

		omniORB: Adding root/<4e843ad2722c0001/2> (activating) to object

		omniORB: State root/<4e843ad2722c0001/2> (activating) -> active

		omniORB: Creating ref to local: root/<4e843ad2722c0001/2>


-------------- next part --------------
An HTML attachment was scrubbed...

More information about the omniORB-list mailing list