[
https://issues.apache.org/jira/browse/CXF-7048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Zhang updated CXF-7048:
----------------------------
Description:
I have a CXF web service deployed to JBoss and a CXF client. The
deliveryAssurance is AtMostOnce.
When the service is fast no retransmission is needed and the response includes
SequenceAcknowledgement. But when the service is slow the client usually sends
retransmissions. The RM framework sends responses to only include the
SequenceAcknowledgement. It does not have the SequenceAcknowledgement in the
actual response to the original request when it request is successfully
processed. But the client expects it and keeps waiting till it times out.
I've verified that dot net client also expects SequenceAcknowledgement in the
response. It makes sense to always send the SequenceAcknowledgement in the
response.
was:
I have a CXF web service deployed to JBoss and a CXF client with WCF. The
deliveryAssurance is AtMostOnce.
When the service is fast no retransmission is needed and the response includes
SequenceAcknowledgement. But when the service is slow the client usually sends
retransmissions. The RM framework sends responses to only include the
SequenceAcknowledgement. It does not send the SequenceAcknowledgement again in
the actual response of the original request. But the client expects it and
keeps waiting till it times out.
I've verified that dot net client has the same behavior. It makes sense to
always send the SequenceAcknowledgement in the response.
> Response does not include SequenceAcknowledgement
> -------------------------------------------------
>
> Key: CXF-7048
> URL: https://issues.apache.org/jira/browse/CXF-7048
> Project: CXF
> Issue Type: Bug
> Components: Core
> Affects Versions: 3.1.7
> Environment: JBoss
> Reporter: Andy Zhang
>
> I have a CXF web service deployed to JBoss and a CXF client. The
> deliveryAssurance is AtMostOnce.
> When the service is fast no retransmission is needed and the response
> includes SequenceAcknowledgement. But when the service is slow the client
> usually sends retransmissions. The RM framework sends responses to only
> include the SequenceAcknowledgement. It does not have the
> SequenceAcknowledgement in the actual response to the original request when
> it request is successfully processed. But the client expects it and keeps
> waiting till it times out.
> I've verified that dot net client also expects SequenceAcknowledgement in the
> response. It makes sense to always send the SequenceAcknowledgement in the
> response.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
