MessageExpiredException

Hello Experts,
We are facing an issue in production system of PI, that all the synchronous sender SOAP communication channels went to error with "SOAP: Call failed: com.sap.engine.interfaces.messaging.api.exception.Message Expired Exception: Message <message ID> (OUTBOUND) expired.
Please help us in fixing this issue.
Regards,
Sunitha

Hi,
We performed the node 1593920 - Synchronous SOAP sender calls:
fine tune PI under high load and apply the recommendation. For a night the messages were processed successfully. But again we see the channels into error.
There was a loadbalancer upgrade was done before the error came. But we are not sure whether this might effect the PI system. Still we changed the thread count and restarted the system. For a while the messages got successfully processed, but after sometime the channels went to error.
Thanks in advance.
Regards,
Sunitha

Similar Messages

MessageExpiredException error in JDBC - RFC scenario using BPM.

Scenario: JDBC( Asynch)- RFC( Synch)- JDBC (Asyc)
We are using XI to read oracle table records to insert the records in R/3 and after the insert in R/3 we return a sap code to update in oracle db.
When we try to process 10 or less rows from db, the process is successfully running, but when we try processing more records we are getting the following error. We tried increase the timeout setting in RFC adapter as per the SAP note and forum.
Detailed error: 
com.sap.aii.af.ra.ms.api.MessageExpiredException: Message 443jdjsd-e432-2ec8-e100-000046eb2e5f(INBOUND) expired.
If I use correlation in asynchronous RFC instead of synchronous RFC, will this solve the problem or is there any better solution for this ?
Any useful steps to change the synchronous RFC to asynchronous RFC in BPM would be great.
Thanks
Steve

Hi,
1. Any suggestions to meet this requirement in XI ?
>>>One option is using ABAP Proxy . Instead of calling Sync. RFC, call synchronous Proxy. So your client proxy, should receive all 200-300 rows at a time, and inside the proxy, and call the RFC. Once all the reocrds are processed, send the response back to BPM
You can try out this.
I think, probably you may require to do looping for each Row.i.e For each row the call the RFC.. As of now try to go with Proxy.
Also try to findout, why the RFC is taking that much of time.. So check for the provision of tuning in the RFC side..
Hope this helps,
regards,
Moorthy
Message was edited by: Krishna Moorthy P

Intermittent issue in PI-com.sap.aii.af.ra.ms.api.MessageExpiredException

Hi everbody,
We are with Intermittent problem in SAP PI 7.0.
Some messages have this error below:
<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.MessageExpiredException:
Message 4bdefeac-f3e8-01de-e100-8000ac103265(INBOUND)
expired</SAP:AdditionalText>
The error above is appearing in Synchronous messages in trx sxi_monitor.
We read the note 730870 and the timeout parameters is ok.
We tried to stop/start in 'SAP XI AF CPA Cache' and 'SAP XI AF Messaging' but it not worked.
We have one message in a SAP but I think they do not have idea yet.
The adapters are involved are RFC and SOAP.
We changed the parameters:
- 'xiadapter.inbound.timeout.default' from 180000 to 300000 .
- 'syncMessageDeliveryTimeoutMsec' from 300000 to 600000 .
- 'syncMessageRemover.checkInterval' from 60 to 5 .
Please, could you have some idea to resolve this issue ?
ps: The error started after the stop/start for renew certification in keystore (j2ee) .
Best Regards,
Victor Yamanaka

Hi victor,
could you please refer the Note 791379
Extract from a FAQ :
At the beginning of a synchronous RFC call the RfcAdapter (sender channel) builds up the XI request-message and will send this to the Adapter Engine with a timeout. After this it will wait till the response-message reaches or the timeout expires. In case of timeout the exception named above is thrown. The timeout used by RfcAdapter for synchronous calls can be configured for the whole RfcAdapter as a property of the RfcAdapter J2EE Service. To change it's value open the service properties sheet like and change the value of "syncMessageDeliveryTimeoutMsec". Notice that this value is specified in milliseconds. After changing the property store the properties by clicking the save-button (disk symbol) on top of the page.If a similar error messages is shown for a receiver channel the timeout setting is done in the inbound XI-Adapter of the Adapter Engine and not via the above described setting in the RFC-Adapter. The value of xiadapter.inbound.timeout.default from J2EE Service 'SAP XI Adapter: XI' is used in this case.
similar forum post :com.sap.aii.af.ra.ms.api.MessageExpiredException
see if you have not referred this already.
Regards,
Srinivas

