[omniORB] omniNames: Problem reading 4.0.0 logfile with 4.0.7.

[Duncan Grisby]

On Tuesday 28 November, "JHJE (Jan Holst Jensen)" wrote:

> I have upgraded our main production COS naming server to omniORB 4.0.7.
> In the process, I transferred the log file from the old machine running
> 4.0.0 to the new machine and expected it to be able to reuse the old log
> file (the new machine has the same IP address and network configuration
> as the old one, so I would expect it to work, right ?). But omniNames
> fails with an "Aborted" message when I try to use the old log file.

The problem is that omniORB 4.0.0 had a misinterpretation of the CORBA
spec about system assigned object ids. That was fixed at some point
before 4.0.7, meaning that old object ids became invalid. You can make
them valid again by setting the poaUniquePersistentSystemIds parameter
to 0.

Cheers,

Duncan.

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