SSL SOAP Adapter Error - SSLException while handshaking -

I'm receiving the following error in a SOAP receiver adapter over https:
ssl_debug(9): Sending v3 client_hello message, requesting version 3.1...
ssl_debug(9): Received alert message: Alert Fatal: unexpected message
ssl_debug(9): SSLException while handshaking: Peer sent alert: Alert Fatal: unexpected message
ssl_debug(9): Shutting down SSL layer...
Both the ABAP and JAVA stacks are configured properly for SSL as per the help.sap.com instructions.
Here is more detailed information (sorry for the formatting):
#1.5#00144F37BB49006B0000010000001F4D00043969FB64B9E3#1189027258874#com.sap.aii.messaging.net.HTTPClientConnection#sap.com/com.sap.aii.af.soapadapter#com.sap.aii.messaging.net.HTTPClientConnection.getInputStream(Socket)#J2EE_GUEST#0##sl07e02_DX2_1679550#PIAPPLUSER#d86bf0a05bf511dcba2f00144f37bb49#XI SOAP[BS_XXX_SOAP_getUpdateHTTPSTesting/BS_MDX/MDX]_58508##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/SAPLibraries/SAPXDK#Plain###failed to get the input stream from socket: iaik.security.ssl.SSLException: Peer sent alert: Alert Fatal: unexpected message#
Any help is greatly appreciated. I've searched everywhere for any help on "unexpected message" but have found none. There is no info here. I hope you can help. Thanks.

I think you can use Altova XML spy, see following link:
http://www.altova.com/support_faq_installation.html#q4_install
Is XMLSpy® 2007 also available for Linux, Unix, Macintosh, OS/2, etc.?
Since XMLSpy® 2007 is a high-performance development environment, it is written entirely in C++ and is tightly integrated with the Windows operating system. It is also possible to use XMLSpy® 2007 on other operating systems with Windows Emulation Software. More Information can be found on our Platforms page. Please note that we cannot give any technical support or make any warranties regarding the usability of XMLSpy® 2007 in such a scenario.
Is it possible to install XMLSpy® 2007 on a Citrix / Windows Terminal Server?
If you wish to install XMLSpy® 2007 on a server such as Citrix or Windows Terminal Server then there are two things to bear in mind:
A) You MUST purchase concurrent licenses of XMLSpy® 2007 for use in a terminal server environment as opposed to the installed (per seat) licensing model.
B) No technical support can be provided by Altova for technical issues that may arise as a result of using XMLSpy® 2007 in a Terminal Server environment.

Similar Messages

SSLException while handshaking: Peer sent alert: Alert Fatal: decrypt error

