[omniORB] unexpected Python exception during up-call

Discussion:

Jian Wu

2008-06-03 15:31:24 UTC

Dear All,

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.

It there any way to get the tracebacks?

Jian Wu

--
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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.omniorb-support.com/pipermail/omniorb-list/attachments/20080603/354d4bcb/attachment.htm

Duncan Grisby

2008-06-04 15:42:06 UTC

Permalink

During execution, a unexceped execption is caught at the python servant side
-------------------------------------------------------------------------------------------------------------
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 --
-- ***@grisby.org --
-- http://www.grisby.org --

Jian Wu

2008-07-16 19:21:43 UTC

Permalink

Hello Duncan,

Here are the loggings.

omniORB: (4) inputMessage: from giop:tcp:172.19.26.170:58962 272 bytes
omniORB: (4)
4749 4f50 0102 0000 0000 0104 0000 0028 GIOP...........(
0000 0000 0000 0025 0000 001d ff50 6572 .......%.....Per
7369 7374 656e 745f 504f 4100 4b53 5841 sistent_POA.KSXA
5f6d 6f64 2e4b 5358 4157 4178 0000 001d _mod.KSXAWAx....
6765 745f 7265 7375 6c74 5f73 7761 704d get_result_swapM
3245 616e 6445 324d 5f66 636e 0043 6865 2EandE2M_fcn.Che
0000 0000 6c43 6875 0000 0032 4944 4c3a ....lChu...2IDL:
4b53 5841 5f6d 6f64 2f4b 5358 415f 6765 KSXA_mod/KSXA_ge
745f 7265 7375 6c74 5f73 7761 704d 3245 t_result_swapM2E
616e 6445 324d 5f63 623a 312e 3000 6172 andE2M_cb:1.0.ar
0000 0001 0000 0000 0000 0064 0001 0200 ...........d....
0000 000e 3137 322e 3139 2e32 362e 3137 ....172.19.26.17
3000 e640 0000 000e fe48 7df5 7cca 3200 ***@.....H}.|.2.
0000 0000 0001 0000 0000 0002 0000 0000 ................
0000 0008 0000 0000 4154 5400 0000 0001 ........ATT.....
0000 001c 0000 0000 0001 0001 0000 0001 ................
0501 0001 0001 0109 0000 0001 0001 0109 ................
omniORB: (4) Dispatching remote call 'get_result_swapM2EandE2M_fcn' to:
root/Persistent_POA<KSXA.mod.KSXA> (active)
omniORB: (4) Creating Python ref to remote: root<1>
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: (4) Caught an unexpected Python exception during up-call.
TypeError: 'NoneType' object is not callable
omniORB: (4) throw UNKNOWN from pyServant.cc:587
(MAYBE,UNKNOWN_PythonException)
omniORB: (4) omniRemoteIdentity deleted.
omniORB: (4) ObjRef(IDL:KSXA_mod/KSXA_get_result_swapM2EandE2M_cb:1.0)
-- deleted.
omniORB: (0) inputMessage: from giop:tcp:172.19.26.170:58944 24 bytes
omniORB: (0)
4749 4f50 0102 0001 0000 000c 0000 0004 GIOP............
0000 0000 0000 0000 ........

Any further suggestion to identify the problem?

Thanks,

Jian

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

Post by Jian Wu
During execution, a unexceped execption is caught at the python
----------------------------------------------------------------------
---------------------------------------
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 --
-- ***@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.

Jian Wu

2008-06-05 16:44:57 UTC

Permalink

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:***@grisby.org]
Sent: Wednesday, June 04, 2008 11:42 AM
To: Jian Wu
Cc: omniorb-***@omniorb-support.com
Subject: Re: [omniORB] unexpected Python exception during up-call

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

2008-06-25 17:03:07 UTC

Permalink

Post by Jian Wu
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 .

Sorry for the long delay in replying. There's nothing obvious about your
code or the traceback, I'm afraid. What does your servant implementation
look like? Is there any possibility that the method could end up being
set to None?

Cheers,

Duncan.

--
-- Duncan Grisby --
-- ***@grisby.org --
-- http://www.grisby.org --