Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

CXF client exception: Interceptor for {XXX} has thrown exception, unwinding now

Avatar

Level 4

Dear all,

 

I have done  6.5 in-place upgrade. We are facing 'org.apache.cxf.interceptor.Fault: Could not send Message.' when we submit soap request to CRM. When I checked the message, I noticed that the header is missing in the soap message. 

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"><soap:Body><ns2:test1 xmlns:ns2="urn:sap-com:document:sap:soap:functions:mc-style">........................................................................................................................................</ns2:test1></soap:Body></soap:Envelope>

...

....

Caused by: org.apache.cxf.transport.http.HTTPException: HTTP response '401: Unauthorized' when communicating with http://<crmhostname>:8000/sap/bc/srt/scs/sap/test1?sap-client=600

 

 

Could anyone advice, please? 

 

 

Thanks in advance.

1 Accepted Solution

Avatar

Correct answer by
Level 5

This might be a permission issue. Checking the username and password in place and then the below link might help:

https://stackoverflow.com/questions/9078726/cxf-client-exception-interceptor-for-xxx-has-thrown-exce... 

"After debugging in the cxf code and seeking help in the cxf mailing list, I finally solved this problem. The problem is caused by the inbound message, the http message lacks the content-type header, which causes the CXF fail to create an XMLStreamReader, and then failed to read the content, thus a NullPointerException is thrown. Many thanks to the guys in the CXF community!

I asked a question and got answer there: http://cxf.547215.n5.nabble.com/CXF-client-exception-Interceptor-for-XXX-has-thrown-exception-unwind..."

 

In your case some other parameter might be null/missing and that might be causing the issue. Debugging will help you to find out what exactly is not in place.

View solution in original post

0 Replies

Avatar

Correct answer by
Level 5

This might be a permission issue. Checking the username and password in place and then the below link might help:

https://stackoverflow.com/questions/9078726/cxf-client-exception-interceptor-for-xxx-has-thrown-exce... 

"After debugging in the cxf code and seeking help in the cxf mailing list, I finally solved this problem. The problem is caused by the inbound message, the http message lacks the content-type header, which causes the CXF fail to create an XMLStreamReader, and then failed to read the content, thus a NullPointerException is thrown. Many thanks to the guys in the CXF community!

I asked a question and got answer there: http://cxf.547215.n5.nabble.com/CXF-client-exception-Interceptor-for-XXX-has-thrown-exception-unwind..."

 

In your case some other parameter might be null/missing and that might be causing the issue. Debugging will help you to find out what exactly is not in place.