Hi Nasseam, I agree, I am also guessing that you are trying to run some remotely hosted secured sevice. I have seen It takes some time when we run interop samples in CXF 2.2 against MS servers, they download the wsdl xsds, apply xslt to make references local, then cipher suite configuration takes place.
If you can try the same against the locally hosted service, it should not take long time. You can use a profiler to just see where CPU consumption is taking most of the time. I am sure they should'nt be CXF specific runtime classes. :) With Regards, Mayank On Wed, Jun 3, 2009 at 1:18 AM, Daniel Kulp <[email protected]> wrote: > > It SOUNDS like your client is downloading a bunch of schemas and stuff via > https. If there are a bunch of schemas or they are large or the net > connection is slow, that can definitely take a significant amount of time. > > Couple options: > 1) If you can, download everything ahead of time and package them with the > client and point the client at the packaged version. > > 2) Pass a "null" URL for the WSDL to the Service object when you create it. > It will just use the annotations on the objects then and not download the > wsdl/schemas. You will need to provide the endpoint URL to the port > (normally, that is pulled from the WSDL), but usually not a big deal. > > Dan > > > On Tue June 2 2009 5:02:53 am Nasseam Elkarra wrote: > > Hello, > > > > I'm using the latest version (2.2.2) with Java 1.6 and am noticing a > > slow init time. I generated the client stubs and am just trying to > > call a service and it is taking 4 minutes! The duration of the actual > > web service call is 3 seconds. > > > > I keep getting this message like a hundred times: > > Jun 2, 2009 1:16:12 AM org.apache.cxf.transport.https.SSLUtils > > getCiphersuites > > INFO: The cipher suites have not been configured, falling back to > > cipher suite filters. > > Jun 2, 2009 1:16:12 AM org.apache.cxf.transport.https.SSLUtils > > getCiphersuites > > INFO: The cipher suite filters have not been configured, falling back > > to default filters. > > Jun 2, 2009 1:16:12 AM org.apache.cxf.transport.https.SSLUtils > > getCiphersFromList > > INFO: The cipher suites have been set to SSL_RSA_WITH_RC4_128_MD5, > > SSL_RSA_WITH_RC4_128_SHA, TLS_RSA_WITH_AES_128_CBC_SHA, > > TLS_RSA_WITH_AES_256_CBC_SHA, TLS_DHE_RSA_WITH_AES_128_CBC_SHA, > > TLS_DHE_RSA_WITH_AES_256_CBC_SHA, TLS_DHE_DSS_WITH_AES_128_CBC_SHA, > > TLS_DHE_DSS_WITH_AES_256_CBC_SHA, SSL_RSA_WITH_3DES_EDE_CBC_SHA, > > SSL_DHE_RSA_WITH_3DES_EDE_CBC_SHA, SSL_DHE_DSS_WITH_3DES_EDE_CBC_SHA, > > SSL_RSA_WITH_DES_CBC_SHA, SSL_DHE_RSA_WITH_DES_CBC_SHA, > > SSL_DHE_DSS_WITH_DES_CBC_SHA, SSL_RSA_EXPORT_WITH_RC4_40_MD5, > > SSL_RSA_EXPORT_WITH_DES40_CBC_SHA, > > SSL_DHE_RSA_EXPORT_WITH_DES40_CBC_SHA, > > SSL_DHE_DSS_EXPORT_WITH_DES40_CBC_SHA, TLS_KRB5_WITH_RC4_128_SHA, > > TLS_KRB5_WITH_RC4_128_MD5, TLS_KRB5_WITH_3DES_EDE_CBC_SHA, > > TLS_KRB5_WITH_3DES_EDE_CBC_MD5, TLS_KRB5_WITH_DES_CBC_SHA, > > TLS_KRB5_WITH_DES_CBC_MD5, TLS_KRB5_EXPORT_WITH_RC4_40_SHA, > > TLS_KRB5_EXPORT_WITH_RC4_40_MD5, TLS_KRB5_EXPORT_WITH_DES_CBC_40_SHA, > > TLS_KRB5_EXPORT_WITH_DES_CBC_40_MD5. > > > > Any help is much appreciated. > > > > Thanks! > > Nasseam > > -- > Daniel Kulp > [email protected] > http://www.dankulp.com/blog >
