[omniORB] omniORB 4.3: chokes on default configuration file
Duncan Grisby
duncan at grisby.org
Sun Aug 30 10:03:00 UTC 2020
On Fri, 2020-08-28 at 21:32 +0200, Thomas Braun via omniORB-list wrote:
>
> omniORB: (0) 2020-08-28 21:21:55.252509: ORB_init failed: Bad
> parameter
> (2097152 # 2 MBytes.) for ORB configuration option giopMaxMsgSize,
> reason: Invalid value, exp
> ect n >= 8192 or n == 0
>
> Caught CORBA::INITIALIZE
>
>
> The problem is the value for giopMaxMsgSize in the config file, as
> the parser does not ignore trailing whitespace and comments and can
> then not parse the value into a number.
Thanks for reporting that. There was a change in the config file parser
to make it a bit more strict about valid values, and it caused it to
dislike that line. I have changed the sample.cfg file to remove that
trailing comment.
Duncan.
--
-- Duncan Grisby --
-- duncan at grisby.org --
-- http://www.grisby.org --
More information about the omniORB-list
mailing list