[omniORB] I got error message "unable to connect the object C OMM_FAILUE"

JHJE (Jan Holst Jensen) jhje at novonordisk.com
Thu Sep 11 09:29:45 BST 2003


> Message: 7
> Date: Wed, 10 Sep 2003 13:02:17 -0700 (PDT)
> From: Wei Chen <chenwei624 at yahoo.com>
> Subject: [omniORB] I got error message "unable to connect the object
> 	COMM_FAILUE"

> I write a server in Java with IBM WebSphere Developer.
> And I wrote a client based on the omniORB compiled
> IDL. As I start the client I got error message:
> "unable to connect the object COMM_FAILUE".

>From your trace it looks to me like omniORB isn't able to contact your local
name service which apparently runs on port 9080 (?).

> omniORB: (0) Initial reference `NameService' resolved from configuration
file.
> omniORB: (0) Invoke '_is_a' on remote: key<0x4e616d6553657276696365>
> omniORB: (1) AsyncInvoker: thread id = 1 has started.
> Total threads = 1
> omniORB: (1) Scavenger task execute.
> omniORB: (0) Client opened connection to giop:tcp:127.0.0.1:9080
> omniORB: (0) sendChunk: to giop:tcp:127.0.0.1:9080 100 bytes
> omniORB: (0) 
> 4749 4f50 0100 0100 5800 0000 0000 0000 GIOP....X.......
> 0200 0000 016f 7773 0b00 0000 4e61 6d65 .....ows....Name
> 5365 7276 6963 6566 0600 0000 5f69 735f Servicef...._is_
> 6100 6620 0000 0000 2800 0000 4944 4c3a a.f ....(...IDL:
> 6f6d 672e 6f72 672f 436f 734e 616d 696e omg.org/CosNamin
> 672f 4e61 6d69 6e67 436f 6e74 6578 743a g/NamingContext:
> 312e 3000                               1.0.
> omniORB: (1) Scan for idle connections (1063221421,25000000)
> omniORB: (1) Scan for idle connections done (1063221421,25000000).
> omniORB: (0) throw giopStream::CommFailure from
>    giopStream.cc:825(0,MAYBE,COMM_FAILURE_WaitingForReply)

I have just had a similar problem with a Pascal orb. In my case it helped to
run the omniORB client with "-ORBlcdMode 1" to force GIOP down to "lowest
common denominator".

If this still does not help you might try running omniNames instead of what
you are currently running (WebSphere name server ?) - if possible.

Hope this helps

-- Jan Holst Jensen, Novo Nordisk A/S, Denmark



More information about the omniORB-list mailing list