Re: timeout policy and JacORB-3.1

Pascal,

if there is no connection from the client to the server yet, then the
connection timeout will take precedence over the per-object timeout, even
if the connection timeout is longer. Maybe you can check the
connection-level timeout in jacorb.properties. Maybe that has changed to a
different default in 3.0/3.1.

Andre


On Thu, Nov 29, 2012 at 9:17 AM, Pascal VERDIER <[email protected]> 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  -  [email protected].**
> inf.fu-berlin.de <[email protected]>
> https://lists.spline.inf.fu-**berlin.de/mailman/listinfo/**
> jacorb-developer<https://lists.spline.inf.fu-berlin.de/mailman/listinfo/jacorb-developer>
>
_______________________________________________
jacorb-developer maillist  -  [email protected]
https://lists.spline.inf.fu-berlin.de/mailman/listinfo/jacorb-developer