MessageExpiredException in the Sync XI--JDBC scenario

Hello experts,
I am developing a scenario
run a report in ECC, the report will get data from other database via JDBC and then display in ECC client.
thus i develop a sync scenario,
but sometimes i sent the request, and then wait for 3 minutes, at last get the exception: com.sap.engine.interfaces.messaging.api.exception.MessageExpiredException
This can not be always reproduced, but it happens very frequently.
I searched in the forum it seems lots of people get the trouble but i didnt see a solution.
I dont think expand the timeout parameter is a good idea, because when it works, it only take 1 second to complete the whole interaction, but when it doesnt, it takes 3 minutes then timeout.
Could you give me some guide here? Thanks a lot in advance!
Best regards, Charlie

Hi Charlie,
At times, it happens in Synchronous calls to XI box. One way I suggest is to handle the situation with optimum time-outs and adjusting in the ABAP reports (if possible - at least try to recall the service).
[How to Investigate Timeouts In Synchronous XI/PI Scenarios|http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c059d583-a551-2c10-e095-eb5d95e03747?quicklink=index&overridelayout=true] could help to find out the time-out settings.
Mean time, you can check why the time-outs are occurring. Does it happen because of Network latency, database time-out etc.
Let me know your thoughts on this approach. I am also looking forward for better handling of this situation.
Regards,
Nikhil Bose

JDBC adapter MessageExpiredException

Hi there,
I am using JDBC adapter in a integration process. After a call is made to the database, it is coming back with the following error:
com.sap.aii.af.ra.ms.api.MessageExpiredException: Message aa3cb50e-4e57-eb4e-9d79-0f4a9759a6b4(INBOUND).
This error does not occur every time but only occurs i.e. once in 10 times.
What could be the reason for it and what required to prevent it.
1. Is it that the database to where the call is made is real slow and not fine tuned or
2. Do I need to change any timeout parameter in XI for JDBC adapter.
Please advise.
Regards,
Faiq

Hi Faiq -
There is a timeout property that determines how long the XI messaging system waits for synchronous responses. Once the timeout is reached, a MessageExpiredException can occur.
This property name is xiadapter.inbound.timeout.default within the SAP XI Adapter: XI J2EE service (access from J2EE visual admin tool).
See Note 791379 for more details.
Regards,
Jin

MessageExpiredException: Sync application request expired..

Hi,
we are calling a SOAP HTTP AXIS receiver (web service) HTTP. Sometimes the service providers request
takes 3 minutes to reply and we get the following exception :
com.sap.engine.interfaces.messaging.api.exception.MessageExpiredException: Sync application request expired.. Setting message to status failed.
I've set timeout parameter to 300000 milliseconds for parameter timeout of AF_Adapters/axis/AFAdapterBean but the timeout is still less... is there another place I need to increase the timeout.
Thanks.
Thierry

Your guess is as good as mine, but the question to answer here is, why is the response taking 3 minutes. If this is by design, then you may want to look at the design and see if asynchronous messaging works better for you. Playing with timeout will only lead you to a point but with 3 minutes of delay in a synchronous service is simply unacceptable even if there is no human being on the consumer side.
Thanks
KK

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

Issue with BPM Consuming a lot of Time

