[Ace-users] [tao-users] Policy creation failures (Security, Messaging)
jochen.rothenbacher at nsn.com
Mon Nov 19 03:34:31 CST 2007
are there any news regarding the problem of using strategies and messaging?
I'm asking because I've also have problems using Receive-Wait(RW) wait
strategy (see attached posting) and messaging.
Johnny Willemsen wrote:
> I have seen recently a problem with strategies and messaging, but security
> and messaging should work.
> Johnny Willemsen
> Remedy IT
> Postbus 101
> 2650 AC Berkel en Rodenrijs
> The Netherlands
> www.theaceorb.nl / www.remedy.nl
> *** Integrated compile and test statistics see
> http://scoreboard.theaceorb.nl ***
> *** Commercial service and support for ACE/TAO/CIAO ***
> *** See http://www.theaceorb.nl/en/support.html ***
> "Venkat" <swara101 at yahoo.com> wrote in message
> news:<1193806055.319689.316920 at i38g2000prf.googlegroups.com>...
>> Hello TAO team,
>> Following is the PRF details for the problem
>> TAO VERSION: 1.6.1
>> ACE VERSION: 5.6.1
>> HOST MACHINE and OPERATING SYSTEM:
>> amd64, NetBSD 3.1
>> TARGET MACHINE and OPERATING SYSTEM, if different from HOST:
>> THE $ACE_ROOT/ace/config.h FILE [if you use a link to a platform-
>> specific file, simply state which one]:
>> THE $ACE_ROOT/include/makeinclude/platform_macros.GNU FILE :
>> CONTENTS OF $ACE_ROOT/bin/MakeProjectCreator/config/default.features
>> AREA/CLASS/EXAMPLE AFFECTED:
>> COMPILATION? No
>> LINKING? No
>> EXECUTION? Yes
>> Application - Messaging and Security Policy configuration failure
>> Setup application with SSLIOP secuirty. Configuration of various
>> policies on the orb has a problem.
>> Built an application with SSLIOP security. Following security policy
>> creation works....
>> any_val <<= Security::SecQOPIntegrityAndConfidentiality;
>> orb->create_policy(Security::SecQOPPolicy, any_val);
>> However, creating the following policy causes policy error. Actually,
>> any Messaging policy setup is failing.
>> orb->create_policy(TAO::CONNECTION_TIMEOUT_POLICY_TYPE, cany_val);
>> I ran TAO/tests/AMI_Timeouts to see whether Messaging policy has a
>> problem. The test runs without a problem.
>> It seems the combination of security and Messaging has a problem. Any
>> ideas what could or should be helpful to narrow it down?
>> REPEAT BY:
>> SAMPLE FIX/WORKAROUND:
-------------- next part --------------
An embedded message was scrubbed...
From: Jochen Rothenbacher <jochen.rothenbacher at siemens.com>
Subject: Relative round-trip timeout policy not compatible with
Receive-Wait(RW) wait strategy
Date: Thu, 25 Oct 2007 15:24:46 +0200
More information about the Ace-users