Mailing-List: contact issues-help@cxf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cxf.apache.org
Date: Mon, 16 Apr 2012 13:32:17 +0000 (UTC)
From: "Aki Yoshida (Assigned) (JIRA)" <jira@apache.org>
To: issues@cxf.apache.org
Message-ID: 
 <1324331465.28461.1334583137287.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <344262268.2296.1332425182141.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Assigned] (CXF-4191) RM broken in synchronous Mode
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CXF-4191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Aki Yoshida reassigned CXF-4191:
--------------------------------

    Assignee: Aki Yoshida
    
> RM broken in synchronous Mode
> -----------------------------
>
>                 Key: CXF-4191
>                 URL: https://issues.apache.org/jira/browse/CXF-4191
>             Project: CXF
>          Issue Type: Bug
>          Components: WS-* Components
>    Affects Versions: 2.4.6
>         Environment: CXF 2.4.6, Jdk5 (Jrockit), spring 2.5, maven2, eclipse 3.7, Win xp
>            Reporter: Ben Pezzei
>            Assignee: Aki Yoshida
>            Priority: Critical
>              Labels: Ws-RM, rm
>
> RM-Setup without a decoupled endpoint (therefore: synchronous modus)
> Client is configured with:
> includeOffer=true,
> SequenceTerminationPolicyType.maxLength=1
> AcknowledgementInterval=0
> Server accepts Offers, wsrm-policy:AcknowledgementInterval=0
> pseudo-Log:
> Req 1: createSequence with offer 123 and acksTo:http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous
> Res 1: CreateSequenceResponse with seqid 456
> Req 2: Sequence with Id 456 & lastMessage-flag & actual content
> Res 2: Sequence with Id 123 & lastMessage-flag & SequenceAcknowledgement for Id 456 & actual content
> Req 3: TerminateSequence for Id 456
> Res 3: standard rm header
> Req 4: SequenceAck for 123
> Req 5: standard rm header
> Res 5: standard rm header
> Req 6 from Server: terminateSequence for 123 to w3c.org
> There is another "feature": When the server PortImpl throws an Exception, Request/Response goes as follows:
> Req 1: createSequence with offer 123 and acksTo:http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous
> Res 1: CreateSequenceResponse with seqid 456
> Req 2: Sequence with Id 456 & lastMessage-flag & actual content
> Res 2: Sequence with 456 & lastMessage, Action: NullpointerException, soap:body contains FaulCode & faultstring
> After receiving the response, client throws UnknownSequence: The value of wsrm:Identifier is not a known Sequence identifier.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira