Mailing-List: contact dev-help@cxf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cxf.apache.org
Received-SPF: pass (athena.apache.org: domain of elakito@gmail.com designates
 209.85.192.177 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <5222C66F.6060701@sosnoski.com>
References: <5222C66F.6060701@sosnoski.com>
Date: Mon, 2 Sep 2013 09:57:28 +0200
Message-ID: 
 <CAF8t5XuE2FTu-A47Zm9G5j+RpK1WW1vePfenuSP7_psTi0=eXQ@mail.gmail.com>
Subject: Re: Changing WS-RM default to terminate on shutdown
From: Aki Yoshida <elakito@gmail.com>
To: dev@cxf.apache.org
Content-Type: text/plain; charset=ISO-8859-1

Hi Dennis,
You mean you want to terminate the active sequence when the endpoint
is shutdown? Maybe I am getting what you meant. A sequence should
survive a crash or a normal endpoint shutdown because the persisted
messages for that ws-rm endpoint must survive. So I don't think we
should change the default setting.

We can already try to avoid having non-terminated sequences by setting
the sequence length or validity and let the ws-rm runtime terminate
the sequences periodically.

regards, aki


2013/9/1 Dennis Sosnoski <dms@sosnoski.com>:
> Right now WS-RM handling allows the user to configure sequence termination
> on shutdown, but defaults to no termination of sequences. This looks like an
> incorrect default, since WS-RM relies on having a TerminateSequence message
> in order to free up resources at the destination. I'd like to change this in
> trunk to default to sending the termination, while allowing the user to
> override with an explicit setting.
>
> The cost of this is an added message exchange (or potentially two, if the
> server also terminates a reverse sequence) as part of the client shutdown
> process.
>
> Anyone object?
>
>   - Dennis
>
> --
>
> Dennis M. Sosnoski
> Java SOA and Web Services Consulting <http://www.sosnoski.com/consult.html>
> CXF and Web Services Security Training
> <http://www.sosnoski.com/training.html>
> Web Services Jump-Start <http://www.sosnoski.com/jumpstart.html>
>