[omniORB] unexpected Python exception during up-call

[Jian Wu]

Hello Ducan,

Here is the tracing with -ORBtraceLevel 25 and -ORBtraceInvocations 1.
In the idl, we have a Fucntion Callback Notitfication (fcn) defined with
a callback interface as the input parameter . 


----------------------KSXA.idl---------------------------
module KSXA_mod {
  interface KSXA_get_result_swapM2EandE2M_cb {
    void proc(
      in    long                           error_code
    );
  }; 
  
  interface KSXA {
  	oneway void get_result_swapM2EandE2M_fcn(
      	in    KSXA_get_result_swapM2EandE2M_cb cb
  	);
  };
}
---------------------------------------------------------


---------------------cliet loging------------------------

omniORB: Adding root<4> (activating) to object table.
omniORB: State root<4> (activating) -> active
omniORB: Creating ref to local: root<4>
 target id      : IDL:KSXA_mod/KSXA_get_result_swapM2EandE2M_cb:1.0
 most derived id: IDL:KSXA_mod/KSXA_get_result_swapM2EandE2M_cb:1.0
omniORB: Invoke 'get_result_swapM2EandE2M_fcn' on remote:
root/Persistent_POA<KSXA.mod.KSXA>
omniORB: sendChunk: to giop:tcp:172.19.16.149:55555 272 bytes
omniORB: Return 'get_result_swapM2EandE2M_fcn' on remote:
root/Persistent_POA<KSXA.mod.KSXA>

omniORB: ObjRef(IDL:KSXA_mod/KSXA_get_result_swapM2EandE2M_cb:1.0) --
deleted.
------------------------------------------------------------


---------------------server logging------------------------
omniORB: sendChunk: to giop:tcp:172.19.16.149:33764 36 bytes
omniORB: inputMessage: from giop:tcp:172.19.16.149:33764 272 bytes
omniORB: Dispatching remote call 'get_result_swapM2EandE2M_fcn' to:
root/Persistent_POA<KSXA.mod.KSXA> (active)
omniORB: Creating Python ref to remote: root<4>
 target id      : IDL:KSXA_mod/KSXA_get_result_swapM2EandE2M_cb:1.0
 most derived id: IDL:KSXA_mod/KSXA_get_result_swapM2EandE2M_cb:1.0
omniORB: Caught an unexpected Python exception during up-call.
TypeError: 'NoneType' object is not callable
omniORB: omniRemoteIdentity deleted.
omniORB: ObjRef(IDL:KSXA_mod/KSXA_get_result_swapM2EandE2M_cb:1.0) --
deleted.
omniORB: inputMessage: from giop:tcp:172.19.16.149:33720 24 bytes
----------------------------------------------------------


Do you know what might cause the TypeError of the callback object at the
server side?

Regards,
Jian


-----Original Message-----
From: Duncan Grisby [mailto:duncan at grisby.org] 
Sent: Wednesday, June 04, 2008 11:42 AM
To: Jian Wu
Cc: omniorb-list at omniorb-support.com
Subject: Re: [omniORB] unexpected Python exception during up-call 

On Tuesday 3 June, Jian Wu wrote:

> During execution, a unexceped execption is caught at the python 
> servant side and displayed on the screen:
> 
> ----------------------------------------------------------------------
> ---------------------------------------
> 
> omniORB: Caught an unexpected Python exception during up-call.
> 
> TypeError: 'NoneType' object is not callable
> 
> ----------------------------------------------------------------------
> -----------------------------------------
> 
> However, no logging of tracebacks makes debugging impossible. We use 
> omniorb 4.1.0 and omniorbPy 3.0.

In what context?  If an exception occurs there should usually be a
traceback. What happens if you run with -ORBtraceLevel 25
-ORBtraceInvocations 1  ?

Duncan.

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


-- 
The information contained in this communication and any attachments is confidential and may be privileged, and is for the sole use of the intended recipient(s). Any unauthorized review, use, disclosure or distribution is prohibited.  Unless explicitly stated otherwise in the body of this communication or the attachment thereto (if any), the information is provided on an AS-IS basis without any express or implied warranties or liabilities.  To the extent you are relying on this information, you are doing so at your own risk.   If you are not the intended recipient, please notify the sender immediately by replying to this message and destroy all copies of this message and any attachments. ASML is neither liable for the proper and complete transmission of the information contained in this communication, nor for any delay in its receipt.