MessageExpiredException: during soap to rfc synchronous call

[mrudularane]

Hello Experts ,

We are having soap to rfc synchrnous scenario . But we are getting MessageExpiredException: or no response available error for the same . Also there are no dumps we can see in crm which is our receiver . But if we run rfc manually then we are getting response within seconds . Also when we are putting debugger in rfc and pushing data from altova , it is not reaching to the rfc as debugger is not initiating only and giving the error .Why is it so ?

We have done cache refresh as well as restarted PI as well as CRM servers.

Kindly help .

Regards ,

Mrudula Rane

[pvishnuvardan_reddy · Accepted solution]

Hi Mrudula,

In addition to souvik reply, can you also please check what is the synchronous time maintained in PI system, beyond which PI system will throw messageexpiredexception.

Regards

[mrudularane · Accepted solution]

Hi Vishnu ,

We have checked the above link .

When we go to NWA , we are not getting any option like java system properties .

Also can you please tell me where to check SyncTimeout parameter inside PI Message monioring ?

We have checked in trace level and found <Trace level="1" type="T">Timeout: 300</Trace> .

Regards ,

Mrudula

[pvishnuvardan_reddy · Accepted solution]

Hi Mrudula,

Can you let me know the PI version you are working on.

In NWA, we need to navigate through Configuration->Infrastructure->Java System Properties

Regards

[pvishnuvardan_reddy · Accepted solution]

Hi Mrudula,

We need to maintain the timeout parameter in the SOAP sender channel such that the message queue for specific instance will wait this much time before throwing expiration error.

Refer the below note on this

1621719 - Timeout parameters in SOAP Sender/Receiver Adapter

Setting a Channel-Specific Timeout - Advanced Adapter Engine - SAP Library

If we maintain channel specific timeout, then this will get precedence over the global time out parameter.

Can you check this and let us know the outcome

[mrudularane · Accepted solution]

Hi Vishnu ,

Our version is 7.31.

But let me tell you something.  We are having 2 PI servers of different clients with 7.31 version but we can see java system properties on the other one .

then what is the problem with this one ?

Also can you please tell me where to check SyncTimeout parameter inside PI Message monioring ?

We have checked in trace level and found <Trace level="1" type="T">Timeout: 300</Trace> .

Regards ,

Mrudula .

[pvishnuvardan_reddy · Accepted solution]

Hi Mrudula,

It's very weird that you can not see some tabs in NWA even though you are on PI 7.31 version.

When you say two PI system clients, is there any dependency between them and for the configuration/runtime/design, which PI system is being used.

Also, does post installation steps are done properly on this one?

Regards

[mrudularane · Accepted solution]

Hi Vishnu ,

Yes actually it is weird .

One more thing . you have taken 'client' word wrongly . I did not mean like client 100 and client 200 etc. It means we are working on two different projects (clients). So of course there is no dependency at all .

We are not sure about post installation steps as we have not configured the server . We are just supporting them .

Can you please tell me where to check post installation steps ?

Regards ,

Mrudula

[pvishnuvardan_reddy · Accepted solution]

Hi Mrudula,

Can you refer the below links for the same:

Configuring Process Integration After Installation - SAP Library

  1309239 - Configuration Wizard: PI NetWeaver initial setup

[Former Member · Accepted solution]

Hello Mrudula ,

You are not bale to see all the NWA tabs in one of the servers because you are not having enough authorizations. Reach out to your security team and get the same access as other system.

Thanks

[mrudularane · Accepted solution]

Hi Gaurav ,

We have cross checked the roles and profiles with the other system and both are having exactly same  . Please find below roles and profiles and let me know if we have missed something .

Roles : - 

SAP_ALM_ADMINISTRATOR

SAP_ALM_CUSTOMIZER

SAP_BC_AI_LANDSCAPE_DB_RFC

SAP_BC_ALM_ADMIN

SAP_BC_ALM_ALERT_USER

SAP_BC_ALM_CUST

SAP_BC_BASIS_ADMIN

SAP_BC_BASIS_MONITORING

SAP_BC_WEBSERVICE_PI_CFG_SRV

SAP_SLD_ADMINISTRATOR

SAP_SLD_CONFIGURATOR

SAP_SLD_DEVELOPER

SAP_SLD_GUEST

SAP_SLD_ORGANIZER

SAP_XI_ADMINISTRATOR

SAP_XI_ADMINISTRATOR_ABAP

SAP_XI_ADMINISTRATOR_J2EE

SAP_XI_BPE_ADMINISTRATOR_ABAP

SAP_XI_BPE_ADMINISTRATOR_J2EE

