Issues with Attachments: week of 2015-02-23
CXF - Monday, February 23, 2015 6 Issues with Attachments (sorted oldest to newest) [CXF-6085] JWE JSON Serialization - Created: 2014-11-05 - Updated: 2015-02-16 - Type: New Feature - Fix Versions: [] - Reporter: Daniel Torkian - Assigned: Sergey Beryozkin - Attachments: [initJSONJWE.txt] - https://issues.apache.org/jira/browse/CXF-6085 [CXF-6197] Although the Parts classes are same PhaseInterceptorChain not able to recognize it that they are bother same object of same class type - Created: 2015-01-16 - Updated: 2015-02-11 - Type: Bug - Fix Versions: [NeedMoreInfo] - Reporter: Sanjay Gautam - Assigned: Unassigned - Attachments: [object-Item-Inspect.png, typeClass-debug-inspect.png] - https://issues.apache.org/jira/browse/CXF-6197 [CXF-6221] CDI integration extension does not detect annotations on Karaf - Created: 2015-01-24 - Updated: 2015-02-22 - Type: Bug - Fix Versions: [] - Reporter: Krystian Panek - Assigned: Andriy Redko - Attachments: [hydra.tar.gz, screenshot-1.png] - https://issues.apache.org/jira/browse/CXF-6221 [CXF-6239] Out of memory when using Async connections in Apache CXF - Created: 2015-02-04 - Updated: 2015-02-04 - Type: Bug - Fix Versions: [] - Reporter: Atul Bisaria - Assigned: Unassigned - Attachments: [SnipImage1.JPG, SnipImage2.JPG] - https://issues.apache.org/jira/browse/CXF-6239 [CXF-6254] Buffer Problem using CXF with NTLM Auth and SSL - Created: 2015-02-11 - Updated: 2015-02-12 - Type: Bug - Fix Versions: [] - Reporter: Andreas Reinhardt - Assigned: Unassigned - Attachments: [log.txt] - https://issues.apache.org/jira/browse/CXF-6254 [CXF-6261] Upgrade CXF trunk to use OpenSAML 3.0.x - Created: 2015-02-16 - Updated: 2015-02-18 - Type: Improvement - Fix Versions: [3.1.0] - Reporter: Colm O hEigeartaigh - Assigned: Colm O hEigeartaigh - Attachments: [cxf.opensaml.port.2, cxf.opensaml.port.3] - https://issues.apache.org/jira/browse/CXF-6261
[jira] [Created] (FEDIZ-97) Plugin configuration property naming conflict with WebSphere 8.5
Jan Bernhardt created FEDIZ-97:
--
Summary: Plugin configuration property naming conflict with
WebSphere 8.5
Key: FEDIZ-97
URL: https://issues.apache.org/jira/browse/FEDIZ-97
Project: CXF-Fediz
Issue Type: Bug
Components: Plugin
Affects Versions: 1.1.2
Reporter: Jan Bernhardt
Assignee: Jan Bernhardt
Fix For: 1.2.0
The class {{org.apache.cxf.fediz.was.tai.FedizInterceptor}} requires the
{{config.file.location}} property to point to the fediz config file. However
this property is not available within the FedizIinterceptor because is applies
to a naming pattern which is filtered by WAS 8.5 and thus causing a
{{NullpointerException}}.
To solve this issue, the configuration property must to be renamed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (CXF-6265) org.apache.cxf.xjc-utils:cxf-xjc-runtime:3.0.4 artifact missing on maven central
Franz van Betteraey created CXF-6265: Summary: org.apache.cxf.xjc-utils:cxf-xjc-runtime:3.0.4 artifact missing on maven central Key: CXF-6265 URL: https://issues.apache.org/jira/browse/CXF-6265 Project: CXF Issue Type: Bug Components: Build system Affects Versions: 3.0.4 Reporter: Franz van Betteraey The artifact org.apache.cxf.xjc-utils:cxf-xjc-runtime is missing in version 3.0.4 on maven central. Is it meant to be obsolete/replaced? I can not find any information in the release notes so it suppose it should be available in the latest version. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FEDIZ-96) Nullpointer exception if logout is called before login
[ https://issues.apache.org/jira/browse/FEDIZ-96?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1484#comment-1484 ] Colm O hEigeartaigh commented on FEDIZ-96: -- Does the NPE occur in the RP or IdP? I just tested using trunk and logging out twice via the RP seemed to work ok. How can I reproduce the error? Colm. > Nullpointer exception if logout is called before login > -- > > Key: FEDIZ-96 > URL: https://issues.apache.org/jira/browse/FEDIZ-96 > Project: CXF-Fediz > Issue Type: Bug > Components: IDP >Affects Versions: 1.1.2 >Reporter: Jan Bernhardt >Priority: Minor > Fix For: 1.2.0 > > > If you invoke the logout URL twice or if your session has timed out, you will > get a NullPointerException instead of a logout page. > According to the WS-Federation standard, a logout request should be > idempotent, thus it should be possible to invoke logout on a non existing > session without causing an exception. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CXF-6265) org.apache.cxf.xjc-utils:cxf-xjc-runtime:3.0.4 artifact missing on maven central
[ https://issues.apache.org/jira/browse/CXF-6265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Kulp resolved CXF-6265. -- Resolution: Not a Problem Fix Version/s: Invalid Assignee: Daniel Kulp The XJC subproject has it's own lifecycle and build and JIRA and release schedule and everything. It's latest release is 3.0.2. > org.apache.cxf.xjc-utils:cxf-xjc-runtime:3.0.4 artifact missing on maven > central > > > Key: CXF-6265 > URL: https://issues.apache.org/jira/browse/CXF-6265 > Project: CXF > Issue Type: Bug > Components: Build system >Affects Versions: 3.0.4 >Reporter: Franz van Betteraey >Assignee: Daniel Kulp > Labels: artifact > Fix For: Invalid > > > The artifact org.apache.cxf.xjc-utils:cxf-xjc-runtime is missing in version > 3.0.4 on maven central. Is it meant to be obsolete/replaced? I can not find > any information in the release notes so it suppose it should be available in > the latest version. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CXF-6265) org.apache.cxf.xjc-utils:cxf-xjc-runtime:3.0.4 artifact missing on maven central
[ https://issues.apache.org/jira/browse/CXF-6265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14333424#comment-14333424 ] Franz van Betteraey commented on CXF-6265: -- Thanks Daniel. As the version was constantly in sync with the CXF project (until 3.0.3) I thought they share the same version number. > org.apache.cxf.xjc-utils:cxf-xjc-runtime:3.0.4 artifact missing on maven > central > > > Key: CXF-6265 > URL: https://issues.apache.org/jira/browse/CXF-6265 > Project: CXF > Issue Type: Bug > Components: Build system >Affects Versions: 3.0.4 >Reporter: Franz van Betteraey >Assignee: Daniel Kulp > Labels: artifact > Fix For: Invalid > > > The artifact org.apache.cxf.xjc-utils:cxf-xjc-runtime is missing in version > 3.0.4 on maven central. Is it meant to be obsolete/replaced? I can not find > any information in the release notes so it suppose it should be available in > the latest version. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CXF-6266) Error creating bean with name 'org.apache.cxf.wsdl.WSDLManager' defined in class path resource [META-INF/cxf/cxf.xml]: Instantiation of bean failed
Muhammed Abedur Rahman created CXF-6266: --- Summary: Error creating bean with name 'org.apache.cxf.wsdl.WSDLManager' defined in class path resource [META-INF/cxf/cxf.xml]: Instantiation of bean failed Key: CXF-6266 URL: https://issues.apache.org/jira/browse/CXF-6266 Project: CXF Issue Type: Task Reporter: Muhammed Abedur Rahman I am working on upgrading CXF framework on a Maven Webservice. It worked successfully on CXF version 2.2.6; but I am getting following error when I am trying to upgrade CXF version to 3.0.2; I went through almost all topics related to this in web, but could not find a way out. My implementation is: beans.xml: http://www.springframework.org/schema/beans"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xmlns:jaxrs="http://cxf.apache.org/jaxrs"; xmlns:jaxws="http://cxf.apache.org/jaxws"; xmlns:aop="http://www.springframework.org/schema/aop"; xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans.xsd http://www.springframework.org/schema/aop http://www.springframework.org/schema/aop/spring-aop.xsd http://cxf.apache.org/jaxrs http://cxf.apache.org/schemas/jaxrs.xsd http://cxf.apache.org/jaxws http://cxf.apache.org/schemas/jaxws.xsd";> pom.xml: http://maven.apache.org/POM/4.0.0"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd";> 4.0.0 com.idc.idms cmswebservice 1.0-SNAPSHOT war ustwebservice javax javaee-web-api 6.0 provided javax javaee-api 7.0 provided com.thoughtworks.xstream xstream 1.3.1 log4j log4j 1.2.17 commons-dbutils commons-dbutils 1.3 org.apache.cxf cxf-rt-frontend-jaxrs 3.0.2 org.apache.cxf cxf-rt-frontend-jaxws 3.0.2 org.apache.cxf cxf-rt-transports-http 3.0.2 org.apache.cxf cxf-rt-wsdl 3.0.2 org.apache.cxf cxf-bundle 2.7.6 org.springframework spring-aop 3.2.6.RELEASE org.springframework spring-beans 3.2.6.RELEASE org.springframework spring-context 3.2.6.RELEASE org.springframework spring-core 3.2.6.RELEASE WSUst org.apache.tomcat.maven tomcat7-maven-plugin 2.2 http://localhost:8080/ web.xml: http://java.sun.com/dtd/web-app_2_3.dtd";> contextConfigLocation WEB-INF/beans.xml org.springframework.web.context.ContextLoaderListener CXFServlet CXF Servlet org.apache.cxf.transport.servlet.CXFServlet 1 CXFServlet /* Ust DB Connection jdbc/DbUst javax.sql.DataSource Error Stack: SEVERE: Exception sending context initialized event to listener instance of class org.springframework.web.context.ContextLoaderListener org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.apache.cxf.wsdl.WSDLManager' defined in class path resource [META-INF/cxf/cxf.xml]: Instantiation of bean failed; nested exception is org.springframework.beans.BeanInstantiationException: Could not instantiate bean class [org.apache.cxf.wsdl11.WSDLManagerImpl]: Constructor threw exception; nested exception is java.lang.NoSuchFieldError: REFLECTION at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean(AbstractAutowireCapableBeanFactory.java:883) at org.springframework.beans.factory.support.AbstractAutowire
[jira] [Updated] (CXF-6266) Error creating bean with name 'org.apache.cxf.wsdl.WSDLManager' defined in class path resource [META-INF/cxf/cxf.xml]: Instantiation of bean failed
[ https://issues.apache.org/jira/browse/CXF-6266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Muhammed Abedur Rahman updated CXF-6266: Description: I am working on upgrading CXF framework on a Maven Webservice. It worked successfully on CXF version 2.2.6; but I am getting following error when I am trying to upgrade CXF version to 3.0.2; JDK 1.7; Apache Tomcat - 7.0.39; NetBeans IDE 7.3; I went through almost all topics related to this in web, but could not find a way out. My implementation is: beans.xml: http://www.springframework.org/schema/beans"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xmlns:jaxrs="http://cxf.apache.org/jaxrs"; xmlns:jaxws="http://cxf.apache.org/jaxws"; xmlns:aop="http://www.springframework.org/schema/aop"; xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans.xsd http://www.springframework.org/schema/aop http://www.springframework.org/schema/aop/spring-aop.xsd http://cxf.apache.org/jaxrs http://cxf.apache.org/schemas/jaxrs.xsd http://cxf.apache.org/jaxws http://cxf.apache.org/schemas/jaxws.xsd";> pom.xml: http://maven.apache.org/POM/4.0.0"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd";> 4.0.0 com.idc.idms cmswebservice 1.0-SNAPSHOT war ustwebservice javax javaee-web-api 6.0 provided javax javaee-api 7.0 provided com.thoughtworks.xstream xstream 1.3.1 log4j log4j 1.2.17 commons-dbutils commons-dbutils 1.3 org.apache.cxf cxf-rt-frontend-jaxrs 3.0.2 org.apache.cxf cxf-rt-frontend-jaxws 3.0.2 org.apache.cxf cxf-rt-transports-http 3.0.2 org.apache.cxf cxf-rt-wsdl 3.0.2 org.apache.cxf cxf-bundle 2.7.6 org.springframework spring-aop 3.2.6.RELEASE org.springframework spring-beans 3.2.6.RELEASE org.springframework spring-context 3.2.6.RELEASE org.springframework spring-core 3.2.6.RELEASE WSUst org.apache.tomcat.maven tomcat7-maven-plugin 2.2 http://localhost:8080/ web.xml: http://java.sun.com/dtd/web-app_2_3.dtd";> contextConfigLocation WEB-INF/beans.xml org.springframework.web.context.ContextLoaderListener CXFServlet CXF Servlet org.apache.cxf.transport.servlet.CXFServlet 1 CXFServlet /* Ust DB Connection jdbc/DbUst javax.sql.DataSource Error Stack: SEVERE: Exception sending context initialized event to listener instance of class org.springframework.web.context.ContextLoaderListener org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.apache.cxf.wsdl.WSDLManager' defined in class path resource [META-INF/cxf/cxf.xml]: Instantiation of bean failed; nested exception is org.springframework.beans.BeanInstantiationException: Could not instantiate bean class [org.apache.cxf.wsdl11.WSDLManagerImpl]: Constructor threw exception; nested exception is java.lang.NoSuchFieldError: REFLECTION at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean(AbstractAutowireCapableBeanFactory.java:883) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:839) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean
[jira] [Commented] (CXF-6254) Buffer Problem using CXF with NTLM Auth and SSL
[
https://issues.apache.org/jira/browse/CXF-6254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14333739#comment-14333739
]
Andreas Reinhardt commented on CXF-6254:
Well I've just tried the very same code using CXF 3.0.3 and it worked like a
charm...
we are using maven so we just changed the version property... since 3.0.3
should be backward compatible I guess it's not a big deal anymore...
> Buffer Problem using CXF with NTLM Auth and SSL
> ---
>
> Key: CXF-6254
> URL: https://issues.apache.org/jira/browse/CXF-6254
> Project: CXF
> Issue Type: Bug
>Affects Versions: 2.7.14
>Reporter: Andreas Reinhardt
>Priority: Minor
> Attachments: log.txt
>
>
> I'm trying to connect to a sharepoint WSDL using a generated CXF client.
> While I've had my fun struggling with NTLM authentication (I wasn't using the
> async-client before!) I'm confronted with a new problem.
> I want to upload a binary file using the copy.wsdl from sharepoint which is
> working fine with files approximately smaller than 16kbyte (using SSL &
> NTLM)...
> Using larger files with about ~500kbyte cxf blocks at
> HttpConduit.handleRetrasmits() (first line at getHttpResponse()), coming from
> AsyncHttpConduit.updateCookiesBeforeRetransmit().
> I tried increasing the buffers to an insanely amount like
> {code}
> Bus bus = BusFactory.getDefaultBus();
> bus.setProperty("bus.io.CachedOutputStream.Threshold", String.valueOf(1024 *
> 1024 * 128));
> conduit.getClient().setChunkLength(1024 * 1024 * 128);
> {code}
> altough chunking is disabled - the buffer size comes from that configuration
> (AsyncHttpConduit line 266):
> {code}
> int bufSize = csPolicy.getChunkLength() > 0 ? csPolicy.getChunkLength() :
> 16320;
> inbuf = new SharedInputBuffer(bufSize, allocator);
> outbuf = new SharedOutputBuffer(bufSize, allocator);
> {code}
> but after that I got http code 400 (invalid request) from the sharepoint
> server if the file was larger than those pesky ~16kbyte...
> using the highest loglevel I noticed that in the 1st retransmission the
> buffer is now always sending the same first ~16kbyte to the sslcontext...
> That's all happening in CxfHttpAsyncRequestProducer.produceContent() and as
> far as I can tell it's happening because the buffer is always resettet in
> line 82 at buffer.rewind().
> {code}
> public void produceContent(final ContentEncoder enc, final IOControl ioc)
> throws IOException {
> if (content != null) {
> if (buffer == null) {
> if (content.getTempFile() == null) {
> buffer = ByteBuffer.wrap(content.getBytes());
> } else {
> fis = content.getInputStream();
> chan = (fis instanceof FileInputStream)
> ? ((FileInputStream)fis).getChannel() :
> Channels.newChannel(fis);
> buffer = ByteBuffer.allocate(8 * 1024);
> }
> }
> int i = -1;
> buffer.rewind();
> if (buffer.hasRemaining() && chan != null) {
> i = chan.read(buffer);
> buffer.flip();
> }
> enc.write(buffer);
> if (!buffer.hasRemaining() && i == -1) {
> enc.complete();
> }
> } else {
> buf.produceContent(enc, ioc);
> }
> }
> {code}
> So I guess something is either terribly wrong at my setup or there might be a
> bug here...
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CXF-6266) Error creating bean with name 'org.apache.cxf.wsdl.WSDLManager' defined in class path resource [META-INF/cxf/cxf.xml]: Instantiation of bean failed
[
https://issues.apache.org/jira/browse/CXF-6266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14333843#comment-14333843
]
Daniel Kulp commented on CXF-6266:
--
Why do you have version 2.7.6 of the cxf-bundle in there? That could cause
this. Remove that.
Also, remove all the
{code:xml}
{code}
lines as they aren't needed.
> Error creating bean with name 'org.apache.cxf.wsdl.WSDLManager' defined in
> class path resource [META-INF/cxf/cxf.xml]: Instantiation of bean failed
> ---
>
> Key: CXF-6266
> URL: https://issues.apache.org/jira/browse/CXF-6266
> Project: CXF
> Issue Type: Task
>Reporter: Muhammed Abedur Rahman
>
> I am working on upgrading CXF framework on a Maven Webservice. It worked
> successfully on CXF version 2.2.6; but I am getting following error when I am
> trying to upgrade CXF version to 3.0.2;
> JDK 1.7;
> Apache Tomcat - 7.0.39;
> NetBeans IDE 7.3;
> I went through almost all topics related to this in web, but could not find a
> way out.
> My implementation is:
> beans.xml:
>
> http://www.springframework.org/schema/beans";
>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>xmlns:jaxrs="http://cxf.apache.org/jaxrs";
>xmlns:jaxws="http://cxf.apache.org/jaxws";
>xmlns:aop="http://www.springframework.org/schema/aop";
>xsi:schemaLocation="http://www.springframework.org/schema/beans
> http://www.springframework.org/schema/beans/spring-beans.xsd
>http://www.springframework.org/schema/aop
> http://www.springframework.org/schema/aop/spring-aop.xsd
>http://cxf.apache.org/jaxrs http://cxf.apache.org/schemas/jaxrs.xsd
>http://cxf.apache.org/jaxws http://cxf.apache.org/schemas/jaxws.xsd";>
>
> />
>
>
>
>
>
>
>
>
>
>
>
>
>
> class="org.apache.cxf.jaxrs.provider.JSONProvider">
>
>
>
> pom.xml:
>
> http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/xsd/maven-4.0.0.xsd";>
> 4.0.0
> com.idc.idms
> cmswebservice
> 1.0-SNAPSHOT
> war
> ustwebservice
>
>
> javax
> javaee-web-api
> 6.0
> provided
>
>
> javax
> javaee-api
> 7.0
> provided
>
>
> com.thoughtworks.xstream
> xstream
> 1.3.1
>
>
> log4j
> log4j
> 1.2.17
>
>
> commons-dbutils
> commons-dbutils
> 1.3
>
>
> org.apache.cxf
> cxf-rt-frontend-jaxrs
> 3.0.2
>
>
> org.apache.cxf
> cxf-rt-frontend-jaxws
> 3.0.2
>
>
> org.apache.cxf
> cxf-rt-transports-http
> 3.0.2
>
>
> org.apache.cxf
> cxf-rt-wsdl
> 3.0.2
>
>
> org.apache.cxf
> cxf-bundle
> 2.7.6
>
>
> org.springframework
> spring-aop
> 3.2.6.RELEASE
>
>
> org.springframework
> spring-beans
> 3.2.6.RELEASE
>
>
> org.springframework
> spring-context
> 3.2.6.RELEASE
>
>
> org.springframework
> spring-core
> 3.2.6.RELEASE
>
>
>
> WSUst
>
>
> org.apache.tomcat.maven
> tomcat7-maven-plugin
> 2.2
>
> http://localhost:8080/
>
>
>
>
>
> web.xml:
>
> PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN"
> "http://java.sun.com/dtd/web-app_2_3.dtd";>
>
>
>
>
> contextConfigLocation
> WEB-INF/beans.xml
>
>
>
> org.springframework.web.context.ContextLoaderListener
>
>
>
> CXFServlet
> CXF Servlet
>
> org.apache.cxf.transport.servlet.CXFServlet
>
> 1
>
>
> CXFServlet
> /*
>
>
>
> Ust DB Connection
>
>
[jira] [Commented] (CXF-5417) Support optional JAX-RS 2.0 ConnectionCallback
[ https://issues.apache.org/jira/browse/CXF-5417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14333848#comment-14333848 ] Graham Leggett commented on CXF-5417: - Is there any chance of backporting this to a v2.x version? Currently am in great need of this in production, and waiting for v3.0.0 won't do alas :( > Support optional JAX-RS 2.0 ConnectionCallback > -- > > Key: CXF-5417 > URL: https://issues.apache.org/jira/browse/CXF-5417 > Project: CXF > Issue Type: Improvement > Components: JAX-RS, Transports >Reporter: Sergey Beryozkin >Assignee: Andriy Redko >Priority: Minor > Fix For: 3.0.0-milestone2 > > Attachments: patch-connection-callback-tests.txt, > patch-connection-callback.txt > > > https://jax-rs-spec.java.net/nonav/2.0/apidocs/javax/ws/rs/container/ConnectionCallback.html > lets JAX-RS 2.0 applications receive the notifications when a given client > has disconnected. > We can probably build something on top of the Jetty-specific connector and > also enhance CXF Continuation API. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Issue Comment Deleted] (CXF-5417) Support optional JAX-RS 2.0 ConnectionCallback
[ https://issues.apache.org/jira/browse/CXF-5417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Leggett updated CXF-5417: Comment: was deleted (was: Is there any chance of backporting this to a v2.x version? Currently am in great need of this in production, and waiting for v3.0.0 won't do alas :( ) > Support optional JAX-RS 2.0 ConnectionCallback > -- > > Key: CXF-5417 > URL: https://issues.apache.org/jira/browse/CXF-5417 > Project: CXF > Issue Type: Improvement > Components: JAX-RS, Transports >Reporter: Sergey Beryozkin >Assignee: Andriy Redko >Priority: Minor > Fix For: 3.0.0-milestone2 > > Attachments: patch-connection-callback-tests.txt, > patch-connection-callback.txt > > > https://jax-rs-spec.java.net/nonav/2.0/apidocs/javax/ws/rs/container/ConnectionCallback.html > lets JAX-RS 2.0 applications receive the notifications when a given client > has disconnected. > We can probably build something on top of the Jetty-specific connector and > also enhance CXF Continuation API. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CXF-5144) JAX-RS Client Proxy-based API connection leak
[ https://issues.apache.org/jira/browse/CXF-5144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14334426#comment-14334426 ] Sailendranath Kasavajjhula commented on CXF-5144: - I migrated my application from CXF 2.7.7 to CXF 3.0.4. I have set the Bus property "response.stream.auto.close" to "true". Then, I started getting the below error. The reason being the "entity" is becoming "null", as part of "ResponseImpl.autoClose()" method. I don't get the below exception, if the bus property "response.stream.auto.close" is set to "false". However, if the bus property "response.stream.auto.close" is set to "false", the connection may not be reusable as the input stream is not closed. Could you please suggest, how to proceed. = javax.ws.rs.ProcessingException: java.lang.IllegalStateException: Entity is not available at org.apache.cxf.jaxrs.client.WebClient.handleResponse(WebClient.java:1195) at org.apache.cxf.jaxrs.client.WebClient.doResponse(WebClient.java:1159) at org.apache.cxf.jaxrs.client.WebClient.doChainedInvocation(WebClient.java:1095) at org.apache.cxf.jaxrs.client.WebClient.doInvoke(WebClient.java:893) at org.apache.cxf.jaxrs.client.WebClient.doInvoke(WebClient.java:864) at org.apache.cxf.jaxrs.client.WebClient.invoke(WebClient.java:427) at org.apache.cxf.jaxrs.client.WebClient.get(WebClient.java:610) at com.walmart.platform.soa.common.providers.SOAJSONJAXBProviderTest.getBookTest(SOAJSONJAXBProviderTest.java:44) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:84) at org.testng.internal.Invoker.invokeMethod(Invoker.java:714) at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:901) at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1231) at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127) at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111) at org.testng.TestRunner.privateRun(TestRunner.java:767) at org.testng.TestRunner.run(TestRunner.java:617) at org.testng.SuiteRunner.runTest(SuiteRunner.java:334) at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:329) at org.testng.SuiteRunner.privateRun(SuiteRunner.java:291) at org.testng.SuiteRunner.run(SuiteRunner.java:240) at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52) at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86) at org.testng.TestNG.runSuitesSequentially(TestNG.java:1224) at org.testng.TestNG.runSuitesLocally(TestNG.java:1149) at org.testng.TestNG.run(TestNG.java:1057) at org.testng.remote.RemoteTestNG.run(RemoteTestNG.java:111) at org.testng.remote.RemoteTestNG.initAndRun(RemoteTestNG.java:204) at org.testng.remote.RemoteTestNG.main(RemoteTestNG.java:175) Caused by: java.lang.IllegalStateException: Entity is not available at org.apache.cxf.jaxrs.impl.ResponseImpl.checkEntityIsClosed(ResponseImpl.java:475) at org.apache.cxf.jaxrs.impl.ResponseImpl.getActualEntity(ResponseImpl.java:137) at org.apache.cxf.jaxrs.impl.ResponseImpl.getEntity(ResponseImpl.java:142) at org.apache.cxf.jaxrs.utils.JAXRSUtils.fromResponse(JAXRSUtils.java:1716) at org.apache.cxf.jaxrs.client.WebClient.handleResponse(WebClient.java:1185) ... 31 more > JAX-RS Client Proxy-based API connection leak > - > > Key: CXF-5144 > URL: https://issues.apache.org/jira/browse/CXF-5144 > Project: CXF > Issue Type: Bug > Components: JAX-RS >Reporter: James Wu >Assignee: Sergey Beryozkin > Fix For: 2.6.10, 2.7.7, 3.0.0-milestone1 > > > JAX-RS Client Proxy-based API could not reuse the TCP connection, even though > with keep-alive. The reason is the InputStream did not be closed when the > response body had been handled in ClientProxyImpl.handleResponse(), so do > Webclient.handleResponse(). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (CXF-5144) JAX-RS Client Proxy-based API connection leak
[ https://issues.apache.org/jira/browse/CXF-5144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14334426#comment-14334426 ] Sailendranath Kasavajjhula edited comment on CXF-5144 at 2/24/15 5:30 AM: -- I migrated my application from CXF 2.7.7 to CXF 3.0.4. I have set the Bus property "response.stream.auto.close" to "true". Then, I started getting the below error. The reason being the "entity" is becoming "null", as part of "ResponseImpl.autoClose()" method. I don't get the below exception, if the bus property "response.stream.auto.close" is set to "false". However, if the bus property "response.stream.auto.close" is set to "false", the connection may not be reusable as the input stream is not closed. Could you please suggest, how to proceed. = javax.ws.rs.ProcessingException: java.lang.IllegalStateException: Entity is not available at org.apache.cxf.jaxrs.client.WebClient.handleResponse(WebClient.java:1195) at org.apache.cxf.jaxrs.client.WebClient.doResponse(WebClient.java:1159) at org.apache.cxf.jaxrs.client.WebClient.doChainedInvocation(WebClient.java:1095) at org.apache.cxf.jaxrs.client.WebClient.doInvoke(WebClient.java:893) at org.apache.cxf.jaxrs.client.WebClient.doInvoke(WebClient.java:864) at org.apache.cxf.jaxrs.client.WebClient.invoke(WebClient.java:427) at org.apache.cxf.jaxrs.client.WebClient.get(WebClient.java:610) Caused by: java.lang.IllegalStateException: Entity is not available at org.apache.cxf.jaxrs.impl.ResponseImpl.checkEntityIsClosed(ResponseImpl.java:475) at org.apache.cxf.jaxrs.impl.ResponseImpl.getActualEntity(ResponseImpl.java:137) at org.apache.cxf.jaxrs.impl.ResponseImpl.getEntity(ResponseImpl.java:142) at org.apache.cxf.jaxrs.utils.JAXRSUtils.fromResponse(JAXRSUtils.java:1716) at org.apache.cxf.jaxrs.client.WebClient.handleResponse(WebClient.java:1185) ... 31 more was (Author: ksnath): I migrated my application from CXF 2.7.7 to CXF 3.0.4. I have set the Bus property "response.stream.auto.close" to "true". Then, I started getting the below error. The reason being the "entity" is becoming "null", as part of "ResponseImpl.autoClose()" method. I don't get the below exception, if the bus property "response.stream.auto.close" is set to "false". However, if the bus property "response.stream.auto.close" is set to "false", the connection may not be reusable as the input stream is not closed. Could you please suggest, how to proceed. = javax.ws.rs.ProcessingException: java.lang.IllegalStateException: Entity is not available at org.apache.cxf.jaxrs.client.WebClient.handleResponse(WebClient.java:1195) at org.apache.cxf.jaxrs.client.WebClient.doResponse(WebClient.java:1159) at org.apache.cxf.jaxrs.client.WebClient.doChainedInvocation(WebClient.java:1095) at org.apache.cxf.jaxrs.client.WebClient.doInvoke(WebClient.java:893) at org.apache.cxf.jaxrs.client.WebClient.doInvoke(WebClient.java:864) at org.apache.cxf.jaxrs.client.WebClient.invoke(WebClient.java:427) at org.apache.cxf.jaxrs.client.WebClient.get(WebClient.java:610) at com.walmart.platform.soa.common.providers.SOAJSONJAXBProviderTest.getBookTest(SOAJSONJAXBProviderTest.java:44) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:84) at org.testng.internal.Invoker.invokeMethod(Invoker.java:714) at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:901) at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1231) at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127) at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111) at org.testng.TestRunner.privateRun(TestRunner.java:767) at org.testng.TestRunner.run(TestRunner.java:617) at org.testng.SuiteRunner.runTest(SuiteRunner.java:334) at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:329) at org.testng.SuiteRunner.privateRun(SuiteRunner.java:291) at org.testng.SuiteRunner.run(SuiteRunner.java:240) at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52) at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86) at org.testng.TestNG.runSuitesSequentially(TestNG.java:12
