IP Running

[shweta_walaskar2]

Hello,

We have an Integration process which is working since last 3 years.

It collects IDocs sent every Monday.

Today an issue was reported that data is not received and I found that status of this IP instance is still 'In Process' .

There is no error ,so I cannot restart or delete it.

Can anyone please let me know what can be done?

Thanks.

Regards,

Shweta

[Former Member · Accepted solution]

Hi Swetha,

U have to do the following steps.

1)Refresh the cache(SXI_CACHE).

2)Cancel all system error messages in Message monitoring.

Goto Message Monitoring->Adpter Engine->Select system error Messages->select cacel.

Then all system error message are canceld.

3)Check in Queues SMQ2.if u find any queues remove it r activate it.

Thanks

Ravi

[shweta_walaskar2 · Accepted solution]

Hello Ravi,

1) Cache refreshed

2) There are no System Error messages

3)No entries in SMQ2.

Problem still persists

Thanks.

Regards,

Shweta

[prateek]

You may check the entries in transaction SWWL. If you are ok with deletion of this message, then you may delete the entries from SWWL and then try to process the message again. (Make sure that you remove unnecessary selection criteria in SWWL).

Regards,

Prateek

[Shabarish_Nair]

/people/michal.krawczyk2/blog/2006/06/27/xi-who-said-he-cannot-be-stopped-bpm-jim--sp17 this might help

[shweta_walaskar2]

Hello,

Thanks a lot for your replies.

I am not sure if we can say the problem has been solved but at the moment,we could manage it.

1)SWWL : I was using wrong criteria and finally could delete the IP

but I am still not sure about the reason for this problem.

We analysed it further that first a set of files was sent (we use correlation with Sender ID and Interchange control number)

with some interchange control number and after this a Functional Acknowledgement was sent.

Next set of data was sent with the same interchange control id and not even with a difference of 1 minute,so this satisfied the correlation criteria as well and this data also went to same IP.

Can this be the reason for this problem?

Thanks.

Regards,

Shweta

[Shabarish_Nair]

i gather that could be the issue.

have you done any kind of time out or error handling in your interface?

i suggest doing so to avoid issues in the future

[shweta_walaskar2]

Hello Shabarish,

This is quite an old scenario which is in production for a long time.

You are right,we must enhance this scenario to have error handling in order to avoid such issues in future.

Thanks a lot for your guidance in resolving this problem.

Best Regards,

Shweta