Hello everybody,
I am tryining to establish a connection from SAP PI 7.0 to an external web service that requires SSL with client authentication. I am using the SOAP adapter for that. The private key of us and the public key of the web service were installed in the VA in the TrustedCAs view. In the corresponding receiver channel configuration I have ticked "Configure Certificate Authetication" and selected appropriate entries in "Keystore Entry" and "Keystore View".
Whenever I send a message through the channel I am getting though an error during the SSL handshake: Decrypt error.
Below is the SSL debug log
ssl_debug(15): Sending v3 client_hello message to services.bloomberg.com:443, requesting version 3.1...
ssl_debug(15): Received v3 server_hello handshake message.
ssl_debug(15): Server selected SSL version 3.1.
ssl_debug(15): Server created new session 81:ED:F8:61:3B:51:8E:70...
ssl_debug(15): CipherSuite selected by server: TLS_RSA_WITH_AES_256_CBC_SHA
ssl_debug(15): CompressionMethod selected by server: NULL
ssl_debug(15): Server does not supports secure renegotiation.
ssl_debug(15): Received certificate handshake message with server certificate.
ssl_debug(15): Server sent a 2048 bit RSA certificate, chain has 3 elements.
ssl_debug(15): ChainVerifier: No trusted certificate found, OK anyway.
ssl_debug(15): Received certificate_request handshake message.
ssl_debug(15): Accepted certificate types: RSA, DSA
ssl_debug(15): Accepted certificate authorities:
ssl_debug(15):   CN=XXXXXXXXXXXXXXXXXXXXXXXX
ssl_debug(15):   CN=VeriSign Class 3 International Server CA - G3,OU=Terms of use at https://www.verisign.com/rpa (c)10,OU=VeriSign Trust Network,O=VeriSign, Inc.,C=US
ssl_debug(15):   CN=VeriSign Class 3 Public Primary Certification Authority - G5,OU=(c) 2006 VeriSign, Inc. - For authorized use only,OU=VeriSign Trust Network,O=VeriSign, Inc.,C=US
ssl_debug(15): Received server_hello_done handshake message.
ssl_debug(15): Sending certificate handshake message with RSA client certificate...
ssl_debug(15): Sending client_key_exchange handshake...
ssl_debug(15): Sending certificate_verify handshake message...
ssl_debug(15): Sending change_cipher_spec message...
ssl_debug(15): Sending finished message...
ssl_debug(15): Received alert message: Alert Fatal: decrypt error
ssl_debug(15): SSLException while handshaking: Peer sent alert: Alert Fatal: decrypt error
ssl_debug(15): Shutting down SSL layer...
My first assumption was that it might be caused by missing public key of other side's server in the TrustedCAs view. Now I have assured that we have this key installed (although I am currious why there is still the "ChainVerifier: No trusted certificate found" message in the log).
Does somebody have an idea what could cause this SSL handshake failure?
Best regards,
Maxim

The XPI inspector gave more understanding of the situation. It shows which certificates the remote server is sending, which client certificate is used for authentication and many other topics. Interesting enough the XPI inspector shows that PI trusts the server key whereas the NWA log at the very same time tells that it doesn't. I have posted an OSS message asking to explain why there is this discrepancy.

Adapter error encountered while updating UD_ADUSER_LNAME

Hi,
As a field upadted on OIM user form, While updating the same on target AD, we encounter the following error randomly in OIM 11g
Adapter error encountered while updating UD_ADUSER_LNAME.Setting task status...
*"DATABASE_ERROR" does not correspond to a known Response Code. Using "UNKNOWN*".
Earlier if any one had faced the same issue. Please help.
Regads,
Anil Bansal

Check the field size. Make sure it doesn't exceed to the entered value.
-Prakash

Receiver SOAP Adapter error

Hi All,
         I am getting this response error message in my receiver SOAP Adapter while invoking a synchronous webservice.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <ProcessMessageResponse xmlns="http://Sleek.Integrator.Messaging" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:s="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<ProcessMessageResult>Value cannot be null. Parameter name: Request string is a null reference.</ProcessMessageResult>
</ProcessMessageResponse>
Thx in advance
Ravijeet

Hi All,
         I am still getting the same error value is null. I am not able to track what could be the cause of the error. If I am taking the message from SXMB_MONI and using it in a client tool it is successfully calling the webservice.
Do we need to explicitly mention in some configuration that content type is soap/xml. SOAP header is omitting the content type or is not specifying "soap/xml" as the content type.
I am interacting with a WAF websevice, is there any compatibilty issue with Windows Webservice and SAP XI?
Also what should I pick as the SOAP Action from this wsdl file definition
<wsdl:portType name="IMessageProcessor">
          <wsdl:operation name="ProcessMessage">
               <wsdl:input message="tns:IMessageProcessor_ProcessMessage_InputMessage" wsaw:Action="XXX.Messaging/ProcessMessage"/>
               <wsdl:output message="tns:IMessageProcessor_ProcessMessage_OutputMessage" wsaw:Action="XXX.Messaging/ProcessMessageResponse"/>
          </wsdl:operation>
     </wsdl:portType>
     <wsdl:service name="MessageProcessor">
          <wsdl:port name="BasicHttpBinding_IMessageProcessor" binding="i0:BasicHttpBinding_IMessageProcessor">
               <soap:address location="http://XXX.com/cardax/provisioningservice"/>
          </wsdl:port>
