[jira] [Commented] (CXF-5436) Poorly crafted response caused NullPointerException when processing incoming message

[ https://issues.apache.org/jira/browse/CXF-5436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15829457#comment-15829457 ] Freeman Fang commented on CXF-5436: --- patch applied on behalf of Arnaud Jeansen with thanks

[jira] [Assigned] (CXF-5436) Poorly crafted response caused NullPointerException when processing incoming message

[ https://issues.apache.org/jira/browse/CXF-5436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned CXF-5436: - Assignee: Freeman Fang > Poorly crafted response caused NullPointerException when processing incomi

[jira] [Resolved] (CXF-7211) receiveTimeouts aren't respected anymore since 3.1.9 for requests < 1000ms duration

[ https://issues.apache.org/jira/browse/CXF-7211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CXF-7211. --- Resolution: Not A Problem > receiveTimeouts aren't respected anymore since 3.1.9 for requests < 1000ms

[jira] [Commented] (CXF-7211) receiveTimeouts aren't respected anymore since 3.1.9 for requests < 1000ms duration

[ https://issues.apache.org/jira/browse/CXF-7211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15824954#comment-15824954 ] Freeman Fang commented on CXF-7211: --- Hi Veit, This is a good testcase and I get your poin

[jira] [Assigned] (CXF-7211) receiveTimeouts aren't respected anymore since 3.1.9 for requests < 1000ms duration

[ https://issues.apache.org/jira/browse/CXF-7211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned CXF-7211: - Assignee: Freeman Fang > receiveTimeouts aren't respected anymore since 3.1.9 for requests < 1000ms

[jira] [Commented] (CXF-6567) Allow alternate wildcard in Camel CXF Transport for Blueprint

[ https://issues.apache.org/jira/browse/CXF-6567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15820281#comment-15820281 ] Freeman Fang commented on CXF-6567: --- Hi metatech, FYI, the ARIES-1395 introduce a fine-gr

[jira] [Resolved] (CXF-7210) StringIndexOutOfBoundsException during construction of failover request

[ https://issues.apache.org/jira/browse/CXF-7210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CXF-7210. --- Resolution: Fixed Fix Version/s: 3.1.10 3.2.0 patch applied on behalf of Sebas

[jira] [Assigned] (CXF-7210) StringIndexOutOfBoundsException during construction of failover request

[ https://issues.apache.org/jira/browse/CXF-7210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned CXF-7210: - Assignee: Freeman Fang > StringIndexOutOfBoundsException during construction of failover request >

[jira] [Resolved] (CXF-7206) java9 build is broken since 9-ea+148

[ https://issues.apache.org/jira/browse/CXF-7206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CXF-7206. --- Resolution: Fixed Fix Version/s: 3.2.0 all tests passed with java 9-ea+149 > java9 build is brok

[jira] [Commented] (CXF-7206) java9 build is broken since 9-ea+148

[ https://issues.apache.org/jira/browse/CXF-7206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15803650#comment-15803650 ] Freeman Fang commented on CXF-7206: --- This commit fix most broken http://git-wip-us.apache.

[jira] [Assigned] (CXF-7206) java9 build is broken since 9-ea+148

[ https://issues.apache.org/jira/browse/CXF-7206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned CXF-7206: - Assignee: Freeman Fang > java9 build is broken since 9-ea+148 > ---

[jira] [Created] (CXF-7206) java9 build is broken since 9-ea+148

Freeman Fang created CXF-7206: - Summary: java9 build is broken since 9-ea+148 Key: CXF-7206 URL: https://issues.apache.org/jira/browse/CXF-7206 Project: CXF Issue Type: Sub-task Repor

[jira] [Resolved] (CXF-7205) In JmsPullPoint create session for producer and consumer separately and synchronized the session but not the whole method to avoid deadlock

[ https://issues.apache.org/jira/browse/CXF-7205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CXF-7205. --- Resolution: Fixed Fix Version/s: 3.1.10 3.2.0 > In JmsPullPoint create session

[jira] [Created] (CXF-7205) In JmsPullPoint create session for producer and consumer separately and synchronized the session but not the whole method to avoid deadlock

Freeman Fang created CXF-7205: - Summary: In JmsPullPoint create session for producer and consumer separately and synchronized the session but not the whole method to avoid deadlock Key: CXF-7205 URL: https://issues.a

[jira] [Assigned] (CXF-7205) In JmsPullPoint create session for producer and consumer separately and synchronized the session but not the whole method to avoid deadlock

[ https://issues.apache.org/jira/browse/CXF-7205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned CXF-7205: - Assignee: Freeman Fang > In JmsPullPoint create session for producer and consumer separately and >

[jira] [Resolved] (CXF-7202) the incorrect spring-beans-4.3.xsd/spring-util-4.3.xsd/spring-context-4.3.xsd cause master build extremely slow and sometimes even hang

[ https://issues.apache.org/jira/browse/CXF-7202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CXF-7202. --- Resolution: Fixed Fix Version/s: 3.2.0 > the incorrect spring-beans-4.3.xsd/spring-util-4.3.xsd/s

[jira] [Assigned] (CXF-7202) the incorrect spring-beans-4.3.xsd/spring-util-4.3.xsd/spring-context-4.3.xsd cause master build extremely slow and sometimes even hang

[ https://issues.apache.org/jira/browse/CXF-7202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned CXF-7202: - Assignee: Freeman Fang > the incorrect spring-beans-4.3.xsd/spring-util-4.3.xsd/spring-context-4.3.

[jira] [Created] (CXF-7202) the incorrect spring-beans-4.3.xsd/spring-util-4.3.xsd/spring-context-4.3.xsd cause master build extremely slow and sometimes even hang

Freeman Fang created CXF-7202: - Summary: the incorrect spring-beans-4.3.xsd/spring-util-4.3.xsd/spring-context-4.3.xsd cause master build extremely slow and sometimes even hang Key: CXF-7202 URL: https://issues.apach

[jira] [Resolved] (CXF-7199) drop jetty 8 support for CXF 3.2

[ https://issues.apache.org/jira/browse/CXF-7199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CXF-7199. --- Resolution: Fixed Fix Version/s: 3.2.0 commit http://git-wip-us.apache.org/repos/asf/cxf/commit/

[jira] [Moved] (CXF-7199) drop jetty 8 support for CXF 3.2

[ https://issues.apache.org/jira/browse/CXF-7199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang moved KARAF-4910 to CXF-7199: -- Estimated Complexity: Unknown Workflow: Default workflow, editable

[jira] [Resolved] (CXF-7198) cxf-spring-boot-starter does not work with Spring Boot 1.5.0 or above

[ https://issues.apache.org/jira/browse/CXF-7198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CXF-7198. --- Resolution: Fixed Fix Version/s: 3.2.0 commit fix http://git-wip-us.apache.org/repos/asf/cxf/comm

[jira] [Commented] (CXF-7198) cxf-spring-boot-starter does not work with Spring Boot 1.5.0 or above

[ https://issues.apache.org/jira/browse/CXF-7198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15782773#comment-15782773 ] Freeman Fang commented on CXF-7198: --- Yeah, what I'm going to do is upgrade to springboot 1

[jira] [Assigned] (CXF-7198) cxf-spring-boot-starter does not work with Spring Boot 1.5.0 or above

[ https://issues.apache.org/jira/browse/CXF-7198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned CXF-7198: - Assignee: Freeman Fang > cxf-spring-boot-starter does not work with Spring Boot 1.5.0 or above > --

[jira] [Commented] (CXF-7160) Can not configure CXF http-jetty transport to handle X-Fowarded-for headers with Jetty 9

[ https://issues.apache.org/jira/browse/CXF-7160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15768923#comment-15768923 ] Freeman Fang commented on CXF-7160: --- http://cxf.547215.n5.nabble.com/CXF-3-2-support-jetty

[jira] [Resolved] (CXF-7160) Can not configure CXF http-jetty transport to handle X-Fowarded-for headers with Jetty 9

[ https://issues.apache.org/jira/browse/CXF-7160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CXF-7160. --- Resolution: Fixed > Can not configure CXF http-jetty transport to handle X-Fowarded-for headers > with

[jira] [Comment Edited] (CXF-7160) Can not configure CXF http-jetty transport to handle X-Fowarded-for headers with Jetty 9

[ https://issues.apache.org/jira/browse/CXF-7160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15768899#comment-15768899 ] Freeman Fang edited comment on CXF-7160 at 12/22/16 3:30 AM: - Hi

[jira] [Commented] (CXF-7160) Can not configure CXF http-jetty transport to handle X-Fowarded-for headers with Jetty 9

[ https://issues.apache.org/jira/browse/CXF-7160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15768899#comment-15768899 ] Freeman Fang commented on CXF-7160: --- Hi Sergey, Yes, CXF-7179 covered this one, I will re

[jira] [Commented] (CXF-7160) Can not configure CXF http-jetty transport to handle X-Fowarded-for headers with Jetty 9

[ https://issues.apache.org/jira/browse/CXF-7160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15753629#comment-15753629 ] Freeman Fang commented on CXF-7160: --- Yeah I will take care of both and post on DEV what I

[jira] [Assigned] (CXF-7179) Unable to set ServerConnector in JettyHTTPServerEngine using jetty 9

[ https://issues.apache.org/jira/browse/CXF-7179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned CXF-7179: - Assignee: Freeman Fang > Unable to set ServerConnector in JettyHTTPServerEngine using jetty 9 > ---

[jira] [Resolved] (CXF-7168) CXF WSN Publisher SOAP 1.2 Binding

[ https://issues.apache.org/jira/browse/CXF-7168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CXF-7168. --- Resolution: Fixed Fix Version/s: 3.0.13 3.1.10 > CXF WSN Publisher SOAP 1.2 Bi

[jira] [Commented] (CXF-7168) CXF WSN Publisher SOAP 1.2 Binding

[ https://issues.apache.org/jira/browse/CXF-7168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15750575#comment-15750575 ] Freeman Fang commented on CXF-7168: --- We should create the endpoint with soap1.2 enabled wh

[jira] [Assigned] (CXF-7168) CXF WSN Publisher SOAP 1.2 Binding

[ https://issues.apache.org/jira/browse/CXF-7168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned CXF-7168: - Assignee: Freeman Fang > CXF WSN Publisher SOAP 1.2 Binding > -- >

[jira] [Assigned] (CXF-7160) Can not configure CXF http-jetty transport to handle X-Fowarded-for headers with Jetty 9

[ https://issues.apache.org/jira/browse/CXF-7160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned CXF-7160: - Assignee: Freeman Fang > Can not configure CXF http-jetty transport to handle X-Fowarded-for header

[jira] [Commented] (CXF-5663) IllegalStateException using AsyncHTTPConduit

[ https://issues.apache.org/jira/browse/CXF-5663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15707315#comment-15707315 ] Freeman Fang commented on CXF-5663: --- I strongly suspect this issue was fixed by CXF-7109 a

[jira] [Commented] (CXF-5663) IllegalStateException using AsyncHTTPConduit

[ https://issues.apache.org/jira/browse/CXF-5663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15696838#comment-15696838 ] Freeman Fang commented on CXF-5663: --- Hi Sergey, Sure, I will take a close look when I get

[jira] [Assigned] (CXF-5663) IllegalStateException using AsyncHTTPConduit

[ https://issues.apache.org/jira/browse/CXF-5663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned CXF-5663: - Assignee: Freeman Fang > IllegalStateException using AsyncHTTPConduit > ---

[jira] [Resolved] (CXF-7145) synchronized store and getMessages of JmsPullPoint would cause deadlock

[ https://issues.apache.org/jira/browse/CXF-7145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CXF-7145. --- Resolution: Fixed Fix Version/s: 3.1.9 3.2.0 > synchronized store and getMessa

[jira] [Updated] (CXF-7145) synchronized store and getMessages of JmsPullPoint would cause deadlock

[ https://issues.apache.org/jira/browse/CXF-7145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang updated CXF-7145: -- Description: The JmsPullPoint would be accessed by both the producer client and consumer client, currentl

[jira] [Assigned] (CXF-7145) synchronized store and getMessages of JmsPullPoint would cause deadlock

[ https://issues.apache.org/jira/browse/CXF-7145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned CXF-7145: - Assignee: Freeman Fang > synchronized store and getMessages of JmsPullPoint would cause deadlock >

[jira] [Created] (CXF-7145) synchronized store and getMessages of JmsPullPoint would cause deadlock

Freeman Fang created CXF-7145: - Summary: synchronized store and getMessages of JmsPullPoint would cause deadlock Key: CXF-7145 URL: https://issues.apache.org/jira/browse/CXF-7145 Project: CXF Is

[jira] [Resolved] (CXF-7144) support to specify pullpoint queue name of WS-N

[ https://issues.apache.org/jira/browse/CXF-7144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CXF-7144. --- Resolution: Fixed Fix Version/s: 3.1.9 3.2.0 > support to specify pullpoint qu

[jira] [Assigned] (CXF-7144) support to specify pullpoint queue name of WS-N

[ https://issues.apache.org/jira/browse/CXF-7144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned CXF-7144: - Assignee: Freeman Fang > support to specify pullpoint queue name of WS-N >

[jira] [Created] (CXF-7144) support to specify pullpoint queue name of WS-N

Freeman Fang created CXF-7144: - Summary: support to specify pullpoint queue name of WS-N Key: CXF-7144 URL: https://issues.apache.org/jira/browse/CXF-7144 Project: CXF Issue Type: Improvement

[jira] [Resolved] (CXF-6969) CXF Async HTTP Transport - add supports to configure httpclient with new method

[ https://issues.apache.org/jira/browse/CXF-6969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CXF-6969. --- Resolution: Not A Problem No response so for. Mark as "Not A Problem" and close for now > CXF Async HT

[jira] [Assigned] (CXF-7130) Maven plugin to invoke SOAP service

[ https://issues.apache.org/jira/browse/CXF-7130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned CXF-7130: - Assignee: Freeman Fang > Maven plugin to invoke SOAP service > ---

[jira] [Commented] (CXF-6969) CXF Async HTTP Transport - add supports to configure httpclient with new method

[ https://issues.apache.org/jira/browse/CXF-6969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15663053#comment-15663053 ] Freeman Fang commented on CXF-6969: --- I took a close look at the code, I believe the config

[jira] [Assigned] (CXF-6969) CXF Async HTTP Transport - add supports to configure httpclient with new method

[ https://issues.apache.org/jira/browse/CXF-6969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned CXF-6969: - Assignee: Freeman Fang > CXF Async HTTP Transport - add supports to configure httpclient with new

[jira] [Resolved] (CXF-7122) Infinite loop due to AsyncHTTPConduit read timeout with exhausted connection pool

[ https://issues.apache.org/jira/browse/CXF-7122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CXF-7122. --- Resolution: Fixed > Infinite loop due to AsyncHTTPConduit read timeout with exhausted connection > pool

[jira] [Comment Edited] (CXF-7122) Infinite loop due to AsyncHTTPConduit read timeout with exhausted connection pool

[ https://issues.apache.org/jira/browse/CXF-7122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15646690#comment-15646690 ] Freeman Fang edited comment on CXF-7122 at 11/8/16 6:43 AM: Hi W

[jira] [Comment Edited] (CXF-7122) Infinite loop due to AsyncHTTPConduit read timeout with exhausted connection pool

[ https://issues.apache.org/jira/browse/CXF-7122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15646690#comment-15646690 ] Freeman Fang edited comment on CXF-7122 at 11/8/16 6:41 AM: Hi W

[jira] [Commented] (CXF-7122) Infinite loop due to AsyncHTTPConduit read timeout with exhausted connection pool

[ https://issues.apache.org/jira/browse/CXF-7122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15646690#comment-15646690 ] Freeman Fang commented on CXF-7122: --- Hi William, In ahc 4.0.2 code base, the org.apache.h

[jira] [Comment Edited] (CXF-7122) Infinite loop due to AsyncHTTPConduit read timeout with exhausted connection pool

[ https://issues.apache.org/jira/browse/CXF-7122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15646690#comment-15646690 ] Freeman Fang edited comment on CXF-7122 at 11/8/16 6:37 AM: Hi W

[jira] [Comment Edited] (CXF-7122) Infinite loop due to AsyncHTTPConduit read timeout with exhausted connection pool

[ https://issues.apache.org/jira/browse/CXF-7122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15644164#comment-15644164 ] Freeman Fang edited comment on CXF-7122 at 11/7/16 1:24 PM: Hi W

[jira] [Commented] (CXF-7122) Infinite loop due to AsyncHTTPConduit read timeout with exhausted connection pool

[ https://issues.apache.org/jira/browse/CXF-7122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15644164#comment-15644164 ] Freeman Fang commented on CXF-7122: --- Hi William, Your last comment is very interesting.

[jira] [Commented] (CXF-7122) Infinite loop due to AsyncHTTPConduit read timeout with exhausted connection pool

[ https://issues.apache.org/jira/browse/CXF-7122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15643870#comment-15643870 ] Freeman Fang commented on CXF-7122: --- Hi William, Thanks for your patch but I'm still -1 f

[jira] [Commented] (CXF-7122) Infinite loop due to AsyncHTTPConduit read timeout with exhausted connection pool

[ https://issues.apache.org/jira/browse/CXF-7122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15643233#comment-15643233 ] Freeman Fang commented on CXF-7122: --- Hi William, FYI, with your original patch, with the

[jira] [Commented] (CXF-6969) CXF Async HTTP Transport - add supports to configure httpclient with new method

[ https://issues.apache.org/jira/browse/CXF-6969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15642945#comment-15642945 ] Freeman Fang commented on CXF-6969: --- Hi Sergey, Sure, I will take a close look. Cheers F

[jira] [Commented] (CXF-7122) Infinite loop due to AsyncHTTPConduit read timeout with exhausted connection pool

[ https://issues.apache.org/jira/browse/CXF-7122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15635539#comment-15635539 ] Freeman Fang commented on CXF-7122: --- Hi William, To demonstrate your patch doesn't work,

[jira] [Updated] (CXF-7122) Infinite loop due to AsyncHTTPConduit read timeout with exhausted connection pool

[ https://issues.apache.org/jira/browse/CXF-7122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang updated CXF-7122: -- Attachment: AsyncHTTPConduitTest.java > Infinite loop due to AsyncHTTPConduit read timeout with exhausted

[jira] [Resolved] (CXF-7122) Infinite loop due to AsyncHTTPConduit read timeout with exhausted connection pool

[ https://issues.apache.org/jira/browse/CXF-7122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CXF-7122. --- Resolution: Fixed Fix Version/s: 3.1.9 3.2.0 > Infinite loop due to AsyncHTTPC

[jira] [Commented] (CXF-7122) Infinite loop due to AsyncHTTPConduit read timeout with exhausted connection pool

[ https://issues.apache.org/jira/browse/CXF-7122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15635387#comment-15635387 ] Freeman Fang commented on CXF-7122: --- Hi William, Thanks for the patch, however it can't

[jira] [Assigned] (CXF-7122) Infinite loop due to AsyncHTTPConduit read timeout with exhausted connection pool

[ https://issues.apache.org/jira/browse/CXF-7122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned CXF-7122: - Assignee: Freeman Fang > Infinite loop due to AsyncHTTPConduit read timeout with exhausted connecti

[jira] [Comment Edited] (CXF-6910) don't need setSocketTimeout when create ahc RequestConfig

[ https://issues.apache.org/jira/browse/CXF-6910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15615094#comment-15615094 ] Freeman Fang edited comment on CXF-6910 at 10/28/16 10:59 AM: --

[jira] [Commented] (CXF-6910) don't need setSocketTimeout when create ahc RequestConfig

[ https://issues.apache.org/jira/browse/CXF-6910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15615094#comment-15615094 ] Freeman Fang commented on CXF-6910: --- Hi Sebastien, What I mentioned {code} if there's no

[jira] [Resolved] (CXF-7112) AsyncHTTPConduit ignore the ReceiveTimeout when use Async JAXWS api

[ https://issues.apache.org/jira/browse/CXF-7112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CXF-7112. --- Resolution: Fixed Fix Version/s: 3.1.9 3.2.0 > AsyncHTTPConduit ignore the Rec

[jira] [Assigned] (CXF-7112) AsyncHTTPConduit ignore the ReceiveTimeout when use Async JAXWS api

[ https://issues.apache.org/jira/browse/CXF-7112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned CXF-7112: - Assignee: Freeman Fang > AsyncHTTPConduit ignore the ReceiveTimeout when use Async JAXWS api >

[jira] [Created] (CXF-7112) AsyncHTTPConduit ignore the ReceiveTimeout when use Async JAXWS api

Freeman Fang created CXF-7112: - Summary: AsyncHTTPConduit ignore the ReceiveTimeout when use Async JAXWS api Key: CXF-7112 URL: https://issues.apache.org/jira/browse/CXF-7112 Project: CXF Issue

[jira] [Commented] (CXF-7109) ClientCallback may be invoked twice when Async HTTP Transport is used

[ https://issues.apache.org/jira/browse/CXF-7109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15607569#comment-15607569 ] Freeman Fang commented on CXF-7109: --- patch applied on behalf of Tadayoshi Sato with thank

[jira] [Resolved] (CXF-7109) ClientCallback may be invoked twice when Async HTTP Transport is used

[ https://issues.apache.org/jira/browse/CXF-7109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CXF-7109. --- Resolution: Fixed Fix Version/s: 3.1.9 > ClientCallback may be invoked twice when Async HTTP Tran

[jira] [Assigned] (CXF-7109) ClientCallback may be invoked twice when Async HTTP Transport is used

[ https://issues.apache.org/jira/browse/CXF-7109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned CXF-7109: - Assignee: Freeman Fang > ClientCallback may be invoked twice when Async HTTP Transport is used > --

[jira] [Commented] (CXF-7054) CORBADocLitClientTypeTest failed with java9

[ https://issues.apache.org/jira/browse/CXF-7054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15502284#comment-15502284 ] Freeman Fang commented on CXF-7054: --- Hi Grzegorz, Go ahead for the Jacorb test. Somehow w

[jira] [Commented] (CXF-6732) Allow SOAPAction to be overwritten via RequestContext property

[ https://issues.apache.org/jira/browse/CXF-6732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15502206#comment-15502206 ] Freeman Fang commented on CXF-6732: --- Hi David, IMO each invocation request should carry c

[jira] [Resolved] (CXF-7054) CORBADocLitClientTypeTest failed with java9

[ https://issues.apache.org/jira/browse/CXF-7054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CXF-7054. --- Resolution: Fixed Fix Version/s: 3.2.0 commit fix(with Grzegorz Grzybek's help) http://git-wip-us

[jira] [Resolved] (CXF-7053) CorbaTimeoutTest failed with java9

[ https://issues.apache.org/jira/browse/CXF-7053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CXF-7053. --- Resolution: Fixed Fix Version/s: 3.2.0 patch applied on behalf of Grzegorz Grzybek with thanks ht

[jira] [Commented] (CXF-7054) CORBADocLitClientTypeTest failed with java9

[ https://issues.apache.org/jira/browse/CXF-7054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15500688#comment-15500688 ] Freeman Fang commented on CXF-7054: --- Figured out this {code} Caused by: java.lang.NullPoin

[jira] [Resolved] (CXF-7051) RequestResponseTest.testRequestTopicResponseStaticQueue intermittently failed with java9

[ https://issues.apache.org/jira/browse/CXF-7051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CXF-7051. --- Resolution: Fixed Fix Version/s: 3.2.0 commit fix http://git-wip-us.apache.org/repos/asf/cxf/comm

[jira] [Commented] (CXF-7051) RequestResponseTest.testRequestTopicResponseStaticQueue intermittently failed with java9

[ https://issues.apache.org/jira/browse/CXF-7051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15486590#comment-15486590 ] Freeman Fang commented on CXF-7051: --- The AbstractJMSTester.waitForReceiveInMessage isn't c

[jira] [Commented] (CXF-7055) JAXB generation problems with java9

[ https://issues.apache.org/jira/browse/CXF-7055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15486483#comment-15486483 ] Freeman Fang commented on CXF-7055: --- Hi Grzegorz, Mine is {code} java version "9-ea" Jav

[jira] [Resolved] (CXF-7056) use new JVM options with recent java9 kit

[ https://issues.apache.org/jira/browse/CXF-7056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CXF-7056. --- Resolution: Fixed Fix Version/s: 3.2.0 commit fix http://git-wip-us.apache.org/repos/asf/cxf/comm

[jira] [Updated] (CXF-7056) use new JVM options with recent java9 kit

[ https://issues.apache.org/jira/browse/CXF-7056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang updated CXF-7056: -- Description: since the java9 EA 132, the old style jvm options was dropped, only new style is supported.

[jira] [Created] (CXF-7056) use new JVM options with recent java9 kit

Freeman Fang created CXF-7056: - Summary: use new JVM options with recent java9 kit Key: CXF-7056 URL: https://issues.apache.org/jira/browse/CXF-7056 Project: CXF Issue Type: Sub-task

[jira] [Assigned] (CXF-7056) use new JVM options with recent java9 kit

[ https://issues.apache.org/jira/browse/CXF-7056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned CXF-7056: - Assignee: Freeman Fang > use new JVM options with recent java9 kit > --

[jira] [Commented] (CXF-7055) JAXB generation problems with java9

[ https://issues.apache.org/jira/browse/CXF-7055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15485835#comment-15485835 ] Freeman Fang commented on CXF-7055: --- Hi Grzegorz, A quick question, what's your java9 ve

[jira] [Commented] (CXF-7052) PolicyBasedWss4JInOutTest.testSignedEncryptedPartsWithIncompleteCoverage failed with java9

[ https://issues.apache.org/jira/browse/CXF-7052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15483497#comment-15483497 ] Freeman Fang commented on CXF-7052: --- re-enable this test http://git-wip-us.apache.org/repo

[jira] [Resolved] (CXF-7052) PolicyBasedWss4JInOutTest.testSignedEncryptedPartsWithIncompleteCoverage failed with java9

[ https://issues.apache.org/jira/browse/CXF-7052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CXF-7052. --- Resolution: Cannot Reproduce can't see this failure anymore > PolicyBasedWss4JInOutTest.testSignedEncry

[jira] [Resolved] (CXF-7050) CryptoUtilsTest.testBearerTokenJSONCertificate failed with java9

[ https://issues.apache.org/jira/browse/CXF-7050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CXF-7050. --- Resolution: Fixed Fix Version/s: 3.2.0 commit fix http://git-wip-us.apache.org/repos/asf/cxf/comm

[jira] [Commented] (CXF-7054) CORBADocLitClientTypeTest failed with java9

[ https://issues.apache.org/jira/browse/CXF-7054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15483388#comment-15483388 ] Freeman Fang commented on CXF-7054: --- The failure tests are {code} Tests in error: CORBA

[jira] [Commented] (CXF-7053) CorbaTimeoutTest failed with java9

[ https://issues.apache.org/jira/browse/CXF-7053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15483356#comment-15483356 ] Freeman Fang commented on CXF-7053: --- the exception is like {code} Starting Server Tests ru

[jira] [Commented] (CXF-7050) CryptoUtilsTest.testBearerTokenJSONCertificate failed with java9

[ https://issues.apache.org/jira/browse/CXF-7050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15482902#comment-15482902 ] Freeman Fang commented on CXF-7050: --- get error like {code} Running org.apache.cxf.rs.secur

[jira] [Assigned] (CXF-7054) CORBADocLitClientTypeTest failed with java9

[ https://issues.apache.org/jira/browse/CXF-7054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned CXF-7054: - Assignee: Freeman Fang > CORBADocLitClientTypeTest failed with java9 >

[jira] [Created] (CXF-7054) CORBADocLitClientTypeTest failed with java9

Freeman Fang created CXF-7054: - Summary: CORBADocLitClientTypeTest failed with java9 Key: CXF-7054 URL: https://issues.apache.org/jira/browse/CXF-7054 Project: CXF Issue Type: Sub-task

[jira] [Assigned] (CXF-7053) CorbaTimeoutTest failed with java9

[ https://issues.apache.org/jira/browse/CXF-7053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned CXF-7053: - Assignee: Freeman Fang > CorbaTimeoutTest failed with java9 > -- >

[jira] [Created] (CXF-7053) CorbaTimeoutTest failed with java9

Freeman Fang created CXF-7053: - Summary: CorbaTimeoutTest failed with java9 Key: CXF-7053 URL: https://issues.apache.org/jira/browse/CXF-7053 Project: CXF Issue Type: Sub-task Reporte

[jira] [Assigned] (CXF-7052) PolicyBasedWss4JInOutTest.testSignedEncryptedPartsWithIncompleteCoverage failed with java9

[ https://issues.apache.org/jira/browse/CXF-7052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned CXF-7052: - Assignee: Freeman Fang > PolicyBasedWss4JInOutTest.testSignedEncryptedPartsWithIncompleteCoverage

[jira] [Created] (CXF-7052) PolicyBasedWss4JInOutTest.testSignedEncryptedPartsWithIncompleteCoverage failed with java9

Freeman Fang created CXF-7052: - Summary: PolicyBasedWss4JInOutTest.testSignedEncryptedPartsWithIncompleteCoverage failed with java9 Key: CXF-7052 URL: https://issues.apache.org/jira/browse/CXF-7052 Proje

[jira] [Assigned] (CXF-7051) RequestResponseTest.testRequestTopicResponseStaticQueue intermittently failed with java9

[ https://issues.apache.org/jira/browse/CXF-7051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned CXF-7051: - Assignee: Freeman Fang > RequestResponseTest.testRequestTopicResponseStaticQueue intermittently fai

[jira] [Created] (CXF-7051) RequestResponseTest.testRequestTopicResponseStaticQueue intermittently failed with java9

Freeman Fang created CXF-7051: - Summary: RequestResponseTest.testRequestTopicResponseStaticQueue intermittently failed with java9 Key: CXF-7051 URL: https://issues.apache.org/jira/browse/CXF-7051 Project:

[jira] [Assigned] (CXF-7050) CryptoUtilsTest.testBearerTokenJSONCertificate failed with java9

[ https://issues.apache.org/jira/browse/CXF-7050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned CXF-7050: - Assignee: Freeman Fang > CryptoUtilsTest.testBearerTokenJSONCertificate failed with java9 > ---

[jira] [Created] (CXF-7050) CryptoUtilsTest.testBearerTokenJSONCertificate failed with java9

Freeman Fang created CXF-7050: - Summary: CryptoUtilsTest.testBearerTokenJSONCertificate failed with java9 Key: CXF-7050 URL: https://issues.apache.org/jira/browse/CXF-7050 Project: CXF Issue Typ

[jira] [Resolved] (CXF-7045) Update sample description_swagger2_osgi README.txt

[ https://issues.apache.org/jira/browse/CXF-7045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CXF-7045. --- Resolution: Fixed Fix Version/s: 3.1.8 3.2.0 > Update sample description_swagg

<    3   4   5   6   7   8   9   10   11   12   >