Thanks guys for ur support:
I have the following issue: We have a working BPM scenario in Dev and it used to take 8 sec for processing now we moved objects to QA and with other issues of J2ee engine , BPM is taking too much time like 3 min around
We fixed all the outstanding basis issues like changing parameters etc but nothing improved this scenario.
I dont see any major issue as both dev and qa have identical config any ideas please?
and in some cases i get message saying :
com.sap.aii.af.ra.ms.api.MessageExpiredException: Message f5035300-a76a-11dc-ab84-0017a451bb4c(OUTBOUND) expired.
     at com.sap.aii.af.ra.ms.impl.core.service.Call.execute(Call.java:199)
     at com.sap.aii.af.ra.ms.impl.ServicesImpl.call(ServicesImpl.java:192)
     at com.sap.aii.adapter.xi.ms.XIEventHandler.onCall(XIEventHandler.java:317)
     at com.sap.aii.af.ra.ms.impl.ConnectionImpl.call(ConnectionImpl.java:336)
     at com.sap.aii.af.mp.soap.ejb.AFCallerApplication.perform(AFCallerApplication.java:117)
     at com.sap.aii.messaging.srt.ApplicationBubble.onMessage(ApplicationBubble.java:29)
     at com.sap.aii.messaging.srt.ExtensionBubble.onMessage(ExtensionBubble.java:56)
     at com.sap.aii.af.mp.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:906)
     at com.sap.aii.af.mp.module.ModuleLocalLocalObjectImpl0_3.process(ModuleLocalLocalObjectImpl0_3.java:103)
     at com.sap.aii.af.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:264)
     at com.sap.aii.af.mp.processor.ModuleProcessorLocalLocalObjectImpl0_0.process(ModuleProcessorLocalLocalObjectImpl0_0.java:103)
     at com.sap.aii.af.mp.soap.web.MessageServlet.callModuleProcessor(MessageServlet.java:174)
     at com.sap.aii.af.mp.soap.web.MessageServlet.doPost(MessageServlet.java:441)
     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:387)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:160)
     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:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)

Hi Bujji,
Did you check the disk space available on both the machines? At database level did you compress the log files size? If it is taking much time means.. problem must be with the system resourses..!!
VJ

Performance problem in RFC to JDBC interface

Hello everybody!
i'm working whit SAP PI 7.1
We defined some interfaces RFC - PI - JDBC (SQL server) but we have some performance problem.
If we have many row to write on the table then interface finish in timeout :
Synchronous timeout exceeded.
Returning to application. Exception: com.sap.engine.interfaces.messaging.api.exception.MessageExpiredException: Message 1d1f00b0-fecf-11de-8738-0015600446f0(OUTBOUND) expired.
I read the PI tuning document and i tried to apply configuration whit Advanced Adapter Engine but whitout result.
Now we want change the timeout in visual admin and maybe we solve the error but i'm asking myself....:
It's normal that for write 1500 row in a table we need more than 4 minuts????
It's possible accelerate this process??? After go live we will write messages whit more than 50.000 row.
somebody may help me?
PS: please no link to tuning guide or to notes (to increase the timeout parameter).

This could be because your Database system (JDBC server) is taking more time to insert. The problem is not on PI side but on the receiving system side. Try inserting the same number od rows on the database server itself and check for the time taken for execution. Adding indexes on your database table solves the issue lot of times.
Here PI is not the culprit but definitely the receiver system.
VJ

HTTP request failed. Error code: "500". Error message

Hi ,
When we are trying to test webservices (exposed webservice in PI) scenarios in PI box we are getting error related Adapter framework service
HTTP request failed. Error code: "500". Error message: "Internal Server Error [http://xxxx:xxxx/AdapterFramework/rtc]"
in the RWB it is showing that
com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.engine.interfaces.messaging.api.exception.MessagingException: XIAdapterFramework:GENERAL:com.sap.engine.interfaces.messaging.api.exception.MessageExpiredException: Message 01d76ce0-972e-11e0-c652-b25394b91e0c(INBOUND) expired
Can any body help .
Edited by: subhaniABAP on Jun 15, 2011 11:30 AM

Hi,
If you want to resolve this error when dealing with the messages, please try the cache refresh with the link:
http://host:j2eeport/CPACache/refresh?mode=full
And also go thorugh:
- In Integration Repository/Directory go to menu Environment ->
Clear SLD Data Cache
- In R/3 go to transaction SXI_CACHE -> menu XI Runtime Cache -> Start
Complete Cache Refresh
MESSAGE EXPIRED:
Increase the value of the timeout parameter 'xiadapter.inbound.timeout.default' under Services -> 'XPI Adapter:XI'
to a higher value say '600000'.
Regards,
Caio Cagnani

Messages got stuck in Adapter engine

