[CXF-4191] RM broken in synchronous Mode

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 2.4.6
• Fix Version/s: 2.5.4, 2.6.1
• Component/s: WS-* Components
• Labels: Ws-RM rm

Environment

CXF 2.4.6, Jdk5 (Jrockit), spring 2.5, maven2, eclipse 3.7, Win xp

• Estimated Complexity: Unknown
• Assignee: Akitoshi Yoshida
• Reporter: Ben Pezzei
• Created: 22/Mar/12 14:06
• Updated: 05/Jun/12 13:31
• Resolved: 17/Apr/12 11:09

Description

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.