Initially, I thought your configuration is not picking up your conduit. But I am not sure now what problem you have. You mentions that the same configuration runs on a different environment (I mean, getting the expected timeout exception). And if you are not getting the timeout exception at all, there could be something wrong with the network library. Are the different clients (the one working and the one not working) on the same system?
I didn't ask you which version of CXF you use, but could it be very old? It's been a while since cxf has started to require woodstox's stax unless specifically configured to use something else. In any case, what I could suggest is to turn on the debug log of org.apache.cxf and send one message and see what the log says. regards, aki 2014-05-30 16:13 GMT+02:00 srikanthvaddi <[email protected]>: > hi Yoshida, > > thanks for ur reply, > > the same way i have worked in tomcat+ eclipse it is working , but linux > +was (production development is not working) i am expecting time out > exception , but it is not occuring , can u please reply on this . the thing > is while startup WAs i have not recieved any error > > the below jar's i am using for this module & in my project JSR jar is there > intially i got the error like* Provider > com.bea.xml.stream.XMLOutputFactoryBase not found* after stax.jar including > no error while start up . please let me know if u need any info > > neethi-3.0.1.jar > xmlschema-core-2.0.1 > xercesImpl-2.9.1.jar > geronimo-annotation_1.0.jar > geronimo-jaxws_2.2.jar > geronimo-ws-metadata_2.0.jar > jaxb-api-2.2.3.jar > jaxb-impl-2.2.4-1.jar > wsdl4j-1.6.2.jar > stax.jar > > > > -- > View this message in context: > http://cxf.547215.n5.nabble.com/http-conduit-not-working-tp5744537p5744555.html > Sent from the cxf-user mailing list archive at Nabble.com.
