Oops typo in 3.0.1 netty is not default.
> From: [email protected] > To: [email protected] > Subject: RE: CXF 3.0.0 Standalone JAX-WS Client does not terminate? > Date: Thu, 21 Aug 2014 18:01:47 +0000 > > Hi Dan, > Thanks for the quick reply. I was able to resolve it by calling > bus.shutdown(true), and will try other methods for cleaning. > Is there any documentation or example on "how to configure for netty > transport". I tested 3.0.1 in which netty is default. > Thanks,Venkat > > Subject: Re: CXF 3.0.0 Standalone JAX-WS Client does not terminate? > > From: [email protected] > > Date: Thu, 21 Aug 2014 11:16:51 -0400 > > To: [email protected] > > > > > > Can you try moving to 3.0.1. I believe the use of Netty by default has > > been fixed. It shouldn’t have been picked up by default. > > > > When done with CXF things, you may need to completely shut down the Bus > > object so the shared resources get cleaned up. The async transports > > generally have a background thread pool and such for handling the async > > responses. BusFactory.getDefaultBus().shutdown(true) should handle that. > > > > You can also try closing the JAX-WS clients. All the clients that CXF > > creates implement the Closeable interface so you can cast them to a > > Closeable and call close. In some cases, this can cleanup things. > > > > Dan > > > > > > > > On Aug 20, 2014, at 10:24 AM, venkatesham nalla <[email protected]> wrote: > > > > > Hi, > > > > > > > > > JAX-WS standalone client does not terminate in Apache CXF > > > 3.0.0. However it terminates when the > > > cxf-rt-transports-http-netty-client-3.0.0.jar file is removed from the lib > > > directory. > > > > > > 1) > > > Does CXF 3.0.0 uses netty client automatically > > > when present in the lib directory? If so, how to terminate the standalone > > > client? Looking at the thread dump it might be caused by > > > nioEventLoopGroup threads from netty. > > > > > > 2) > > > How to > > > configure netty transport if it is not automatically used by CXF? There > > > are no configuration > > > xsds similar to http-jetty.xsd. > > > > > > > > > The client configuration is simple as given below. > > > > > > > > > <beans xmlns="http://www.springframework.org/schema/beans"; > > > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > > > xmlns:cxf="http://cxf.apache.org/core"; > > > xmlns:http="http://cxf.apache.org/transports/http/configuration"; > > > xmlns:httpj="http://cxf.apache.org/transports/http-jetty/configuration"; > > > xmlns:jaxws="http://cxf.apache.org/jaxws"; > > > xmlns:sec="http://cxf.apache.org/configuration/security"; > > > xsi:schemaLocation=" > > > > > > > > > > > > http://cxf.apache.org/core > > > http://cxf.apache.org/schemas/core.xsd > > > > > > > > > > > > > > > http://www.springframework.org/schema/beans > > > http://www.springframework.org/schema/beans/spring-beans.xsd > > > > > > > > > > > > > > > http://cxf.apache.org/jaxws > > > http://cxf.apache.org/schemas/jaxws.xsd > > > > > > > > > > > > http://cxf.apache.org/transports/http/configuration > > > http://cxf.apache.org/schemas/configuration/http-conf.xsd > > > > > > > > > > > > > > > http://cxf.apache.org/transports/http-jetty/configuration > > > http://cxf.apache.org/schemas/configuration/http-jetty.xsd > > > > > > > > > > > > http://cxf.apache.org/configuration/security > > > http://cxf.apache.org/schemas/configuration/security.xsd > > > > > > "> > > > > > > <cxf:bus> > > > > > > <cxf:features> > > > > > > <cxf:logging/> > > > > > > > > > > > > </cxf:features> > > > > > > </cxf:bus> > > > Thnaks,Venkat > > > > > > > -- > > Daniel Kulp > > [email protected] - http://dankulp.com/blog > > Talend Community Coder - http://coders.talend.com > > >
