MessagingException: No response available

Hi Experts,
I am facing a problem in Production server (PI 7.1).
I have synchronous interfaces between SOAP to RFC and RFC to RFC via PI.
Some time, the interfaces are failing with the error u201Ccom.sap.engine.interfaces.messaging.api.exception.MessagingException: No response availableu201D
Functional consultant has kept the trace in ECC system (for the RFC calls), we donu2019t find any call/trace for the one which fails with the error u201CNo response availableu201D.
I have checked the auidit log the, the log says as below.
011-06-09 04:40:44 Information RfcAdapter received sRFC for RFC##### from SID/client. Trying to send message synchronously.
2011-06-09 04:40:44 Information MP: entering1
2011-06-09 04:40:44 Information MP: processing local module localejbs/RfcAFBean
2011-06-09 04:40:44 Information The application tries to send an XI message synchronously using connection RFC_http://sap.com/xi/XI/System.
2011-06-09 04:40:44 Information Trying to put the message into the call queue.
2011-06-09 04:40:44 Information Message successfully put into the queue.
2011-06-09 04:40:44 Information The message was successfully retrieved from the call queue.
2011-06-09 04:40:44 Information The message status was set to DLNG.
2011-06-09 04:43:44 Error Received XI System Error. ErrorCode: GENERAL ErrorText: com.sap.engine.interfaces.messaging.api.exception.MessagingException: No response available. ErrorStack: null
2011-06-09 04:43:44 Error Transmitting the message using connection RFC_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: XIAdapterFramework:GENERAL:com.sap.engine.interfaces.messaging.api.exception.MessagingException: No response available..
2011-06-09 04:43:44 Error The message status was set to FAIL.
2011-06-09 04:43:44 Error Returning to application. Exception: com.sap.engine.interfaces.messaging.api.exception.MessagingException: XIAdapterFramework:GENERAL:com.sap.engine.interfaces.messaging.api.exception.MessagingException: No response available.
2011-06-09 04:43:44 Error MP: exception caught with cause com.sap.engine.interfaces.messaging.api.exception.MessagingException: XIAdapterFramework:GENERAL:com.sap.engine.interfaces.messaging.api.exception.MessagingException: No response available.
I am trying to find out the problem.
I think, message is getting failed in AFW and it is not reaching the reciver communication channel.
Do you think, the cache refresh will solve the problem.
As this is critical issue,I need your suggestions. Please let me know, what could be the problem.
Thanks & Regards,
Venu V

Hi,
Thanks for reply.
We had kept the trace in ECC for the calls from SOAP to RFC via PI.
We did not get any trace in ECC for the call which failed.
Trace is there for successful calls.
Still not sure where the problem is?
Thanks & Regards,
Venu V

Similar Messages

JDBC receiver error No response available

Hi All,
I am getting below error in Proxy to JDBC synchronous scenario. This interface is to select the records based on between two dates. when number of records comes above 20000, it is failing with below error in sxmb_moni. i am getting this error in QA system.
With same number of records, it works fine in Development system.
please share your thoughts to overcome this issue.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.engine.interfaces.messaging.api.exception.MessagingException: No response available.</SAP:AdditionalText>
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Regards,
Muni

Hi Inaki,
i check the channel logs. getting below error.
Delivery of the message to the application using connection JDBC_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessageExpiredException: Sync application request expired.. Setting message to status failed
I tried using syncTimeout in the channel. set the value 300000. no luck.
PI dev and QA systems are connected to QA DB.
in the development it takes less than 3 mins to fetch the records. that is why it is successful.
But in the QA , it is taking more than 3 mins. so getting error-ed out. Not sure why syncTimeout setting is not having any impact.
Regards,
Muni.

No response available

Hi,
this may seem like an obvious question but... here it goes anyway. PI is used to call receiver (web service) at an external company through soap channel.
Sometimes, not often, I receive errors such as
<?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.engine.interfaces.messaging.api.exception.MessagingException: No response available.</SAP:AdditionalText>
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
This seems like an error at the provider...
How can I prove it to the provider ? They say the response may be lost on our side.
Thanks.

Hi Thierry Dagnino,
I am also getting this error. But in my case it is SOAP to RFC synchronous scenario.
BizTalk calls XI web service to send data. XI then sends the data to ECC system by calling a RFC enabled function module.
What was the cause of your error? How did you resolve it?
I will be grateful to you if you can tell me the possible root cause of this error?
Thanks & Regards
Gopal