We are doing http to RFC sysnchronous scenario
Message got stuck in adapter engine.so we are getting 500 HTTP timeout error in Http client.
Please help us to find why messages got stuck in Adapter engine.
Below Adapter engine audit log message is pasted for your reference.
Audit Log message:
Time Stamp Status Description
26.09.2008 06:33:54 Success Message successfully received by messaging system. Profile: XI URL: http://devsap01:51000/MessagingSystem/receive/AFW/XI Credential (User): PIISUSER
26.09.2008 06:33:54 Success Using connection RFC_http://sap.com/xi/XI/System. Trying to put the message into the request queue.
26.09.2008 06:33:54 Success Message successfully put into the queue.
26.09.2008 06:33:54 Success The message was successfully retrieved from the request queue.
26.09.2008 06:33:54 Success The message status set to DLNG.
26.09.2008 06:33:54 Success Delivering to channel: RFC_out_Test
26.09.2008 06:33:54 Success MP: entering
26.09.2008 06:33:54 Success MP: processing local module localejbs/RfcAFBean
26.09.2008 06:33:54 Success RFC adapter received a synchronous message. Attempting to send sRFC for ZFTestRFC
26.09.2008 06:33:54 Success RFC adapter received a synchronous message. Attempting to send sRFC for J2EE_GUEST
ime Stamp Status Description
26.09.2008 06:56:15 Success MP: leaving
26.09.2008 06:56:15 Error Delivery of the message to the application using connection RFC_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.MessageExpiredException: Sync application request expired.. Setting message to status failed.
26.09.2008 06:56:15 Error The message status set to FAIL.
26.09.2008 06:56:15 Error Returning synchronous error message to calling application: com.sap.aii.af.ra.ms.api.MessageExpiredException: Sync application request expired..
Kindly advise us on this issue.

Hi krish,
when i send a http request it got stuck in adapter engine with status "delivering" for some time....
We found that RFC got successfully executed in R/3 system but the synchronous message is not delivered to PI.since adapter engine message is having status "delivering"
after some time we got adapter engine message status as "cancelled with error"
Error is Message expired exception which you can see audit log message I have pasted in my previous post.
Meanwhile we also got HTTP timeout error in Http client.
Could you please tell me why it got stuck in Adapter engine with status "delivering" since RFC is executed successfully.
Why we are not getting synchronous message reply back to PI?

How to increase the waiting time for response in Adapter Engine not in IE

Hi Experts,
It is a SOAP to Proxy Synchronous interface. SOAP system is sending the request to PI, PI sending the same request to ECC system, After execution of some logic response back to PI in 7 minutes. In ABAP Stack(sxmb_moni) processing the response message also successfully with success flag after completion of these 7 minutes. But exactly 5 minutes later getting the error at Java Stack RWB- in communication channel monitoring i.e
com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.engine.interfaces.messaging.api.exception.MessageExpiredException: Message bd2bf8d0-b2c2-11e0-c383-001cc4fb5cb7(OUTBOUND) expired. We have set the "runtime-HTTP_TIMEOUT" parameter as 3600. thats why in Integration engine it is processing successfully.
kindly suggest me how to increase the waiting time for response in Adapter Engine. Exactly after 5 mins getting the above error in rwb, but in Integration Engine getting successful flag after 7 mins until then it is waiting for response with status flag Log version.
Thanks & Regards,
Srihari.

Hi,
Please see
How To... Investigate Timeouts In Synchronous XI/PI Scenarios
It will answer all your queries
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c059d583-a551-2c10-e095-eb5d95e03747?QuickLink=index&overridelayout=true

Synchronous scenario(ABAP proxy to HTTP_AAE) getting error exception as "Message Expired Exception"

Dear All,
I have done all the configuration for ABAP proxy scenario using AAE/ICO as per the below "how to guide" using SOAP as sender adapter using xi protocol. My SAP PI is 7.4 dual stack system. here third party is not a webservice its HTTP based we server so no wsdl.
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/70066f78-7794-2c10-2e8c-cb967cef407b?overridelayout=t…
However after running the scenario from ECC I am getting the exception as "Returning to application. Exception: com.sap.engine.interfaces.messaging.api.exception.MessageExpiredException: Message 53289257-97e0-06d0-e100-00000a70d384(OUTBOUND) expired.". I do not have any connection problem to third party(bank) URL. moreover I am able to get the response from bank using classical scenario s in PI, but the response message is not getting pushed to ECC, rather its reaming in PI SXMB_MONI with status "Log version".
Thats the reason I am trying to do using ICO, but using ICO PI is not even sending the request out of PI to bank. Please see the below receiver communication channel message log.
Thanks,
Farhan

