[tao-users] TAO 1.7.4 (I know, its old)

[Ruff, Rob]

To: tao-bugs at cs.wustl.edu
Subject: TAO: Exceptions accessing Naming Service with VS 2019 upgrade

    ACE VERSION: 5.7.4
    TAO VERSION: 1.7.4

    HOST MACHINE and OPERATING SYSTEM: Dell Precision M4800, Windows 10
        If on Windows based OS's, which version of WINSOCK do you
        use?:

    TARGET MACHINE and OPERATING SYSTEM, if different from HOST:
    COMPILER NAME AND VERSION (AND PATCHLEVEL):MS VS 2008 sp1, MS VS 2019

    THE $ACE_ROOT/ace/config.h FILE [if you use a link to a platform-
    specific file, simply state which one]: config-win32.h

    THE $ACE_ROOT/include/makeinclude/platform_macros.GNU FILE [if you
    use a link to a platform-specific file, simply state which one
    (unless this isn't used in this case, e.g., with Microsoft Visual
    C++)]:

    BUILD METHOD USED:
[Experimental ./configure or traditional makefile/project file?]

    CONTENTS OF $ACE_ROOT/bin/MakeProjectCreator/config/default.features
    (used by MPC when you generate your own makefiles):

    AREA/CLASS/EXAMPLE AFFECTED:
[What example failed?  What module failed to compile?]
Naming service access runtime issue

    DOES THE PROBLEM AFFECT:
        COMPILATION? NO
        LINKING? NO
            On Unix systems, did you run make realclean first?
        EXECUTION? YES
        OTHER (please specify)?
[Please indicate whether ACE/TAO, your application, or both are affected.]
Both

    SYNOPSIS:
Trying to migrate from VS 2008 to VS 2019

    DESCRIPTION:
I let VS 2019 auto update the ace/TAO VS 2008 files.  With a few minor changes,
I was able to compile and build everything.  I can start applications but none
can communicate with the naming service.  I always get a CORBA TRANSIENT
exception.

I ran tao_nslist from the debugger and it throws the exception on:

CosNaming::NamingContext_var root_nc =
    CosNaming::NamingContext::_narrow (obj.in ());

Any tips on what could be wrong?

I built the latest ace/tao with vs 2019 and was able to connect tao_nslist to
the naming service but that upgrade would result in quite a few changes to our
code so I was hoping to stick with 5.7.4 if possible.  The software is for
command and control of three communication systems in operation in Antarctica.


    REPEAT BY:
As a simple test, I used naming_service and tao_nslist applications built with
both VS 2008 and VS 2019.  Here are the results:

connect VS 2008 tao_nslist to VS 2008 naming_service - WORKS
connect VS 2019 tao_nslist to VS 2008 naming_service - TRANSIENT exception
connect VS 2008 tao_nslist to VS 2019 naming_service - WORKS
connect VS 2019 tao_nslist to VS 2019 naming_service - TRANSIENT exception

    SAMPLE FIX/WORKAROUND:
[If available ]

________________________________

CONFIDENTIALITY NOTICE: This email constitutes an electronic communication within the meaning of the Electronic Communications Privacy Act, 18 U.S.C. 2510, and its disclosure is strictly limited to the named recipient(s) intended by the sender of this message. This email, and any attachments, may contain confidential and/or proprietary information of Scientific Research Corporation. If you are not a named recipient, any copying, using, disclosing or distributing to others the information in this email and attachments is STRICTLY PROHIBITED. If you have received this email in error, please notify the sender immediately and permanently delete the email, any attachments, and all copies thereof from any drives or storage media and destroy any printouts or hard copies of the email and attachments.

EXPORT COMPLIANCE NOTICE: This email and any attachments may contain technical data subject to U.S export restrictions under the International Traffic in Arms Regulations (ITAR) or the Export Administration Regulations (EAR). Export or transfer of this technical data and/or related information to any foreign person(s) or entity(ies), either within the U.S. or outside of the U.S., may require advance export authorization by the appropriate U.S. Government agency prior to export or transfer. In addition, technical data may not be exported or transferred to certain countries or specified designated nationals identified by U.S. embargo controls without prior export authorization. By accepting this email and any attachments, all recipients confirm that they understand and will comply with all applicable ITAR, EAR and embargo compliance requirements.