SOAP Sender Adapter Not working

[Former Member]

We have the following Synchronous sceanrio: Third Party System <> PI <> SAP ECC

The interface works well in our DEV and PreProd environments but has stopped working in our QA environment.

The SOAP Sender Adapter is giving me the following error:

failed to initialize: org.apache.axis.ConfigurationException: 
java.lang.ClassNotFoundException: ------------------------- Loader Info ------------------------- 
ClassLoader name: library:com.sap.aii.af.axisproviderlib] Living status: alive Direct parent loaders:   system:Frame   library:com.sap.base.technology.facade   library:engine.j2ee14.facade] Resources:   
/usr/sap/XQ1/DVEBMGS01/j2ee/cluster/bin/ext/com.sap.aii.af.axisproviderlib/lib/axis.jar   
/usr/sap/XQ1/DVEBMGS01/j2ee/cluster/bin/ext/com.sap.aii.af.axisproviderlib/lib/commons-discovery-0.2.jar   
/usr/sap/XQ1/DVEBMGS01/j2ee/cluster/bin/ext/com.sap.aii.af.axisproviderlib/lib/commons-logging-1.0.4.jar   
/usr/sap/XQ1/DVEBMGS01/j2ee/cluster/bin/ext/com.sap.aii.af.axisproviderlib/lib/commons-net-1.0.0-dev.jar   
/usr/sap/XQ1/DVEBMGS01/j2ee/cluster/bin/ext/com.sap.aii.af.axisproviderlib/lib/wsdl4j-1.5.1.jar   
/usr/sap/XQ1/DVEBMGS01/j2ee/cluster/bin/ext/com.sap.aii.af.axisproviderlib/lib/xmlsec-1.4.0.jar   
/usr/sap/XQ1/DVEBMGS01/j2ee/cluster/bin/ext/com.sap.aii.af.axisproviderlib/lib/wss4j-1.5.6.jar  
 /usr/sap/XQ1/DVEBMGS01/j2ee/cluster/bin/ext/com.sap.aii.af.axisproviderlib/lib/opensaml-1.0.1.jar   
/usr/sap/XQ1/DVEBMGS01/j2ee/cluster/bin/ext/com.sap.aii.af.axisproviderlib/lib/xalan-2.6.0.jar

Currently the Quality of Service for the communication channel is set to "Best Effort" because it is a Synchronous Interface. However if I change the Quality of Service to "Exactly Once" the message is received by PI without any problems. So the problem is specific to Synchronous.

I tried to create a new communication channel and use that but that didnt help.

We have checked on the server and all the above mentioned .jar files are all in place.

I have compared the Processing Sequence and Module Configuration of the Module tab (for the communication channel) with the other environments and everything seems to be fine.

Any help would be much appreciated.

Thanks,

Krishneel

[Former Member]

Hi Goundar,

Make sure you have all the jars installed and also when you test from SOAP client you are using http instead of https.

The error what you have given clearly states that is some issues with the clases in Axis framework. Once you installed you should restart the box. Try to do a restart and see whether it works or not.

Regards,

---Satish

[Former Member]

Hi Satish,

Yes the required .jar files are installed and we are using HTTP not HTTPS.

Thanks,

Krishneel

[Former Member]

Good news this issue has now been resolved. Basis told me that the QA PI database had run out of space. After adding more space the interface is now working fine.

[markangelo_dihiansan]

Hello,

Can you trying opening the sender Axis URL in IE? The URL should be in the format of

http(s)://host:port/XIAxisAdapter/MessageServlet?

If it does not open, try contacting your BASIS.

Hope this helps,

Mark

[Former Member]

Hi Mark, yes that URL opens the Axis Adapter Message Servlet page fine.

[markangelo_dihiansan]

Hello,

What is the posting URL that you are using? Is it in this form?

http(s)://host:port/XIAxisAdapter/MessageServlet?senderService=yourService&interface=yourInterface&interfaceNamespace=yourIFNS

Hope this helps,

Mark

[Former Member]

Hi Mark,

Yep the URL is in the correct form. I just double checked it...looks all good:

Strange because the interface works fine in the other environments and used to work in QA until a couple of days ago.

Krishneel

[former_member854360]

Hi Krishna,

If you choose Best Effort, specify in the Adapter Framework Parameters under Timeout how many milliseconds to wait before canceling the delivery of the message.

http://help.sap.com/saphelp_nwpi711/helpdata/en/45/a39e244b030063e10000000a11466f/content.htm

[Former Member]

Yes the Timeout is currently set to: 300000

A little more info. The error we are getting in the SOAP client is:

senderChannel 'b4620bdad4053a07a39101c3c7e8d306': Catching exception calling messaging system; nested exception is: 
com.sap.engine.interfaces.messaging.api.exception.MessagingException: Received HTTP response code 500 : Internal Server Error

[former_member854360]

Hi Krishna,

Can you check OSS note 1522630.

[Former Member]

Thanks for the help Debashish but I dont think that note is related to the problem. It talks about adding attachments to the message which are then not accessible in the receiving system.

The problem we are facing does not involve any attachments. Also, the error we are facing occurs in the SOAP channel itelf..doesnt even reach the Integration Engine.

[former_member854360]

Hi Krishna,

ClassLoader name: library:com.sap.aii.af.axisproviderlib] Living status: alive Direct parent loaders:   system:Frame   library:com.sap.base.technology.facade   library:engine.j2ee14.facade] Resources:   
/usr/sap/XQ1/DVEBMGS01/j2ee/cluster/bin/ext/com.sap.aii.af.axisproviderlib/lib/axis.jar   
/usr/sap/XQ1/DVEBMGS01/j2ee/cluster/bin/ext/com.sap.aii.af.axisproviderlib/lib/commons-discovery-0.2.jar   
/usr/sap/XQ1/DVEBMGS01/j2ee/cluster/bin/ext/com.sap.aii.af.axisproviderlib/lib/commons-logging-1.0.4.jar   
/usr/sap/XQ1/DVEBMGS01/j2ee/cluster/bin/ext/com.sap.aii.af.axisproviderlib/lib/commons-net-1.0.0-dev.jar   
/usr/sap/XQ1/DVEBMGS01/j2ee/cluster/bin/ext/com.sap.aii.af.axisproviderlib/lib/wsdl4j-1.5.1.jar

Have you deployed the following Jar.

commons-discovery-0.2.jar

○ commons-logging-1.0.4.jar

○ commons-net-1.0.0-dev.jar

○ wsdl4j-1.5.1.jar

Refer this

http://help.sap.com/saphelp_nw04/helpdata/en/45/a4f8bbdfdc0d36e10000000a114a6b/content.htm

Edited by: Debashish Roy on Jul 18, 2011 10:10 AM

[Former Member]

Yes I had our Basis team look on the QA PI Server and all the required .jar files are in place

http://<host>:<port>/XIAxisAdapter/MessageServlet works fine.