Symptom
An AXIS Receiver communication channel for message processing has been configured, and the following error occurs:
- In the Communication Channel Monitoring tool, the following error is observed:
"Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: no Main"
- In the Default Trace or in an XPI Inspector trace file, the following error might be seen:
"unable to create message
AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.generalException
faultSubcode:
faultString: no Main
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}stackTrace:no Main"
Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.
Read more...
Environment
- PI Release Independent
- SAP NetWeaver
- SAP Process Integration
Product
Keywords
AXIS, no Main, MessagingException, AXIS receiver, Communication Channel, XMLSOAP, AxisFault, FaultString, StackTrace, Module, HandlerBean, AFAdapterBean, Configuration, Process Integration 7.0, PI 7.0, PI 7.01, PI 7.02, Process Integration 7.10, PI 7.10, Process Integration 7.11, PI 7.11, Process Integration 7.30, PI 7.30, Process Integration 7.31, PI 7.31, Process Orchestration 7.40, PI 7.40, PO 7.40, Process Orchestration 7.50, PI 7.50, PO 7.50, NetWeaver, XI, AEX , KBA , BC-XI-CON-AXS , Axis Extention for SOAP Adapter , BC-XI-CON-SOP , SOAP Adapter , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.