SAP_XI_BPE_CONFIGURATOR_ABAP

SAP_XI_BPE_MONITOR_ABAP

SAP_XI_BPE_MONITOR_J2EE

SAP_XI_CONFIGURATOR

SAP_XI_CONFIGURATOR_ABAP

SAP_XI_CONFIGURATOR_EXT_J2EE

SAP_XI_CONFIGURATOR_J2EE

SAP_XI_CONTENT_ORGANIZER

SAP_XI_CONTENT_ORGANIZER_ABAP

SAP_XI_CONTENT_ORGANIZER_J2EE

SAP_XI_DEMOAPP

SAP_XI_DEMOAPP_EXECUTE

SAP_XI_DEVELOPER

SAP_XI_DEVELOPER_ABAP

SAP_XI_DEVELOPER_J2EE

SAP_XI_MONITOR

SAP_XI_MONITOR_ABAP

SAP_XI_MONITOR_J2EE

Profiles :-

SAP_ALL

SAP_NEW

T_ALM_CONF

T_ALM_CUST

T_B0960155

T_B0960156

T_B0960158

T_B0960159

T_BE111057

T_BE112353

T_BE112483

T_BE112637

T_BI560001

T_BI560002

T_BI560003

T_LA930142

T_X1940101

T_X1940103

T_X1990086

T_X1990087

T_X1990090

T_X1990091

T_X1990092

T_YA670018

T_YA670111

T_YB250041

T_YB250045

T_YB250046

T_YB250047

T_YB250048

T_YB250049

T_YB250055

T_YD160027

T_YD160050

Regards ,

Mrudula

[former_member183908]

i hope you are calling the correct RFC from PI also you have done the required mappings etc....

if you still have the issue please try to expose your RFC as webservice and test using WSNavigator from SOAMAANGER or SOAPUI

Thanks

[vishnu_pallamreddy]

Hi Mrudula,

Please put external debugger in RFC and please mention same username and password in external system to push the data.

Which version of ECC system you are using?

Please check whether you imported RFC correctly or not?

Check your mappings once.

and try to re import the RFC.

[suman_saha]

are you using the same user id in RFC communication channel and to set debug point?

[Former Member]

Hello mrudula,

It seems to be some problem with RFC.

Reasons:

1. Response from RFC expires.

2. Data sent from remote system does not stop at the debugger in RFC.

So in SAP system, kindly perform connection test and authorization test with PI system. (t-code : SM59)

Also, just to cross-check, kindly perform the same checks from PI system to SAP system as well.

Let me know the results, so that we can sort out the final conclusion.

Kind Regards,

Souvik

[mrudularane]

Hello All ,

The issue was solved . It was observed that code written in one of the rfc was taking 7 mins to execute . Hence it was giving timeout and it may be possible that there was traffic or something in CRM hence it was not calling the other RFCs also . Can it be possible ?

Because we have checked everything as you all mentioned and everything was fine .

Now to avoid such issues in future , we have decided to add timeout parameters in channels .

How to check value of sync timeout  in NWA?

if we use timeout parameter in soap sender  do we need to set syncTimeout parameter  for rfc receiver adapter using RFCAFBean Module ?

Regards ,

Mrudula

[former_member183908]

setting timeout parameters is not the best practice if you are on lower version of PI it will impact the entire PI system and not specific to your scenario and if you are on latest PI versions you have the option to set scenario specific time out parameters.

Thanks

[Former Member]

Hello mrudula,

As Pavan suggested, instead of setting time out parameter in PI, you can do some performance tuning of the corresponding code.

Few possible reasons for code taking a relatively long time to execute are:

1. Indexes might not have been created for certain transparent tables.

2. SELECT Query might involve * suffixing it, instead of that you can use corresponding field names.

3. If any where inner join is being used, instead you can use FOR ALL ENTRIES in the ABAP code.

4. Avoid using nested loops.

5. There might be a WAIT statement involved somewhere in the code. Please figure out the purpose of that statement, and then try to reduce it.

Above are a few suggested check steps in ABAP code. Elsewise you can take help from an ABAPer to analyze the performance of the code.

One more suggestion will be to check the daily EWA (Early Watch Alert) Report from BASIS for this code and tune it with help from ABAPer.

Note : The above was tuning while interacting with database. You can also tune parameters at OS level.

Assuming that OS involved is UNIX/LINUX, you can always contact UNIX team for their support.

Otherwise, the other option will be to use a higher version JDK. This will help for the message to pass quickly through adapter engine of Integration Server of PI, thereby improving performance from PI point of view.

Kind Regards,

Souvik