on 02-18-2009 6:46 AM
Hi All,
I am trying to send the following soap request to XI
=======================================================================
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:gip="urn:pmintl.com/Gips02">
<soapenv:Header/>
<soapenv:Body>
<gip:MT_GIPSTOSMDLSYN_REQ>
<Source>
<xmlDocument><sender><name>GiPS</name><environment>Dev</environment><UserID>ymargub</UserID></sender><message GiPSChange="C69695" op="Release"><Col N="RELEASE_DATE">2009-01-22</Col><Col N="CHG_DESCRIPTION">Automatic Release</Col></message></xmlDocument>
</Source>
</gip:MT_GIPSTOSMDLSYN_REQ>
</soapenv:Body>
</soapenv:Envelope>
================================================================================
I am getting a error as shown below . In runtime workbench under communication channel it is also showing "null pointer exception". The details of message given below . Can anyone please analyse where it is going wrong. Everything from sender agreement to communication channel is in place.
=================================================================================
<!-- 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>ADAPTER.JAVA_EXCEPTION</code>
<text>java.lang.NullPointerException at com.sap.aii.af.sdk.xi.mo.xmb.XMBMessageOperator.getQualityOfServiceAsString(XMBMessageOperator.java:2048) at com.sap.aii.adapter.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:843) at sun.reflect.GeneratedMethodAccessor789_10002.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:43) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute
Hi,
The error that you are getting is because of a patch problem.....please install the necessary patch...for more information refer this SAP Note: 1239995.
Regards,
Abhishek
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I regenerated the wsdl. checked all soap adapter parameters and also hit the url generated in the wsdl file in internet explorer on which I am prompted with userid and password and then shown message servlet is in status OK. But still the same problem continues.Please any more solutions
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Abdur,
If it an application error response..
Can u please refer to the link below for Handling Web Service SOAP Fault Responses in SAP NetWeaver XI->SOAP Fault - Application Error Response
/people/jin.shin/blog/2007/05/21/handling-web-service-soap-fault-responses-in-sap-netweaver-xi
Regards,
Madhu
Hi,
Please cross check the URL that you are giving in Proposed URL option wihile you are generating the WSDL.
Type the URL that you are using as i mentioned in above in Intenet Explorer and press Enter. This should give Message servelet ok.
Then clear CPA Cache and test your scenario, it will work ( Provided you should fill SOAP Adatpter parameters correctly in ID).
Thanks
Subbu
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
There could be some problem with wsdl generation. Regenerate the wsdl in PI and try to run the scenario again.
Regards,
Prateek
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
93 | |
10 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.