[jacorb-developer] timeout policy and JacORB-3.1

[Phil Mesnier]

Hi Pascal,

How are you setting the policy? My guess is you are using object.set_policy_override () to do it, then using the original object. If that is the case, you now need to do something like:

CORBA.object new_obj = object.set_policy_override (policies,…);
// narrow new_obj to actual type 
// use new reference

The function behavior changed because the older implementation was not spec compliant. CORBA.object.set_policy_override() is supposed to return a new object reference with the policies applied, but is not supposed to modify the original object's policy set.

Now if that is not the case, please send a small test program that demonstrates what you are observing.

Best regards,
Phil


On Nov 29, 2012, at 8:17 AM, Pascal VERDIER wrote:

> Hi Jacorb developers
> 
> I am using JacORB since 2004 and I use policy to set a timeout on my CORBA objects.
> I decided to port my application to JacORB-3.1 and it seems to work fine except the timeout.
> I write a simple idl/server/client  with a set policy as explain in /Quality of Service/ chapter.
> I tested it with JacORB-2.3.  It works fine (org.omg.CORBA.TIMEOUT exception is thrown)
> I tried it with JacORB-3.1 and JacORB-3.0, no timeout occurred, and a call can takes a long time.
> 
> Did I missed something ?
> Thanks for your help.
> Pascal
> _______________________________________________
> jacorb-developer maillist  -  jacorb-developer at lists.spline.inf.fu-berlin.de
> https://lists.spline.inf.fu-berlin.de/mailman/listinfo/jacorb-developer

--
Phil Mesnier
Principal Software Engineer and Partner,   http://www.ociweb.com
Object Computing, Inc.                     +01.314.579.0066 x225