cancel
Showing results for 
Search instead for 
Did you mean: 

javax.xml.rpc.soap.SOAPFaultException: "Server Error" while calling a WSDL

Former Member
0 Kudos

Hi

I am using a WSDL in my java code by creating proxy.

I am getting an exception on below line of code

XX_RESPONSE res = port.XX_XX_Forecast(req);

exception :

javax.xml.rpc.soap.SOAPFaultException: "Server Error"

hat could be the possibility.

is it from XI side or Java side.

Shall I catch a XI person on my floor to solve this !!

Thanks

Accepted Solutions (0)

Answers (2)

Answers (2)

JoelTrinidade
Active Contributor
0 Kudos

Hi Saurabh,

Its a error on the XI side. Please go and catch a XI guy on your floor but not to tightly.....:)

Jokes apart just show these three lines from the error log , rest all he would understand.... its simple

"<context>XIAdapter</context>

<code>ADAPTER.JAVA_EXCEPTION</code>

<text>com.sap.aii.af.service.cpa.CPAException: invalid channel (party:service:channel) = <null>"

Rgds

joel

Edited by: joel trinidade on Feb 25, 2009 12:25 PM

Former Member
0 Kudos

Hi Joel

I asked an Xi person for this problem.

He then tsted it from Altova client.

He told me that it is working fine....and that problem is from Java side

Anything which I can tell him to put my point further ...!!

Thanks

Former Member
0 Kudos

Hi

check the URL which you use, make sure this "channel=party:service:channel" has all required/ valid names.

http://help.sap.com/saphelp_nw04/helpdata/en/fc/5ad93f130f9215e10000000a155106/content.htm

Regards

Vishnu

Former Member
0 Kudos

Hi Vishnu

channel=party:service:channel"

Do we set these in NWDS somewhere or in J2EE visual administrator tool.....

or in XI part somewhere...!!

Please comment

Former Member
0 Kudos

Hi

The crux is the URL (which should hit XI), which has to be in the format specified by SAP as per above link.

Every tool/ IDE has its own way of generating the call, using the WSDL. you need NOT seperately enter these details of channel etc, elsewhere.

Easiest is test with any soap client, using the given WSDL

/people/community.user/blog/2006/09/19/xi-webservice-studio--a-plain-jane-soap-tool

Make sure that you are using the right WSDL (search above SAP help link for correct way to generate WSDL in XI, it is the task of XI person).

Blogs on Other IDEs & methods

/people/riyaz.sayyad/blog/2006/05/08/consuming-xi-web-services-using-web-dynpro-150-part-ii

/people/riyaz.sayyad/blog/2006/05/07/consuming-xi-web-services-using-web-dynpro-150-part-i

/people/community.user/blog/2007/04/05/consuming-webservice-in-visual-composer-2

/people/abhijeet.jangam/blog/2006/05/27/developing-single-document-wsdl-to-schedule-a-web-service

Regards

Vishnu

Former Member
0 Kudos

Thanks Vishnu...

WSDL forwarded by my manager was wong

I tested it and it threw same exception.

Infact the XI person which I asked for to test WSDL was having right version of WSDL.

nyways...1 more help..

Now, is there any way in NWDS to replace contents of used WSDL.

Because only 1 "=" is missing in WSDL..

Thanks

Former Member
0 Kudos

Hi

Glad to know that the issue is fixed.

It is better not to adjust WSDL manually & to reload the new one, to ensure everything is OK.

Regards

Vishnu

Former Member
0 Kudos

To be more specific :

Error is

<detail xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">

<s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">

<context>XIAdapter</context>

<code>ADAPTER.JAVA_EXCEPTION</code>

<text>com.sap.aii.af.service.cpa.CPAException: invalid channel (party:service:channel) = &lt;null&gt;

at com.sap.aii.af.mp.soap.web.MessageServlet.getChannel(MessageServlet.java:499)

at com.sap.aii.af.mp.soap.web.MessageServlet.doPost(MessageServlet.java:409)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)

at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)

at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)

at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)

at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)

at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)

at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)

at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)

at java.security.AccessController.doPrivileged(AccessController.java:215)

at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)</text>

</s:SystemError>

</detail>