MARSHAL exception

[Duncan Grisby]

On Wed, 2015-12-23 at 20:03 +0000, Sanjay K wrote:

> omniORB: (1) 2015-12-23 14:58:47.224000: throw MARSHAL from
> GIOP_C.cc:218 (NO,MARSHAL_InvalidEnumValue)

Well, that's pretty clearly telling you that you have an invalid value
for an enum.

> I looked at the code, GIOP_C.cc:218 , which is
> OMNIORB_FOR_EACH_SYS_EXCEPTION(CHECK_AND_IF_MATCH_THROW_SYSTEM_EXCEPTION). Looks to me it's a general exception handling.

Yes, that's the general exception handling for when the client receives
an exception from the server. The server will log the details about
where it was unhappy about the enum.

> Is there any way to know, which EnumValue cause this exception, as
> many EnumValues get transferred to other end.

Look at the tracing on the server to see where it threw the exception.
You can also run with -ORBtraceInvocations 1 to see the name of the
operation that is being called when the error occurs.

Duncan.

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