cancel
Showing results for 
Search instead for 
Did you mean: 

ClassCastException when calling SOAP adapter

Former Member
0 Kudos

Hello,

I created a Web service interface to an ABAP RFC

via XI and a corresponding communication channel

(SOAP/HTTP to a specific message interface with data

types, message types, mappings etc. defined in the

integration repository). Sending SOAP messages

and receiving the correct replies works fine.

However, when I transport the relevant objects

from our test system to the consolidation system

by exporting and then importing via the file system

(all objects of the software component in the integration

repository, all objects of the communication scenario

in the integration directory), the

ClassCastException given below is returned

when sending the same SOAP messages

to the consolidation system. Other SOAP interfaces

work, but the one I imported does not.

Unfortunately, the request neither shows up in

the XmlMonitor nor in MessageMonitoring in the

Runtime workbench, so I do not get a further

indication what actually went wrong.

Questions:

- Has anyone had a similar problem or the same

error message? If so, what was the cause?

- Does anyone (maybe from SAP) know what exactly

happens in the mentioned code line where the

exception is thrown?

- Where could I look to find further information

about the error?

System information:

- SAP BASE 6.40, XI 3.0 with Service Pack 15

Thanks + Cheers,

Guido

***

<?xml version='1.0'?>

<!-- see the documentation -->

<SOAP:Envelope xmlns:SOAP='http://schemas.xmlsoap.org/soap/envelope/'>

<SOAP:Body>

<SOAP:Fault>

<faultcode>SOAP:Server</faultcode>

<faultstring>Server Error</faultstring>

<detail>

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

<context>XIAdapter</context>

<code>ClassCastException</code>

<text><![CDATA[

java.lang.ClassCastException

at com.sap.aii.af.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:227)

at com.sap.aii.af.mp.processor.ModuleProcessorLocalLocalObjectImpl0.process(ModuleProcessorLocalLocalObjectImpl0.java:103)

at com.sap.aii.af.mp.soap.web.MessageServlet.callModuleProcessor(MessageServlet.java:159)

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

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:390)

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

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

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

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

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

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

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

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(Native Method)

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

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:160)

]]></text>

</s:SystemError>

</detail>

</SOAP:Fault>

</SOAP:Body>

</SOAP:Envelope>

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

I call XI SOAP ADAPTER,alaways return the error,Could you give me some suggests?

Former Member
0 Kudos

In case someone has the same problem:

it turned out that on the test system,

support package 15 had already been installed,

whereas the consolidation system ran with support

package 14. This caused the described problem.

Message was edited by: Guido Wimmel

Former Member
0 Kudos

Hi,

looking to the stack trace provided by i found this

>>at java.security.AccessController.doPrivileged(Native >>Method)

this means that you have defined assigned users for the business service in configuration directory.

Make sure the client is making the webservice call using that specific user.

cheers,

naveen