Hi,
As per the log, the message has started 23:18:02 and failed at 23.23:02 it took 5min time, if message is not process certain time this kind of errors comes up. Have you changed adapter type for existing SOAP communication channel or created new? provide complete log of the message from starting time to ending time if possible.

JDBC error with Oracle Database

Hi,
We are now facing some problems when using Oracle JDBC in XI JDBC Adapter, and this problem happens randomly.
Our oracle is ver 8.1.5, jdbc ver 9.2.0.1 ojdbc14.jar, J2RE 1.4.2 IBM AIX build ca142-20060824.
The following exceptions have been found in log viewer:
Exception caught when executing statement for table/stored proc. 'cgjs_zj_zjb' (structure 'SELECTSTMT'):
java.sql.SQLException: Io exception: There is no process to read data written to a pipe.
     at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:134)
     at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:179)
     at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:334)
     at oracle.jdbc.ttc7.TTC7Protocol.handleIOException(TTC7Protocol.java:3668)
     at oracle.jdbc.ttc7.TTC7Protocol.doOall7(TTC7Protocol.java:1986)
     at oracle.jdbc.ttc7.TTC7Protocol.parseExecuteDescribe(TTC7Protocol.java:850)
     at oracle.jdbc.driver.OracleStatement.doExecuteQuery(OracleStatement.java:2599)
     at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:2963)
     at oracle.jdbc.driver.OracleStatement.executeQuery(OracleStatement.java:653)
     at com.sap.aii.adapter.jdbc.SAXHandler.executeQuery(xml2sql.java(Compiled Code))
     at com.sap.aii.adapter.jdbc.SAXHandler.executeQuery(xml2sql.java(Inlined Compiled Code))
     at com.sap.aii.adapter.jdbc.SAXHandler.SQLsel(xml2sql.java(Compiled Code))
     at com.sap.aii.adapter.jdbc.SAXHandler.processList(xml2sql.java(Compiled Code))
     at com.sap.aii.adapter.jdbc.SAXHandler.endElement(xml2sql.java(Compiled Code))
     at com.sap.engine.lib.xml.parser.handlers.SAXDocHandler.endElement(SAXDocHandler.java(Compiled Code))
     at com.sap.engine.lib.xml.parser.XMLParser.scanEndTag(XMLParser.java(Compiled Code))
     at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java(Compiled Code))
     at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java(Compiled Code))
     at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java(Compiled Code))
     at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java(Compiled Code))
     at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java(Compiled Code))
     at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java(Compiled Code))
     at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java(Inlined Compiled Code))
     at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java(Compiled Code))
     at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java(Inlined Compiled Code))
     at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java(Compiled Code))
     at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java(Compiled Code))
     at javax.xml.parsers.SAXParser.parse(Unknown Source)
     at javax.xml.parsers.SAXParser.parse(Unknown Source)
     at com.sap.aii.adapter.jdbc.xml2sql.service(xml2sql.java:211)
     at com.sap.aii.adapter.jdbc.XI2JDBC.onInternalMessage(XI2JDBC.java:481)
     at com.sap.aii.adapter.jdbc.SapAdapterServiceFrameImpl.callSapAdapter(SapAdapterServiceFrameImpl.java:175)
     at com.sap.aii.af.modules.CallAdapterWithMessageBean.process_receiver(CallAdapterWithMessageBean.java:226)
     at com.sap.aii.af.modules.CallAdapterWithMessageBean.process(CallAdapterWithMessageBean.java:164)
     at com.sap.aii.af.mp.module.ModuleLocalLocalObjectImpl0_1.process(ModuleLocalLocalObjectImpl0_1.java:103)
     at com.sap.aii.af.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:264)
     at com.sap.aii.af.mp.processor.ModuleProcessorLocalLocalObjectImpl0_0.process(ModuleProcessorLocalLocalObjectImpl0_0.java:103)
     at com.sap.aii.af.listener.AFWListenerBean.onMessage(AFWListenerBean.java:267)
     at com.sap.aii.af.listener.AFWListenerLocalObjectImpl0_0.onMessage(AFWListenerLocalObjectImpl0_0.java:103)
     at com.sap.aii.af.ra.ms.impl.ServicesImpl.deliver(ServicesImpl.java:306)
     at com.sap.aii.adapter.xi.ms.XIEventHandler.onDeliver(XIEventHandler.java:1034)
     at com.sap.aii.af.ra.ms.impl.core.queue.RequestConsumer.onMessage(RequestConsumer.java:118)
     at com.sap.aii.af.ra.ms.impl.core.queue.Queue.run(Queue.java(Compiled Code))
     at com.sap.aii.af.ra.ms.runtime.MSWorkWrapper.run(MSWorkWrapper.java:56)
     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))
    Hope you can help me.
    B'Rgds,
                 YiNing

