[jira] [Created] (CXF-7095) CDI integration doesn't use the right bus to create the server factory
Romain Manni-Bucau created CXF-7095: --- Summary: CDI integration doesn't use the right bus to create the server factory Key: CXF-7095 URL: https://issues.apache.org/jira/browse/CXF-7095 Project: CXF Issue Type: Bug Components: JAX-RS Affects Versions: 3.1.7 Reporter: Romain Manni-Bucau See http://cxf.547215.n5.nabble.com/cxi-integration-multiple-buses-during-deployment-td5773977.html In short when creating the server in the cdi extension, the bus should be propagated. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CXF-7092) Swagger2Feature tries to resolve swagger-ui resources with api-docs
[
https://issues.apache.org/jira/browse/CXF-7092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Kieselhorst updated CXF-7092:
Fix Version/s: (was: 3.1.8)
3.2.0
> Swagger2Feature tries to resolve swagger-ui resources with api-docs
> ---
>
> Key: CXF-7092
> URL: https://issues.apache.org/jira/browse/CXF-7092
> Project: CXF
> Issue Type: Bug
> Components: JAX-RS
>Affects Versions: 3.1.7
> Environment: Spring Boot 1.4.1
> Swagger 2.2.2
>Reporter: Dennis Kieselhorst
>Priority: Minor
> Fix For: 3.2.0
>
> Attachments: cxf7092.png
>
>
> Add Swagger2Feature for customization to the class annotated with
> @SpringBootApplication, e.g.:
> {code:java}
>@Bean
>public Swagger2Feature swagger2Feature() {
> Swagger2Feature swagger2Feature = new Swagger2Feature();
> swagger2Feature.setPrettyPrint(true);
> swagger2Feature.setContact("person who knows the API");
> return swagger2Feature;
>}
> {code}
> Open url for swagger UI in browser will fail with:
> {noformat}
> Caused by: java.io.FileNotFoundException: JAR entry
> META-INF/resources/webjars/swagger-ui/2.2.2/api-docs/lib/swagger-oauth.js not
> found in /work/m2repository/org/webjars/swagger-ui/2.2.2/swagger-ui-2.2.2.jar
> at
> sun.net.www.protocol.jar.JarURLConnection.connect(JarURLConnection.java:142)
> at
> sun.net.www.protocol.jar.JarURLConnection.getInputStream(JarURLConnection.java:150)
> at java.net.URL.openStream(URL.java:1045)
> at
> org.apache.cxf.jaxrs.swagger.Swagger2Feature$SwaggerUIService.getResource(Swagger2Feature.java:298)
> ... 102 more
> {noformat}
> Please note that it works correctly when the Swagger2Feature is
> auto-configured without customizations.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CXF-7092) Swagger2Feature tries to resolve swagger-ui resources with api-docs
[
https://issues.apache.org/jira/browse/CXF-7092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15585382#comment-15585382
]
Dennis Kieselhorst commented on CXF-7092:
-
So the problem here is the scan-packages: org.apache.cxf.jaxrs.swagger". If it
is present in addition to the @Bean Swagger2Feature it get messed up.
I suggest to simply replace the one from scan-packages if it is manually
configured.
> Swagger2Feature tries to resolve swagger-ui resources with api-docs
> ---
>
> Key: CXF-7092
> URL: https://issues.apache.org/jira/browse/CXF-7092
> Project: CXF
> Issue Type: Bug
> Components: JAX-RS
>Affects Versions: 3.1.7
> Environment: Spring Boot 1.4.1
> Swagger 2.2.2
>Reporter: Dennis Kieselhorst
> Fix For: 3.2.0
>
> Attachments: cxf7092.png
>
>
> Add Swagger2Feature for customization to the class annotated with
> @SpringBootApplication, e.g.:
> {code:java}
>@Bean
>public Swagger2Feature swagger2Feature() {
> Swagger2Feature swagger2Feature = new Swagger2Feature();
> swagger2Feature.setPrettyPrint(true);
> swagger2Feature.setContact("person who knows the API");
> return swagger2Feature;
>}
> {code}
> Open url for swagger UI in browser will fail with:
> {noformat}
> Caused by: java.io.FileNotFoundException: JAR entry
> META-INF/resources/webjars/swagger-ui/2.2.2/api-docs/lib/swagger-oauth.js not
> found in /work/m2repository/org/webjars/swagger-ui/2.2.2/swagger-ui-2.2.2.jar
> at
> sun.net.www.protocol.jar.JarURLConnection.connect(JarURLConnection.java:142)
> at
> sun.net.www.protocol.jar.JarURLConnection.getInputStream(JarURLConnection.java:150)
> at java.net.URL.openStream(URL.java:1045)
> at
> org.apache.cxf.jaxrs.swagger.Swagger2Feature$SwaggerUIService.getResource(Swagger2Feature.java:298)
> ... 102 more
> {noformat}
> Please note that it works correctly when the Swagger2Feature is
> auto-configured without customizations.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CXF-7092) Swagger2Feature tries to resolve swagger-ui resources with api-docs
[
https://issues.apache.org/jira/browse/CXF-7092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Kieselhorst updated CXF-7092:
Priority: Minor (was: Major)
> Swagger2Feature tries to resolve swagger-ui resources with api-docs
> ---
>
> Key: CXF-7092
> URL: https://issues.apache.org/jira/browse/CXF-7092
> Project: CXF
> Issue Type: Bug
> Components: JAX-RS
>Affects Versions: 3.1.7
> Environment: Spring Boot 1.4.1
> Swagger 2.2.2
>Reporter: Dennis Kieselhorst
>Priority: Minor
> Fix For: 3.2.0
>
> Attachments: cxf7092.png
>
>
> Add Swagger2Feature for customization to the class annotated with
> @SpringBootApplication, e.g.:
> {code:java}
>@Bean
>public Swagger2Feature swagger2Feature() {
> Swagger2Feature swagger2Feature = new Swagger2Feature();
> swagger2Feature.setPrettyPrint(true);
> swagger2Feature.setContact("person who knows the API");
> return swagger2Feature;
>}
> {code}
> Open url for swagger UI in browser will fail with:
> {noformat}
> Caused by: java.io.FileNotFoundException: JAR entry
> META-INF/resources/webjars/swagger-ui/2.2.2/api-docs/lib/swagger-oauth.js not
> found in /work/m2repository/org/webjars/swagger-ui/2.2.2/swagger-ui-2.2.2.jar
> at
> sun.net.www.protocol.jar.JarURLConnection.connect(JarURLConnection.java:142)
> at
> sun.net.www.protocol.jar.JarURLConnection.getInputStream(JarURLConnection.java:150)
> at java.net.URL.openStream(URL.java:1045)
> at
> org.apache.cxf.jaxrs.swagger.Swagger2Feature$SwaggerUIService.getResource(Swagger2Feature.java:298)
> ... 102 more
> {noformat}
> Please note that it works correctly when the Swagger2Feature is
> auto-configured without customizations.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CXF-7095) CDI integration doesn't use the right bus to create the server factory
[ https://issues.apache.org/jira/browse/CXF-7095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andriy Redko updated CXF-7095: -- Fix Version/s: 3.1.9 > CDI integration doesn't use the right bus to create the server factory > -- > > Key: CXF-7095 > URL: https://issues.apache.org/jira/browse/CXF-7095 > Project: CXF > Issue Type: Bug > Components: JAX-RS >Affects Versions: 3.1.7 >Reporter: Romain Manni-Bucau >Assignee: Andriy Redko > Fix For: 3.1.9 > > > See > http://cxf.547215.n5.nabble.com/cxi-integration-multiple-buses-during-deployment-td5773977.html > In short when creating the server in the cdi extension, the bus should be > propagated. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (CXF-7095) CDI integration doesn't use the right bus to create the server factory
[ https://issues.apache.org/jira/browse/CXF-7095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andriy Redko reassigned CXF-7095: - Assignee: Andriy Redko > CDI integration doesn't use the right bus to create the server factory > -- > > Key: CXF-7095 > URL: https://issues.apache.org/jira/browse/CXF-7095 > Project: CXF > Issue Type: Bug > Components: JAX-RS >Affects Versions: 3.1.7 >Reporter: Romain Manni-Bucau >Assignee: Andriy Redko > Fix For: 3.1.9 > > > See > http://cxf.547215.n5.nabble.com/cxi-integration-multiple-buses-during-deployment-td5773977.html > In short when creating the server in the cdi extension, the bus should be > propagated. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CXF-7095) CDI integration doesn't use the right bus to create the server factory
[ https://issues.apache.org/jira/browse/CXF-7095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andriy Redko resolved CXF-7095. --- Resolution: Fixed Fix Version/s: 3.2.0 > CDI integration doesn't use the right bus to create the server factory > -- > > Key: CXF-7095 > URL: https://issues.apache.org/jira/browse/CXF-7095 > Project: CXF > Issue Type: Bug > Components: JAX-RS >Affects Versions: 3.1.7 >Reporter: Romain Manni-Bucau >Assignee: Andriy Redko > Fix For: 3.2.0, 3.1.9 > > > See > http://cxf.547215.n5.nabble.com/cxi-integration-multiple-buses-during-deployment-td5773977.html > In short when creating the server in the cdi extension, the bus should be > propagated. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CXF-7096) Server side memory leaking if clients do not send CloseSequence
Andy Zhang created CXF-7096: --- Summary: Server side memory leaking if clients do not send CloseSequence Key: CXF-7096 URL: https://issues.apache.org/jira/browse/CXF-7096 Project: CXF Issue Type: Bug Components: Core Affects Versions: 3.1.8, 3.1.7, 3.1.6 Environment: Windows 7, CXF3.1.6, CXF3.1.7 and CXF3.1.8, Visual Studio 12 client Reporter: Andy Zhang Fix For: 3.1.9 I have a dot net client that invokes a RM web service many times. It does not send CloseSequence at the end. The server side tries to terminate the sequence based on inactivityTimeout in the WSDL. It does not seem to cleanup the sequence completely since the memory usage gets bigger and bigger and eventually the server will run out of memory. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CXF-7096) Server side memory leaking if clients do not send CloseSequence
[ https://issues.apache.org/jira/browse/CXF-7096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Zhang updated CXF-7096: Environment: Windows 7, CXF3.1.6, CXF3.1.7 and CXF3.1.8, Visual Studio 12 client, Java 7, JBoss EAP 6 (was: Windows 7, CXF3.1.6, CXF3.1.7 and CXF3.1.8, Visual Studio 12 client) Priority: Blocker (was: Major) Description: I have a dot net client that invokes a RM web service many times. It does not send CloseSequence at the end. The server side tries to terminate the sequence based on inactivityTimeout in the WSDL. But it does not seem to cleanup the sequence completely since the memory usage gets bigger and bigger and eventually the server will run out of memory. (was: I have a dot net client that invokes a RM web service many times. It does not send CloseSequence at the end. The server side tries to terminate the sequence based on inactivityTimeout in the WSDL. It does not seem to cleanup the sequence completely since the memory usage gets bigger and bigger and eventually the server will run out of memory.) > Server side memory leaking if clients do not send CloseSequence > --- > > Key: CXF-7096 > URL: https://issues.apache.org/jira/browse/CXF-7096 > Project: CXF > Issue Type: Bug > Components: Core >Affects Versions: 3.1.6, 3.1.7, 3.1.8 > Environment: Windows 7, CXF3.1.6, CXF3.1.7 and CXF3.1.8, Visual > Studio 12 client, Java 7, JBoss EAP 6 >Reporter: Andy Zhang >Priority: Blocker > Labels: features > Fix For: 3.1.9 > > > I have a dot net client that invokes a RM web service many times. It does not > send CloseSequence at the end. The server side tries to terminate the > sequence based on inactivityTimeout in the WSDL. But it does not seem to > cleanup the sequence completely since the memory usage gets bigger and bigger > and eventually the server will run out of memory. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CXF-7048) Response does not include SequenceAcknowledgement
[ https://issues.apache.org/jira/browse/CXF-7048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Zhang updated CXF-7048: Priority: Blocker (was: Critical) > 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 >Priority: Blocker > Fix For: 3.1.9 > > > 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. When the request is successfully > processed it does not include the SequenceAcknowledgement in the actual > response. But the client expects it and keeps waiting till it times out. > dot net client also always expects SequenceAcknowledgement in the response. > If the SequenceAcknowledgement is not found it returns a fault saying "A > reply message was received with no acknowledgement." -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CXF-7048) Response does not include SequenceAcknowledgement
[ https://issues.apache.org/jira/browse/CXF-7048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Zhang updated CXF-7048: Fix Version/s: (was: 3.1.8) 3.1.9 > 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 >Priority: Critical > Fix For: 3.1.9 > > > 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. When the request is successfully > processed it does not include the SequenceAcknowledgement in the actual > response. But the client expects it and keeps waiting till it times out. > dot net client also always expects SequenceAcknowledgement in the response. > If the SequenceAcknowledgement is not found it returns a fault saying "A > reply message was received with no acknowledgement." -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CXF-7048) Response does not include SequenceAcknowledgement
[ https://issues.apache.org/jira/browse/CXF-7048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Zhang updated CXF-7048: Environment: JBoss EAP 6, Windows 7, Java 7, Visual Studio 12, CXF 3.1.7 (was: JBoss) > 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 EAP 6, Windows 7, Java 7, Visual Studio 12, CXF > 3.1.7 >Reporter: Andy Zhang >Priority: Blocker > Fix For: 3.1.9 > > > 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. When the request is successfully > processed it does not include the SequenceAcknowledgement in the actual > response. But the client expects it and keeps waiting till it times out. > dot net client also always expects SequenceAcknowledgement in the response. > If the SequenceAcknowledgement is not found it returns a fault saying "A > reply message was received with no acknowledgement." -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CXF-7048) Response does not include SequenceAcknowledgement
[ 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 dot net client. The deliveryAssurance is AtMostOnce. When the service is fast and the response includes SequenceAcknowledgement. But when the service is slow the client usually sends retransmissions. The response corresponding to the retransmission only includes the SequenceAcknowledgement. When the request is successfully processed the response is sent back to client without SequenceAcknowledgement. But the client expects it always in the response. If the client does not find SequenceAcknowledgement it returns a fault to the server saying "A reply message was received with no acknowledgement." The client will keep waiting till it times out. Could you please always include the SequenceAcknowledgement in the actual response? was: 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. When the request is successfully processed it does not include the SequenceAcknowledgement in the actual response. But the client expects it and keeps waiting till it times out. dot net client also always expects SequenceAcknowledgement in the response. If the SequenceAcknowledgement is not found it returns a fault saying "A reply message was received with no acknowledgement." > 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 EAP 6, Windows 7, Java 7, Visual Studio 12, CXF > 3.1.7 >Reporter: Andy Zhang >Priority: Blocker > Fix For: 3.1.9 > > > I have a CXF web service, deployed to JBoss, and a dot net client. The > deliveryAssurance is AtMostOnce. > When the service is fast and the response includes SequenceAcknowledgement. > But when the service is slow the client usually sends retransmissions. The > response corresponding to the retransmission only includes the > SequenceAcknowledgement. When the request is successfully processed the > response is sent back to client without SequenceAcknowledgement. But the > client expects it always in the response. If the client does not find > SequenceAcknowledgement it returns a fault to the server saying "A reply > message was received with no acknowledgement." The client will keep waiting > till it times out. > Could you please always include the SequenceAcknowledgement in the actual > response? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CXF-7096) Server side memory leaking if clients do not send CloseSequence
[ https://issues.apache.org/jira/browse/CXF-7096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15587837#comment-15587837 ] Andy Zhang commented on CXF-7096: - [~dkulp] Hi Daniel, is there a work around to this problem? I've been trying to fix the issue in 3.1.7 but have got any good progress. > Server side memory leaking if clients do not send CloseSequence > --- > > Key: CXF-7096 > URL: https://issues.apache.org/jira/browse/CXF-7096 > Project: CXF > Issue Type: Bug > Components: Core >Affects Versions: 3.1.6, 3.1.7, 3.1.8 > Environment: Windows 7, CXF3.1.6, CXF3.1.7 and CXF3.1.8, Visual > Studio 12 client, Java 7, JBoss EAP 6 >Reporter: Andy Zhang >Priority: Blocker > Labels: features > Fix For: 3.1.9 > > > I have a dot net client that invokes a RM web service many times. It does not > send CloseSequence at the end. The server side tries to terminate the > sequence based on inactivityTimeout in the WSDL. But it does not seem to > cleanup the sequence completely since the memory usage gets bigger and bigger > and eventually the server will run out of memory. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (CXF-7048) Response does not include SequenceAcknowledgement
[ https://issues.apache.org/jira/browse/CXF-7048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Zhang reopened CXF-7048: - > 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 EAP 6, Windows 7, Java 7, Visual Studio 12, CXF > 3.1.7 >Reporter: Andy Zhang >Priority: Blocker > Fix For: 3.1.9 > > > I have a CXF web service, deployed to JBoss, and a dot net client. The > deliveryAssurance is AtMostOnce. > When the service is fast and the response includes SequenceAcknowledgement. > But when the service is slow the client usually sends retransmissions. The > response corresponding to the retransmission only includes the > SequenceAcknowledgement. When the request is successfully processed the > response is sent back to client without SequenceAcknowledgement. But the > client expects it always in the response. If the client does not find > SequenceAcknowledgement it returns a fault to the server saying "A reply > message was received with no acknowledgement." The client will keep waiting > till it times out. > Could you please always include the SequenceAcknowledgement in the actual > response? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CXF-7096) Server side memory leaking if clients do not send CloseSequence
[ https://issues.apache.org/jira/browse/CXF-7096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Zhang updated CXF-7096: Description: I have a dot net client that invokes a RM web service many times. It does not send CloseSequence at the end. The server side tries to terminate the sequence based on inactivityTimeout in the WSDL. But it does not seem to cleanup the sequence completely since the memory usage gets larger and larger and eventually the server will run out of memory. (was: I have a dot net client that invokes a RM web service many times. It does not send CloseSequence at the end. The server side tries to terminate the sequence based on inactivityTimeout in the WSDL. But it does not seem to cleanup the sequence completely since the memory usage gets bigger and bigger and eventually the server will run out of memory.) > Server side memory leaking if clients do not send CloseSequence > --- > > Key: CXF-7096 > URL: https://issues.apache.org/jira/browse/CXF-7096 > Project: CXF > Issue Type: Bug > Components: Core >Affects Versions: 3.1.6, 3.1.7, 3.1.8 > Environment: Windows 7, CXF3.1.6, CXF3.1.7 and CXF3.1.8, Visual > Studio 12 client, Java 7, JBoss EAP 6 >Reporter: Andy Zhang >Priority: Blocker > Labels: features > Fix For: 3.1.9 > > > I have a dot net client that invokes a RM web service many times. It does not > send CloseSequence at the end. The server side tries to terminate the > sequence based on inactivityTimeout in the WSDL. But it does not seem to > cleanup the sequence completely since the memory usage gets larger and larger > and eventually the server will run out of memory. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Issue Comment Deleted] (CXF-7048) Response does not include SequenceAcknowledgement
[ https://issues.apache.org/jira/browse/CXF-7048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Zhang updated CXF-7048: Comment: was deleted (was: As a work around I added the missing SequenceAcknowledgement but the client still complains. Please ignore this ticket.) > 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 EAP 6, Windows 7, Java 7, Visual Studio 12, CXF > 3.1.7 >Reporter: Andy Zhang >Priority: Blocker > Fix For: 3.1.9 > > > I have a CXF web service, deployed to JBoss, and a dot net client. The > deliveryAssurance is AtMostOnce. > When the service is fast and the response includes SequenceAcknowledgement. > But when the service is slow the client usually sends retransmissions. The > response corresponding to the retransmission only includes the > SequenceAcknowledgement. When the request is successfully processed the > response is sent back to client without SequenceAcknowledgement. But the > client expects it always in the response. If the client does not find > SequenceAcknowledgement it returns a fault to the server saying "A reply > message was received with no acknowledgement." The client will keep waiting > till it times out. > Could you please always include the SequenceAcknowledgement in the actual > response? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CXF-7048) Response does not include SequenceAcknowledgement
[ 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 dot net client. The deliveryAssurance is AtMostOnce. When the service is fast and the response includes SequenceAcknowledgement. But when the service is slow the client usually sends retransmissions. The response corresponding to the retransmission only includes the SequenceAcknowledgement. When the request is successfully processed the response is sent back to client without SequenceAcknowledgement. But the client expects it always in the response. If the client does not find SequenceAcknowledgement it returns a fault to the server saying "A reply message was received with no acknowledgement." The client will keep waiting till it times out. Similarly the response of CloseSequence and TerminateSequence do not have expected SequenceAcknowledgement either. Could you please always include the SequenceAcknowledgement in the responses if applicable? was: I have a CXF web service, deployed to JBoss, and a dot net client. The deliveryAssurance is AtMostOnce. When the service is fast and the response includes SequenceAcknowledgement. But when the service is slow the client usually sends retransmissions. The response corresponding to the retransmission only includes the SequenceAcknowledgement. When the request is successfully processed the response is sent back to client without SequenceAcknowledgement. But the client expects it always in the response. If the client does not find SequenceAcknowledgement it returns a fault to the server saying "A reply message was received with no acknowledgement." The client will keep waiting till it times out. Similarly the response of CloseSequence and TerminateSequence do not have expected SequenceAcknowledgement either. Could you please always include the SequenceAcknowledgement in the actual 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 EAP 6, Windows 7, Java 7, Visual Studio 12, CXF > 3.1.7 >Reporter: Andy Zhang >Priority: Blocker > Fix For: 3.1.9 > > > I have a CXF web service, deployed to JBoss, and a dot net client. The > deliveryAssurance is AtMostOnce. > When the service is fast and the response includes SequenceAcknowledgement. > But when the service is slow the client usually sends retransmissions. The > response corresponding to the retransmission only includes the > SequenceAcknowledgement. When the request is successfully processed the > response is sent back to client without SequenceAcknowledgement. But the > client expects it always in the response. If the client does not find > SequenceAcknowledgement it returns a fault to the server saying "A reply > message was received with no acknowledgement." The client will keep waiting > till it times out. > Similarly the response of CloseSequence and TerminateSequence do not have > expected SequenceAcknowledgement either. > Could you please always include the SequenceAcknowledgement in the responses > if applicable? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CXF-7048) Response does not include SequenceAcknowledgement
[ 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 dot net client. The deliveryAssurance is AtMostOnce. When the service is fast and the response includes SequenceAcknowledgement. But when the service is slow the client usually sends retransmissions. The response corresponding to the retransmission only includes the SequenceAcknowledgement. When the request is successfully processed the response is sent back to client without SequenceAcknowledgement. But the client expects it always in the response. If the client does not find SequenceAcknowledgement it returns a fault to the server saying "A reply message was received with no acknowledgement." The client will keep waiting till it times out. Similarly the response of CloseSequence and TerminateSequence do not have expected SequenceAcknowledgement either. Could you please always include the SequenceAcknowledgement in the actual response? was: I have a CXF web service, deployed to JBoss, and a dot net client. The deliveryAssurance is AtMostOnce. When the service is fast and the response includes SequenceAcknowledgement. But when the service is slow the client usually sends retransmissions. The response corresponding to the retransmission only includes the SequenceAcknowledgement. When the request is successfully processed the response is sent back to client without SequenceAcknowledgement. But the client expects it always in the response. If the client does not find SequenceAcknowledgement it returns a fault to the server saying "A reply message was received with no acknowledgement." The client will keep waiting till it times out. Could you please always include the SequenceAcknowledgement in the actual 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 EAP 6, Windows 7, Java 7, Visual Studio 12, CXF > 3.1.7 >Reporter: Andy Zhang >Priority: Blocker > Fix For: 3.1.9 > > > I have a CXF web service, deployed to JBoss, and a dot net client. The > deliveryAssurance is AtMostOnce. > When the service is fast and the response includes SequenceAcknowledgement. > But when the service is slow the client usually sends retransmissions. The > response corresponding to the retransmission only includes the > SequenceAcknowledgement. When the request is successfully processed the > response is sent back to client without SequenceAcknowledgement. But the > client expects it always in the response. If the client does not find > SequenceAcknowledgement it returns a fault to the server saying "A reply > message was received with no acknowledgement." The client will keep waiting > till it times out. > Similarly the response of CloseSequence and TerminateSequence do not have > expected SequenceAcknowledgement either. > Could you please always include the SequenceAcknowledgement in the actual > response? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
