CXF users and developers,
https://issues.apache.org/jira/browse/CXF-5231 (and later
https://issues.apache.org/jira/browse/CXF-5719) changed the way the exception
stack trace is encoded and decoded (in resp. AbstractSoapInterceptor and
ClientFaultConverter). This seems to have introduced coupling between CXF
versions on the client and server - if the client is upgraded to the version
having this change before the server, it may experience unexpected exceptions
of the following sort:
java.lang.NumberFormatException: For input string: "3826
com.company.app.service.SomeServer"
at
java.lang.NumberFormatException.forInputString(NumberFormatException.java:48)
~[na:1.6.0_45]
at java.lang.Integer.parseInt(Integer.java:458) ~[na:1.6.0_45]
at java.lang.Integer.parseInt(Integer.java:499) ~[na:1.6.0_45]
at
org.apache.cxf.interceptor.ClientFaultConverter.parseStackTrackLine(ClientFaultConverter.java:287)
~[cxf-2.7.10.jar:2.7.10]
at
org.apache.cxf.interceptor.ClientFaultConverter.setStackTrace(ClientFaultConverter.java:249)
~[cxf-2.7.10.jar:2.7.10]
at
org.apache.cxf.interceptor.ClientFaultConverter.handleMessage(ClientFaultConverter.java:79)
~[cxf-2.7.10.jar:2.7.10]
...
because Message.EXCEPTION_CAUSE_SUFFIX rather than "\n" is considered stack
trace line separator now.
Did anybody encountered this before? Is there any recommended solution, other
than dropping ClientFaultConverter and using something more relaxed instead?
Thank you
Vadim
________________________________
NOTICE: Morgan Stanley is not acting as a municipal advisor and the opinions or
views contained herein are not intended to be, and do not constitute, advice
within the meaning of Section 975 of the Dodd-Frank Wall Street Reform and
Consumer Protection Act. If you have received this communication in error,
please destroy all electronic and paper copies and notify the sender
immediately. Mistransmission is not intended to waive confidentiality or
privilege. Morgan Stanley reserves the right, to the extent permitted under
applicable law, to monitor electronic communications. This message is subject
to terms available at the following link:
http://www.morganstanley.com/disclaimers If you cannot access these links,
please notify us by reply message and we will send the contents to you. By
messaging with Morgan Stanley you consent to the foregoing.