Sorry, No Valid Responsibility Available

Dear All,
We have defined the users and Responsibilities. But whenever i am logging into the user, system is showing the two responsibilities but when i clicking any one of the responsibility, Its showing an error as "Sorry, No Valid Responsibility Available.
*Note : We have done Function and Menu Exclusion as per User Responsibility Matrix.*
Please suggest me what could be the reason.
Thanks & Regards,
Aditya

Check this forum, same kind of discussion before.
Function not available to this responsibility. -- Error
Re: No functions available for User Management Responsibility
Responsibility not shown

On the Apple Watch, has anyone figured out a way (if possible) to remove some of the redundant auto responses available when using Messages?

There are some responses that always show which I would never use, such as BRB, that I'd like to completely remove. There are other responses that are excessively redundant. I don't need Thx, Thanks, Thank you. and Thanks! as separate available auto responses every single time. Anyone else had better luck figuring that out?
Overall I'm really liking the Watch so far. The only thing bringing it down is sone of those small details.

Visit the Apple Watch app, then go to My Watch > Messages > Default Replies.
You can add your own but there will still be Apple auto default replies too.
Kinda lame. Hope there's a new option to get rid of those in the future. I'd rather ALWAYS dictate and not have those 'smart responses' there at all.

Receiver RFC adapter issue! Please help!

Hi Experts,
I have 4 XI interfaces. All of these are Webservice to RFC scenarios. Moreover all of them are synchronous.
Request message: Webservice (SOAP Adapter) ---> XI -
> RFc Adapter ---> ECC Function modules
Response message: Webservice (SOAP Adapter) <- XI < RFc Adapter <- ECC Function modules
As you can see above, external system calls XI web service via SOAP Adapter. The input data is then sent from SOAP Adapter to RFC adapter to call RFC function module in the receiving side. The receiving system is SAP ECC system.
The receiver ECC system has two instances. For example SP0 ad SP1.
In the receiver determination step we have maintained a rule such that if the Plant value in the input message is XYZ then send data to SP0. But if the plant value in ABC then send data to SP1.
This Conditional rule is working fine.
However we are getting couple of issues with only one instance of ECC (SP0).
1. com.sap.engine.interfaces.messaging.api.exception.MessageExpiredException: Message badfa070-b163-11de-a4c1-001cc495e48a(INBOUND) expired
2. NO_MAPPINGPROGRAM_FOUND. Mapping program is not available in runtime cache: Object ID C2B41FFDFD4635BAB1E41AE53C0D10CE Software Component 5394F420463611DAC1CFFBBC0A01BC16
3. com.sap.engine.interfaces.messaging.api.exception.MessagingException: No response available
The above listed errors are generated occasionally. Sometimes no errors are generated even when the same input data is sent again and message is successfully processed.
I have verified the input data and everything is OK with that.
Mapping object is available in XI and cache was also refreshed. I additionally reactivated the objects in XI as well.
So what could be the real root cause of this? Please help!
Thanks
Gopal

1. com.sap.engine.interfaces.messaging.api.exception.MessageExpiredException: Message badfa070-b163-11de-a4c1-
001cc495e48a(INBOUND) expired
Check the Timeout parameter of your adapter.....for requests which expire with this error confirm from the SAP end that the message processing is done well within the Timeout period of the adapter.
Refer this note for more info on the above occuring error and the possible way to avoid it: https://service.sap.com/sap/support/notes/791379
Update:
Even problem 3 seems to be occuring due to insufficient Timeout specified for the adapter.....if possible try increasing the Timeout in VA
Regards,
Abhishek.
Edited by: abhishek salvi on Oct 6, 2009 1:42 PM

Error "soap fault: No operation available for request" in proxy to soap Scenario

