[omniORB] propagating exceptions

Srikanth Mandava Srikanth.Mandava at cosinecom.com
Tue Mar 16 11:03:09 GMT 2004


I'm not doing a rethrow in this case. The exception does not come to my
application code at all. It's exiting the client from the stub layer after
handling the system exception.
 
- Srikanth

-----Original Message-----
From: Michael Shearer [mailto:mshearer at aastra.com]
Sent: Tuesday, March 16, 2004 10:56 AM
To: Srikanth Mandava; omniorb-list at omniorb-support.com
Subject: RE: [omniORB] propagating exceptions


I'm not too familiar with Python but I assume you're attempting to rethrow
the exception to the application once you've handled it in the server, is
that correct?  For example:
 
try{
    //whatever
}
catch(Exception)
{
    //handler
    throw;
}
 
I was having similar problems in C++ a while back because of a bug with the
GNU compiler.  Propagating exceptions doesn't work when you compile you're
code using a rethrow and when using the "-fomit_frame_pointer" flag.  If
you're using g++, that might be the problem.
 
Mike
 
Michael Shearer 
CVX SS7 Gateway (CSG) Engineer 
Aastra Telecom US, CVX Division 
8 Federal Street 
Billerica, MA, USA, 01821-3570
* Phone (978) 436-4248 
* Fax (978) 436-4233
* Internet Mail mshearer at aastra.com
* Web www.aastra.com 

-----Original Message-----
From: omniorb-list-bounces at omniorb-support.com
[mailto:omniorb-list-bounces at omniorb-support.com]On Behalf Of Srikanth
Mandava
Sent: Tuesday, March 16, 2004 1:43 PM
To: 'omniorb-list at omniorb-support.com'
Subject: [omniORB] propagating exceptions


          Hi, 

I'm using omniORB python to generate stubs to talk to a CORBA server. When a
COMM_FAILURE or other system exceptions are thrown from the CORBA server,
these are not being propagated to the application. The client is quitting
after the stubs handle the exception instead of propagating them to the
application code. Is there a way to get the system exceptions propagated to
the application code?

In the example code below, the exception is not propagated to the
commandexecutor.py module. 

Thanks 
Srikanth 

example: 


03/12/04 22:52:39 : Traceback (most recent call last): 
  File "./commandexecutor.py", line 117, in executeShowConfigCommand 
    exec(commandString, helpers.__dict__, localStore) 
  File "<string>", line 1, in ? 
  File "/opt/ipnos/cli/generated/omniidl/systemservice_idl.py", line 1354,
in showBootConfigConfig 
    return _omnipy.invoke(self, "showBootConfigConfig",
_0_cosinecom.agent.SystemService._d_showBootConfigConfig, args) 
INV_OBJREF: Minor: 0x0, COMPLETED_NO 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.omniorb-support.com/pipermail/omniorb-list/attachments/20040316/8aba5959/attachment.htm


More information about the omniORB-list mailing list