No yet to test using the lastest cxf version. And it is not easy to reproduce this problem even using the lastest version, because it is not appeared everytime.
If you current have not fixed it, is there any temp solution to avoid this issue? On Fri, Feb 22, 2013 at 4:23 PM, Willem jiang <[email protected]>wrote: > IBM JDK will perform the GC proactively. I think we should be able to fix > this issue as the mail thread tells. > Did you have chance to try to use the latest CXF version ? > > > -- > Willem Jiang > > Red Hat, Inc. > FuseSource is now part of Red Hat > Web: http://www.fusesource.com | http://www.redhat.com > Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/) > (English) > http://jnn.iteye.com (http://jnn.javaeye.com/) (Chinese) > Twitter: willemjiang > Weibo: 姜宁willem > > > > > > On Friday, February 22, 2013 at 11:42 AM, Min Yang wrote: > > > Hi , > > > > Sometimes we met the following exception in our application, which just > > only call the getConduit method like this. I noticed that someone also > > mentioned this on > > > http://mail-archives.apache.org/mod_mbox/cxf-dev/201211.mbox/%[email protected]%3E > > . > > > > I just want to know if this is a defect of apache cxf, and do you have > plan > > to fix it? > > > > Client client = ClientProxy.getClient(port); > > HTTPConduit http = (HTTPConduit) client.getConduit(); > > ... > > > > > Stack Dump = java.lang.NullPointerException > > > at > > > > > > > org.apache.cxf.endpoint.AbstractConduitSelector.getSelectedConduit(AbstractConduitSelector.java:90) > > > at > > > > > > > org.apache.cxf.endpoint.UpfrontConduitSelector.selectConduit(UpfrontConduitSelector.java:77) > > > at org.apache.cxf.endpoint.ClientImpl.getConduit(ClientImpl.java:847) > > > at > > > > > > > com.ibm.jaxws.properties.servlet.TestServlet.getProperties(TestServlet.java:74) > > > at > > > > > > com.ibm.jaxws.properties.servlet.TestServlet.doGet(TestServlet.java:66) > > > at javax.servlet.http.HttpServlet.service(HttpServlet.java:575) > > > at javax.servlet.http.HttpServlet.service(HttpServlet.java:668) > > > at > > > > > > > com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1237) > > > at > > > > > > > com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:760) > > > at > > > > > > > com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:443) > > > at > > > > > > > com.ibm.ws.webcontainer.filter.WebAppFilterManager.invokeFilters(WebAppFilterManager.java:1033) > > > at > > > > > > com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:4507) > > > at > > > > > > > com.ibm.ws.webcontainer.osgi.DynamicVirtualHost$2.handleRequest(DynamicVirtualHost.java:282) > > > at > > > > > > com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:954) > > > at > > > > > > > com.ibm.ws.webcontainer.osgi.DynamicVirtualHost$2.run(DynamicVirtualHost.java:252) > > > at > > > > > > > com.ibm.ws.http.dispatcher.internal.channel.HttpDispatcherLink$TaskWrapper.run(HttpDispatcherLink.java:535) > > > at com.ibm.ws.threading.internal.Worker.executeWork(Worker.java:439) > > > at com.ibm.ws.threading.internal.Worker.run(Worker.java:421) > > > at java.lang.Thread.run(Thread.java:770) > > > > > > ] > > at > > componenttest.custom.junit.runner.FATRunner.blowup(FATRunner.java:151) > > at > > componenttest.custom.junit.runner.FATRunner.access$300(FATRunner.java:48) > > at > > > componenttest.custom.junit.runner.FATRunner$1.evaluate(FATRunner.java:140) > > at > > > componenttest.custom.junit.runner.FATRunner$2.evaluate(FATRunner.java:168) > > > >
