Hello,
After changing over to a new set of certificates (and a new testing enpoint)
code that was working is now generating:
javax.xml.ws.soap.SOAPFaultException: Fault string, and possibly fault code,
not set
at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:161)
Does
Modifying the code with may be the log entries (in various
BindingFactoryManagerImpl parts and AbstractJAXRSFactoryBean NPE poit
level) to get a better idea of the ordering and then redeploying might
help...It is tricky
Sergey
On 09/02/18 16:51, Andrei Shakirin wrote:
Hi Sergey,
Thanks
Hi Sergey,
Thanks for your response.
Yeah ... these are my favourite issues: happens once per 20 starts, only on
some environments, not really debuggable.
Thanks for the hints, will fighting.
Regards,
Andrei.
> -Original Message-
> From: Sergey Beryozkin [mailto:sberyoz...@gmail.com]
Hi Andrei
Looks like the problem is happening earlier,
https://github.com/apache/cxf/blob/cxf-3.1.7/rt/frontend/jaxrs/src/main/java/org/apache/cxf/jaxrs/AbstractJAXRSFactoryBean.java#L99
and the stack-trace suggests that BindingFactoryManager is null, it is
not set as a bus extension.
Why
Hi Sergey,
Could you quick look in following stack trace, occurs sometimes by startup CXF
client in OSGi Karaf container:
2018-02-09 04:02:11,452 WARN
[{{bundle.name,org.apache.cxf.cxf-rt-transports-http}{bundle.version,3.1.7}{bundle.id,252}}]
[null]
