cancel
Showing results for 
Search instead for 
Did you mean: 

Invalid channel???

Former Member
0 Kudos

Hi

We are having some problems with our SOAP adapter. When I try to send a message with soap client tool Quasar I get this response:

<i><SOAP:Fault xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"><faultcode>SOAP:Server</faultcode><faultstring>Server Error</faultstring><detail>

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

<context>XIAdapter</context>

<code>CPAException</code>

<text>

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

at com.sap.aii.af.mp.soap.web.MessageServlet.getChannelID(MessageServlet.java:415)

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

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

at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)</i>

But when I am belive that the adress used is the right one: server.50000/XISOAPAdapter/MessageServlet?channel=:service:channel

I have tested with Message servlet:

Message Servlet is in Status OK

Status information:

Servlet com.sap.aii.af.mp.soap.web.MessageServlet (Version $Id: //tc/aii/30_VAL_REL/src/_adapters/_soap/java/com/sap/aii/af/mp/soap/web/MessageServlet.java#14 $) bound to /MessageServlet

Classname ModuleProcessor: null

Lookupname for localModuleProcessorLookupName: localejbs/ModuleProcessorBean

Lookupname for remoteModuleProcessorLookupName: null

ModuleProcessorClass not instantiated

ModuleProcessorLocal is Instance of com.sap.aii.af.mp.processor.ModuleProcessorLocalLocalObjectImpl0

ModuleProcessorRemote not instantiated

I have can also display info about the service on this adress.

serverl:50000/XISOAPAdapter/HelperServlet?action=FindChannel&channel=:service:channel

What can cause this, I am stuck...

Regards,

Morten

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi,

Please check if you didn't make a typo in channel name (I think that you are aware of case sensitivity). Please also verify your WSDL file. Check status in adapter monitor and finally in the worst case restart adapter maybe it will help you.

Regards,

Wojciech

Answers (2)

Answers (2)

bhavesh_kantilal
Active Contributor
0 Kudos

Hi,

Might not actually solve your problem,. but, you can actually send the SOAP message directly to the integration engine and avoid a Sender SOAP adapter Completely!

For how to do this, check this blog,

/people/stefan.grube/blog/2006/09/21/using-the-soap-inbound-channel-of-the-integration-engine

Regards,

Bhavesh

Former Member
0 Kudos

The problem was Quasar I belive.

I have tested with an other client and it works fine.

Morten,

Former Member
0 Kudos

dumb answer

but i hope you have replace the service and channel names properly.

Former Member
0 Kudos

Yes I have replaced the service and channel names

I have checked for typos also. There might be an error in the test client, I use Quasar 3.0.1. Any experience with this program http://www.integrationcentral.com/product.html ?

Morten

Former Member
0 Kudos

Hi,

Please check WTP as a webservice client. Here is link:

http://download.eclipse.org/webtools/downloads/

Regards,

Wojciech

Former Member
0 Kudos