Problem with SQL system's interfaces.

[svalluri23]

Hi Experts,

There are a Proxy to JDBC Synchronous interface in Production environment. Here getting the error " XIAdapterFramework- com.sap.engine.interfaces.messaging.api.exception.MessageExpiredException: Message

4e53d84e-9a45-363a-e100-0000960096aa(INBOUND) expired". We can able to see the inbound payload from R/3 system but can't able to get the response payload from Sql system. At this time in R/3 system's T.code smq2 messages stucking in queues with status" sys fail" with description as " An exception occurred that was not caught. Particularly for this SQL server's interfaces are not working remaining all working smoothly. Asynchronous interfaces are working at the same time.

BASIS team restarted the java stack of PI system, immediately all stucked messages in queues were cleared and issues resolved automatically, but again and again repeating only after 6pm since last 3 days, after restarting the PI java stack automatically resolving the problem. It is not at all the right solution bcz it is PRODUCTION System. Kindly suggest me.

Thanks & Regards,

Srihari.

[pedro_baroni3]

Hi Srihari,

See thread below:

[MessageExpiredException in the Sync XI--JDBC scenario|;

and SAP Notes

[1356789 - Configuring timeout for dummy SQL query in advanced mode|https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1356789]

[1078420 - XI/PI JDBC Adapter: Setting JDBC driver properties for DB|https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1078420]

[1586058 - XI/PI Adapter for SQL Server:Overcoming DB Connection Issues|https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1586058]

[1579879 - Adapter Framework - Message expired exception|https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/sno/ui_entry/entry.htm?param=69765F6D6F64653D3030312669765F7361706E6F7465735F6E756D6265723D3135373938373926]

Regards.

Pedro Baroni

[svalluri23]

Thanks Barony for your reply, Actually it happened due to network issues.

Regards,

Srihari.