Thx in advance
Ravijeet

SOAP Adapter Error with HTTPS

Guys,
I have created one SOAP Adapter Receiver as a configuration below:
Target URL = https://www.server.com/ws.asmx (example)
Configure Certificate Athenticate (i have use one certificate configured in key store from Visual Admin)
Configura Proxy (i have used same proxy, port user and pass from web browser).
But when i execute my interface, occurs the follow error:
Connection reset
Can anybody helpe, please?

Hello,
finally you run your request from your ERP System about your ICF.
To establish a SSL Connection to the Web Service target system about an SAP WebAS and ICF, it is necessary to create a certificate on client site about Internet explorer using target URL and importing it on STRUST. Take the junction "SSL-Client (Anonym)" to include your certificate for your system.
Take a reboot of ICM Monitor.
Then create a HTTP Connection to rhe external server via SM59 (Typ G).
Don't forget to configure the following points:
Under the menu tab Registration&Security:
- Registration Process: No Registration
- status of security protocols: activ and ANONYM SSL-Client (Anonym)
In most cases, you don't need to edit your user data.
Only then one can usually connect about SAP XI or PI to some servers with SSL method.

Sender SOAP adapter error 401

Hello All,
Here the scenario is SOAP -> XI -> SAP ECC.
When the webservice is seding the message I am getting error in Sender SOAP channel.
Message is not going to Integration Engine.
Its failing with 401Un Authorized in sender soap adapter channel.My sender soap channel is plain channel with no authentication check and certificated etc.When webservice is seding request to XI its sending wit some usernmae which was there on XI box.I am facing this issue in Quality Env. The same is working fine in Dev box.
Please give me the list of points that I need to check here.
Thanks,
Regards,
Naresh

Hi,
I am facing this issue in Quality Env. The same is working fine in Dev box.
Once the scenario is transported from Dev to QA the location where the Webservice is hosted will also change
Hence you will have to change the target URL .....just the HostName / IP address and the port for all the webservices (that you transported to QA)
Once you are in QA and with no change to the URL the sender (which I suppose is also in QA env) will be still trying to ping the same old Dev-URL....in such situation the sender is bound to get UnAuthorized error....
So one in all change the URL in your WebService to point to QA and then test....
Same logic applicable to QA --> PROD
Regards,
Abhishek.

SOAP Adapter Error

I am working on a scenario:
SOAP Client <-----> XI <----> Web service.
I am using SOAP Adapter on both sender and receiver side.
I downloaded the WSDL for the webservice and imported it in IR and created Message Interfaces based on it and I am also done with the configuration side.
I am trying to send a soap request to XI via XMLSPY using my XI generated wsdl ( Generated a web service in XI using my scenario).
I am getting an error back in XMLSPY when I send a soap request.
<?xml version="1.0"?>

<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>DeliveryException</code>
                         <text><![CDATA[
com.sap.aii.af.ra.ms.api.DeliveryException: Received HTTP response code
500 : Timeout
     at
com.sap.aii.af.ra.ms.impl.core.queue.CallConsumer.onMessage(CallConsumer.java:144)
     at com.sap.aii.af.ra.ms.impl.core.queue.Queue.run(Queue.java:512)
     at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
     at
com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:74)
     at
com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:141)
          ]]></text>
                    </s:SystemError>
               </detail>
          </SOAP:Fault>
     </SOAP:Body>
