Discussion:
[omniORB] omniORB: Unknown exception caught by a server thread at GIOP_S.cc: line 307
Michael Teske
2008-11-19 22:08:31 UTC
Permalink
Hi,

recently I got "omniORB: Unknown exception caught by a server thread at
GIOP_S.cc: line 307" output in my stderr. The caller of the method did
not get any response at all.
After googling I found a tip to run the program with -ORBtraceLevel 25
and now I saw this:

omniORB: inputMessage: (body) from
giop:tcp:[::ffff:192.168.130.59]:38506 3848 bytes
omniORB: throw MARSHAL from giopImpl12.cc:811
(NO,MARSHAL_MessageSizeExceedLimitOnServer)
omniORB: Unknown exception caught by a server thread at GIOP_S.cc: line 307

Shouldn't GIOP_S.cc catch that MARSHAL exception and throw it to the sender?

Greetings,
Michael
Duncan Grisby
2008-12-29 23:33:04 UTC
Permalink
Post by Michael Teske
recently I got "omniORB: Unknown exception caught by a server thread
at GIOP_S.cc: line 307" output in my stderr. The caller of the method
did not get any response at all.
After googling I found a tip to run the program with -ORBtraceLevel 25
omniORB: inputMessage: (body) from
giop:tcp:[::ffff:192.168.130.59]:38506 3848 bytes
omniORB: throw MARSHAL from giopImpl12.cc:811
(NO,MARSHAL_MessageSizeExceedLimitOnServer)
omniORB: Unknown exception caught by a server thread at GIOP_S.cc: line 307
Shouldn't GIOP_S.cc catch that MARSHAL exception and throw it to the sender?
Yes, it should, sort-of. It can't send the MARSHAL exception since it
can only do that once it has received the whole message, and the whole
point of the message size limit is to prevent it having to do that. What
it can do is send a MessageError message. I've fixed it in CVS so it
does that.

Cheers,

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