Return-Path: X-Original-To: apmail-cxf-issues-archive@www.apache.org Delivered-To: apmail-cxf-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 81A5A11231 for ; Fri, 29 Aug 2014 16:06:57 +0000 (UTC) Received: (qmail 62856 invoked by uid 500); 29 Aug 2014 16:06:57 -0000 Delivered-To: apmail-cxf-issues-archive@cxf.apache.org Received: (qmail 62814 invoked by uid 500); 29 Aug 2014 16:06:57 -0000 Mailing-List: contact issues-help@cxf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cxf.apache.org Delivered-To: mailing list issues@cxf.apache.org Received: (qmail 62644 invoked by uid 99); 29 Aug 2014 16:06:57 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 29 Aug 2014 16:06:57 +0000 Date: Fri, 29 Aug 2014 16:06:57 +0000 (UTC) From: "Daniel Kulp (JIRA)" To: issues@cxf.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (CXF-5968) Setting use.async.http.conduit property causes IllegalArgumentException MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CXF-5968?page=3Dcom.atlassian.= jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Kulp resolved CXF-5968. ------------------------------ Resolution: Fixed Fix Version/s: 3.0.2 2.7.13 Assignee: Daniel Kulp Fixed to re-allow true/false values. Not that true is an alias for ALWAYS= and false for NEVER so using the Always/Never values should work. > Setting use.async.http.conduit property causes IllegalArgumentException > ----------------------------------------------------------------------- > > Key: CXF-5968 > URL: https://issues.apache.org/jira/browse/CXF-5968 > Project: CXF > Issue Type: Bug > Components: Configuration, Transports > Affects Versions: 3.0.1 > Environment: SunOS 5.10 > Reporter: Przemys=C5=82aw O=C5=82tarzewski > Assignee: Daniel Kulp > Labels: IllegalArgumentException, UseAsyncPolicy, async, cxf= , enum > Fix For: 2.7.13, 3.0.2 > > > After upgrading from CXF 3.0.0 to 3.0.1 we are experiencing an IllegalArg= umentException in every request from a generated client code to the target = WS, probably related to following cxf.xml fragment: > {noformat} > [...] > =09 > =09=09[...] > =09=09 > =09=09=09 > =09=09 > =09=09=09 > =09=09=09 > =09=09 > =09 > [...] > {noformat} > Exception: > {noformat} > java.lang.IllegalArgumentException: No enum const class org.apache.cxf.tr= ansport.http.asyncclient.AsyncHTTPConduitFactory$UseAsyncPolicy.TRUE > at java.lang.Enum.valueOf(Enum.java:196) > at org.apache.cxf.transport.http.asyncclient.AsyncHTTPConduitFact= ory$UseAsyncPolicy.valueOf(AsyncHTTPConduitFactory.java:90) > at org.apache.cxf.transport.http.asyncclient.AsyncHTTPConduit.set= upConnection(AsyncHTTPConduit.java:153) > at org.apache.cxf.transport.http.HTTPConduit.prepare(HTTPConduit.= java:483) > at org.apache.cxf.interceptor.MessageSenderInterceptor.handleMess= age(MessageSenderInterceptor.java:46) > at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseIn= terceptorChain.java:307) > at org.apache.cxf.endpoint.ClientImpl.doInvoke(ClientImpl.java:51= 4) > at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:423) > at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:326) > at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:279) > at org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.jav= a:96) > at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.= java:137) > ... 12 common frames omitted > {noformat} > The value 'true' for 'use.async.http.conduit' property seems to be conver= ted to uppercase, then passed directly to 'valueOf' method of Enum. > According to online documentation, such configuration should result in us= ing AsyncHTTPConduitFactory$UseAsyncPolicy.ALWAYS by CXF. > It works as expected in 3.0.0, having the effect of using async http clie= nt for every request. > It seems that using the following configuration is a valid workaround: > {noformat} > [...] > =09 > =09=09[...] > =09=09 > =09=09=09 > =09=09 > =09=09=09=09 > > =09=09 > =09 > [...] > {noformat} > The online documentation states that the above configuration is similar (= not identical) to using 'use.async.http.conduit' property. What are the dif= ferences (if any)? Is it a valid workaround? > Best Regards, > Przemys=C5=82aw O=C5=82tarzewski -- This message was sent by Atlassian JIRA (v6.2#6252)