[omniORB] Meaning of exceptions.

[Janandith Jayawardena]

Hi ,

I'm getting

Minor: UNKNOWN_PythonException, COMPLETED_MAYBE

and

Minor: COMM_FAILURE_MarshalArguments, COMPLETED_NO

in my application. I would like to know the meaning of these exceptions and what causes them to be thrown.

Thanks,
Janandith.




-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.omniorb-support.com/pipermail/omniorb-list/attachments/20090806/16237b5d/attachment.htm

[Igor Lautar]

Hi,

Post by Janandith Jayawardena
Minor: UNKNOWN_PythonException, COMPLETED_MAYBE

Your python application is throwing an exception that is not defined (in IDL)
to be thrown from this call, thus exception is unknown.

Post by Janandith Jayawardena
Minor: COMM_FAILURE_MarshalArguments, COMPLETED_NO

(this one I'm not 100% sure)
Client could not marshal arguments provided to call, and is throwing
COMM_FAILURE. Be careful when using sequences, enums and any fields. These are
most user error prone. So check how you define arguments to function call that
is throwing this.

Regards,
Igor

[Igor Lautar]

Hi,

COMPLETED_YES means call got to server and exception occurred after call was
executed.

COMPLETED_NO means call never got to server, or if it got there, it did not
have any sideeffects (like actually invoking call).

COMPLETED_MAYBE means actual state cannot be determined.

There is a great resource for CORBA programming, 'Advanced CORBA Programming
with C++' by Michi Henning and Steve Vinoski. You can find answers to these
(and much more) questions in it. I would say its a mandatory read if you want
to get serious with CORBA...

Regards,

Post by Janandith Jayawardena
Hi,
Thanks,
What does the COMPLETED_MAYBE and COMPLETED_NO mean. I assume
COMPLETED_MAYBE means that the operation may be completed and COMPLETED_NO
mean operation did not complete.
Is there any other meaning.
regards,
Janandith.
________________________________
Sent: Thursday, August 6, 2009 2:11:27 PM
Subject: Re: [omniORB] Meaning of exceptions.
Hi,

Post by Janandith Jayawardena
Minor: UNKNOWN_PythonException, COMPLETED_MAYBE

Your python application is throwing an exception that is not defined (in
IDL) to be thrown from this call, thus exception is unknown.

Post by Janandith Jayawardena
Minor: COMM_FAILURE_MarshalArguments, COMPLETED_NO

(this one I'm not 100% sure)
Client could not marshal arguments provided to call, and is throwing
COMM_FAILURE. Be careful when using sequences, enums and any fields. These
are most user error prone. So check how you define arguments to function
call that is throwing this.
Regards,
Igor

[Duncan Grisby]

Post by Janandith Jayawardena
Minor: UNKNOWN_PythonException, COMPLETED_MAYBE

Python server-side code threw a non-CORBA exception, or a CORBA
user exception that wasn't declared in the IDL. It will have output a
traceback to stderr on the server.

Post by Janandith Jayawardena
and
Minor: COMM_FAILURE_MarshalArguments, COMPLETED_NO

The network connection broke while the client was sending the arguments
for a call. There are many reasons why that may have occurred. One
possibility is that you are sending argument data larger than the
configured maximum message size, which causes omniORB to drop the
connection. See the giopMaxMsgSize parameter here:

http://omniorb.sourceforge.net/omni41/omniORB/omniORB004.html#toc24

If that's not the problem, run with -ORBtraceLevel 25. That will output
lots of diagnostic information that will help trace the problem.

Cheers,

Duncan.