nice trick:)
This problem hasn't been solved yet, and now I found something harder to solve with this Oracle database and it's JDBC when I was using a synchronous scenario.
Check the following adapter log:
2007-02-28 10:03:53 Success Message successfully received by messaging system. Profile: XI URL: http://sapxidev:50000/MessagingSystem/receive/AFW/XI Credential (User): XIISUSER
2007-02-28 10:03:53 Success Using connection JDBC_http://sap.com/xi/XI/System. Trying to put the message into the request queue.
2007-02-28 10:03:53 Success Message successfully put into the queue.
2007-02-28 10:03:53 Success The message was successfully retrieved from the request queue.
2007-02-28 10:03:53 Success The message status set to DLNG.
2007-02-28 10:03:53 Success Delivering to channel: JDBC_RECV_PO_SBC
2007-02-28 10:03:53 Success MP: entering
2007-02-28 10:03:53 Success MP: processing local module localejbs/CallSapAdapter
2007-02-28 10:03:53 Success Receiver JDBC adapter: processing started; QoS required: BestEffort
2007-02-28 10:10:59 Success JDBC adapter receiver channel JDBC_RECV_PO_SBC: processing started; party , service PO_SYS
2007-02-28 10:10:59 Success SELECT BUSID, BUDAT, EDPER, BKTXT, XBLNR, BUZEI, BSCHL, HKONT, LIFNR, NEWUM, DMBTR, GSBER, MATNR, MENGE, ZUONR, SGTXT, XREF1, XREF2, XREF3, IDXSP, MWSKZ, RMVCT, RSTGR, ZTERM, ZFBDT, ZLSCH, XNEGP, KOSTL, AUFNR, LGORT_I, LGORT_O, GRUND, BWART, BSELM, STATS, ERFME, ZZFIELD2 FROM SAP_ZJB WHERE (STATS=O AND EDPER=9105)
2007-02-28 10:11:01 Success UPDATE SAP_ZJB SET STATS=U WHERE (STATS=O AND EDPER=9105)
2007-02-28 10:11:01 Success Database request processed successfully
2007-02-28 10:11:01 Success MP: leaving
2007-02-28 10:11:01 Error Delivery of the message to the application using connection JDBC_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.MessageExpiredException: Sync application request expired.. Setting message to status failed.
2007-02-28 10:11:01 Error The message status set to FAIL.
2007-02-28 10:11:01 Error Returning synchronous error message to calling application: com.sap.aii.af.ra.ms.api.MessageExpiredException: Sync application request expired..
Between the 2007-02-28 10:03:53 and 2007-02-28 10:10:59, what takes it so long to process? Also it happens randomly.
Since it is synchronous, the remote database table has been updated but the connection with XI has been disconnected for timeout issue, which lead to unrecoverable data inconsistent problem.
Anyone who can help me?

Issue in RFC to File Scenario

Hi All,
I am working on SAP PI 7.31 dual stack. I have configured a simple RFC to File scenario with aysnchronous interface. I am using classic configuration.
In Sender RFC channel monitoring I am getting the below exception and the file is not created.
"Error in processing caused by : com.sap.aii.af.lib.mp.module.ModuleException : call to messaging system failed: com.sap.engine.interfaces.messaging.api.exception.MessageExpiredException: Message xxxxxxxxxxx(OUTBOUND) expired".
Please suggest me what could be the issue.
Thanks,
Madhurima

Hi Madhu
As the log says the function module is try to execute synchronously.
But as per your requirement it should be asynchronous. Please remove all the export parameters from the function module.
Then re-import the function module in PI and adjust mapping and operation mapping.
Stop and start the RFC sender adapter so that it will get the new metadata of the function module.
The function module should have only import parameters so that it will act like a asynchronous interface.

MessageExpiredException

Similar Messages

Maybe you are looking for