[omniORB] Omnipy-Omniorb crashes performing narrow operation.

Jose Carlos Lopez jlopez at iac.es
Wed Oct 13 12:37:27 BST 2004


Hello,

I have a problem with the current TAO Naming Service version  and the 
access from a python client from Solaris 2.9/2.8. I have compiled 
OMNIORB 4.0.4 and OMNIPY for Solaris 2.9 with GCC 3.4.2.

The problem comes when I try to access TAO Name Service(executing on 
Solaris 2.8) from a python client that is running on Solaris 2.8.  If
I use the  OmniORB naming service I have no problem. Neither If  I 
execute the python client on the PC. Neither if
I execute the same code from a client running linux.

The problem is caused by the following operation:   rootContext = 
obj._narrow(CosNaming.NamingContext)
and the result is  the abortion of the python client.


This is the ouput OMNIORB generates:

ImageServer:connect:ORB_Init start
omniORB: Distribution date: Fri Jul 30 11:57:22 BST 2004 dgrisby
omniORB: My addresses are: 
omniORB: 127.0.0.1
omniORB: 161.72.64.32
omniORB: Maximum supported GIOP version is 1.2
omniORB: Native char code sets: ISO-8859-1 UTF-8.
omniORB: Transmission char code sets: ISO-8859-1(1.2) ISO-8859-1(1.1) ISO-8859-1(1.0) UTF-8(1.2) UTF-8(1.1).
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::nogal:12008
omniORB:   abortOnInternalError = 0
omniORB:   acceptBiDirectionalGIOP = 0
omniORB:   acceptMisalignedTcIndirections = 0
omniORB:   bootstrapAgentHostname = 
omniORB:   bootstrapAgentPort = 900
omniORB:   clientCallTimeOutPeriod = 0
omniORB:   clientTransportRule = * unix,ssl,tcp
omniORB:   diiThrowsSysExceptions = 0
omniORB:   dumpConfiguration = 0
omniORB:   endPoint = giop:tcp::
omniORB:   endPointPublishAllIFs = 0
omniORB:   giopMaxMsgSize = 2097152
omniORB:   giopTargetAddressMode = KeyAddr
omniORB:   id = omniORB4
omniORB:   inConScanPeriod = 180
omniORB:   lcdMode = 0
omniORB:   maxGIOPConnectionPerServer = 5
omniORB:   maxGIOPVersion = 1.2
omniORB:   maxInterleavedCallsPerConnection = 5
omniORB:   maxServerThreadPerConnection = 100
omniORB:   maxServerThreadPoolSize = 100
omniORB:   nativeCharCodeSet = ISO-8859-1
omniORB:   nativeWCharCodeSet = UTF-16
omniORB:   objectTableSize = 0
omniORB:   offerBiDirectionalGIOP = 0
omniORB:   omniORB_27_CompatibleAnyExtraction = 0
omniORB:   oneCallPerConnection = 1
omniORB:   outConScanPeriod = 120
omniORB:   poaHoldRequestTimeout = 0
omniORB:   poaUniquePersistentSystemIds = 1
omniORB:   principal = [Null]
omniORB:   scanGranularity = 5
omniORB:   serverCallTimeOutPeriod = 0
omniORB:   serverTransportRule = * unix,ssl,tcp
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:   traceInvocations = 0
omniORB:   traceLevel = 40
omniORB:   traceThreadId = 0
omniORB:   unixTransportDirectory = /tmp/omni-%u
omniORB:   unixTransportPermission =  777
omniORB:   useTypeCodeIndirections = 1
omniORB:   verifyObjectExistsAndType = 1
omniORB: omniORBpy distribution date: Fri Jul 30 11:58:00 BST 2004 dgrisby
omniORB: Python thread state scavenger start.
ImageServer:connect:Resolve References start
omniORB: Creating ref to remote: key<NameService>
 target id      : IDL:omg.org/CORBA/Object:1.0
 most derived id: 
omniORB: Initial reference `NameService' resolved from configuration file.
omniORB: Creating Python ref to remote: key<NameService>
 target id      : IDL:omg.org/CORBA/Object:1.0
 most derived id: 
ImageServer:connect:Narrow  start
omniORB: AsyncInvoker: thread id = 2 has started. Total threads = 1
omniORB: Scavenger task execute.
omniORB: Client attempt to connect to giop:tcp:nogal:12008
omniORB: Client opened connection to giop:tcp:161.72.64.32:12008
omniORB: sendChunk: to giop:tcp:161.72.64.32:12008 103 bytes
omniORB: 
4749 4f50 0100 0000 0000 005b 0000 0000 GIOP.......[....
0000 0002 0120 2020 0000 000b 4e61 6d65 .....   ....Name
5365 7276 6963 656e 0000 0006 5f69 735f Servicen...._is_
6100 6563 0000 0000 0000 002b 4944 4c3a a.ec.......+IDL:
6f6d 672e 6f72 672f 436f 734e 616d 696e omg.org/CosNamin
672f 4e61 6d69 6e67 436f 6e74 6578 7445 g/NamingContextE
7874 3a31 2e30 00                       xt:1.0.
omniORB: inputMessage: from giop:tcp:161.72.64.32:12008 204 bytes
omniORB: 
4749 4f50 0100 0001 0000 00c0 0000 0000 GIOP............
0000 0002 0000 0003 0000 002b 4944 4c3a ...........+IDL:
6f6d 672e 6f72 672f 436f 734e 616d 696e omg.org/CosNamin
672f 4e61 6d69 6e67 436f 6e74 6578 7445 g/NamingContextE
7874 3a31 2e30 0074 0000 0001 0000 0000 xt:1.0.t........
0000 0078 0001 0200 0000 0006 6e6f 6761 ...x........noga
6c00 2ee8 0000 0033 1401 0f00 4e55 5000 l......3....NUP.
0000 1500 0000 0000 0000 0100 4e61 6d65 ............Name
5365 7276 6963 6500 0000 0005 0000 0001 Service.........
4e61 6d65 5365 7276 6963 6502 0000 0002 NameService.....
0000 0000 0000 0008 0000 0000 5441 4f00 ............TAO.
0000 0001 0000 0014 0000 0000 0001 0001 ................
0000 0000 0001 0109 0000 0000           ............
omniORB: Creating ref to remote: key<....NUP.............NameService.........NameService>
 target id      : IDL:omg.org/CORBA/Object:1.0
 most derived id: IDL:omg.org/CosNaming/NamingContextExt:1.0
Abort



Someone has any idea about what the problem can be?

Thanks a lot for your help.
Carlos.




More information about the omniORB-list mailing list