Hi Experts,
Unable to trace the below error when pushing the message from RWB while testing the PROXY to SOAP interface
Delivering the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: No operation available for request {http://schemas.xmlsoap.org/soap/envelope/}Envelope.
Thank you very much if any one provided the solution
Regards,
Yugandhar

Hi Yugandhar,
Check the below thread,
Connecting from SAP PI To Salesforce
Regards
RK N.

SOAP Receiver Adapter - Read Header data on Synchronous Response

I have a scenario - flat file to SOAP. The web service provider sends a response that contains data in the Header that I need to access. I have tried to use the "Do Not Use SOAP envelope" option on my receiver SOAP adapter, and I have configured my request message type to include the soap envelope elements. However I'm getting the following error from the web service
com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 415 Cannot process the message because the content type 'application/xml' was not the expected type 'text/xml; charset=utf-8'.
I've read some inputs on this error that say to use the Transform bean to adjust the content to text/xml. However I'm not sure how to do that. If that is the correct resolution to my problem, can someone provide detailed steps on how to add the Transform bean to the adapter module. I have no experience with adding items to the module tab.
If there are other ways to tackle this scenario to get access to the SOAP Header from the SOAP receiver adapter, please share those as well.
Thanks in advance.
Chris

Resolved with the following blog
/people/varadharajan.krishnasamy/blog/2007/01/09/troubleshooting-soap-message--xi

SOAP Response error:

HI Experts,
Here my scenario is RFC PI SOAP synchronous interface. While sending the message from PI receiver system is expeting SAOP envelop I added this envelop with xslt mapping. Even response message is coming with SOAP envelop I removed with Xslt.. now I am getting below error message in response:
*Here i am not using any authoentication. it is not required..*
In SXMB_moni:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 401 Unauthorized</SAP:AdditionalText>
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
In communication channel:
Description
23.11.2011 14:45:11.557     Information     The message was successfully received by the messaging system. Protocol: XI URL: http://r3vidci.got.volvo.net:52000/MessagingSystem/receive/AFW/XI Credential (User): PIISUSER
23.11.2011 14:45:11.564     Information     Using connection SOAP_http://sap.com/xi/XI/System. Trying to put the message into the request queue.
23.11.2011 14:45:11.568     Information     Message successfully put into the queue.
23.11.2011 14:45:11.572     Information     The message was successfully retrieved from the request queue.
23.11.2011 14:45:11.573     Information     The message status was set to DLNG.
23.11.2011 14:45:11.577     Information     Delivering to channel: SOAP_Receiver_BOSS_VID
23.11.2011 14:45:11.577     Information     MP: entering1
23.11.2011 14:45:11.579     Information     MP: processing local module localejbs/AF_Modules/MessageTransformBean
23.11.2011 14:45:11.599     Information     Transform: using Transform.Class: $identity
23.11.2011 14:45:11.634     Information     Transform: transforming the payload ...
23.11.2011 14:45:11.637     Information     Transform: successfully transformed
23.11.2011 14:45:11.638     Information     MP: processing local module localejbs/sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean
23.11.2011 14:45:11.676     Information     SOAP: request message entering the adapter with user J2EE_GUEST
23.11.2011 14:45:11.695     Information     SOAP: completed the processing
23.11.2011 14:45:11.696     Information     SOAP: continuing to response message bf2ba0ac-15e1-11e1-cc01-00000c601d4e
23.11.2011 14:45:11.696     Error     SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 401 Unauthorized
23.11.2011 14:45:11.698     Error     MP: exception caught with cause com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 401 Unauthorized
23.11.2011 14:45:11.699     Error     Adapter Framework caught exception: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 401 Unauthorized
23.11.2011 14:45:11.700     Error     Delivering the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 401 Unauthorized. Setting message to status failed.23.11.2011 14:45:11.704     Error     The message status was set to FAIL.

Hi Rajesh,
I tried with XMLSPY.. i am able to send and get the responce witout any authentication.. I gone through vijay's blog... but i din't find any solution in that..
one more thing.. here inteface is sending from SAP portal system > SAP ECC> SAPI--> webservice(Microsoft system). whenever Portal team sending the message to SAP they are getting below error"
call to messaging system failed: com.sap.engine.interfaces.messaging.api.exception.MessagingException: XIAdapterFramework:GENER
In PI I am getting below error:
.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 401 Unauthorized

Handling Soap Fault Response.

Hi All,
I have a Proxy to SOAP scenario.
While testing from SoapUI --
I am getting response for the valid input and for the invalid input the response is below.
In the scenario through SAP PI , the valid input given from the HTTP client is getting a valid response and the scenario is running fine.
But while checking the negative test, giving the invalid input, it is ending in a System error in PI.
We have to handle this and send the error back to the source system.
FAULT RESPONSE IN SoapUI :
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
   <soap:Body>
      <soap:Fault>
         <faultcode>soap:Client</faultcode>
         <faultstring>System.Web.Services.Protocols.SoapException: Server was unable to read request. ---> System.InvalidOperationException: There is an error in XML document (6, 45). ---> System.InvalidOperationException: Instance validation error: 'AD' is not a valid value for Currency.
   at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReader1.Read1_Currency(String s)
   at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReader1.Read2_ConversionRate()
   at Microsoft.Xml.Serialization.GeneratedAssembly.ArrayOfObjectSerializer.Deserialize(XmlSerializationReader reader)
   at System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader, String encodingStyle, XmlDeserializationEvents events)
   --- End of inner exception stack trace ---
   at System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader, String encodingStyle, XmlDeserializationEvents events)
   at System.Web.Services.Protocols.SoapServerProtocol.ReadParameters()
   --- End of inner exception stack trace ---
   at System.Web.Services.Protocols.SoapServerProtocol.ReadParameters()
   at System.Web.Services.Protocols.WebServiceHandler.CoreProcessRequest()</faultstring>
         <detail/>
      </soap:Fault>
   </soap:Body>