</SOAP:Envelope>
I tried to check runtime message monitoring. Here are the details:
Audit Log for Message: d3294f20-b2dc-11da-8994-003048805a88
Time Stamp Status Description
2006-03-13 17:00:46 Success SOAP: request message leaving the adapter
(call)
2006-03-13 17:00:46 Success Application attempting to send an XI
message synchronously using connection AFW.
2006-03-13 17:00:46 Success Trying to put the message into the call
queue.
2006-03-13 17:00:46 Success Message successfully put into the queue.
2006-03-13 17:00:46 Success The message was successfully retrieved from
the call queue.
2006-03-13 17:00:46 Success The message status set to DLNG.
2006-03-13 17:00:46 Error Returning synchronous error notification to
calling application: Received HTTP response code 500 : Internal Server
Error.
2006-03-13 17:00:46 Error Transmitting the message using connection
http://diamond:8005/sap/xi/engine?type=entry failed, due to: Received
HTTP response code 500 : Internal Server Error.
2006-03-13 17:00:46 Error The message status set to FAIL.
2006-03-13 17:00:46 Error Returning to application. Exception: Received
HTTP response code 500 : Internal Server Error
2006-03-13 17:00:46 Error SOAP: call failed:
com.sap.aii.af.ra.ms.api.DeliveryException: Received HTTP response code 500 : Internal Server
Error
Can anyone suggest what could be wrong here?
Thanks,
Shubha.

Hi,
You can first test your Adapter Engine from "Runtime Work Bench".
Follow the steps for testing the SOAP Adapter from XI.
Step 1 :- Component Monitoring--> Click Adapter Engine.
Step 2 :- Select the "Test Message" Tab
Step 3 :- Give details for send to = http://host:port/XISOAPAdapter/MessageServlet?channel=:<service>:<channel> ,interface name, service, namespace
Step 4 :- Payload should be Soap Request. and click send message.
Check the result in SXMB_MONI.
Note : You can create SOAP Request from WSDL using the following tool.
http://www.gotdotnet.com/Community/UserSamples/Details.aspx?SampleGuid=65a1d4ea-0f7a-41bd-8494-e916ebc4159c
Regards,
Rakesh.

Receiver SOAP Adapter : Error Connection Refused (errno: 239)

Hello
I am testing a simple scenario using SOAP Adapter. I am getting the following error.
com.sap.aii.af.ra.ms.api.DeliveryException: Connection refused (errno:239)
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: Connection refused (errno:239)</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Can you please tell me what could be the error for the following scenario.
Best Regards,
Kiran

Hi Venkat,
We are actually not using the sender comm channel
http://<server>:<port>/ sap/xi/engine?type=entry&version=3.0&Sender.Party=<party name>&Sender.Service=<>&Interface=<namespace>^<interface>
This stated endpoint is fine there is no error with it.
Thanks.
Kiran

SOAP adapter error: invalid content type for SOAP: TEXT/HTML.

Dear SAP experts,
Need your help again here.
Currently, i am getting this specific error in my RWB logs.
The connection is from SAP XI going to Trading Partner via SOAP adapter.
The specific error is:
Delivery of the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: java.io.IOException: invalid content type for SOAP: TEXT/HTML.
I've already searched on what is causing the issue and it seems majority of the information is that, the error might be due to incorrect/wrong URL that was set in the configurations in the SAP XI communication channel.
Can you confirm this one?
DO you have any thoughts on this error?
Please help.
Thank you very much!
Fred

Hi Freddiesan,
First of all, test your URL acessing it from SAP PI server's local browser to check firewall and router settings.
If it works, check these blogs:
Regards,
Rogério
Edited by: Rogério Tambellini on Jul 3, 2009 12:52 PM

FTP Adapter Errors out while translating

Hi,
I am using a FTP adapter to put a text file using a bpel process. But the FTP adapter errors out with the following error:oracle/xml/parser/schema/XMLSchema
Is there a way to fix this issue?? Please advise.
Thanks
PS

