cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Kulp (JIRA)" <>
Subject [jira] [Commented] (CXF-6689) .close() is never called on org.apache.cxf.transport.http.URLConnectionHTTPConduit
Date Mon, 23 Nov 2015 17:45:11 GMT


Daniel Kulp commented on CXF-6689:

I believe if you call:

when you are done with the proxy or wait long enough for the garbage collector/finalizer to
collect the proxy, the close() method is called.   The close(Message) method is used to close
anything specific for that message/exchange.   For example, cleaning up any input streams,
maybe commit a transaction for JMS, etc....  It can leave connections open for future requests.
   The close() is for the entire proxy for doing things like shutting down connections.

> .close() is never called on org.apache.cxf.transport.http.URLConnectionHTTPConduit
> ----------------------------------------------------------------------------------
>                 Key: CXF-6689
>                 URL:
>             Project: CXF
>          Issue Type: Bug
>          Components: JAX-WS Runtime
>    Affects Versions: 2.7.16
>            Reporter: Marco Rietveld
> If you look at 
> you'll see that only the {{.close(Message)}} method is called on the {{Conduit}} instance.

> Unfortunately, the only {{.close()}} method that the {{org.apache.cxf.transport.http.URLConnectionHTTPConduit}}
has, does not take an argument, which (AFAICT?), means that close is never called on the {{URLConnectionHTTPConduit}}

> This has consequences, among others, that if you do the following, it will succeed: 
> 1. Create a JAX-WS client proxy with correct login info. 
> 2. Create a JAX-WS client proxy with incorrect login info. 
> In some situations, the following (subsequent to the above steps) step will also succeed:

> 3. Do a webservice call with the JAX-WS client proxy created with incorrect login info.

This message was sent by Atlassian JIRA

View raw message