</soap:Envelope>
*System error message in SAP PI* :
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?> <SAP:Error SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"><SAP:Category>XIAdapterFramework</SAP:Category><SAP:Code area="MESSAGE">GENERAL</SAP:Code><SAP:P1/><SAP:P2/><SAP:P3/><SAP:P4/><SAP:AdditionalText>com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: System.Web.Services.Protocols.SoapException: Server was unable to read request. ---> System.InvalidOperationException: There is an error in XML document (1, 328). ---> System.InvalidOperationException: Instance validation error: 'US' is not a valid value for Currency.
   at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReader1.Read1_Currency(String s)
   at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReader1.Read2_ConversionRate()
   at Microsoft.Xml.Serialization.GeneratedAssembly.ArrayOfObjectSerializer.Deserialize(XmlSerializationReader reader)
   at System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader, String encodingStyle, XmlDeserializationEvents events)
   --- End of inner exception stack trace ---
   at System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader, String encodingStyle, XmlDeserializationEvents events)
   at System.Web.Services.Protocols.SoapServerProtocol.ReadParameters()
   --- End of inner exception stack trace ---
   at System.Web.Services.Protocols.SoapServerProtocol.ReadParameters()
   at System.Web.Services.Protocols.WebServiceHandler.CoreProcessRequest()</SAP:AdditionalText><SAP:Stack/><SAP:Retry>M</SAP:Retry></SAP:Error>
I want to capture the text in Fault string in the Fault response and send it back to the Source system.
I have referred many blogs but i am unable to do it.
Will java mapping work as this is a response from the Target Webservice and NOT an errorin PI.

Hello.
If your scenario is ECC -> Proxy -> PI -> SOAP -> WS -> SOAP -> PI -> Proxy -> ECC.
In ESR create a Fault Message Type, and added to your Service Interface (Outboun/Inbound), use a XSLT mapping to take anyway format response, rebuid your proxy ABAP and see your "message fault" on exception tab.
this works for me.
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:xs="http://www.w3.org/2001/XMLSchema">
     <xsl:output method="xml" version="1.0" encoding="UTF-8" indent="yes"/>
     <xsl:template match="/">
          <ns0:FMT_ResponseAuth>
                    <standard>
                         <faultText>
                              <xsl:value-of select="//detail"/>
                         </faultText>
                    </standard>
          </ns0:FMT_ResponseAuth>
     </xsl:template>
I hope this help you.
Edited by: KrlosRios on Nov 2, 2011 5:59 PM

Error in response message

Hi Experts,
I am doing SAP to Portal system scenario using SOAP. I am sending request to Portal and getting response from their system.
I need to put the response message in file. While capturing response message i am getting error as below.
com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: No such operation 'createDocumentWithAttachmentsRequest'
I am getting XML string in response message.
Can anyone please suggest how to capture XML string in the respone message.. if i need to do any java mapping what logic exactly i need to build.
Appreciate your valuable inputs.
Thanks,
Srikanth

Hi Srikanth,
>>>Can anyone please suggest how to capture XML string in the respone message.. if i need to do any java mapping what logic exactly i need to build.
Please see the below link, it will explain you that how to capture SOAP Response.
SOAP Response Message Capture in PI 7.1
Regards,
P.Rajesh

Error at SOAP response channel

Dear All,
I have created a synchronous PROXY to SOAP scenario. But I am getting the following error in the receiver SOAP Adapter.
Message processing failed. Cause:
com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP:
response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION -
soap fault: System.Web.Services.Protocols.SoapException: Server was unable to
process request. ---> System.NullReferenceException: Object reference not set
to an instance of an object.
--- End of inner exception stack trace ---
Please suggest what may be the reason for it.
Thanks and Regards,
Rana Brata De
SAP PI Consultant