Hi,
To do the alert configuration as suggested, please go through the information below.
From SP 14 on PMI-free alerting was introduced. That means before SP 14 one has to configure and activate the End-to-End Monitoring, and to schedule the report SXMSALERT_PROCESS_DATA_GET in order to extract the alerts from the PMI data. For SP 14 and higher, that's not longer necessary.
If no alerts are being delivered, please check if "Suppress multiple alerts of this rule" is checked for your rule.
For SP 14 and higher you could also have a look at the report sxmsalert_logreader. This report shows some information about alerts being created or not.
You'll find more information about trouble shooting the alerting in SAP Note 913858.
Also just check if this batch program (RSALERTPROC) is running or not.
The links below on Alert Management (ALM) will be of good help to you:
http://help.sap.com/saphelp_nw04/helpdata/en/3f/567ddea69d3d4c93a6aedabd08899e/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/3f/81023cfa699508e10000000a11402f/frameset.htm
Meanwhile look at these forum threads also:
Alerts not getting triggered from Adapter Framework
Alert Configs...
Also, In ALRTCATDEF, go to SETTINGS--> CONFIGURATION. By default, the option selected is INTERNAL PROCESSING. Select the option SMTP FORWARDING AS XML and give the email id. This will enable you to send an email alert whenever an error occurs in XI.
I hope I have answered your queries. If u want help with anything else please do reply back.
Regards,
abhy
PS: AWARD POINTS FOR HELPFUL ANSWERS.

FTP Adapter errors out while writing a file

Hi ,
I am facing this problem while using FTP adapter tries to write a file on a specific remote machine.The Adapter throws this following error:
Missing class: oracle.tip.adapter.api.TranslationAware
     Dependent class: oracle.tip.adapter.file.outbound.FileInteractionSpec
     Loader: global.libraries:1.0
     Code-Source: /XXX/ias/product/asmt_10131/j2ee/oc4j_soa/applib/fileAdapter.jar
     Configuration: <code-source> in /XXX/ias/product/asmt_10131/j2ee/oc4j_soa/config/server.xml
The missing class is available from the following locations:
     1. Code-Source: /XXX/ias/product/asmt_10131/bpel/lib/orabpel.jar (from <code-source> in /XXX/ias/product/asmt_10131/j2ee/oc4j_soa/config/server.xml)
     This code-source is available in loader oracle.bpel.common:10.1.3.
</summary>
Any Suggestions will be helpful.
Thanks
PS

Hi Rama Krishna
Are you saying that you are transferring data of your
internal table to another server using a FM??? Am not
sure if that can be done.
How about trying this way????
Download the data to a file on your application
server, using open dataset statement. Then transfer this
file to the other server using FM's FTP_CONNECT, FTP_COMMAND ....
Kind Regards
Eswar

SOAP Adapter - Error because of special character (u00FC - Umlaut) in payload

Hello,
We have a SOAP sync scenario.
SAP -> PI 7.0 -> 3rd Party system
We have a special character (ü - Umlaut) as part of the payload.
When the message enters message pipeline in PI, I can see the payload XML till message branching step.
From Message mapping step, i get the message - "The XML page cannot be displayed. An invalid character was found in text content" in SXMB_MONI.
In communication channel monitoring, I see the following error:
SOAP: error occured: com.sap.aii.af.ra.ms.api.RecoverableException: Parsing Error: com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: Unsupported character: 72(:main:, row:2, col:2106)(:main:, row=2, col=2106) -> com.sap.engine.lib.xml.parser.ParserException: Unsupported character: 72(:main:, row:2, col:2106): java.io.IOException: Parsing Error: com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: Unsupported character: 72(:main:, row:2, col:2106)(:main:, row=2, col=2106) -> com.sap.engine.lib.xml.parser.ParserException: Unsupported character: 72(:main:, row:2, col:2106)
But, when I pass the same message(with special character) to the 3rd party system using SOAP UI, i get a valid response back.
So, what is going wrong in PI?
Thanks,
Chandra

