cxf-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Beilin, Vadim" <>
Subject stacktrace compatibility
Date Thu, 04 Dec 2014 14:16:14 GMT
CXF users and developers, (and later
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"
                at java.lang.NumberFormatException.forInputString(
                at java.lang.Integer.parseInt( ~[na:1.6.0_45]
                at java.lang.Integer.parseInt( ~[na:1.6.0_45]
                at org.apache.cxf.interceptor.ClientFaultConverter.parseStackTrackLine(
                at org.apache.cxf.interceptor.ClientFaultConverter.setStackTrace(
                at org.apache.cxf.interceptor.ClientFaultConverter.handleMessage(

because Message.EXCEPTION_CAUSE_SUFFIX rather than "\n" is considered stack trace line separator

Did anybody encountered this before? Is there any recommended solution, other than dropping
ClientFaultConverter  and using something more relaxed instead?

Thank you


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: 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.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message