Hi,
We have faced similar problem in production some time back .
At target system end web service validates the payload below inserting into back end system (d/b).If the validation fails then it throws the error to PI system .
For us the backend system notified that there end front end service validation failed due to data issue and thrown exception to PI.
Share the payload to target system folks and ask them to check ,they will have test suite to test it from there end . If not share the time at which you received error,they will check there logs and update you on the cause .
Regards
Venkat

SOAP response message error

Hi,
We have a scenario where in we perform a synchronous send from a BPM and post the request to a url using a SOAP receiver channel.
When we test the scenario,the message fails in PI with the following error "com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Internal Server Error"But when we try to test the same in SOAPUI by using the same payload,we do not have any issues in getting the response back.
Please could anyone advise on what could be the issue.
Thanks and Regards,
Induja

>
Induja Ramesh wrote:
> Resolved.
How?

SOAP: response message contains an error XIServer/UNKNOWN/ADAPTER.JAVA_EXCE

Hi ,
I am getting below error in SOAP reciever channel.
Delivering the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIServer/UNKNOWN/ADAPTER.JAVA_EXCEPTION - com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Connection SOAP_http://sap.com/xi/XI/System is currently not started. at com.sap.aii.adapter.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:996) at sun.reflect.GeneratedMethodAccessor501_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(Interceptors_Transaction.java:38) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133) at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164) at $Proxy2662_10002.process(Unknown Source) at com.sap.aii.af.app.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:275) at sun.reflect.GeneratedMethodAccessor326_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(Interceptors_Transaction.java:38) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133) at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164) at $Proxy114_10002.process(Unknown Source) at com.sap.aii.adapter.soap.web.MessageServlet.callModuleProcessor(MessageServlet.java:175) at com.sap.aii.adapter.soap.web.MessageServlet.doPost(MessageServlet.java:470) at javax.servlet.http.HttpServlet.service(HttpServlet.java:727) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:163) at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:82) at com.sap.engine.services.servlets_jsp.server.servlet.AuthenticationFilter.doFilter(AuthenticationFilter.java:124) at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:74) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:425) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:289) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:376) at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:85) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71) at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:160) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71) at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:67) at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71) at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60) at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71) at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27) at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71) at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29) at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71) at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:309) at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.run(Processor.java:222) 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:152) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:247)

Hi,
Can you please elaborate more on your problem.
Regards,
Raghu.

Passing parameter to response pipeline

Hi,
I'm trying to do the following:
- PS1 calls a BS1 that inserts some stuff to a database. This BS1 doesn't return anything (I'm using some database exposed through JCA adapters).
- I need to know the specific messageID that reached that BS1 (and was inserted), on the response pipeline in order to block the pipeline until I got some response available for that messageID.
I know that:
- when you call a routenode your soap body is removed. so if your BS doesn't return anything you are stuck with a null body on your response pipeline.
My question is: how can I pass a messageID (that was previously defined on SOAP body on request pipeline) to response pipeline on that same PS1?
My guess is: using some transport header that isn't overwrited during runtime!! but which one? I'm using http transport.
thanks for all your help! :)
Edited by: enok on 18-May-2010 10:14

I'm trying to do the following:
- PS1 calls a BS1 that inserts some stuff to a database. This BS1 doesn't return anything (I'm using some database exposed through JCA adapters).
- I need to know the specific messageID that reached that BS1 (and was inserted), on the response pipeline in order to block the pipeline until I got some response available for that messageID.
As you have indicated that JCA BS is a request only (no response). So what is that you are expecting as response "block the pipeline until I got some response"?
Can you please explain?I know that:
- when you call a routenode your soap body is removed. so if your BS doesn't return anything you are stuck with a null body on your response pipeline.
My question is: how can I pass a messageID (that was previously defined on SOAP body on request pipeline) to response pipeline on that same PS1?
Easy. Store the messageID (that was previously defined on SOAP body on request pipeline) in a xml variable in request pipeline before the route node. Use the same varaible to populate the response payload in response pipelineMy guess is: using some transport header that isn't overwrited during runtime!! but which one? I'm using http transport.
Don't go with above approach even though it solves your use-case. storing in varaible is lot elegant and easy to implement/maintain.Manoj

MessagingException: No response available

Similar Messages

Maybe you are looking for