Hi Gouri,
you are right. My message is successful in SXMB_MONI, and the error is coming from comm channel monitoring with deliverin to target.
My sender is a proxy, and we can not specify any encoding in proxy sender.
I did not specify any encoding in SOAP Receiver aswell.
This is the sequence in comm channel monitoring:
Success: Delivering to channel: CI_SOAP_Receiver_Sync
Success: MP: Entering module processor
Success: MP: Processing local module localejbs/sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean
Success: SOAP: request message entering the adapter with user J2EE_GUEST
Error: SOAP: call failed: java.io.IOException: Parsing Error: com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: Unsupported character: 72(:main:, row:2, col:2046)(:main:, row=2, col=2046) -> com.sap.engine.lib.xml.parser.ParserException: Unsupported character: 72(:main:, row:2, col:2046)
Error SOAP: error occured: com.sap.aii.af.ra.ms.api.RecoverableException: Parsing Error: com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: Unsupported character: 72(:main:, row:2, col:2046)(:main:, row=2, col=2046) -> com.sap.engine.lib.xml.parser.ParserException: Unsupported character: 72(:main:, row:2, col:2046): java.io.IOException: Parsing Error: com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: Unsupported character: 72(:main:, row:2, col:2046)(:main:, row=2, col=2046) -> com.sap.engine.lib.xml.parser.ParserException: Unsupported character: 72(:main:, row:2, col:2046)
So, what can i do to fix this?
Thanks,
Chandra
Edited by: Chandra Sekhar H on Mar 3, 2011 12:25 PM

Web Service SOAP Adapter Error

Hi all
We just upgraded from PI7.0SP13 to SP18. We have a couple of Web Services running that worked fine in SP13. Now, after the upgrade they don't work anymore, and we get the following error when trying to execute the SOAP request:
com.sap.aii.af.service.cpa.impl.exception.CPALookupException: Couldn't retrieve binding for the given channelId: Binding:CID=a1a08d8558de39c691a8c80a4f524b1c;
     at com.sap.aii.af.service.cpa.impl.lookup.AbstractLookupManager.getBindingByChannelId(AbstractLookupManager.java:361)
     at com.sap.aii.af.mp.soap.web.MessageServlet.doPost(MessageServlet.java:424)
     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:401)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
     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:104)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
I've tried all the things that I have found in the forum, e.g. CPA cache refresh, restart the system, make channel inactive and active again in ID, stop and start in channel monitoring, but nothing appears to be helping.
Can anybody help?
Thank you,
Daniel

Hi Prateek
We do not use HTTPS. It is a simple Web Service that is called via HTTP with a request that calls a BAPI using the RFC adapter and returns the answer from the BAPI via the Web Service.
<wsdl:service name="MI_GETACCOUNTADDRTOWRITE_OU_SYService">
     <wsdl:port name="MI_GETACCOUNTADDRTOWRITE_OU_SYPort" binding="p1:MI_GETACCOUNTADDRTOWRITE_OU_SYBinding" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
               <soap:address location="http://<domain.name>:50000/XISOAPAdapter/MessageServlet?channel=:BS_GETACCOUNTADDRTOWRITE:CC_S_SOAP_GETACCOUNTADDRTOWRITE&version=3.0&Sender.Service=BS_GETACCOUNTADDRTOWRITE&Interface=http%3A%2F%2Fxxxxxx.com%2Fxi%2Faccount%5EMI_GETACCOUNTADDRTOWRITE_OU_SY" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"/>
          </wsdl:port>
     </wsdl:service>
Thank you,
Daniel

XI SOAP adapter : Error during parsing the SOAP part

