[omniORB] Re: omniORB Send Error (Doug McCorkle)

Doug McCorkle mccdo at iastate.edu
Sat Dec 20 11:25:22 GMT 2003


> Hello,
>      I am using omniORB4 with a client implemented with Java2. I am using an
> omni nameserver. When I try to query the client for data I get this omniORB
> error:
> 
> omniORB: LocateRequest to remote:
> key<0xafabcb00000000028fd5a31f0000000800000001000000000a>
> omniORB: Client opened connection to giop:tcp:129.186.232.210:8045
> omniORB: sendChunk: to giop:tcp:129.186.232.210:8045 49 bytes
> omniORB: inputMessage: from giop:tcp:129.186.232.210:8045 20 bytes
> omniORB: Invoke 'update' on remote:
> key<0xafabcb00000000028fd5a31f0000000800000001000000000a>
> omniORB:  send codeset service context: (ISO-8859-1,UTF-16)
> omniORB: sendChunk: to giop:tcp:129.186.232.210:8045 92 bytes
> omniORB: inputMessage: from giop:tcp:129.186.232.210:8045 252 bytes
> omniORB: throw UNKNOWN from GIOP_C.cc:241 (MAYBE,0x535500ca)
> 
> and then my cpp server side app core dumps. Both the client and server can
> connect to the nameserver with no problems. The client can query the cpp server
> with no problems but when the server queries the client the above error occurs.
> Any suggestions for resolving this error? 
> 
> Doug
> 




I just noticed that when the intial connection of the client takes place this
output occurs:



omniORB: Server accepted connection from giop:tcp:129.186.232.164:32974
omniORB: AsyncInvoker: thread id = 3 has started. Total threads = 3
omniORB: giopWorker task execute.
omniORB: Accepted connection from giop:tcp:129.186.232.164:32974 because of this
rule: "* unix,ssl,tcp"
omniORB: inputMessage: from giop:tcp:129.186.232.164:32974 404 bytes
omniORB:  recieve codeset service context and set TCS to (ISO-8859-1,UTF-16)
omniORB: Dispatching remote call 'attach' to: root<0> (active)
omniORB: Creating ref to remote:
key<0xafabcb000000000294a123f90000000800000001000000000a>
 target id      : IDL:Observer:1.0
 most derived id: IDL:Observer:1.0
IOR:010000001100000049444c3a4f627365727665723a312e300000000001000000000000006800000000010200000000103132392e3138362e3233322e3136340080cd000000000019afabcb000000000294a123f90000000800000001000000000a0000000000000100000001000000200000000000010001000000020501000100010020000101090000000100010100
omniORB: Creating ref to remote:
key<0xafabcb000000000294a123f90000000800000001000000000a>
 target id      : IDL:omg.org/CORBA/Object:1.0
 most derived id: IDL:Observer:1.0
|   Client 0 connected!
omniORB: sendChunk: to giop:tcp:129.186.232.164:32974 24 bytes
omniORB: omniRemoteIdentity deleted.
omniORB: ObjRef(IDL:Observer:1.0) -- deleted.



Is this "omniORB: ObjRef(IDL:Observer:1.0) -- deleted." a good or bad thing?

Doug







More information about the omniORB-list mailing list