AW: [omniORB] can't get rid of omniORB.BAD_PARAM_WrongPythonType

[Duncan Grisby]

On Monday 2 April, "Daschner, Stefan" wrote:

> Is there a possibility to get more information in such a case
> e.g. which parameter is bad ?

Unfortunately, adding the kind of tracking of what value came from where
would really kill performance, so it doesn't do it. You can get some
clue by looking at the line of code referenced in the log message you
get with traceExceptions=1. That will show you what type it was looking
for when it failed.

> Another question:
> I noticed that I get the following errors on server side when the client program (normally) ends:
> omniORB: Error in network receive (start of message): giop:tcp:127.0.0.1:27199
> omniORB: throw giopStream::CommFailure from giopStream.cc:874(0,NO,COMM_FAILURE_UnMarshalArguments)

They aren't errors. It's just omniORB reporting and then catching the
connection closure.

Cheers,

Duncan.

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