Hello experts,
We have several scenarios SOAP to IDocs.
We are on XI 3.0 SP19, and since 9/6/09 around 4:00 PM GMT, our SOAP channels used to communicate with a specific 3rd party all stoped accepting incoming SOAP requests. All the messages are stucked on third party side, and we get the following error in the defaulttrace and application logs :
#1.5#001125A5BCD00066000076850013109E00046BF6A963E479#1244607054865#/Applications/ExchangeInfrastructure/AdapterFramework/SAPLibraries/SAPXDK#sap.com/com.sap.aii.af.soapadapter#com.sap.aii.messaging.mo.Message.reparseRootDocument()#PIMSOAP#21217##pxaci_PXA_6443451#PIMSOAP#a71ebfa0556d11decc24001125a5bcd0#SAPEngine_Application_Thread[impl:3]_50##0#0#Error#1#com.sap.aii.messaging.mo.Message#Plain###Error during parsing the SOAP part --- java.lang.NullPointerException#
It happened at the same time on all the environments for every interfaces using SOAP message from this sender to XI. That's the reason why we think it is a global issue, but we can not find anything concerning this error. Has anybody encountered this error or would have any clue of where it comes from ?
Many thanks,
Best regards,
Guislain

Hello Michal,
Thanks a lot for your help. Actualy we have tested with SOAP UI yesterday and this is what came out of the tests :
test 1 : we tried to call the XI service with the wsdl and put dummy data inside --> test OK
test 2 : we loaded in SOAP UI one of the file from our partner and tried to call the service --> test NOT OK
test 3 : we realized that there were some blank lines at the beginning of the file provided by the partner. we removed these blank lines --> test OK.
So we first thought that the format of the file sent by the partner was wrong and this is why we were getting the parsing error, because of these blank line. The thing is that these blank lines have always been here ! We have checked with old successful messages and they contain also these lines and if we test them in SOAP UI we get an error also. so it does not seems to come from this.
Moreover, as I said in my previous message, it happened on all the environments approximatly at the same time, so we are suspecting a global problem, but which one ? That's the million dollar question
Would you have any other ideas ?
Thanks a lot,
Best regards,
Guislain

Sender Soap Adapter - error

Hi,
I am testing SOAP to RFC Scenario in Quality landscape. I am getting the following error
<?xml version="1.0"?>

<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>ModuleUnknownException</code>
                         <text><![CDATA[
com.sap.aii.af.mp.module.ModuleException: either no channelID specified or no channel found for the specified party, service, and channel name, MessageServlet(Version $Id: //tc/xi/NW04_16_REL/src/_adapters/_soap/java/com/sap/aii/af/mp/soap/web/MessageServlet.java#2 $)
     at com.sap.aii.af.mp.soap.web.MessageServlet.doPost(MessageServlet.java:380)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java(Compiled Code))
     at javax.servlet.http.HttpServlet.service(HttpServlet.java(Compiled Code))
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java(Compiled Code))
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java(Compiled Code))
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java(Inlined Compiled Code))
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java(Compiled Code))
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java(Compiled Code))
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java(Compiled Code))
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java(Inlined Compiled Code))
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java(Compiled Code))
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java(Compiled Code))
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java(Compiled Code))
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java(Compiled Code))
     at java.security.AccessController.doPrivileged1(Native Method)
     at java.security.AccessController.doPrivileged(AccessController.java(Compiled Code))
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java(Compiled Code))
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java(Compiled Code))
          ]]></text>
                    </s:SystemError>
               </detail>
          </SOAP:Fault>
     </SOAP:Body>
</SOAP:Envelope>
Done CPACache refresh 2 times, Done java stack restart, Checked whether URL is correct or not. Almost all checks are done. Still error exists. Any help on this greatly appreciated.
Regards,
Daniel.LA

Hi Daniel,
                There could be error in places
     a) there could be a error in the payload of this message where Receiver agreement wasnt sepcified.
     b) Check in the configuration for this particular Combination if everything rightly defined or not(check CC, Recevier agreement, Serice .etc)............
Solution could be that if there is an error in Conifguration then
1) Make the approperiate changes
2) Activate all the objects
3) Refresh cache
Reward with points if helpful
Regards
Sai Ganesh

SSL SOAP Adapter Error - SSLException while handshaking -

Similar Messages

Maybe you are looking for