Wait…. I thought there was actually and error that was preventing the client from working. You keep describing it as an error and you make it sound like it connected fine with 3.0.1 but wasn’t with 3.0.2.
This is just a warning log entry. Thus, it would be categorized as minor. Something to be fixed, yes, but a very minor thing that you can work around by updating your logging to not log the warning. Dan > On Nov 10, 2014, at 12:56 PM, membersound2 <[email protected]> wrote: > > Hello, > > I have a problem upgrading from 3.0.1 to 3.0.2: I have a productive soap > webservice client. Connection is made via default HTTPS, everything works > fine. > > But in 3.0.2, I'm suddenly getting the following error about a 100 times: > /*Nov 03, 2014 1:11:20 PM org.apache.cxf.configuration.jsse.SSLUtils > getDefaultKeyStoreManagers WARNING: Default key managers cannot be > initialized: C:\Users\Administrator.keystore (The system cannot find the > file specified)/ > > The is strange because: > 1. it was working in the previous version without complains! > 2. the soap services does not use any specific custom SSL certificate, and > thus it should work out of the box as the docs state: > > /When using an "https" URL, CXF will, by default, use the certs and > keystores that are part of the JDK. For many HTTPs applications, that is > enough and no configuration is necessary. > / > I also created an issue for this > (https://issues.apache.org/jira/browse/CXF-6094) which was closed as "not a > problem". Anyhow I still believe this IS actually a problem if the behavior > changes that dramatically. > > Could you help here? What can I do to get rid of the error? > > > > -- > View this message in context: > http://cxf.547215.n5.nabble.com/CXF-client-Default-key-managers-cannot-be-initialized-3-0-2-only-tp5750930.html > Sent from the cxf-user mailing list archive at Nabble.com. -- Daniel Kulp [email protected] - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com
